You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Suresh Kumar Anaparti <su...@apache.org> on 2024/07/10 12:15:52 UTC
[VOTE] Apache CloudStack 4.19.1.0 (RC1)
Hi All,
I have created a 4.19.1.0 release (RC1), with the following artifacts up
for testing and a vote:
Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604
Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/
PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS
The vote will be open until 16th July 2024.
For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
For users convenience, the packages from this release candidate (RC1) and
4.19.1.0 systemvm templates are available here:
https://download.cloudstack.org/testing/4.19.1.0-RC1/
https://download.cloudstack.org/systemvm/4.19/
Regards,
Suresh
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Rohit Yadav <ro...@shapeblue.com>.
Jimmy,
I usually test using packages and in VMs that support nested virtualisation manually or use mbx https://github.com/shapeblue/mbx
Regards.
Regards.
________________________________
From: Jimmy Huybrechts <ji...@linservers.com>
Sent: Wednesday, July 10, 2024 6:39:30 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <de...@cloudstack.apache.org>
Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Hi,
What would be the easiest to test this without having to turn up a complete environment in servers.
--
Jimmy
From: Suresh Kumar Anaparti <su...@apache.org>
Date: Wednesday, 10 July 2024 at 14:16
To: dev <de...@cloudstack.apache.org>, users <us...@cloudstack.apache.org>
Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Hi All,
I have created a 4.19.1.0 release (RC1), with the following artifacts up
for testing and a vote:
Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604<https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604>
Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/<https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/>
PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS<https://dist.apache.org/repos/dist/release/cloudstack/KEYS>
The vote will be open until 16th July 2024.
For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
For users convenience, the packages from this release candidate (RC1) and
4.19.1.0 systemvm templates are available here:
https://download.cloudstack.org/testing/4.19.1.0-RC1/<https://download.cloudstack.org/testing/4.19.1.0-RC1/>
https://download.cloudstack.org/systemvm/4.19/<https://download.cloudstack.org/systemvm/4.19/>
Regards,
Suresh
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Rohit Yadav <ro...@shapeblue.com>.
Jimmy,
I usually test using packages and in VMs that support nested virtualisation manually or use mbx https://github.com/shapeblue/mbx
Regards.
Regards.
________________________________
From: Jimmy Huybrechts <ji...@linservers.com>
Sent: Wednesday, July 10, 2024 6:39:30 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <de...@cloudstack.apache.org>
Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Hi,
What would be the easiest to test this without having to turn up a complete environment in servers.
--
Jimmy
From: Suresh Kumar Anaparti <su...@apache.org>
Date: Wednesday, 10 July 2024 at 14:16
To: dev <de...@cloudstack.apache.org>, users <us...@cloudstack.apache.org>
Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Hi All,
I have created a 4.19.1.0 release (RC1), with the following artifacts up
for testing and a vote:
Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604<https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604>
Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/<https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/>
PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS<https://dist.apache.org/repos/dist/release/cloudstack/KEYS>
The vote will be open until 16th July 2024.
For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
For users convenience, the packages from this release candidate (RC1) and
4.19.1.0 systemvm templates are available here:
https://download.cloudstack.org/testing/4.19.1.0-RC1/<https://download.cloudstack.org/testing/4.19.1.0-RC1/>
https://download.cloudstack.org/systemvm/4.19/<https://download.cloudstack.org/systemvm/4.19/>
Regards,
Suresh
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Jimmy Huybrechts <ji...@linservers.com>.
Hi,
What would be the easiest to test this without having to turn up a complete environment in servers.
--
Jimmy
From: Suresh Kumar Anaparti <su...@apache.org>
Date: Wednesday, 10 July 2024 at 14:16
To: dev <de...@cloudstack.apache.org>, users <us...@cloudstack.apache.org>
Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Hi All,
I have created a 4.19.1.0 release (RC1), with the following artifacts up
for testing and a vote:
Git Branch and Commit SHA:
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcloudstack%2Ftree%2F4.19.1.0-RC20240710T1604&data=05%7C02%7Cjimmy%40linservers.com%7Cb48f933879c44f618cf008dca0da13c4%7C6611e9df91314823a2eeee8204e95dba%7C0%7C0%7C638562105698109919%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=0XNEbMYVmPI37l9Gw6H%2BFKUSvBoDp9a%2BaVWxdpKAY9o%3D&reserved=0<https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604>
Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
Source release (checksums and signatures are available at the same
location):
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fcloudstack%2F4.19.1.0%2F&data=05%7C02%7Cjimmy%40linservers.com%7Cb48f933879c44f618cf008dca0da13c4%7C6611e9df91314823a2eeee8204e95dba%7C0%7C0%7C638562105698124904%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qRmX2f91NoDHp%2Bt0xLDfC4dvKhwvgcibY77MhGAfEXQ%3D&reserved=0<https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/>
PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Fcloudstack%2FKEYS&data=05%7C02%7Cjimmy%40linservers.com%7Cb48f933879c44f618cf008dca0da13c4%7C6611e9df91314823a2eeee8204e95dba%7C0%7C0%7C638562105698132342%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qQNsJ3fP2kUi361GtPk6gVFqmnkpBosWd4qPB207Yt8%3D&reserved=0<https://dist.apache.org/repos/dist/release/cloudstack/KEYS>
The vote will be open until 16th July 2024.
For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
For users convenience, the packages from this release candidate (RC1) and
4.19.1.0 systemvm templates are available here:
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownload.cloudstack.org%2Ftesting%2F4.19.1.0-RC1%2F&data=05%7C02%7Cjimmy%40linservers.com%7Cb48f933879c44f618cf008dca0da13c4%7C6611e9df91314823a2eeee8204e95dba%7C0%7C0%7C638562105698139239%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=93YlW1niRnCOFt0htIpgUz5obVoSepFDeknIoH6QcuY%3D&reserved=0<https://download.cloudstack.org/testing/4.19.1.0-RC1/>
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownload.cloudstack.org%2Fsystemvm%2F4.19%2F&data=05%7C02%7Cjimmy%40linservers.com%7Cb48f933879c44f618cf008dca0da13c4%7C6611e9df91314823a2eeee8204e95dba%7C0%7C0%7C638562105698144549%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Vok5d%2Bz%2FlrJv6Pr764f18grAI5C3GfC9V29x2qUjelo%3D&reserved=0<https://download.cloudstack.org/systemvm/4.19/>
Regards,
Suresh
Re: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
Posted by Rohit Yadav <ro...@shapeblue.com>.
Good idea Daan!
Regards.
________________________________
From: Daan Hoogland <da...@gmail.com>
Sent: Friday, July 12, 2024 17:09
To: dev <de...@cloudstack.apache.org>
Cc: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
This is a bit off topic, so renaming the thread. Can we instate a
similar procedure as for views for stored procedures?
it seems to me we can de exactly the same for those stored procedures
and maybe even hijack the views dir so no issues occur with those in
the future. It would guarantee these are recreated on every update and
also always have the latest version as needed.
On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
<su...@apache.org> wrote:
...
> > ________________________________
> > From: Nux <nu...@li.nux.ro>
> > Sent: Friday, July 12, 2024 02:44
> > To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> > Cc: users <us...@cloudstack.apache.org>
> > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> >
> > Rohit,
> >
> > That's a very good point about the routines, thanks for sharing how to
> > restore them.
...
> > On 2024-07-11 12:52, Rohit Yadav wrote:
...
> > > *
> > > I hit an issue with idempotent routines missing on cloud_usage db
> > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > --no-create-info --no-data --routines cloud_usage >
> > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > my fault while moving DB servers and forgot the -R option where I
> > > forgot to backup the routines)
--
Daan
Re: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
Posted by Daan Hoogland <da...@gmail.com>.
people,
https://github.com/apache/cloudstack/pull/9385 contains a draft of
what I mean. I think we can make this work. Thanks to Guto who wrote
the views version of this.
any comments welcome
On Fri, Jul 12, 2024 at 2:58 PM Daan Hoogland <da...@gmail.com> wrote:
>
> good point Wei, So we'll have to create a separate dir/procedure from
> that if the views (that need to be created after the tables.
>
> On Fri, Jul 12, 2024 at 2:14 PM Wei ZHOU <us...@gmail.com> wrote:
> >
> > +1
> >
> > procedures can be created before db upgrades
> >
> > -Wei
> >
> > On Fri, Jul 12, 2024 at 1:40 PM Daan Hoogland <da...@gmail.com> wrote:
> > >
> > > This is a bit off topic, so renaming the thread. Can we instate a
> > > similar procedure as for views for stored procedures?
> > >
> > > it seems to me we can de exactly the same for those stored procedures
> > > and maybe even hijack the views dir so no issues occur with those in
> > > the future. It would guarantee these are recreated on every update and
> > > also always have the latest version as needed.
> > >
> > > On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
> > > <su...@apache.org> wrote:
> > > ...
> > > > > ________________________________
> > > > > From: Nux <nu...@li.nux.ro>
> > > > > Sent: Friday, July 12, 2024 02:44
> > > > > To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> > > > > Cc: users <us...@cloudstack.apache.org>
> > > > > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> > > > >
> > > > > Rohit,
> > > > >
> > > > > That's a very good point about the routines, thanks for sharing how to
> > > > > restore them.
> > > ...
> > > > > On 2024-07-11 12:52, Rohit Yadav wrote:
> > > ...
> > > > > > *
> > > > > > I hit an issue with idempotent routines missing on cloud_usage db
> > > > > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > > > > --no-create-info --no-data --routines cloud_usage >
> > > > > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > > > > my fault while moving DB servers and forgot the -R option where I
> > > > > > forgot to backup the routines)
> > >
> > > --
> > > Daan
>
>
>
> --
> Daan
--
Daan
Re: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
Posted by Daan Hoogland <da...@gmail.com>.
people,
https://github.com/apache/cloudstack/pull/9385 contains a draft of
what I mean. I think we can make this work. Thanks to Guto who wrote
the views version of this.
any comments welcome
On Fri, Jul 12, 2024 at 2:58 PM Daan Hoogland <da...@gmail.com> wrote:
>
> good point Wei, So we'll have to create a separate dir/procedure from
> that if the views (that need to be created after the tables.
>
> On Fri, Jul 12, 2024 at 2:14 PM Wei ZHOU <us...@gmail.com> wrote:
> >
> > +1
> >
> > procedures can be created before db upgrades
> >
> > -Wei
> >
> > On Fri, Jul 12, 2024 at 1:40 PM Daan Hoogland <da...@gmail.com> wrote:
> > >
> > > This is a bit off topic, so renaming the thread. Can we instate a
> > > similar procedure as for views for stored procedures?
> > >
> > > it seems to me we can de exactly the same for those stored procedures
> > > and maybe even hijack the views dir so no issues occur with those in
> > > the future. It would guarantee these are recreated on every update and
> > > also always have the latest version as needed.
> > >
> > > On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
> > > <su...@apache.org> wrote:
> > > ...
> > > > > ________________________________
> > > > > From: Nux <nu...@li.nux.ro>
> > > > > Sent: Friday, July 12, 2024 02:44
> > > > > To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> > > > > Cc: users <us...@cloudstack.apache.org>
> > > > > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> > > > >
> > > > > Rohit,
> > > > >
> > > > > That's a very good point about the routines, thanks for sharing how to
> > > > > restore them.
> > > ...
> > > > > On 2024-07-11 12:52, Rohit Yadav wrote:
> > > ...
> > > > > > *
> > > > > > I hit an issue with idempotent routines missing on cloud_usage db
> > > > > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > > > > --no-create-info --no-data --routines cloud_usage >
> > > > > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > > > > my fault while moving DB servers and forgot the -R option where I
> > > > > > forgot to backup the routines)
> > >
> > > --
> > > Daan
>
>
>
> --
> Daan
--
Daan
Re: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
Posted by Daan Hoogland <da...@gmail.com>.
good point Wei, So we'll have to create a separate dir/procedure from
that if the views (that need to be created after the tables.
On Fri, Jul 12, 2024 at 2:14 PM Wei ZHOU <us...@gmail.com> wrote:
>
> +1
>
> procedures can be created before db upgrades
>
> -Wei
>
> On Fri, Jul 12, 2024 at 1:40 PM Daan Hoogland <da...@gmail.com> wrote:
> >
> > This is a bit off topic, so renaming the thread. Can we instate a
> > similar procedure as for views for stored procedures?
> >
> > it seems to me we can de exactly the same for those stored procedures
> > and maybe even hijack the views dir so no issues occur with those in
> > the future. It would guarantee these are recreated on every update and
> > also always have the latest version as needed.
> >
> > On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
> > <su...@apache.org> wrote:
> > ...
> > > > ________________________________
> > > > From: Nux <nu...@li.nux.ro>
> > > > Sent: Friday, July 12, 2024 02:44
> > > > To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> > > > Cc: users <us...@cloudstack.apache.org>
> > > > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> > > >
> > > > Rohit,
> > > >
> > > > That's a very good point about the routines, thanks for sharing how to
> > > > restore them.
> > ...
> > > > On 2024-07-11 12:52, Rohit Yadav wrote:
> > ...
> > > > > *
> > > > > I hit an issue with idempotent routines missing on cloud_usage db
> > > > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > > > --no-create-info --no-data --routines cloud_usage >
> > > > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > > > my fault while moving DB servers and forgot the -R option where I
> > > > > forgot to backup the routines)
> >
> > --
> > Daan
--
Daan
Re: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
Posted by Daan Hoogland <da...@gmail.com>.
good point Wei, So we'll have to create a separate dir/procedure from
that if the views (that need to be created after the tables.
On Fri, Jul 12, 2024 at 2:14 PM Wei ZHOU <us...@gmail.com> wrote:
>
> +1
>
> procedures can be created before db upgrades
>
> -Wei
>
> On Fri, Jul 12, 2024 at 1:40 PM Daan Hoogland <da...@gmail.com> wrote:
> >
> > This is a bit off topic, so renaming the thread. Can we instate a
> > similar procedure as for views for stored procedures?
> >
> > it seems to me we can de exactly the same for those stored procedures
> > and maybe even hijack the views dir so no issues occur with those in
> > the future. It would guarantee these are recreated on every update and
> > also always have the latest version as needed.
> >
> > On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
> > <su...@apache.org> wrote:
> > ...
> > > > ________________________________
> > > > From: Nux <nu...@li.nux.ro>
> > > > Sent: Friday, July 12, 2024 02:44
> > > > To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> > > > Cc: users <us...@cloudstack.apache.org>
> > > > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> > > >
> > > > Rohit,
> > > >
> > > > That's a very good point about the routines, thanks for sharing how to
> > > > restore them.
> > ...
> > > > On 2024-07-11 12:52, Rohit Yadav wrote:
> > ...
> > > > > *
> > > > > I hit an issue with idempotent routines missing on cloud_usage db
> > > > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > > > --no-create-info --no-data --routines cloud_usage >
> > > > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > > > my fault while moving DB servers and forgot the -R option where I
> > > > > forgot to backup the routines)
> >
> > --
> > Daan
--
Daan
Re: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
Posted by Wei ZHOU <us...@gmail.com>.
+1
procedures can be created before db upgrades
-Wei
On Fri, Jul 12, 2024 at 1:40 PM Daan Hoogland <da...@gmail.com> wrote:
>
> This is a bit off topic, so renaming the thread. Can we instate a
> similar procedure as for views for stored procedures?
>
> it seems to me we can de exactly the same for those stored procedures
> and maybe even hijack the views dir so no issues occur with those in
> the future. It would guarantee these are recreated on every update and
> also always have the latest version as needed.
>
> On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
> <su...@apache.org> wrote:
> ...
> > > ________________________________
> > > From: Nux <nu...@li.nux.ro>
> > > Sent: Friday, July 12, 2024 02:44
> > > To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> > > Cc: users <us...@cloudstack.apache.org>
> > > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> > >
> > > Rohit,
> > >
> > > That's a very good point about the routines, thanks for sharing how to
> > > restore them.
> ...
> > > On 2024-07-11 12:52, Rohit Yadav wrote:
> ...
> > > > *
> > > > I hit an issue with idempotent routines missing on cloud_usage db
> > > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > > --no-create-info --no-data --routines cloud_usage >
> > > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > > my fault while moving DB servers and forgot the -R option where I
> > > > forgot to backup the routines)
>
> --
> Daan
Re: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
Posted by Wei ZHOU <us...@gmail.com>.
+1
procedures can be created before db upgrades
-Wei
On Fri, Jul 12, 2024 at 1:40 PM Daan Hoogland <da...@gmail.com> wrote:
>
> This is a bit off topic, so renaming the thread. Can we instate a
> similar procedure as for views for stored procedures?
>
> it seems to me we can de exactly the same for those stored procedures
> and maybe even hijack the views dir so no issues occur with those in
> the future. It would guarantee these are recreated on every update and
> also always have the latest version as needed.
>
> On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
> <su...@apache.org> wrote:
> ...
> > > ________________________________
> > > From: Nux <nu...@li.nux.ro>
> > > Sent: Friday, July 12, 2024 02:44
> > > To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> > > Cc: users <us...@cloudstack.apache.org>
> > > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> > >
> > > Rohit,
> > >
> > > That's a very good point about the routines, thanks for sharing how to
> > > restore them.
> ...
> > > On 2024-07-11 12:52, Rohit Yadav wrote:
> ...
> > > > *
> > > > I hit an issue with idempotent routines missing on cloud_usage db
> > > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > > --no-create-info --no-data --routines cloud_usage >
> > > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > > my fault while moving DB servers and forgot the -R option where I
> > > > forgot to backup the routines)
>
> --
> Daan
Re: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
Posted by Rohit Yadav <ro...@shapeblue.com>.
Good idea Daan!
Regards.
________________________________
From: Daan Hoogland <da...@gmail.com>
Sent: Friday, July 12, 2024 17:09
To: dev <de...@cloudstack.apache.org>
Cc: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
This is a bit off topic, so renaming the thread. Can we instate a
similar procedure as for views for stored procedures?
it seems to me we can de exactly the same for those stored procedures
and maybe even hijack the views dir so no issues occur with those in
the future. It would guarantee these are recreated on every update and
also always have the latest version as needed.
On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
<su...@apache.org> wrote:
...
> > ________________________________
> > From: Nux <nu...@li.nux.ro>
> > Sent: Friday, July 12, 2024 02:44
> > To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> > Cc: users <us...@cloudstack.apache.org>
> > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> >
> > Rohit,
> >
> > That's a very good point about the routines, thanks for sharing how to
> > restore them.
...
> > On 2024-07-11 12:52, Rohit Yadav wrote:
...
> > > *
> > > I hit an issue with idempotent routines missing on cloud_usage db
> > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > --no-create-info --no-data --routines cloud_usage >
> > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > my fault while moving DB servers and forgot the -R option where I
> > > forgot to backup the routines)
--
Daan
stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
Posted by Daan Hoogland <da...@gmail.com>.
This is a bit off topic, so renaming the thread. Can we instate a
similar procedure as for views for stored procedures?
it seems to me we can de exactly the same for those stored procedures
and maybe even hijack the views dir so no issues occur with those in
the future. It would guarantee these are recreated on every update and
also always have the latest version as needed.
On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
<su...@apache.org> wrote:
...
> > ________________________________
> > From: Nux <nu...@li.nux.ro>
> > Sent: Friday, July 12, 2024 02:44
> > To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> > Cc: users <us...@cloudstack.apache.org>
> > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> >
> > Rohit,
> >
> > That's a very good point about the routines, thanks for sharing how to
> > restore them.
...
> > On 2024-07-11 12:52, Rohit Yadav wrote:
...
> > > *
> > > I hit an issue with idempotent routines missing on cloud_usage db
> > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > --no-create-info --no-data --routines cloud_usage >
> > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > my fault while moving DB servers and forgot the -R option where I
> > > forgot to backup the routines)
--
Daan
stored procedures and versions (Was: [VOTE] Apache CloudStack 4.19.1.0 (RC1))
Posted by Daan Hoogland <da...@gmail.com>.
This is a bit off topic, so renaming the thread. Can we instate a
similar procedure as for views for stored procedures?
it seems to me we can de exactly the same for those stored procedures
and maybe even hijack the views dir so no issues occur with those in
the future. It would guarantee these are recreated on every update and
also always have the latest version as needed.
On Fri, Jul 12, 2024 at 11:37 AM Suresh Kumar Anaparti
<su...@apache.org> wrote:
...
> > ________________________________
> > From: Nux <nu...@li.nux.ro>
> > Sent: Friday, July 12, 2024 02:44
> > To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> > Cc: users <us...@cloudstack.apache.org>
> > Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> >
> > Rohit,
> >
> > That's a very good point about the routines, thanks for sharing how to
> > restore them.
...
> > On 2024-07-11 12:52, Rohit Yadav wrote:
...
> > > *
> > > I hit an issue with idempotent routines missing on cloud_usage db
> > > (borrowed them from mbx env with: mysqldump --no-create-db
> > > --no-create-info --no-data --routines cloud_usage >
> > > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > > my fault while moving DB servers and forgot the -R option where I
> > > forgot to backup the routines)
--
Daan
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Suresh Kumar Anaparti <su...@apache.org>.
Hi All,
There are some issues reported for RC1. One of the issues [1] - relates to
storage access check from the host, seems to be critical and we've a
working fix for this. I'll check and work on the other issues. I'll cut
another RC on 15th July 2024 (Mon).
I'm closing this voting thread. Thank you all for your testing efforts on
RC1.
[1] https://github.com/apache/cloudstack/issues/9371
Regards,
Suresh
On Fri, Jul 12, 2024 at 12:22 PM Rohit Yadav <ro...@shapeblue.com>
wrote:
> All,
>
> I've to revise my vote to a -1 (binding), as there's a regression in the
> VM deployment logic which currently seems to affect anything non-shared
> storage (like local storage).
>
> 2024-07-12 11:49:29,799 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e)
> (logid:e1cb31f5) Trying to find a potenial host and associated storage
> pools from the suitable host/pool lists for this VM 2024-07-12 11:49:29,800
> DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e)
> (logid:e1cb31f5) Checking if host: 26 can access any suitable storage pool
> for volume: ROOT 2024-07-12 11:49:29,800 DEBUG
> [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927
> job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Host: 26 cannot access
> pool: 22 2024-07-12 11:49:29,800 DEBUG
> [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927
> job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Host: 26 can prepare
> access to pool: 22 2024-07-12 11:49:29,801 DEBUG
> [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927
> job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Found a potential host
> id: 26 name: kvm1.onprem.in and associated storage pools for this VM
> 2024-07-12 11:49:29,801 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e)
> (logid:e1cb31f5) Returning Deployment Destination:
> Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
> :
> Dest[Zone(1)-Pod(1)-Cluster(2)-Host(26)-Storage(Volume(1122|ROOT-->Pool(22))]
> 2024-07-12 11:49:29,801 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e)
> (logid:e1cb31f5) Deployment found - Attempt #1 - P0=VM instance
> {"id":852,"instanceName":"i-2-852-VM","type":"User","uuid":"2a0d3f68-f5ca-4679-bf52-7c7e7c9750b2"},
> P0=Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
> :
> Dest[Zone(1)-Pod(1)-Cluster(2)-Host(26)-Storage(Volume(1122|ROOT-->Pool(22))]
>
> In the above example, it chooses KVM1 (in my env) for host and KVM2 for
> storage pool for deploying local storage VM which obviously fails. This
> happens due to an invalid check that returns true for local storage:
> https://github.com/apache/cloudstack/blob/4.19/server/src/main/java/com/cloud/storage/StorageManagerImpl.java#L2795
>
> This wasn't caught earlier as with NFS, it would still pass it being
> shared primary storage.
>
>
> Regards.
>
>
>
>
> ________________________________
> From: Nux <nu...@li.nux.ro>
> Sent: Friday, July 12, 2024 02:44
> To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> Cc: users <us...@cloudstack.apache.org>
> Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
>
> Rohit,
>
> That's a very good point about the routines, thanks for sharing how to
> restore them.
> Hope your marriage is intact after this little adventure. :)
>
> I'll be doing some testing shortly.
>
> On 2024-07-11 12:52, Rohit Yadav wrote:
> > +0 (binding)
> >
> >
> > *
> > Tested fresh installation of EL8 packages, deployed VM from newly
> > created template on a newly created network; tested VM, volume &
> > network lifecycles using both mbx & health check tests passing
> > w/Trillian/BO
> > *
> > Tested upgrade from 4.19.0.2 EL8 to 4.19.1.0 RC1 EL8 pkgs using mbx;
> > tested upgrading systemvms, VRs (with/without cleanup and live patch on
> > an isolated network; deployed new VM & volumes and tested old ones)
> > *
> > Felt dangerous and upgraded my CloudStack 4.19.0.2 homelab to 4.19.1.0
> > RC1 using deb packages (hope there are no major blockers to piss off
> > wife :))
> > *
> > Upgrade went OK on the three Ubuntu 22.04 based 3xKVM hosts
> > *
> > I hit an issue with idempotent routines missing on cloud_usage db
> > (borrowed them from mbx env with: mysqldump --no-create-db
> > --no-create-info --no-data --routines cloud_usage >
> > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > my fault while moving DB servers and forgot the -R option where I
> > forgot to backup the routines)
> > *
> > Tested homelab storage: nfs, local storage & ceph - OK; hosts upgraded
> > OK;
> > *
> > Post upgrade, after deleting systemvms I found the SSVM & CPVM starting
> > to be stuck. I restarted the mgmt server and after a while the SSVM
> > came up but the CPVM was stuck. I repeated the same, but again SSVM
> > came up but CPVM struggle and after a few agent restarts it came up
> > eventually.
> > *
> > Post this, tested several VM, volume and network lifecycles worked OK
> >
> > I've logged the issue here -
> > https://github.com/apache/cloudstack/issues/9371 to triage further if
> > it's an issue in RC1 or to help investigate if it was an env issue. I'm
> > happy to change my vote to a +1 if it's just my env issue.
> >
> >
> > Regards.
> >
> >
> >
> >
> > ________________________________
> > From: Suresh Kumar Anaparti <su...@apache.org>
> > Sent: Wednesday, July 10, 2024 17:45
> > To: dev <de...@cloudstack.apache.org>; users
> > <us...@cloudstack.apache.org>
> > Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> >
> > Hi All,
> >
> > I have created a 4.19.1.0 release (RC1), with the following artifacts
> > up
> > for testing and a vote:
> >
> > Git Branch and Commit SHA:
> > https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604
> > Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/
> >
> > PGP release keys (signed using
> > D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > The vote will be open until 16th July 2024.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> > indicate
> > "(binding)" with their vote?
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > For users convenience, the packages from this release candidate (RC1)
> > and
> > 4.19.1.0 systemvm templates are available here:
> > https://download.cloudstack.org/testing/4.19.1.0-RC1/
> > https://download.cloudstack.org/systemvm/4.19/
> >
> > Regards,
> > Suresh
>
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Suresh Kumar Anaparti <su...@apache.org>.
Hi All,
There are some issues reported for RC1. One of the issues [1] - relates to
storage access check from the host, seems to be critical and we've a
working fix for this. I'll check and work on the other issues. I'll cut
another RC on 15th July 2024 (Mon).
I'm closing this voting thread. Thank you all for your testing efforts on
RC1.
[1] https://github.com/apache/cloudstack/issues/9371
Regards,
Suresh
On Fri, Jul 12, 2024 at 12:22 PM Rohit Yadav <ro...@shapeblue.com>
wrote:
> All,
>
> I've to revise my vote to a -1 (binding), as there's a regression in the
> VM deployment logic which currently seems to affect anything non-shared
> storage (like local storage).
>
> 2024-07-12 11:49:29,799 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e)
> (logid:e1cb31f5) Trying to find a potenial host and associated storage
> pools from the suitable host/pool lists for this VM 2024-07-12 11:49:29,800
> DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e)
> (logid:e1cb31f5) Checking if host: 26 can access any suitable storage pool
> for volume: ROOT 2024-07-12 11:49:29,800 DEBUG
> [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927
> job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Host: 26 cannot access
> pool: 22 2024-07-12 11:49:29,800 DEBUG
> [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927
> job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Host: 26 can prepare
> access to pool: 22 2024-07-12 11:49:29,801 DEBUG
> [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927
> job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Found a potential host
> id: 26 name: kvm1.onprem.in and associated storage pools for this VM
> 2024-07-12 11:49:29,801 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e)
> (logid:e1cb31f5) Returning Deployment Destination:
> Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
> :
> Dest[Zone(1)-Pod(1)-Cluster(2)-Host(26)-Storage(Volume(1122|ROOT-->Pool(22))]
> 2024-07-12 11:49:29,801 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e)
> (logid:e1cb31f5) Deployment found - Attempt #1 - P0=VM instance
> {"id":852,"instanceName":"i-2-852-VM","type":"User","uuid":"2a0d3f68-f5ca-4679-bf52-7c7e7c9750b2"},
> P0=Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
> :
> Dest[Zone(1)-Pod(1)-Cluster(2)-Host(26)-Storage(Volume(1122|ROOT-->Pool(22))]
>
> In the above example, it chooses KVM1 (in my env) for host and KVM2 for
> storage pool for deploying local storage VM which obviously fails. This
> happens due to an invalid check that returns true for local storage:
> https://github.com/apache/cloudstack/blob/4.19/server/src/main/java/com/cloud/storage/StorageManagerImpl.java#L2795
>
> This wasn't caught earlier as with NFS, it would still pass it being
> shared primary storage.
>
>
> Regards.
>
>
>
>
> ________________________________
> From: Nux <nu...@li.nux.ro>
> Sent: Friday, July 12, 2024 02:44
> To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
> Cc: users <us...@cloudstack.apache.org>
> Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
>
> Rohit,
>
> That's a very good point about the routines, thanks for sharing how to
> restore them.
> Hope your marriage is intact after this little adventure. :)
>
> I'll be doing some testing shortly.
>
> On 2024-07-11 12:52, Rohit Yadav wrote:
> > +0 (binding)
> >
> >
> > *
> > Tested fresh installation of EL8 packages, deployed VM from newly
> > created template on a newly created network; tested VM, volume &
> > network lifecycles using both mbx & health check tests passing
> > w/Trillian/BO
> > *
> > Tested upgrade from 4.19.0.2 EL8 to 4.19.1.0 RC1 EL8 pkgs using mbx;
> > tested upgrading systemvms, VRs (with/without cleanup and live patch on
> > an isolated network; deployed new VM & volumes and tested old ones)
> > *
> > Felt dangerous and upgraded my CloudStack 4.19.0.2 homelab to 4.19.1.0
> > RC1 using deb packages (hope there are no major blockers to piss off
> > wife :))
> > *
> > Upgrade went OK on the three Ubuntu 22.04 based 3xKVM hosts
> > *
> > I hit an issue with idempotent routines missing on cloud_usage db
> > (borrowed them from mbx env with: mysqldump --no-create-db
> > --no-create-info --no-data --routines cloud_usage >
> > cloud_usage-routines.sql ; and applied this in my homelab env; likely
> > my fault while moving DB servers and forgot the -R option where I
> > forgot to backup the routines)
> > *
> > Tested homelab storage: nfs, local storage & ceph - OK; hosts upgraded
> > OK;
> > *
> > Post upgrade, after deleting systemvms I found the SSVM & CPVM starting
> > to be stuck. I restarted the mgmt server and after a while the SSVM
> > came up but the CPVM was stuck. I repeated the same, but again SSVM
> > came up but CPVM struggle and after a few agent restarts it came up
> > eventually.
> > *
> > Post this, tested several VM, volume and network lifecycles worked OK
> >
> > I've logged the issue here -
> > https://github.com/apache/cloudstack/issues/9371 to triage further if
> > it's an issue in RC1 or to help investigate if it was an env issue. I'm
> > happy to change my vote to a +1 if it's just my env issue.
> >
> >
> > Regards.
> >
> >
> >
> >
> > ________________________________
> > From: Suresh Kumar Anaparti <su...@apache.org>
> > Sent: Wednesday, July 10, 2024 17:45
> > To: dev <de...@cloudstack.apache.org>; users
> > <us...@cloudstack.apache.org>
> > Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
> >
> > Hi All,
> >
> > I have created a 4.19.1.0 release (RC1), with the following artifacts
> > up
> > for testing and a vote:
> >
> > Git Branch and Commit SHA:
> > https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604
> > Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/
> >
> > PGP release keys (signed using
> > D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > The vote will be open until 16th July 2024.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> > indicate
> > "(binding)" with their vote?
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > For users convenience, the packages from this release candidate (RC1)
> > and
> > 4.19.1.0 systemvm templates are available here:
> > https://download.cloudstack.org/testing/4.19.1.0-RC1/
> > https://download.cloudstack.org/systemvm/4.19/
> >
> > Regards,
> > Suresh
>
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Rohit Yadav <ro...@shapeblue.com>.
All,
I've to revise my vote to a -1 (binding), as there's a regression in the VM deployment logic which currently seems to affect anything non-shared storage (like local storage).
2024-07-12 11:49:29,799 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Trying to find a potenial host and associated storage pools from the suitable host/pool lists for this VM 2024-07-12 11:49:29,800 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Checking if host: 26 can access any suitable storage pool for volume: ROOT 2024-07-12 11:49:29,800 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Host: 26 cannot access pool: 22 2024-07-12 11:49:29,800 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Host: 26 can prepare access to pool: 22 2024-07-12 11:49:29,801 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Found a potential host id: 26 name: kvm1.onprem.in and associated storage pools for this VM 2024-07-12 11:49:29,801 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Returning Deployment Destination: Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(2)-Host(26)-Storage(Volume(1122|ROOT-->Pool(22))] 2024-07-12 11:49:29,801 DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Deployment found - Attempt #1 - P0=VM instance {"id":852,"instanceName":"i-2-852-VM","type":"User","uuid":"2a0d3f68-f5ca-4679-bf52-7c7e7c9750b2"}, P0=Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(2)-Host(26)-Storage(Volume(1122|ROOT-->Pool(22))]
In the above example, it chooses KVM1 (in my env) for host and KVM2 for storage pool for deploying local storage VM which obviously fails. This happens due to an invalid check that returns true for local storage: https://github.com/apache/cloudstack/blob/4.19/server/src/main/java/com/cloud/storage/StorageManagerImpl.java#L2795
This wasn't caught earlier as with NFS, it would still pass it being shared primary storage.
Regards.
________________________________
From: Nux <nu...@li.nux.ro>
Sent: Friday, July 12, 2024 02:44
To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
Cc: users <us...@cloudstack.apache.org>
Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Rohit,
That's a very good point about the routines, thanks for sharing how to
restore them.
Hope your marriage is intact after this little adventure. :)
I'll be doing some testing shortly.
On 2024-07-11 12:52, Rohit Yadav wrote:
> +0 (binding)
>
>
> *
> Tested fresh installation of EL8 packages, deployed VM from newly
> created template on a newly created network; tested VM, volume &
> network lifecycles using both mbx & health check tests passing
> w/Trillian/BO
> *
> Tested upgrade from 4.19.0.2 EL8 to 4.19.1.0 RC1 EL8 pkgs using mbx;
> tested upgrading systemvms, VRs (with/without cleanup and live patch on
> an isolated network; deployed new VM & volumes and tested old ones)
> *
> Felt dangerous and upgraded my CloudStack 4.19.0.2 homelab to 4.19.1.0
> RC1 using deb packages (hope there are no major blockers to piss off
> wife :))
> *
> Upgrade went OK on the three Ubuntu 22.04 based 3xKVM hosts
> *
> I hit an issue with idempotent routines missing on cloud_usage db
> (borrowed them from mbx env with: mysqldump --no-create-db
> --no-create-info --no-data --routines cloud_usage >
> cloud_usage-routines.sql ; and applied this in my homelab env; likely
> my fault while moving DB servers and forgot the -R option where I
> forgot to backup the routines)
> *
> Tested homelab storage: nfs, local storage & ceph - OK; hosts upgraded
> OK;
> *
> Post upgrade, after deleting systemvms I found the SSVM & CPVM starting
> to be stuck. I restarted the mgmt server and after a while the SSVM
> came up but the CPVM was stuck. I repeated the same, but again SSVM
> came up but CPVM struggle and after a few agent restarts it came up
> eventually.
> *
> Post this, tested several VM, volume and network lifecycles worked OK
>
> I've logged the issue here -
> https://github.com/apache/cloudstack/issues/9371 to triage further if
> it's an issue in RC1 or to help investigate if it was an env issue. I'm
> happy to change my vote to a +1 if it's just my env issue.
>
>
> Regards.
>
>
>
>
> ________________________________
> From: Suresh Kumar Anaparti <su...@apache.org>
> Sent: Wednesday, July 10, 2024 17:45
> To: dev <de...@cloudstack.apache.org>; users
> <us...@cloudstack.apache.org>
> Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
>
> Hi All,
>
> I have created a 4.19.1.0 release (RC1), with the following artifacts
> up
> for testing and a vote:
>
> Git Branch and Commit SHA:
> https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604
> Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/
>
> PGP release keys (signed using
> D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 16th July 2024.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> For users convenience, the packages from this release candidate (RC1)
> and
> 4.19.1.0 systemvm templates are available here:
> https://download.cloudstack.org/testing/4.19.1.0-RC1/
> https://download.cloudstack.org/systemvm/4.19/
>
> Regards,
> Suresh
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Rohit Yadav <ro...@shapeblue.com>.
All,
I've to revise my vote to a -1 (binding), as there's a regression in the VM deployment logic which currently seems to affect anything non-shared storage (like local storage).
2024-07-12 11:49:29,799 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Trying to find a potenial host and associated storage pools from the suitable host/pool lists for this VM 2024-07-12 11:49:29,800 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Checking if host: 26 can access any suitable storage pool for volume: ROOT 2024-07-12 11:49:29,800 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Host: 26 cannot access pool: 22 2024-07-12 11:49:29,800 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Host: 26 can prepare access to pool: 22 2024-07-12 11:49:29,801 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Found a potential host id: 26 name: kvm1.onprem.in and associated storage pools for this VM 2024-07-12 11:49:29,801 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Returning Deployment Destination: Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(2)-Host(26)-Storage(Volume(1122|ROOT-->Pool(22))] 2024-07-12 11:49:29,801 DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-43:ctx-7277b927 job-10187/job-10188 ctx-c5bfa38e) (logid:e1cb31f5) Deployment found - Attempt #1 - P0=VM instance {"id":852,"instanceName":"i-2-852-VM","type":"User","uuid":"2a0d3f68-f5ca-4679-bf52-7c7e7c9750b2"}, P0=Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(2)-Host(26)-Storage(Volume(1122|ROOT-->Pool(22))]
In the above example, it chooses KVM1 (in my env) for host and KVM2 for storage pool for deploying local storage VM which obviously fails. This happens due to an invalid check that returns true for local storage: https://github.com/apache/cloudstack/blob/4.19/server/src/main/java/com/cloud/storage/StorageManagerImpl.java#L2795
This wasn't caught earlier as with NFS, it would still pass it being shared primary storage.
Regards.
________________________________
From: Nux <nu...@li.nux.ro>
Sent: Friday, July 12, 2024 02:44
To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
Cc: users <us...@cloudstack.apache.org>
Subject: Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Rohit,
That's a very good point about the routines, thanks for sharing how to
restore them.
Hope your marriage is intact after this little adventure. :)
I'll be doing some testing shortly.
On 2024-07-11 12:52, Rohit Yadav wrote:
> +0 (binding)
>
>
> *
> Tested fresh installation of EL8 packages, deployed VM from newly
> created template on a newly created network; tested VM, volume &
> network lifecycles using both mbx & health check tests passing
> w/Trillian/BO
> *
> Tested upgrade from 4.19.0.2 EL8 to 4.19.1.0 RC1 EL8 pkgs using mbx;
> tested upgrading systemvms, VRs (with/without cleanup and live patch on
> an isolated network; deployed new VM & volumes and tested old ones)
> *
> Felt dangerous and upgraded my CloudStack 4.19.0.2 homelab to 4.19.1.0
> RC1 using deb packages (hope there are no major blockers to piss off
> wife :))
> *
> Upgrade went OK on the three Ubuntu 22.04 based 3xKVM hosts
> *
> I hit an issue with idempotent routines missing on cloud_usage db
> (borrowed them from mbx env with: mysqldump --no-create-db
> --no-create-info --no-data --routines cloud_usage >
> cloud_usage-routines.sql ; and applied this in my homelab env; likely
> my fault while moving DB servers and forgot the -R option where I
> forgot to backup the routines)
> *
> Tested homelab storage: nfs, local storage & ceph - OK; hosts upgraded
> OK;
> *
> Post upgrade, after deleting systemvms I found the SSVM & CPVM starting
> to be stuck. I restarted the mgmt server and after a while the SSVM
> came up but the CPVM was stuck. I repeated the same, but again SSVM
> came up but CPVM struggle and after a few agent restarts it came up
> eventually.
> *
> Post this, tested several VM, volume and network lifecycles worked OK
>
> I've logged the issue here -
> https://github.com/apache/cloudstack/issues/9371 to triage further if
> it's an issue in RC1 or to help investigate if it was an env issue. I'm
> happy to change my vote to a +1 if it's just my env issue.
>
>
> Regards.
>
>
>
>
> ________________________________
> From: Suresh Kumar Anaparti <su...@apache.org>
> Sent: Wednesday, July 10, 2024 17:45
> To: dev <de...@cloudstack.apache.org>; users
> <us...@cloudstack.apache.org>
> Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
>
> Hi All,
>
> I have created a 4.19.1.0 release (RC1), with the following artifacts
> up
> for testing and a vote:
>
> Git Branch and Commit SHA:
> https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604
> Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/
>
> PGP release keys (signed using
> D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 16th July 2024.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> For users convenience, the packages from this release candidate (RC1)
> and
> 4.19.1.0 systemvm templates are available here:
> https://download.cloudstack.org/testing/4.19.1.0-RC1/
> https://download.cloudstack.org/systemvm/4.19/
>
> Regards,
> Suresh
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Nux <nu...@li.nux.ro>.
Rohit,
That's a very good point about the routines, thanks for sharing how to
restore them.
Hope your marriage is intact after this little adventure. :)
I'll be doing some testing shortly.
On 2024-07-11 12:52, Rohit Yadav wrote:
> +0 (binding)
>
>
> *
> Tested fresh installation of EL8 packages, deployed VM from newly
> created template on a newly created network; tested VM, volume &
> network lifecycles using both mbx & health check tests passing
> w/Trillian/BO
> *
> Tested upgrade from 4.19.0.2 EL8 to 4.19.1.0 RC1 EL8 pkgs using mbx;
> tested upgrading systemvms, VRs (with/without cleanup and live patch on
> an isolated network; deployed new VM & volumes and tested old ones)
> *
> Felt dangerous and upgraded my CloudStack 4.19.0.2 homelab to 4.19.1.0
> RC1 using deb packages (hope there are no major blockers to piss off
> wife :))
> *
> Upgrade went OK on the three Ubuntu 22.04 based 3xKVM hosts
> *
> I hit an issue with idempotent routines missing on cloud_usage db
> (borrowed them from mbx env with: mysqldump --no-create-db
> --no-create-info --no-data --routines cloud_usage >
> cloud_usage-routines.sql ; and applied this in my homelab env; likely
> my fault while moving DB servers and forgot the -R option where I
> forgot to backup the routines)
> *
> Tested homelab storage: nfs, local storage & ceph - OK; hosts upgraded
> OK;
> *
> Post upgrade, after deleting systemvms I found the SSVM & CPVM starting
> to be stuck. I restarted the mgmt server and after a while the SSVM
> came up but the CPVM was stuck. I repeated the same, but again SSVM
> came up but CPVM struggle and after a few agent restarts it came up
> eventually.
> *
> Post this, tested several VM, volume and network lifecycles worked OK
>
> I've logged the issue here -
> https://github.com/apache/cloudstack/issues/9371 to triage further if
> it's an issue in RC1 or to help investigate if it was an env issue. I'm
> happy to change my vote to a +1 if it's just my env issue.
>
>
> Regards.
>
>
>
>
> ________________________________
> From: Suresh Kumar Anaparti <su...@apache.org>
> Sent: Wednesday, July 10, 2024 17:45
> To: dev <de...@cloudstack.apache.org>; users
> <us...@cloudstack.apache.org>
> Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
>
> Hi All,
>
> I have created a 4.19.1.0 release (RC1), with the following artifacts
> up
> for testing and a vote:
>
> Git Branch and Commit SHA:
> https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604
> Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/
>
> PGP release keys (signed using
> D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 16th July 2024.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> For users convenience, the packages from this release candidate (RC1)
> and
> 4.19.1.0 systemvm templates are available here:
> https://download.cloudstack.org/testing/4.19.1.0-RC1/
> https://download.cloudstack.org/systemvm/4.19/
>
> Regards,
> Suresh
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Nux <nu...@li.nux.ro>.
Rohit,
That's a very good point about the routines, thanks for sharing how to
restore them.
Hope your marriage is intact after this little adventure. :)
I'll be doing some testing shortly.
On 2024-07-11 12:52, Rohit Yadav wrote:
> +0 (binding)
>
>
> *
> Tested fresh installation of EL8 packages, deployed VM from newly
> created template on a newly created network; tested VM, volume &
> network lifecycles using both mbx & health check tests passing
> w/Trillian/BO
> *
> Tested upgrade from 4.19.0.2 EL8 to 4.19.1.0 RC1 EL8 pkgs using mbx;
> tested upgrading systemvms, VRs (with/without cleanup and live patch on
> an isolated network; deployed new VM & volumes and tested old ones)
> *
> Felt dangerous and upgraded my CloudStack 4.19.0.2 homelab to 4.19.1.0
> RC1 using deb packages (hope there are no major blockers to piss off
> wife :))
> *
> Upgrade went OK on the three Ubuntu 22.04 based 3xKVM hosts
> *
> I hit an issue with idempotent routines missing on cloud_usage db
> (borrowed them from mbx env with: mysqldump --no-create-db
> --no-create-info --no-data --routines cloud_usage >
> cloud_usage-routines.sql ; and applied this in my homelab env; likely
> my fault while moving DB servers and forgot the -R option where I
> forgot to backup the routines)
> *
> Tested homelab storage: nfs, local storage & ceph - OK; hosts upgraded
> OK;
> *
> Post upgrade, after deleting systemvms I found the SSVM & CPVM starting
> to be stuck. I restarted the mgmt server and after a while the SSVM
> came up but the CPVM was stuck. I repeated the same, but again SSVM
> came up but CPVM struggle and after a few agent restarts it came up
> eventually.
> *
> Post this, tested several VM, volume and network lifecycles worked OK
>
> I've logged the issue here -
> https://github.com/apache/cloudstack/issues/9371 to triage further if
> it's an issue in RC1 or to help investigate if it was an env issue. I'm
> happy to change my vote to a +1 if it's just my env issue.
>
>
> Regards.
>
>
>
>
> ________________________________
> From: Suresh Kumar Anaparti <su...@apache.org>
> Sent: Wednesday, July 10, 2024 17:45
> To: dev <de...@cloudstack.apache.org>; users
> <us...@cloudstack.apache.org>
> Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
>
> Hi All,
>
> I have created a 4.19.1.0 release (RC1), with the following artifacts
> up
> for testing and a vote:
>
> Git Branch and Commit SHA:
> https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604
> Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/
>
> PGP release keys (signed using
> D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 16th July 2024.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> For users convenience, the packages from this release candidate (RC1)
> and
> 4.19.1.0 systemvm templates are available here:
> https://download.cloudstack.org/testing/4.19.1.0-RC1/
> https://download.cloudstack.org/systemvm/4.19/
>
> Regards,
> Suresh
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Rohit Yadav <ro...@shapeblue.com>.
+0 (binding)
*
Tested fresh installation of EL8 packages, deployed VM from newly created template on a newly created network; tested VM, volume & network lifecycles using both mbx & health check tests passing w/Trillian/BO
*
Tested upgrade from 4.19.0.2 EL8 to 4.19.1.0 RC1 EL8 pkgs using mbx; tested upgrading systemvms, VRs (with/without cleanup and live patch on an isolated network; deployed new VM & volumes and tested old ones)
*
Felt dangerous and upgraded my CloudStack 4.19.0.2 homelab to 4.19.1.0 RC1 using deb packages (hope there are no major blockers to piss off wife :))
*
Upgrade went OK on the three Ubuntu 22.04 based 3xKVM hosts
*
I hit an issue with idempotent routines missing on cloud_usage db (borrowed them from mbx env with: mysqldump --no-create-db --no-create-info --no-data --routines cloud_usage > cloud_usage-routines.sql ; and applied this in my homelab env; likely my fault while moving DB servers and forgot the -R option where I forgot to backup the routines)
*
Tested homelab storage: nfs, local storage & ceph - OK; hosts upgraded OK;
*
Post upgrade, after deleting systemvms I found the SSVM & CPVM starting to be stuck. I restarted the mgmt server and after a while the SSVM came up but the CPVM was stuck. I repeated the same, but again SSVM came up but CPVM struggle and after a few agent restarts it came up eventually.
*
Post this, tested several VM, volume and network lifecycles worked OK
I've logged the issue here - https://github.com/apache/cloudstack/issues/9371 to triage further if it's an issue in RC1 or to help investigate if it was an env issue. I'm happy to change my vote to a +1 if it's just my env issue.
Regards.
________________________________
From: Suresh Kumar Anaparti <su...@apache.org>
Sent: Wednesday, July 10, 2024 17:45
To: dev <de...@cloudstack.apache.org>; users <us...@cloudstack.apache.org>
Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Hi All,
I have created a 4.19.1.0 release (RC1), with the following artifacts up
for testing and a vote:
Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604
Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/
PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS
The vote will be open until 16th July 2024.
For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
For users convenience, the packages from this release candidate (RC1) and
4.19.1.0 systemvm templates are available here:
https://download.cloudstack.org/testing/4.19.1.0-RC1/
https://download.cloudstack.org/systemvm/4.19/
Regards,
Suresh
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Jimmy Huybrechts <ji...@linservers.com>.
Hi,
What would be the easiest to test this without having to turn up a complete environment in servers.
--
Jimmy
From: Suresh Kumar Anaparti <su...@apache.org>
Date: Wednesday, 10 July 2024 at 14:16
To: dev <de...@cloudstack.apache.org>, users <us...@cloudstack.apache.org>
Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Hi All,
I have created a 4.19.1.0 release (RC1), with the following artifacts up
for testing and a vote:
Git Branch and Commit SHA:
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcloudstack%2Ftree%2F4.19.1.0-RC20240710T1604&data=05%7C02%7Cjimmy%40linservers.com%7Cb48f933879c44f618cf008dca0da13c4%7C6611e9df91314823a2eeee8204e95dba%7C0%7C0%7C638562105698109919%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=0XNEbMYVmPI37l9Gw6H%2BFKUSvBoDp9a%2BaVWxdpKAY9o%3D&reserved=0<https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604>
Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
Source release (checksums and signatures are available at the same
location):
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fcloudstack%2F4.19.1.0%2F&data=05%7C02%7Cjimmy%40linservers.com%7Cb48f933879c44f618cf008dca0da13c4%7C6611e9df91314823a2eeee8204e95dba%7C0%7C0%7C638562105698124904%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qRmX2f91NoDHp%2Bt0xLDfC4dvKhwvgcibY77MhGAfEXQ%3D&reserved=0<https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/>
PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Fcloudstack%2FKEYS&data=05%7C02%7Cjimmy%40linservers.com%7Cb48f933879c44f618cf008dca0da13c4%7C6611e9df91314823a2eeee8204e95dba%7C0%7C0%7C638562105698132342%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qQNsJ3fP2kUi361GtPk6gVFqmnkpBosWd4qPB207Yt8%3D&reserved=0<https://dist.apache.org/repos/dist/release/cloudstack/KEYS>
The vote will be open until 16th July 2024.
For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
For users convenience, the packages from this release candidate (RC1) and
4.19.1.0 systemvm templates are available here:
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownload.cloudstack.org%2Ftesting%2F4.19.1.0-RC1%2F&data=05%7C02%7Cjimmy%40linservers.com%7Cb48f933879c44f618cf008dca0da13c4%7C6611e9df91314823a2eeee8204e95dba%7C0%7C0%7C638562105698139239%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=93YlW1niRnCOFt0htIpgUz5obVoSepFDeknIoH6QcuY%3D&reserved=0<https://download.cloudstack.org/testing/4.19.1.0-RC1/>
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownload.cloudstack.org%2Fsystemvm%2F4.19%2F&data=05%7C02%7Cjimmy%40linservers.com%7Cb48f933879c44f618cf008dca0da13c4%7C6611e9df91314823a2eeee8204e95dba%7C0%7C0%7C638562105698144549%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Vok5d%2Bz%2FlrJv6Pr764f18grAI5C3GfC9V29x2qUjelo%3D&reserved=0<https://download.cloudstack.org/systemvm/4.19/>
Regards,
Suresh
Re: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Posted by Rohit Yadav <ro...@shapeblue.com>.
+0 (binding)
*
Tested fresh installation of EL8 packages, deployed VM from newly created template on a newly created network; tested VM, volume & network lifecycles using both mbx & health check tests passing w/Trillian/BO
*
Tested upgrade from 4.19.0.2 EL8 to 4.19.1.0 RC1 EL8 pkgs using mbx; tested upgrading systemvms, VRs (with/without cleanup and live patch on an isolated network; deployed new VM & volumes and tested old ones)
*
Felt dangerous and upgraded my CloudStack 4.19.0.2 homelab to 4.19.1.0 RC1 using deb packages (hope there are no major blockers to piss off wife :))
*
Upgrade went OK on the three Ubuntu 22.04 based 3xKVM hosts
*
I hit an issue with idempotent routines missing on cloud_usage db (borrowed them from mbx env with: mysqldump --no-create-db --no-create-info --no-data --routines cloud_usage > cloud_usage-routines.sql ; and applied this in my homelab env; likely my fault while moving DB servers and forgot the -R option where I forgot to backup the routines)
*
Tested homelab storage: nfs, local storage & ceph - OK; hosts upgraded OK;
*
Post upgrade, after deleting systemvms I found the SSVM & CPVM starting to be stuck. I restarted the mgmt server and after a while the SSVM came up but the CPVM was stuck. I repeated the same, but again SSVM came up but CPVM struggle and after a few agent restarts it came up eventually.
*
Post this, tested several VM, volume and network lifecycles worked OK
I've logged the issue here - https://github.com/apache/cloudstack/issues/9371 to triage further if it's an issue in RC1 or to help investigate if it was an env issue. I'm happy to change my vote to a +1 if it's just my env issue.
Regards.
________________________________
From: Suresh Kumar Anaparti <su...@apache.org>
Sent: Wednesday, July 10, 2024 17:45
To: dev <de...@cloudstack.apache.org>; users <us...@cloudstack.apache.org>
Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC1)
Hi All,
I have created a 4.19.1.0 release (RC1), with the following artifacts up
for testing and a vote:
Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240710T1604
Commit: 2dbd80d692d6f5a207f90a07ac0b7583a41b71cd
Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/
PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS
The vote will be open until 16th July 2024.
For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
For users convenience, the packages from this release candidate (RC1) and
4.19.1.0 systemvm templates are available here:
https://download.cloudstack.org/testing/4.19.1.0-RC1/
https://download.cloudstack.org/systemvm/4.19/
Regards,
Suresh