Re: Dependency additions to OpenStack SRU exception
On Fri, Nov 17, 2023 at 3:54 PM Andreas Hasenack wrote: > Hi, > > On Fri, Nov 17, 2023 at 5:48 PM Corey Bryant > wrote: > >> On Thu, Nov 16, 2023 at 4:31 PM Andreas Hasenack >> wrote: >> >>> Hi Corey, >>> >>> On Fri, Sep 1, 2023 at 11:52 AM Corey Bryant >>> wrote: >>> >>>> Hi Robie, >>>> >>>> Thanks for taking a look. >>>> >>>> On Wed, Aug 30, 2023 at 9:34 AM Robie Basak >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> As a list of 46 packages this is rather large and non-trivial to >>>>> review. >>>>> Presumably we'll want to group them by upstream (are all managed by the >>>>> OpenStack umbrella upstream, or are there exceptions?) and then take a >>>>> view on them as a whole. >>>>> >>>> >>>> All of the packages in this list fall under the OpenStack umbrella >>>> upstream. The source can be found at: https://opendev.org/explore/repos >>>> All of these packages were specifically chosen because they are >>>> dependencies of the existing packages in our SRU exception list. >>>> >>> >>> Could you also check the reverse dependencies of these packages in the >>> Ubuntu Archive, to see what, if anything, other than openstack, might be >>> using them? If we start updating them to new upstream versions, albeit >>> still within a stable release track, we might be affecting their rdeps. >>> >>> >> Hi Andreas, >> >> Thanks for taking a look. >> >> I've put a full list of rdepends here: >> https://github.com/coreycb/reverse-depends/blob/main/reverse-depends >> > > Thanks for this! > > >> It is mostly OpenStack packages, but I did find a few non-openstack >> packages: >> >> fence-agents-compute (Depends: python3-novaclient) >> fence-agents-openstack (Depends: python3-novaclient) >> fence-agents-ironic (Depends: python3-openstackclient) >> jeepyb (Depends: python3-swiftclient) >> prometheus-openstack-exporter (Depends: python3-cinderclient, >> python3-keystoneclient, python3-neutronclient, python3-novaclient, >> python3-swift) >> python3-novnc (Depends: python3-oslo.config, Reverse Depends: >> nova-novncproxy, qemu-web-desktop) >> > > Interesting, fence-agents are part of the HA stack and looked after by the > server team. The rdep on novaclient suggests it could also be relying on > command-line options to the /usr/bin/nova tool. I suppose incompatible > changes in the command-line arguments are also strictly not allowed? > > That is correct, incompatible changes to the the CLI are not allowed. > >> >> It is worth noting that OpenStack stable releases cannot include >> incompatible API changes. >> >> And given the example from Robie below on python-ovsdbapp, when he >>> analyzed python-ovsdbapp, do you think you would be able to highlight >>> usptream changes in behavior, if they exist, in the future SRUs? In >>> general, MREs should not have those, of course. >>> >>> >> I'm hesitant to do this because I think it would get noisy. In my >> experience, bug fixes often change behavior, but not in an incompatible way. >> >> Would it be useful to provide a summary of commits included in a stable >> release? We might be able to include that in the debian/changelog even. In >> some cases, such as neutron, I probably would not want to do that because >> the number of commits (sometimes 50+) could pollute the changelog, but I >> think in general it could be useful to end users. >> > > We wouldn't want something like this in d/changelog, no. We would be > relying on you do perform this check, and highlight what you think could be > an incompatible change, or significant change in behavior. Would that work? > > Yes, that makes sense. -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Dependency additions to OpenStack SRU exception
On Thu, Nov 16, 2023 at 4:31 PM Andreas Hasenack wrote: > Hi Corey, > > On Fri, Sep 1, 2023 at 11:52 AM Corey Bryant > wrote: > >> Hi Robie, >> >> Thanks for taking a look. >> >> On Wed, Aug 30, 2023 at 9:34 AM Robie Basak >> wrote: >> >>> Hi, >>> >>> As a list of 46 packages this is rather large and non-trivial to review. >>> Presumably we'll want to group them by upstream (are all managed by the >>> OpenStack umbrella upstream, or are there exceptions?) and then take a >>> view on them as a whole. >>> >> >> All of the packages in this list fall under the OpenStack umbrella >> upstream. The source can be found at: https://opendev.org/explore/repos >> All of these packages were specifically chosen because they are >> dependencies of the existing packages in our SRU exception list. >> > > Could you also check the reverse dependencies of these packages in the > Ubuntu Archive, to see what, if anything, other than openstack, might be > using them? If we start updating them to new upstream versions, albeit > still within a stable release track, we might be affecting their rdeps. > > Hi Andreas, Thanks for taking a look. I've put a full list of rdepends here: https://github.com/coreycb/reverse-depends/blob/main/reverse-depends It is mostly OpenStack packages, but I did find a few non-openstack packages: fence-agents-compute (Depends: python3-novaclient) fence-agents-openstack (Depends: python3-novaclient) fence-agents-ironic (Depends: python3-openstackclient) jeepyb (Depends: python3-swiftclient) prometheus-openstack-exporter (Depends: python3-cinderclient, python3-keystoneclient, python3-neutronclient, python3-novaclient, python3-swift) python3-novnc (Depends: python3-oslo.config, Reverse Depends: nova-novncproxy, qemu-web-desktop) It is worth noting that OpenStack stable releases cannot include incompatible API changes. And given the example from Robie below on python-ovsdbapp, when he analyzed > python-ovsdbapp, do you think you would be able to highlight usptream > changes in behavior, if they exist, in the future SRUs? In general, MREs > should not have those, of course. > > I'm hesitant to do this because I think it would get noisy. In my experience, bug fixes often change behavior, but not in an incompatible way. Would it be useful to provide a summary of commits included in a stable release? We might be able to include that in the debian/changelog even. In some cases, such as neutron, I probably would not want to do that because the number of commits (sometimes 50+) could pollute the changelog, but I think in general it could be useful to end users. Thanks, Corey > > >> On Fri, Jul 14, 2023 at 11:44:04AM -0400, Corey Bryant wrote: >>> > python-ovsdbapp >>> >>> This one was in the queue and so I reviewed it independently as >>> requested as a one-off microrelease update SRU. I ended up rejecting it >>> as there was what looked like a behavioural change with no explanation >>> as to why it is required, and most other upstream bugfixes did not come >>> with tests. Details at: >>> https://bugs.launchpad.net/charm-neutron-api/+bug/2007919/comments/19 >>> >>> I'm noting this in this thread for the record in case this has any >>> bearing on the larger view. >>> >> >> For the behavioral change [1], I think there is minimal regression >> potential as the change is limited to an exception path where sleeps and >> reconnects were determined to be unnecessary. I'd have appreciated it if >> they would have provided a bug reference for the commit to provide more >> context, however with that said, it seems they are making a code >> improvement here for performance reasons and they found it to be useful >> enough to backport to stable branches. >> [1] >> https://opendev.org/openstack/ovsdbapp/commit/ab3e0cb0d0865417efbf103f44954573a5ba92ac >> >> It is certainly not ideal to have missing unit tests. It's important to >> consider that we perform testing above and beyond the unit tests that are >> run as part of our package builds. The regression testing that we have in >> place for OpenStack is run for all stable releases. For that we deploy a >> full OpenStack cloud and then run tempest integration tests that exercise >> all of the packages and the cloud solution as a whole. >> >> I think we have a solid history of limiting regression potential for >> OpenStack users in our stable releases and that remains very important to >> us. One issue we have is that individual backports of bug fixes for all of >> these packages doesn't scale well. Another issue is that
Re: Dependency additions to OpenStack SRU exception
On Fri, Sep 1, 2023 at 10:51 AM Corey Bryant wrote: > Hi Robie, > > Thanks for taking a look. > > On Wed, Aug 30, 2023 at 9:34 AM Robie Basak > wrote: > >> Hi, >> >> As a list of 46 packages this is rather large and non-trivial to review. >> Presumably we'll want to group them by upstream (are all managed by the >> OpenStack umbrella upstream, or are there exceptions?) and then take a >> view on them as a whole. >> > > All of the packages in this list fall under the OpenStack umbrella > upstream. The source can be found at: https://opendev.org/explore/repos > All of these packages were specifically chosen because they are > dependencies of the existing packages in our SRU exception list. > > >> >> On Fri, Jul 14, 2023 at 11:44:04AM -0400, Corey Bryant wrote: >> > python-ovsdbapp >> >> This one was in the queue and so I reviewed it independently as >> requested as a one-off microrelease update SRU. I ended up rejecting it >> as there was what looked like a behavioural change with no explanation >> as to why it is required, and most other upstream bugfixes did not come >> with tests. Details at: >> https://bugs.launchpad.net/charm-neutron-api/+bug/2007919/comments/19 >> >> I'm noting this in this thread for the record in case this has any >> bearing on the larger view. >> > > For the behavioral change [1], I think there is minimal regression > potential as the change is limited to an exception path where sleeps and > reconnects were determined to be unnecessary. I'd have appreciated it if > they would have provided a bug reference for the commit to provide more > context, however with that said, it seems they are making a code > improvement here for performance reasons and they found it to be useful > enough to backport to stable branches. > [1] > https://opendev.org/openstack/ovsdbapp/commit/ab3e0cb0d0865417efbf103f44954573a5ba92ac > > It is certainly not ideal to have missing unit tests. It's important to > consider that we perform testing above and beyond the unit tests that are > run as part of our package builds. The regression testing that we have in > place for OpenStack is run for all stable releases. For that we deploy a > full OpenStack cloud and then run tempest integration tests that exercise > all of the packages and the cloud solution as a whole. > > I think we have a solid history of limiting regression potential for > OpenStack users in our stable releases and that remains very important to > us. One issue we have is that individual backports of bug fixes for all of > these packages doesn't scale well. Another issue is that we have clouds > that are running with outdated code that is missing available bug fixes. > With code that is running 5 or even up to 10 years in production, providing > these bug fixes to our users is important. > > Would it be useful to the SRU team if we were to pre-test our stable point > releases in a PPA and post the results to accompany new stable release > requests? > > Corey > Hello Robie and SRU team, I wanted to check in on this and see if there is anything I can do to help this review any easier. Please let me know if I can help in any way. Thanks, Corey -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Dependency additions to OpenStack SRU exception
Hi Robie, Thanks for taking a look. On Wed, Aug 30, 2023 at 9:34 AM Robie Basak wrote: > Hi, > > As a list of 46 packages this is rather large and non-trivial to review. > Presumably we'll want to group them by upstream (are all managed by the > OpenStack umbrella upstream, or are there exceptions?) and then take a > view on them as a whole. > All of the packages in this list fall under the OpenStack umbrella upstream. The source can be found at: https://opendev.org/explore/repos All of these packages were specifically chosen because they are dependencies of the existing packages in our SRU exception list. > > On Fri, Jul 14, 2023 at 11:44:04AM -0400, Corey Bryant wrote: > > python-ovsdbapp > > This one was in the queue and so I reviewed it independently as > requested as a one-off microrelease update SRU. I ended up rejecting it > as there was what looked like a behavioural change with no explanation > as to why it is required, and most other upstream bugfixes did not come > with tests. Details at: > https://bugs.launchpad.net/charm-neutron-api/+bug/2007919/comments/19 > > I'm noting this in this thread for the record in case this has any > bearing on the larger view. > For the behavioral change [1], I think there is minimal regression potential as the change is limited to an exception path where sleeps and reconnects were determined to be unnecessary. I'd have appreciated it if they would have provided a bug reference for the commit to provide more context, however with that said, it seems they are making a code improvement here for performance reasons and they found it to be useful enough to backport to stable branches. [1] https://opendev.org/openstack/ovsdbapp/commit/ab3e0cb0d0865417efbf103f44954573a5ba92ac It is certainly not ideal to have missing unit tests. It's important to consider that we perform testing above and beyond the unit tests that are run as part of our package builds. The regression testing that we have in place for OpenStack is run for all stable releases. For that we deploy a full OpenStack cloud and then run tempest integration tests that exercise all of the packages and the cloud solution as a whole. I think we have a solid history of limiting regression potential for OpenStack users in our stable releases and that remains very important to us. One issue we have is that individual backports of bug fixes for all of these packages doesn't scale well. Another issue is that we have clouds that are running with outdated code that is missing available bug fixes. With code that is running 5 or even up to 10 years in production, providing these bug fixes to our users is important. Would it be useful to the SRU team if we were to pre-test our stable point releases in a PPA and post the results to accompany new stable release requests? Corey -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Dependency additions to OpenStack SRU exception
Hello SRU team, I'm seeking your approval to add several OpenStack dependencies to the SRU exception list at: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates The goal here is to provide our users with reduced risk by proactively providing stable releases for these dependencies. Often times, important bug fixes are provided in these dependencies. Additionally, this will allow us to provide the package versions that upstream testing is performed with, further reducing risk. [1] You will notice that these package additions are scoped to, and tightly coupled with, the existing packages in our SRU exception list. It is also important to note that these packages are all covered by our existing regression testing. Following are the packages that we would like to add to the exception list: = OpenStack Clients = These projects provide python and CLI clients that correspond to OpenStack services. python-aodhclient python-barbicanclient python-cinderclient python-designateclient python-glanceclient python-gnocchiclient python-heatclient python-keystoneclient python-manilaclient python-neutronclient python-novaclient python-swiftclient python-octaviaclient python-openstackclient = OpenStack Oslo Libraries = The olso libraries provide common code used across multiple OpenStack projects. python-oslo.cache python-oslo.concurrency python-oslo.config python-oslo.context python-oslo.db python-oslo.i18n python-oslo.limit python-oslo.log python-oslo.messaging python-oslo.metrics python-oslo.middleware python-oslo.policy python-oslo.privsep python-oslo.reports python-oslo.rootwrap python-oslo.serialization python-oslo.service python-oslo.upgradecheck python-oslo.utils python-oslo.versionedobjects = Other Dependencies = python-ceilometermiddleware python-glance-store python-keystoneauth1 python-keystonemiddleware python-neutron-lib python-octavia-lib python-openstacksdk python-os-brick python-os-ken python-os-vif python-osc-placement python-ovsdbapp Thank you for your consideration. Corey [1] Upstream testing is performed against the versions listed in https://opendev.org/openstack/requirements/src/branch/master/upper-constraints.txt (there are separate branches for each openstack release). These versions get updated when upstream releases new stable versions. -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: [python3-glance-store] Package update request
As part of the SRU process, the patched package will get accepted into focal-proposed for testing, and then once it passes testing it will get promoted to focal-updates. If you could do that testing once it gets to -proposed, that would be very helpful. We should open a new bug here: https://bugs.launchpad.net/ubuntu/+source/python-glance-store to track the SRU. Sometimes we re-use upstream bugs for package fixes but since the upstream bug is a partial fix, I think we should probably open a new one. If you can sign up to do the testing I can upload the patched package for the SRU team to review. Thanks, Corey On Thu, Aug 4, 2022 at 4:09 AM Lemarchand Cedric wrote: > Hi Corey, > > Thanks for the info, unfortunately upgrade to newer release is not an > option now. > > What do you mean exactly by test it and report back to SRU ? Should I > apply patch to current version/files of glance-store, en reports if Glances > tests went well ? > > Cédric Lemarchand > DSI TDF > +33 6 37 23 40 93 > > > On 3 Aug 2022, at 21:58, Corey Bryant > wrote: > > > > Hi Cedric, > > > > It looks like this is fixed in the victoria+ releases. Victoria through > Xena are available via the cloud archive for focal, if it helps. > > If we were to SRU the fix for focal, would you be able to test it and > report back results to the SRU bug? > > > > Thanks, > > Corey > > > > > > > > On Wed, Aug 3, 2022 at 12:21 PM Lemarchand Cedric < > cedric.lemarch...@tdf.fr> wrote: > > Hello, > > > > I would like to know if this patch [1] can be applied to package > python3-glance-store (2.0.0-0ubuntu3) in focal-updates. > > > > It is about real performance improvements regarding glance image upload > when using Ceph/rbd backend and when the source image size is not known. > > > > https://review.opendev.org/c/openstack/glance_store/+/762498 > > > > Sorry for the noise if this is not the good place to ask, if so please > advice. > > -- > > Ubuntu-devel-discuss mailing list > > Ubuntu-devel-discuss@lists.ubuntu.com > > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: [python3-glance-store] Package update request
Hi Cedric, It looks like this is fixed in the victoria+ releases. Victoria through Xena are available via the cloud archive for focal, if it helps. If we were to SRU the fix for focal, would you be able to test it and report back results to the SRU bug? Thanks, Corey On Wed, Aug 3, 2022 at 12:21 PM Lemarchand Cedric wrote: > Hello, > > I would like to know if this patch [1] can be applied to package > python3-glance-store (2.0.0-0ubuntu3) in focal-updates. > > It is about real performance improvements regarding glance image upload > when using Ceph/rbd backend and when the source image size is not known. > > https://review.opendev.org/c/openstack/glance_store/+/762498 > > Sorry for the noise if this is not the good place to ask, if so please > advice. > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu 21.10 SRUs
On Tue, Jul 5, 2022 at 3:40 PM Brian Murray wrote: > Ubuntu 21.10, Impish Indri, will be reaching its End of Life next week > on July 14th. Looking at the pending SRU report[1] I see that there > are still several SRUs for that release which are unverified. If these > are important to you or someone you know please get them verified so > that a member of the SRU team can release them. > > [1] https://people.canonical.com/~ubuntu-archive/pending-sru.html > > Thanks! > -- > Brian Murray > > Some of these are OpenStack and we are okay leaving them in impish-proposed at this point. Apologies for leaving them unverified. It's important to note that these were meaningful to get into Impish. The path to the Xena cloud archive goes through Impish (until Impish is EOL) and we have verified these in the backported cloud archive. We have just had problems with our Impish verification process. Thank you, Corey -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 1904730] Re: neutron-agent-sriov fails to create port
This bug was fixed in the package pyroute2 - 0.4.21-0.1ubuntu2.1~cloud0 --- pyroute2 (0.4.21-0.1ubuntu2.1~cloud0) xenial-queens; urgency=medium . * New update for the Ubuntu Cloud Archive. . pyroute2 (0.4.21-0.1ubuntu2.1) bionic; urgency=medium . * Increase default recv-buf size (LP: #1904730) - d/p/increase-recvbuf-size.patch: increase recvbuf size from 16k to 32k. ** Changed in: cloud-archive/queens Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904730 Title: neutron-agent-sriov fails to create port To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1904730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904730] Update Released
The verification of the Stable Release Update for pyroute2 has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904730 Title: neutron-agent-sriov fails to create port To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1904730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975634] Re: [SRU] Xena stable releases
** Description changed: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: +* cinder 19.1.0 * neutron 19.3.0 * manila 13.0.3 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] Waiting for the following before moving forward: https://review.opendev.org/c/openstack/releases/+/842971 ** Also affects: cinder (Ubuntu) Importance: Undecided Status: New ** Changed in: cinder (Ubuntu) Status: New => Triaged ** Changed in: cinder (Ubuntu) Status: Triaged => Invalid ** Changed in: manila (Ubuntu) Status: New => Invalid ** Description changed: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: -* cinder 19.1.0 + * cinder 19.1.0 * neutron 19.3.0 * manila 13.0.3 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] - Waiting for the following before moving forward: https://review.opendev.org/c/openstack/releases/+/842971 + I've added cinder to this SRU after neutron and manila were accepted. ** No longer affects: cinder (Ubuntu) ** No longer affects: cinder (Ubuntu Impish) ** Description changed: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: * cinder 19.1.0 * neutron 19.3.0 * manila 13.0.3 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] - I've added cinder to this SRU after neutron and manila were accepted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975634 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1975634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965297] Please test proposed package
Hello Edward, or anyone else affected, Accepted neutron into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:xena-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/xena Status: In Progress => Fix Committed ** Tags added: verification-xena-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965297 Title: l3ha don't set backup qg ports down To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1965297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967895] Please test proposed package
Hello Corey, or anyone else affected, Accepted manila into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:xena-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/xena Status: New => Fix Committed ** Tags added: verification-xena-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967895 Title: [SRU] manila stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1967895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967895] Please test proposed package
Hello Corey, or anyone else affected, Accepted manila into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:wallaby-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967895 Title: [SRU] manila stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1967895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975634] Please test proposed package
Hello Corey, or anyone else affected, Accepted neutron into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:xena-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975634 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1975634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975634] Please test proposed package
Hello Corey, or anyone else affected, Accepted manila into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:xena-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/xena Status: Triaged => Fix Committed ** Tags added: verification-xena-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975634 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1975634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965297] Re: l3ha don't set backup qg ports down
** Changed in: cloud-archive Status: Triaged => Fix Committed ** Changed in: cloud-archive/yoga Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965297 Title: l3ha don't set backup qg ports down To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1965297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] Re: [SRU] Xena stable releases
I've uploaded a new cinder 2:19.1.0-0ubuntu1 to the impish unapproved queue with a changes file that includes 2:19.0.0-0ubuntu4. That should allow us to move forward and have both updates in impish-proposed for testing. ** Changed in: cinder (Ubuntu Impish) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976101] Re: py310 failure - AssertionError: Lists differ: ['[extra]'] != ['extra']
** Also affects: stevedore (Ubuntu) Importance: Undecided Status: New ** No longer affects: castellan ** Also affects: python-stevedore Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976101 Title: py310 failure - AssertionError: Lists differ: ['[extra]'] != ['extra'] To manage notifications about this bug go to: https://bugs.launchpad.net/python-stevedore/+bug/1976101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976106] Re: [SRU] FTBFS logging_user_identity_format's default is using deprecated (now removed) tenant
** Description changed: - python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. - 4.0.0 likely landed in Jammy after python-castellan. Now python- - oslo.log fails on Jammy rebuilds as seen here: - https://people.canonical.com/~ginggs/ftbfs-report/test- - rebuild-20220506-jammy-jammy.html + [Impact] + python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy after python-castellan. Now python-oslo.log fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html [1] https://review.opendev.org/c/openstack/oslo.context/+/815938 + + [Test Case] + A successful build of the python-oslo.context package will verify this fix. + + [Regression Potential] + The only regression potential that I see is for users who are already on Jammy and using the new python3-oslo.context with the existing python-oslo.log 4.6.1-0ubuntu1 as oslo.context has removed the (long deprecated) tenant argument. After this new version of python-oslo.log is avaialble, that regression goes away. ** Description changed: [Impact] python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy after python-castellan. Now python-oslo.log fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html [1] https://review.opendev.org/c/openstack/oslo.context/+/815938 [Test Case] A successful build of the python-oslo.context package will verify this fix. [Regression Potential] - The only regression potential that I see is for users who are already on Jammy and using the new python3-oslo.context with the existing python-oslo.log 4.6.1-0ubuntu1 as oslo.context has removed the (long deprecated) tenant argument. After this new version of python-oslo.log is avaialble, that regression goes away. + This is fixing a regression in Jammy. If the version of python3-oslo.context in Jammy is used with the existing python-oslo.log (4.6.1-0ubuntu1), logging_user_identity_format's default will cause a failure as oslo.context has removed the (long deprecated) tenant argument. After this new version of python-oslo.log is available, that regression goes away. ** Description changed: [Impact] python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy after python-castellan. Now python-oslo.log fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html [1] https://review.opendev.org/c/openstack/oslo.context/+/815938 [Test Case] A successful build of the python-oslo.context package will verify this fix. [Regression Potential] - This is fixing a regression in Jammy. If the version of python3-oslo.context in Jammy is used with the existing python-oslo.log (4.6.1-0ubuntu1), logging_user_identity_format's default will cause a failure as oslo.context has removed the (long deprecated) tenant argument. After this new version of python-oslo.log is available, that regression goes away. + This is fixing a regression in Jammy. If the version of python3-oslo.context in Jammy is used with the existing python-oslo.log (4.6.1-0ubuntu1), logging_user_identity_format's default will cause a failure as oslo.context has removed the (long deprecated) tenant argument. After this new version of python-oslo.log is available, the regression will be fixed. ** Description changed: [Impact] - python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy after python-castellan. Now python-oslo.log fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html + python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy after python-oslo.log. Now python-oslo.log fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html [1] https://review.opendev.org/c/openstack/oslo.context/+/815938 [Test Case] A successful build of the python-oslo.context package will verify this fix. [Regression Potential] This is fixing a regression in Jammy. If the version of python3-oslo.context in Jammy is used with the existing python-oslo.log (4.6.1-0ubuntu1), logging_user_identity_format's default will cause a failure as oslo.context has removed the (long deprecated) tenant argument. After this new version of python-oslo.log is available, the regression will be fixed. ** Also affects: python-oslo.log (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: python-oslo.log (Ubuntu Jammy) Status: New => Triaged ** Changed in: python-oslo.log (Ubuntu Jammy) Importance: Undecided => High ** Changed in: python-oslo.log (Ubuntu) Status: New
[Bug 1976102] Re: [SRU] Fix FTBFS for jammy
** Description changed: [Impact] - python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy Remove the deprecated argument tenant from RequestContext. Now python-castellan fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html + python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy after python-castellan. Remove the deprecated argument tenant from RequestContext. Now python-castellan fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html [1] https://review.opendev.org/c/openstack/oslo.context/+/815938 [Test Case] A successful build of the python-oslo.context package will verify this fix. [Regression Potential] This is a doc and unit test only update, so there is not much concern with regression. ** Description changed: [Impact] - python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy after python-castellan. Remove the deprecated argument tenant from RequestContext. Now python-castellan fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html + python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy after python-castellan. Now python-castellan fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html [1] https://review.opendev.org/c/openstack/oslo.context/+/815938 [Test Case] A successful build of the python-oslo.context package will verify this fix. [Regression Potential] This is a doc and unit test only update, so there is not much concern with regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976102 Title: [SRU] Fix FTBFS for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-castellan/+bug/1976102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976106] [NEW] [SRU] FTBFS logging_user_identity_format's default is using deprecated (now removed) tenant
Public bug reported: [Impact] python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy after python-castellan. Now python-oslo.log fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html [1] https://review.opendev.org/c/openstack/oslo.context/+/815938 [Test Case] A successful build of the python-oslo.context package will verify this fix. [Regression Potential] The only regression potential that I see is for users who are already on Jammy and using the new python3-oslo.context with the existing python-oslo.log 4.6.1-0ubuntu1 as oslo.context has removed the (long deprecated) tenant argument. After this new version of python-oslo.log is avaialble, that regression goes away. ** Affects: python-oslo.log (Ubuntu) Importance: Undecided Status: New ** Summary changed: - logging_user_identity_format's default is using deprecated (now removed) tenant + [SRU] FTBFS logging_user_identity_format's default is using deprecated (now removed) tenant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976106 Title: [SRU] FTBFS logging_user_identity_format's default is using deprecated (now removed) tenant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-oslo.log/+bug/1976106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976102] Re: [SRU] Fix FTBFS for jammy
** Tags added: block-proposed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976102 Title: [SRU] Fix FTBFS for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-castellan/+bug/1976102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976102] [NEW] [SRU] Fix FTBFS for jammy
Public bug reported: [Impact] python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy Remove the deprecated argument tenant from RequestContext. Now python-castellan fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html [1] https://review.opendev.org/c/openstack/oslo.context/+/815938 [Test Case] A successful build of the python-oslo.context package will verify this fix. [Regression Potential] This is a doc and unit test only update, so there is not much concern with regression. ** Affects: python-castellan (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: python-castellan (Ubuntu Jammy) Importance: Medium Status: Triaged ** Description changed: + [Impact] + python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy Remove the deprecated argument tenant from RequestContext. Now python-castellan fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test- rebuild-20220506-jammy-jammy.html [1] https://review.opendev.org/c/openstack/oslo.context/+/815938 + + [Test Case] + A successful build of the python-oslo.context package will verify this fix. + + [Regression Potential] + This is a doc and unit test only update, so there is not much concern with regression. ** Description changed: [Impact] - - python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. - 4.0.0 likely landed in Jammy Remove the deprecated argument tenant from - RequestContext. Now python-castellan fails on Jammy rebuilds as seen - here: https://people.canonical.com/~ginggs/ftbfs-report/test- - rebuild-20220506-jammy-jammy.html + python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy Remove the deprecated argument tenant from RequestContext. Now python-castellan fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html [1] https://review.opendev.org/c/openstack/oslo.context/+/815938 [Test Case] A successful build of the python-oslo.context package will verify this fix. [Regression Potential] This is a doc and unit test only update, so there is not much concern with regression. ** Also affects: python-castellan (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: python-castellan (Ubuntu) Status: New => Fix Released ** Changed in: python-castellan (Ubuntu Jammy) Status: New => Triaged ** Changed in: python-castellan (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976102 Title: [SRU] Fix FTBFS for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-castellan/+bug/1976102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965297] Re: l3ha don't set backup qg ports down
** Also affects: cloud-archive/victoria Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Changed in: cloud-archive/xena Status: In Progress => Triaged ** Changed in: cloud-archive/wallaby Importance: Undecided => High ** Changed in: cloud-archive/wallaby Status: New => Triaged ** Changed in: cloud-archive/victoria Importance: Undecided => High ** Changed in: cloud-archive/victoria Status: New => Triaged ** Changed in: cloud-archive/ussuri Importance: Undecided => High ** Changed in: cloud-archive/ussuri Status: New => Triaged ** Also affects: neutron (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu Focal) Importance: Undecided => High ** Changed in: neutron (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965297 Title: l3ha don't set backup qg ports down To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1965297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965297] Re: l3ha don't set backup qg ports down
** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu Impish) Status: New => Triaged ** Changed in: neutron (Ubuntu Jammy) Status: New => Triaged ** Changed in: neutron (Ubuntu Impish) Importance: Undecided => High ** Changed in: neutron (Ubuntu Jammy) Importance: Undecided => High ** Changed in: neutron (Ubuntu Kinetic) Status: New => Triaged ** Changed in: neutron (Ubuntu Kinetic) Importance: Undecided => High ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/zed Importance: Undecided Status: New ** Also affects: cloud-archive/yoga Importance: Undecided Status: New ** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Changed in: cloud-archive/xena Status: New => Triaged ** Changed in: cloud-archive/yoga Status: New => Triaged ** Changed in: cloud-archive/zed Status: New => Triaged ** Changed in: cloud-archive/yoga Importance: Undecided => High ** Changed in: cloud-archive/xena Importance: Undecided => High ** Changed in: cloud-archive/zed Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965297 Title: l3ha don't set backup qg ports down To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1965297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975594] Re: OVN backports for Neutron Ussuri
** Description changed: [Impact] The upstream Neutron stable/ussuri branch is in extended-maintenance mode which means patches are still accepted but they aren't cutting any new stable releases. Therefore this bug is being opened to backport a series of OVN patches that are needed for functionality on Ussuri (Focal). + + Specifically the following bugs require fixes: + LP#1914394 + LP#1946588 + LP#1951872 + LP#1961013 + LP#1965819 + LP#1927077 + LP#1953295 + LP#1928031 + LP#1952550 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] All of these patches have already landed in the upstream stable/ussuri branch. All of these patches have also been included in later stable releases of neutron in Ubuntu. The last of these patches are included via the following point releases: https://bugs.launchpad.net/cloud-archive/+bug/1975632 https://bugs.launchpad.net/cloud-archive/+bug/1975634 https://bugs.launchpad.net/cloud-archive/+bug/1975636 ** Description changed: [Impact] The upstream Neutron stable/ussuri branch is in extended-maintenance mode which means patches are still accepted but they aren't cutting any new stable releases. Therefore this bug is being opened to backport a series of OVN patches that are needed for functionality on Ussuri (Focal). Specifically the following bugs require fixes: - LP#1914394 - LP#1946588 - LP#1951872 - LP#1961013 - LP#1965819 - LP#1927077 - LP#1953295 - LP#1928031 - LP#1952550 + LP #1914394 + LP #1946588 + LP #1951872 + LP #1961013 + LP #1965819 + LP #1927077 + LP #1953295 + LP #1928031 + LP: #1952550 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] All of these patches have already landed in the upstream stable/ussuri branch. All of these patches have also been included in later stable releases of neutron in Ubuntu. The last of these patches are included via the following point releases: https://bugs.launchpad.net/cloud-archive/+bug/1975632 https://bugs.launchpad.net/cloud-archive/+bug/1975634 https://bugs.launchpad.net/cloud-archive/+bug/1975636 ** Description changed: [Impact] The upstream Neutron stable/ussuri branch is in extended-maintenance mode which means patches are still accepted but they aren't cutting any new stable releases. Therefore this bug is being opened to backport a series of OVN patches that are needed for functionality on Ussuri (Focal). Specifically the following bugs require fixes: - LP #1914394 - LP #1946588 - LP #1951872 - LP #1961013 - LP #1965819 - LP #1927077 - LP #1953295 - LP #1928031 + LP: #1914394 + LP: #1946588 + LP: #1951872 + LP: #1961013 + LP: #1965819 + LP: #1927077 + LP: #1953295 + LP: #1928031 LP: #1952550 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] All of these patches have already landed in the upstream stable/ussuri branch. All of these patches have also been included in later stable releases of neutron in
[Bug 1975594] Re: OVN backports for Neutron Ussuri
** Description changed: [Impact] The upstream Neutron stable/ussuri branch is in extended-maintenance mode which means patches are still accepted but they aren't cutting any new stable releases. Therefore this bug is being opened to backport a series of OVN patches that are needed for functionality on Ussuri (Focal). [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] + All of these patches have been included in later stable releases of neutron already. The last of these patches are included via the following point releases: + https://bugs.launchpad.net/cloud-archive/+bug/1975632 + https://bugs.launchpad.net/cloud-archive/+bug/1975634 + https://bugs.launchpad.net/cloud-archive/+bug/1975636 ** Description changed: [Impact] The upstream Neutron stable/ussuri branch is in extended-maintenance mode which means patches are still accepted but they aren't cutting any new stable releases. Therefore this bug is being opened to backport a series of OVN patches that are needed for functionality on Ussuri (Focal). [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] - All of these patches have been included in later stable releases of neutron already. The last of these patches are included via the following point releases: + All of these patches have already landed in the upstream stable/ussuri branch. + All of these patches have also been included in later stable releases of neutron in Ubuntu. The last of these patches are included via the following point releases: https://bugs.launchpad.net/cloud-archive/+bug/1975632 https://bugs.launchpad.net/cloud-archive/+bug/1975634 https://bugs.launchpad.net/cloud-archive/+bug/1975636 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975594 Title: OVN backports for Neutron Ussuri To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1975594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975594] Re: OVN backports for Neutron Ussuri
** Description changed: - The upstream Neutron stable/ussuri branch is in extended-maintenance - mode which means patches are still accepted but they aren't cutting any - new stable releases. Therefore this bug is being opened to backport a - series of OVN patches that are needed for functionality on Ussuri - (Focal). + [Impact] + The upstream Neutron stable/ussuri branch is in extended-maintenance mode which means patches are still accepted but they aren't cutting any new stable releases. Therefore this bug is being opened to backport a series of OVN patches that are needed for functionality on Ussuri (Focal). + + [Test Case] + The following SRU process was followed: + https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates + + In order to avoid regression of existing consumers, the OpenStack team + will run their continuous integration test against the packages that are + in -proposed. A successful run of all available tests will be required + before the proposed packages can be let into -updates. + + The OpenStack team will be in charge of attaching the output summary of + the executed tests. The OpenStack team members will not mark + ‘verification-done’ until this has happened. + + [Regression Potential] + In order to mitigate the regression potential, the results of the + aforementioned tests are attached to this bug. + + [Discussion] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975594 Title: OVN backports for Neutron Ussuri To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1975594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975600] Re: [MIR] jaraco.context
** Description changed: - TBC + [Availability] + Currently in universe + + [Rationale] + python3-jaraco.text has a new dependency on python3-jaraco.context. + + Reverse-depends chain from the ceph packages that depend on this: + ceph-mgr/ceph-mgr-cephadm/ceph-mgr-dashboard <- python3-cherrypy3 <- python3-jaraco.collections <- python3-jaraco.text <- python3-jarico.context + + [Security] + No security history + + [Quality Assurance] + Package works out of the box with no prompting. There are no major bugs in Ubuntu and there are no major bugs in Debian. Unit tests are run during build. + + [Dependencies] + All are in main + + [Standards Compliance] + FHS and Debian Policy compliant + + [Maintenance] + Simple python package that the OpenStack Team will take care of + + [Background] + Provides various context managers extending functionality of Python's contextlib. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975600 Title: [MIR] jaraco.context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jaraco.context/+bug/1975600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975594] Re: OVN backports for Neutron Ussuri
** Also affects: neutron (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu) Status: New => Invalid ** Changed in: neutron (Ubuntu Focal) Status: New => Triaged ** Changed in: neutron (Ubuntu Focal) Importance: Undecided => High ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Changed in: cloud-archive/ussuri Status: New => Triaged ** Changed in: cloud-archive/ussuri Importance: Undecided => High ** Changed in: cloud-archive Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975594 Title: OVN backports for Neutron Ussuri To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1975594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975632] Re: [SRU] Yoga stable releases
** Also affects: cloud-archive/yoga Importance: Undecided Status: New ** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu) Status: New => Invalid ** Changed in: cloud-archive Status: New => Invalid ** Changed in: cloud-archive/yoga Status: New => Triaged ** Changed in: neutron (Ubuntu Jammy) Status: New => Triaged ** Changed in: neutron (Ubuntu Jammy) Importance: Undecided => High ** Changed in: cloud-archive/yoga Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975632 Title: [SRU] Yoga stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1975632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975634] Re: [SRU] Xena stable releases
** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Changed in: cloud-archive/xena Status: New => Triaged ** Changed in: cloud-archive/xena Importance: Undecided => High ** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu Impish) Status: New => Triaged ** Changed in: neutron (Ubuntu Impish) Importance: Undecided => High ** Changed in: neutron (Ubuntu) Status: New => Invalid ** Changed in: cloud-archive Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975634 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1975634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975594] [NEW] OVN backports for Neutron Ussuri
Public bug reported: The upstream Neutron stable/ussuri branch is in extended-maintenance mode which means patches are still accepted but they aren't cutting any new stable releases. Therefore this bug is being opened to backport a series of OVN patches that are needed for functionality on Ussuri (Focal). ** Affects: neutron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975594 Title: OVN backports for Neutron Ussuri To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1975594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967895] Re: [SRU] manila stable releases
Manila has been approved and added to https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates. ** Changed in: manila (Ubuntu Impish) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967895 Title: [SRU] manila stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1967895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Request New OpenStack SRU Exception for Manila
On Mon, May 23, 2022 at 3:37 PM Steve Langasek wrote: > Hi Corey, > > On Mon, May 23, 2022 at 11:50:56AM -0400, Corey Bryant wrote: > > Hello SRU Team,I'd like to request that Manila be included in the > > OpenStack SRU Exception list at > > https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates. > > Manila is an OpenStack project that provides Shared Filesystems as a > > service to instances.Manila is already included in our regression > > testing and is validated via Tempest smoke tests: > > > https://github.com/openstack-charmers/charmed-openstack-tester/commit/bcc923acefc67f09e0dccc852fc020abed359ac9 > > Thanks,Corey > > I was surprised to learn with this email thread that manila wasn't already > in the list. Yes, please go ahead and add it to the wiki page. (I would > do > it, but the wiki continues to not let me log in.) > > Great, thank you. I've added manila to the list. Corey -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
[Bug 1904580] Please test proposed package
Hello Diko, or anyone else affected, Accepted nova into ussuri-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:ussuri-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-ussuri-needed to verification-ussuri-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-ussuri-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/ussuri Status: Triaged => Fix Committed ** Tags added: verification-ussuri-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904580 Title: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Please test proposed package
Hello Diko, or anyone else affected, Accepted nova into victoria-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:victoria-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-victoria-needed to verification-victoria-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-victoria-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/victoria Status: Triaged => Fix Committed ** Tags added: verification-victoria-needed ** Changed in: cloud-archive/zed Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904580 Title: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Please test proposed package
Hello Diko, or anyone else affected, Accepted nova into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:wallaby-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/wallaby Status: Triaged => Fix Committed ** Tags added: verification-wallaby-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904580 Title: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Please test proposed package
Hello Diko, or anyone else affected, Accepted nova into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:xena-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/xena Status: Triaged => Fix Committed ** Tags added: verification-xena-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904580 Title: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] Please test proposed package
Hello Felipe, or anyone else affected, Accepted nova into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:xena-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] Please test proposed package
Hello Felipe, or anyone else affected, Accepted neutron into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:xena-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] Please test proposed package
Hello Felipe, or anyone else affected, Accepted horizon into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:xena-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/xena Status: New => Fix Committed ** Tags added: verification-xena-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930446] Re: Wallaby ceilometer.compute.discovery fails to get domain metadata
** Changed in: ceilometer (Ubuntu Impish) Status: Triaged => Fix Released ** Changed in: cloud-archive/xena Status: Triaged => Fix Released ** Changed in: cloud-archive/wallaby Status: Triaged => Fix Released ** Changed in: ceilometer (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930446 Title: Wallaby ceilometer.compute.discovery fails to get domain metadata To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1930446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930446] Re: Wallaby ceilometer.compute.discovery fails to get domain metadata
** Changed in: ceilometer (Ubuntu Jammy) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930446 Title: Wallaby ceilometer.compute.discovery fails to get domain metadata To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1930446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940834] Re: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova
This bug was fixed in the package horizon - 4:18.6.3-0ubuntu1~cloud1 --- horizon (4:18.6.3-0ubuntu1~cloud1) focal-victoria; urgency=medium . * d/p/0001-Fix-for-Resize-instance-button.patch: Fixes resize instance widget (LP: #1940834). ** Changed in: cloud-archive/victoria Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940834 Title: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940834] Update Released
The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940834 Title: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940834] Re: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova
This bug was fixed in the package horizon - 4:19.2.0-0ubuntu1~cloud1 --- horizon (4:19.2.0-0ubuntu1~cloud1) focal-wallaby; urgency=medium . [ Corey Bryant ] * d/gbp.conf: Create stable/wallaby branch. . [ Hemanth Nakkina ] * d/p/0001-Fix-for-Resize-instance-button.patch: Fixes resize instance widget (LP: #1940834). ** Changed in: cloud-archive/wallaby Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940834 Title: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940834] Update Released
The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940834 Title: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940834] Re: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova
This bug was fixed in the package horizon - 4:20.1.1-0ubuntu2~cloud0 --- horizon (4:20.1.1-0ubuntu2~cloud0) focal-xena; urgency=medium . * New update for the Ubuntu Cloud Archive. . horizon (4:20.1.1-0ubuntu2) impish; urgency=medium . * d/p/0001-Fix-for-Resize-instance-button.patch: Fixes resize instance widget (LP: #1940834). ** Changed in: cloud-archive/xena Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940834 Title: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940834] Update Released
The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940834 Title: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Request New OpenStack SRU Exception for Manila
Hello SRU Team,I'd like to request that Manila be included in the OpenStack SRU Exception list at https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates. Manila is an OpenStack project that provides Shared Filesystems as a service to instances.Manila is already included in our regression testing and is validated via Tempest smoke tests: https://github.com/openstack-charmers/charmed-openstack-tester/commit/bcc923acefc67f09e0dccc852fc020abed359ac9 Thanks,Corey -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
[Bug 1967895] Re: [SRU] manila stable releases
I've just uploaded a new manila 1:13.0.2-0ubuntu1 to the impish unapproved queue to include LP:1952763 in its changes file. More details are at: https://bugs.launchpad.net/charm-manila- ganesha/+bug/1952763/comments/25 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967895 Title: [SRU] manila stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1967895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952763] Re: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403)
Brian, I've just uploaded a new manila 1:13.0.2-0ubuntu1 to the impish unapproved queue that includes this bug in its changes file. If it is ok with the SRU team, we'd like to carry both of the outstanding SRUs for manila in impish-proposed. With impish EOL in July, we are ok with carrying these in proposed until then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952763 Title: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1952763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902338] Re: package manila-api 1:10.0.0-0ubuntu0.20.04.1~cloud0 failed to install/upgrade: installed manila-api package post-installation script subprocess returned error exit status 1
I've dropped debconf support from manila in kinetic 1:14.0.0-0ubuntu2. ** Changed in: manila (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902338 Title: package manila-api 1:10.0.0-0ubuntu0.20.04.1~cloud0 failed to install/upgrade: installed manila-api package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manila/+bug/1902338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967895] Re: [SRU] manila stable releases
Hi Brian, I've done some work to get openstack regression testing coverage, specifically: https://github.com/openstack-charmers/charmed-openstack- tester/commit/bcc923acefc67f09e0dccc852fc020abed359ac9 Also, and not a requirement, but I've submitted for main inclusion of manila: https://bugs.launchpad.net/ubuntu/+source/manila/+bug/1975493 Thanks, Corey -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967895 Title: [SRU] manila stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1967895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975493] [NEW] [MIR] manila
Public bug reported: [Availability] Currently in universe [Rationale] Manila is an OpenStack project that we're ready to support in main. [Security] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6519 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27781 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9543 [Quality Assurance] Package works out of the box with no prompting. There are no major bugs in Ubuntu and there are no major bugs in Debian. Unit tests are run during build. [Dependencies] All are in main (see version 1:14.0.0-0ubuntu2 in kinetic) [Standards Compliance] FHS and Debian Policy compliant [Maintenance] Python package that the OpenStack Team will take care of [Background] Manila is an OpenStack project that provides Shared Filesystems as a service. It provides coordinated access to shared or distributed file systems. While the primary consumption of file shares would be across OpenStack Compute instances, the service is also intended to be accessible as an independent capability in line with the modular design established by other OpenStack services. Manila is extensible for multiple backends (to support vendor or file system specific nuances / capabilities) and accommodates any of a variety of shared or distributed file system types. ** Affects: manila (Ubuntu) Importance: Undecided Status: New ** Description changed: [Availability] Currently in universe [Rationale] Manila is an OpenStack project that we're ready to support in main. [Security] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6519 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27781 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9543 [Quality Assurance] Package works out of the box with no prompting. There are no major bugs in Ubuntu and there are no major bugs in Debian. Unit tests are run during build. [Dependencies] All are in main (see version 1:14.0.0-0ubuntu2 in kinetic) [Standards Compliance] FHS and Debian Policy compliant [Maintenance] Python package that the OpenStack Team will take care of [Background] - Manila is an OpenStack project that provides Shared Filesystems as a service. - It provides coordinated access to shared or distributed file systems. While - the primary consumption of file shares would be across OpenStack Compute - instances, the service is also intended to be accessible as an independent - capability in line with the modular design established by other OpenStack - services. Manila is extensible for multiple backends (to support vendor or - file system specific nuances / capabilities) and accommodates any of a - variety of shared or distributed file system types. + Manila is an OpenStack project that provides Shared Filesystems as a service. It provides coordinated access to shared or distributed file systems. While the primary consumption of file shares would be across OpenStack Compute instances, the service is also intended to be accessible as an independent capability in line with the modular design established by other OpenStack services. Manila is extensible for multiple backends (to support vendor or file system specific nuances / capabilities) and accommodates any of a variety of shared or distributed file system types. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975493 Title: [MIR] manila To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manila/+bug/1975493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902338] Re: package manila-api 1:10.0.0-0ubuntu0.20.04.1~cloud0 failed to install/upgrade: installed manila-api package post-installation script subprocess returned error exit status 1
Hello Hiten, Thank you for reporting this bug. It looks like you're hitting debconf questions, which were inherited from Debian. I plan to drop those soon. As a work-around you should be able to turn off deconf questions (noninteractive) with 'dpkg-reconfigure debconf'. Thank you, Corey -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902338 Title: package manila-api 1:10.0.0-0ubuntu0.20.04.1~cloud0 failed to install/upgrade: installed manila-api package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manila/+bug/1902338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902338] Re: package manila-api 1:10.0.0-0ubuntu0.20.04.1~cloud0 failed to install/upgrade: installed manila-api package post-installation script subprocess returned error exit status 1
Additional details from DpkgTerminalLog.txt:
Registering service and endpoints for manila with type share at
http://172.16.21.40:8786/v1/$(tenant_id)s
Failed to discover available identity versions when contacting
http://127.0.0.1:35357/v3/. Attempting to parse version from URL.
Unable to establish connection to http://127.0.0.1:35357/v3/auth/tokens:
HTTPConnectionPool(host='127.0.0.1', port=35357): Max retries exceeded with
url: /v3/auth/tokens (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused',))
Warning - data is empty
Failed to discover available identity versions when contacting
http://127.0.0.1:35357/v3/. Attempting to parse version from URL.
Unable to establish connection to http://127.0.0.1:35357/v3/auth/tokens:
HTTPConnectionPool(host='127.0.0.1', port=35357): Max retries exceeded with
url: /v3/auth/tokens (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused',))
dpkg: error processing package manila-api (--configure):
installed manila-api package post-installation script subprocess returned
error exit status 1
** Changed in: manila (Ubuntu)
Importance: Undecided => Medium
** Changed in: manila (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902338
Title:
package manila-api 1:10.0.0-0ubuntu0.20.04.1~cloud0 failed to
install/upgrade: installed manila-api package post-installation script
subprocess returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/manila/+bug/1902338/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907494] Re: base64 encodestring is deprecated and removed in python 3.9
** Changed in: manila (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907494 Title: base64 encodestring is deprecated and removed in python 3.9 To manage notifications about this bug go to: https://bugs.launchpad.net/manila/+bug/1907494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Please test proposed package
Hello Diko, or anyone else affected, Accepted nova into yoga-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:yoga-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-yoga-needed to verification-yoga-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-yoga-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/yoga Status: Triaged => Fix Committed ** Tags added: verification-yoga-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904580 Title: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Re: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open
Thank you Felipe and Rodrigo for this fix. It's been uploaded to focal, impish, jammy unapproved queues, and victoria/wallaby staging for the cloud archive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904580 Title: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Re: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open
** Description changed: + [Impact] Charm revision: 320 Cloud: bionic-ussuri Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open. Load key "/var/lib/nova/.ssh/id_rsa": bad permissions nova@10.35.80.49: Permission denied (publickey). This was preventing nova resizing: /var/log/nova/nova-compute.log:2020-11-17 13:14:42.210 100221 ERROR oslo_messaging.rpc.server Command: ssh -o BatchMode=yes 10.35.80.49 mkdir -p /var/lib/nova/instances/39caee98-b81c-4cef-9810-815f2ecf1fc4 Manually setting to 0600 fixed the issue. + + Note (coreycb): It's important to note that /var/lib/nova/.ssh/ and + files contained in that directory are not created by the package. + Therefore the package should avoid changing permissions for this + directory. + + [Test Case] + Install a previous version of the nova-common package. + Setup ssh as described here (at least the creation of /var/lib/nova/.ssh/ files and chmod accordingly. + Upgrade to the patched version of nova-common and confirm the /var/lib/nova/.ssh/ directory/file modes haven't changed. + + [Regression Potential] + This is actually fixing a regression that was introduced to the package when we introduced the postinst code that does a blanket chmod to all of /var/lib/nova/. Assuming the test case above passes, I can't see any way for this to cause a regression. ** Description changed: [Impact] Charm revision: 320 Cloud: bionic-ussuri Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open. Load key "/var/lib/nova/.ssh/id_rsa": bad permissions nova@10.35.80.49: Permission denied (publickey). This was preventing nova resizing: /var/log/nova/nova-compute.log:2020-11-17 13:14:42.210 100221 ERROR oslo_messaging.rpc.server Command: ssh -o BatchMode=yes 10.35.80.49 mkdir -p /var/lib/nova/instances/39caee98-b81c-4cef-9810-815f2ecf1fc4 Manually setting to 0600 fixed the issue. Note (coreycb): It's important to note that /var/lib/nova/.ssh/ and files contained in that directory are not created by the package. Therefore the package should avoid changing permissions for this directory. [Test Case] Install a previous version of the nova-common package. Setup ssh as described here (at least the creation of /var/lib/nova/.ssh/ files and chmod accordingly. Upgrade to the patched version of nova-common and confirm the /var/lib/nova/.ssh/ directory/file modes haven't changed. [Regression Potential] - This is actually fixing a regression that was introduced to the package when we introduced the postinst code that does a blanket chmod to all of /var/lib/nova/. Assuming the test case above passes, I can't see any way for this to cause a regression. + This is actually fixing a regression that was introduced to the package when we introduced the postinst code that does a blanket chmod to all of /var/lib/nova/. Assuming the test case above passes, I can't see any way for this to cause another regression. ** Description changed: [Impact] Charm revision: 320 Cloud: bionic-ussuri Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open. Load key "/var/lib/nova/.ssh/id_rsa": bad permissions nova@10.35.80.49: Permission denied (publickey). This was preventing nova resizing: /var/log/nova/nova-compute.log:2020-11-17 13:14:42.210 100221 ERROR oslo_messaging.rpc.server Command: ssh -o BatchMode=yes 10.35.80.49 mkdir -p /var/lib/nova/instances/39caee98-b81c-4cef-9810-815f2ecf1fc4 Manually setting to 0600 fixed the issue. Note (coreycb): It's important to note that /var/lib/nova/.ssh/ and files contained in that directory are not created by the package. Therefore the package should avoid changing permissions for this directory. [Test Case] Install a previous version of the nova-common package. - Setup ssh as described here (at least the creation of /var/lib/nova/.ssh/ files and chmod accordingly. + Setup ssh as described here (at least the creation of /var/lib/nova/.ssh/ files and chmod accordingly): https://docs.openstack.org/nova/pike/admin/ssh-configuration.html Upgrade to the patched version of nova-common and confirm the /var/lib/nova/.ssh/ directory/file modes haven't changed. [Regression Potential] This is actually fixing a regression that was introduced to the package when we introduced the postinst code that does a blanket chmod to all of /var/lib/nova/. Assuming the test case above passes, I can't see any way for this to cause another regression. ** Also affects: nova (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Kinetic) Importance: Undecided Assignee: Rodrigo Barbieri (rodrigo-barbieri2010) Status: Triaged ** Also affects: nova (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: nova (Ubuntu Focal) Status: New => Triaged **
[Bug 1952763] Re: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403)
This bug was fixed in the package manila - 1:13.0.0-0ubuntu2~cloud0 --- manila (1:13.0.0-0ubuntu2~cloud0) focal-xena; urgency=medium . * New update for the Ubuntu Cloud Archive. . manila (1:13.0.0-0ubuntu2) impish; urgency=medium . [ Corey Bryant ] * d/gbp.conf: Create stable/xena branch. * d/rules: Drop generation of policy.json in favor of policy-in-code (LP: #1952763). ** Changed in: cloud-archive/xena Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952763 Title: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1952763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952763] Update Released
The verification of the Stable Release Update for manila has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952763 Title: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1952763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952763] Re: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403)
focal-xena/proposed verified successfully: https://review.opendev.org/c/openstack/charm-manila-ganesha/+/841328 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952763 Title: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1952763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940834] Please test proposed package
Hello lmercl, or anyone else affected, Accepted horizon into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:xena-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/xena Status: Fix Released => Fix Committed ** Tags added: verification-xena-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940834 Title: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940834] Please test proposed package
Hello lmercl, or anyone else affected, Accepted horizon into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:wallaby-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/wallaby Status: Triaged => Fix Committed ** Tags added: verification-wallaby-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940834 Title: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940834] Please test proposed package
Hello lmercl, or anyone else affected, Accepted horizon into victoria-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:victoria-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-victoria-needed to verification-victoria-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-victoria-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/victoria Status: Fix Released => Fix Committed ** Tags added: verification-victoria-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940834 Title: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952763] Re: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403)
** Changed in: cloud-archive/yoga Status: Fix Committed => Fix Released ** Changed in: cloud-archive Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952763 Title: [SRU] manilaclient.common.apiclient.exceptions.Forbidden: Access was denied to this resource. (HTTP 403) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1952763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962582] Re: [SRU] Xena stable releases
This bug was fixed in the package horizon - 4:20.1.1-0ubuntu1~cloud0 --- horizon (4:20.1.1-0ubuntu1~cloud0) focal-xena; urgency=medium . * New upstream release for the Ubuntu Cloud Archive. . horizon (4:20.1.1-0ubuntu1) impish; urgency=medium . [ Corey Bryant ] * d/gbp.conf: Create stable/xena branch. . [ Felipe Reyes ] * New stable point release for OpenStack Xena (LP: #1962582). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962582 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1962582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962582] Update Released
The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962582 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1962582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948507] Re: TypeError when computing QOS feature name
This bug was fixed in the package cinder - 2:18.1.0-0ubuntu1~cloud2 --- cinder (2:18.1.0-0ubuntu1~cloud2) focal-wallaby; urgency=medium . * d/p/fix-qos-computation.patch: Cherry-pick from upstream review to fix TypeError exception when generating QOS feature name (LP: #1948507). ** Changed in: cloud-archive/wallaby Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948507 Title: TypeError when computing QOS feature name To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1948507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948507] Update Released
The verification of the Stable Release Update for cinder has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948507 Title: TypeError when computing QOS feature name To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1948507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948507] Re: TypeError when computing QOS feature name
This bug was fixed in the package cinder - 2:19.0.0-0ubuntu4~cloud0 --- cinder (2:19.0.0-0ubuntu4~cloud0) focal-xena; urgency=medium . * New update for the Ubuntu Cloud Archive. . cinder (2:19.0.0-0ubuntu4) impish; urgency=medium . * d/p/fix-qos-computation.patch: Cherry-pick from upstream review to fix TypeError exception when generating QOS feature name (LP: #1948507). ** Changed in: cloud-archive/xena Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948507 Title: TypeError when computing QOS feature name To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1948507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948507] Update Released
The verification of the Stable Release Update for cinder has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948507 Title: TypeError when computing QOS feature name To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1948507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948507] Re: TypeError when computing QOS feature name
focal-xena and focal-wallaby are both successful in the charm-cinder- netapp gate when running with proposed: https://review.opendev.org/c/openstack/charm-cinder-netapp/+/833770 ** Tags removed: verification-wallaby-needed verification-xena-needed ** Tags added: verification-wallaby-done verification-xena-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948507 Title: TypeError when computing QOS feature name To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1948507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958863] Re: [SRU] neutron-l3-agent attempts to use non-existing --config-file=/etc/neutron/fwaas_driver.ini
** Changed in: cloud-archive/wallaby Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958863 Title: [SRU] neutron-l3-agent attempts to use non-existing --config- file=/etc/neutron/fwaas_driver.ini To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1958863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] Re: [SRU] Xena stable releases
Thanks Felipe. These branches have all been merged, pushed and uploaded to the impish unapproved queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] Re: [SRU] Xena stable releases
** Also affects: cinder Importance: Undecided Status: New ** No longer affects: cinder ** Also affects: cinder (Ubuntu) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu) Importance: Undecided Status: New ** Changed in: horizon (Ubuntu) Status: New => Invalid ** Changed in: cinder (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
This bug is going to need SRU details outlined and then the ubuntu-sru team will need to be subscribed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971960 Title: [FTBFS] python-xmlsec fails to build on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-xmlsec/+bug/1971960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
A fixed version of python-xmlsec has been uploaded to the jammy unapproved queue: https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971960 Title: [FTBFS] python-xmlsec fails to build on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-xmlsec/+bug/1971960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970244] Re: [SRU] Enable support for Zed Cloud Archive
This has been successfully verified. root@j1:~# apt policy software-properties-common software-properties-common: Installed: 0.99.22.1 Candidate: 0.99.22.1 Version table: *** 0.99.22.1 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.99.22 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages root@j1:~# apt policy keystone-common root@j1:~# sudo add-apt-repository cloud-archive:zed-proposed --yes ... root@j1:~# sudo add-apt-repository cloud-archive:zed --yes ... root@j1:~# sudo apt install keystone-common --yes ... root@j1:~# apt policy keystone-common keystone-common: Installed: 2:21.0.0+git2022050409.884f88148-0ubuntu1~cloud0 Candidate: 2:21.0.0+git2022050409.884f88148-0ubuntu1~cloud0 Version table: *** 2:21.0.0+git2022050409.884f88148-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-proposed/zed/main amd64 Packages 500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/zed/main amd64 Packages 100 /var/lib/dpkg/status 2:21.0.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970244 Title: [SRU] Enable support for Zed Cloud Archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962582] Re: [SRU] Xena stable releases
I've manually verified horizon 20.1.1 on xena-proposed and have also run regression successfully. == Totals == Ran: 99 tests in 1384.8597 sec. - Passed: 89 - Skipped: 9 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 1 Sum of execute time for each test: 520.1634 sec. ** Tags removed: verification-xena-needed ** Tags added: verification-xena-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962582 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1962582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970244] [NEW] [SRU] Enable support for Zed Cloud Archive
Public bug reported: Please add support for: cloud-archive:zed cloud-archive:zed-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the zed cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:zed sudo add-apt-repository cloud-archive:zed-proposed [Regression potential] Limited - just a data item addition ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Description changed: Please add support for: -cloud-archive:zed -cloud-archive:zed-proposed + cloud-archive:zed + cloud-archive:zed-proposed - This will also need to be SRU'd back to focal. + This will also need to be SRU'd back to jammy. [Impact] - End users have to manually enable the yoga cloud archive pockets. + End users have to manually enable the zed cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:zed sudo add-apt-repository cloud-archive:zed-proposed [Regression potential] Limited - just a data item addition -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970244 Title: [SRU] Enable support for Zed Cloud Archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891238] Re: [RM] neutron-fwaas, vmware-nsx
Steve, let's remove vmware-nsx as well. ** Summary changed: - [RM] neutron-fwaas + [RM] neutron-fwaas, vmware-nsx ** Changed in: vmware-nsx (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891238 Title: [RM] neutron-fwaas, vmware-nsx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networking-odl/+bug/1891238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960319] Re: Missing dependency for neutron-server: openvswitch-common
This bug was fixed in the package neutron - 2:20.0.0-0ubuntu3~cloud0 --- neutron (2:20.0.0-0ubuntu3~cloud0) focal-yoga; urgency=medium . * New update for the Ubuntu Cloud Archive. . neutron (2:20.0.0-0ubuntu3) jammy; urgency=medium . * d/control: Add openvswitch-common dependency to neutron-server binary package (LP: #1960319). ** Changed in: cloud-archive Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960319 Title: Missing dependency for neutron-server: openvswitch-common To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1960319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960319] Re: Missing dependency for neutron-server: openvswitch-common
** Changed in: cloud-archive Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960319 Title: Missing dependency for neutron-server: openvswitch-common To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1960319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960319] Re: Missing dependency for neutron-server: openvswitch-common
** Also affects: cloud-archive Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Triaged ** Changed in: cloud-archive Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960319 Title: Missing dependency for neutron-server: openvswitch-common To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1960319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967895] Re: [SRU] manila stable releases
The manila-ganesha charm is testing with wallaby-proposed in bundles for now to pick up this fix: https://review.opendev.org/c/openstack/charm-manila-ganesha/+/833896 ** Also affects: charm-manila-ganesha Importance: Undecided Status: New ** Changed in: charm-manila-ganesha Status: New => Triaged ** Changed in: charm-manila-ganesha Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967895 Title: [SRU] manila stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1967895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960319] Re: Missing dependency for neutron-server: openvswitch-common
I think I've hit this in a different code-path (see traceback below), but the same solution is required (neutron-common needs openvswitch- common). This change introduced the new call to ovsdb-client: https://review.opendev.org/c/openstack/neutron/+/822299 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource Traceback (most recent call last): 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 426, in __call__ 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource result = fn(*args, **kwargs) 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py", line 1644, in delete_mac_binding_entries_by_mac 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource return processutils.execute(*cmd, 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_concurrency/processutils.py", line 395, in execute 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource obj = subprocess.Popen(cmd, 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/eventlet/green/subprocess.py", line 58, in __init__ 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource subprocess_orig.Popen.__init__(self, args, 0, *argss, **kwds) 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource self._execute_child(args, executable, preexec_fn, close_fds, 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource raise child_exception_type(errno_num, err_msg, err_filename) 2022-04-07 15:52:11.730 69218 ERROR neutron.api.v2.resource FileNotFoundError: [Errno 2] No such file or directory: 'ovsdb-client' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960319 Title: Missing dependency for neutron-server: openvswitch-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1960319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960319] Re: Missing dependency for neutron-server: openvswitch-common
** Changed in: neutron (Ubuntu) Status: New => Triaged ** Changed in: neutron (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960319 Title: Missing dependency for neutron-server: openvswitch-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1960319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967895] Please test proposed package
Hello Corey, or anyone else affected, Accepted manila into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:wallaby-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/wallaby Status: New => Fix Committed ** Tags added: verification-wallaby-needed ** Also affects: charm-manila Importance: Undecided Status: New ** Changed in: charm-manila Status: New => Triaged ** Changed in: charm-manila Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967895 Title: [SRU] manila stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila/+bug/1967895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967895] Re: [SRU] manila stable releases
Uploaded to impish unapproved queue: https://launchpad.net/ubuntu/impish/+queue?queue_state=1_text= ** Also affects: manila (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: manila (Ubuntu) Status: New => Invalid ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967895 Title: [SRU] manila stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1967895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967895] [NEW] [SRU] manila stable releases
Public bug reported: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: * impish/xena: manila 13.0.2 * wallaby: manila 12.1.1 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] ** Affects: manila (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] - This release sports mostly bug-fixes and we would like to make sure all of our - users have access to these improvements. + This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: -* impish/xena: manila 13.0.2 -* wallaby: manila 12.1.1 + * impish/xena: manila 13.0.2 + * wallaby: manila 12.1.1 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates - In order to avoid regression of existing consumers, the OpenStack team will - run their continuous integration test against the packages that are in - -proposed. A successful run of all available tests will be required before the - proposed packages can be let into -updates. + In order to avoid regression of existing consumers, the OpenStack team + will run their continuous integration test against the packages that are + in -proposed. A successful run of all available tests will be required + before the proposed packages can be let into -updates. - The OpenStack team will be in charge of attaching the output summary of the - executed tests. The OpenStack team members will not mark ‘verification-done’ until - this has happened. + The OpenStack team will be in charge of attaching the output summary of + the executed tests. The OpenStack team members will not mark + ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967895 Title: [SRU] manila stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manila/+bug/1967895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory
This bug was fixed in the package libvirt - 8.0.0-1ubuntu6~cloud0
---
libvirt (8.0.0-1ubuntu6~cloud0) focal-yoga; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (8.0.0-1ubuntu6) jammy; urgency=medium
.
* d/control: recommend swtpm-tools (LP: #1948748)
.
libvirt (8.0.0-1ubuntu5) jammy; urgency=medium
.
* apparmor: Fix QEMU access for UEFI variable files. Backported from
upstream master commit 7aec69b7fb9d0c. (Closes: #1006324, LP: #1962035)
Refresh apparmor_profiles_local_include.patch to resolve the conflict.
.
libvirt (8.0.0-1ubuntu4) jammy; urgency=medium
.
* No-change rebuild against libwireshark15.
.
libvirt (8.0.0-1ubuntu3) jammy; urgency=medium
.
* Revert "d/rules, d/libvirt-daemon-system.{postinst,prerm}: never stop
system services and sockets."
Due to the fix being in debhelper we no more need this mitigation now.
(LP: #1959054)
.
libvirt (8.0.0-1ubuntu2) jammy; urgency=medium
.
* No-change rebuild to update maintainer scripts, see LP: 1959054
.
libvirt (8.0.0-1ubuntu1) jammy; urgency=medium
.
* Merge 8.0.0 from Debian unstable (LP: #1946869)
Among many other fixes and improvements this fixes ceph usage
in regard to apparmor (LP: #1588576)
Remaining changes:
- libvirt-uri.sh: Automatically switch default libvirt URI for users
via user profile (xen URI on dom0, qemu:///system otherwise)
[contains lintian fixups of 6.6.0-1ubuntu1]
- Disable libssh2 support (universe dependency)
- d/control: add libzfslinux-dev to build-deps
- d/control: drop libvirt-lxc, vbox and xen drivers to suggest
- d/control: breaks replaces for augeas lenses move in 6.0.0-1
(follows Debian, droppable >22.04)
- debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI
Secure Boot enabled variants of the OVMF firmware and variable store for
the paths where we ship these files in Ubuntu.
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
In addition to just enabling it our solution provides:
+ do not autostart if subnet is already taken (e.g. in guests).
+ iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
the group based access to libvirt functions as it was used in Ubuntu
for quite a long time.
+ d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
+ d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- d/p/u/parallel-shutdown.patch: set parallel shutdown by default.
- Update README.Debian with Ubuntu changes
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- fix autopkgtests (LP 1899180)
+ d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
+ d/t/control: fix smoke-qemu-session by ensuring the service will run
installing libvirt-daemon-system
+ d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
long as the following undefine succeeds
+ d/t/smoke-lxc: use systemd instead of sysV to restart the service
+ d/t/control, d/t/smoke-lxc: retry service restart and skip test if
failing; This was flaky on some release/architectures
+ d/t/smoke-lxc: retry check_domain being flaky on arm64
- dnsmasq related enhancements
[now contains dnsmasq-as-priv-user of 6.6.0-1ubuntu1]
+ run dnsmasq as libvirt-dnsmasq (LP: 1743718)
+ d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
+ d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
on purge
+ d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
libvirt-dnsmasq and adapt the self tests to expect that config
+ d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group
+ Add dnsmasq configuration to work with system wide dnsmasq-base
- d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default
machine type correctly with newer qemu/libvirt
- d/p/ubuntu/lp-1861125-ubuntu-models: recognize Ubuntu models for
(LP 1861125) fixups
- d/p/ubuntu/wait-for-qemu-kvm.patch - avoid hangs on startup (LP 1887592)
- Apparmor Delta that is Ubuntu specific or yet to be upstreamed
split into logical pieces. File names in debian/patches/ubuntu-aa/:
+ 0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
+ 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
libvirt-qemu: Add 9p support
+
[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory
** Changed in: cloud-archive Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927519 Title: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965819] Re: list object has no attribute 'acked'
** Also affects: python-ovsdbapp (Ubuntu) Importance: Undecided Status: New ** Changed in: python-ovsdbapp (Ubuntu) Status: New => Triaged ** Changed in: python-ovsdbapp (Ubuntu) Importance: Undecided => High ** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu) Status: New => Triaged ** Changed in: neutron (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965819 Title: list object has no attribute 'acked' To manage notifications about this bug go to: https://bugs.launchpad.net/networking-ovn/+bug/1965819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953363] Re: [MIR] python-xmlschema, elementpath, importlib-resources
New version of python3-xmlschema is now in jammy-proposed. ** Changed in: python-xmlschema (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953363 Title: [MIR] python-xmlschema, elementpath, importlib-resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elementpath/+bug/1953363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940834] Please test proposed package
Hello lmercl, or anyone else affected, Accepted horizon into ussuri-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:ussuri-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-ussuri-needed to verification-ussuri-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-ussuri-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/ussuri Status: Triaged => Fix Committed ** Tags added: verification-ussuri-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940834 Title: Horizon not show flavor details in instance and resize is not possible - Flavor ID is not supported by nova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
