October 2022 - openstack-discuss - lists.openstack.org

[all][tc] Technical Committee next weekly meeting on 2022 Oct 6 at 1500 UTC
by Ghanshyam Mann 05 Oct '22

05 Oct '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2022 Oct 6, at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Oct 5 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[Keystone][Swift] Using policy.json to prohibit specific API operations by policy?
by Andrew Boring 05 Oct '22

05 Oct '22

Hi all, I'm looking to support a situation where one class of Keystone users in a given domain can create Swift containers (either within a single, dedicated project or within their own projects) but *cannot* change ACLs on those containers, while a second class of users *can* alter ACLs on their own containers. For example, User A is in the first class (defined by role) and can perform all CRUD operations, EXCEPT update pre-defined ACLmetadata on those containers. User B is in the second class and CAN update ACLs on their respecitive containers, like any other standard user. Something like this AWS policy condition ("Granting permissions to multiple accounts with added conditions") is directionally what I'm trying to achieve: https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-polici… Keystone docs imply that I can create policy.json files for all services: "You can define actions for OpenStack service roles in the /etc/PROJECT/policy.yaml files. For example, define actions for Compute service roles in the /etc/nova/policy.yaml file." -https://docs.openstack.org/keystone/yoga/admin/cli-manage-projects-users-and-roles.html But I can't find any indication that Swift actually supports this. So, does Swift support the Oslo policy.json stuff, and if so, is it documented anywhere? Is it simply a "install oslo policy and add it to the pipeline in proxy-server.conf"? If not, is there another/preferred way to achieve the desired restrictions on Swift API operations by policy for a given Keystone domain? Thanks. -- Andrew Boring andrew(a)andrewboring.com

2 1

[tacker] Critical bug report and backport the fix
by Yuta Kazato 05 Oct '22

05 Oct '22

Yasufumi, Ueha, Tacker and Release management team Hi, thanks for your agreements and supports it this issue. We could backport fix patches to stable/zed. I'm glad to release Openstack Zed:) https://releases.openstack.org/zed/ See you next Antelope vPTG! Yuta > Hi Yuta and Yasufumi, > > +1 > > And we have a patch for another critical bug related with pm interface. > The bug report [1] and the fix patch [2] have been already posted. > This patch also requires a backport to stable/zed. > > [1]https://bugs.launchpad.net/tacker/+bug/1990828 > [2]https://review.opendev.org/c/openstack/tacker/+/859377 > > Best Regards, > Ueha > > -----Original Message----- > From: Yasufumi Ogawa <yasufum.o at gmail.com> > Sent: Tuesday, September 27, 2022 10:42 AM > To: openstack-discuss at lists.openstack.org > Subject: Re: [tacker] Critical bug report and backport the fix > > Hi Yuta, > > On 2022/09/26 16:57, Yuta Kazato wrote: > > Hi tacker team, > > > > As you know, new bug report #1990793 [1] related to K8s resource name > > and v2 API is submitted by Masaki. > > The bug will appear if K8s resource name contains `-`. > > > > I think this is a critical issue because users often set resource > > names that contain `-`. > Agree. > > > Fortunately, the fix patch [2] has already been submitted. > > > > I suggest that we should backport the fix patch to the stable/zed > > branch before Zed release. > > What do you think? > We should fix the issue in stable/zed, or this k8s support doesn't work for many usecases. > > Yasufumi > > > > [1] https://bugs.launchpad.net/tacker/+bug/1990793 > > [2] https://review.opendev.org/c/openstack/tacker/+/859206 > > > > Yuta > > -- Yuta Kazato (風戸雄太) NTT Network Innovation Center. tel: +81-422-59-6754 mail:yuta.kazato.nw@hco.ntt.co.jp

1 0

OpenStack Zed is officially released!
by Előd Illés 05 Oct '22

05 Oct '22

Hello OpenStack community, The official OpenStack Zed release announcement has been sent out: http://lists.openstack.org/pipermail/openstack-announce/2022-October/002061… Thanks to all who were a part of the Zed development cycle! This marks the official opening of the openstack/releases repository for 2023.1 Antelope releases, and freezes are now lifted. stable/zed is now a fully normal stable branch, and the normal stable policy applies from now on. Thanks, Előd Illés and the Release Management team

5 4

[release][ironic] Release desired for Ironic bugfix/N branches
by Jay Faulkner 05 Oct '22

05 Oct '22

Hey all, I was attempting to perform a release of all maintained Ironic branches. The long term support branches cut as part of the integrated OpenStack release have been requested via gerrit, as documented ( https://review.opendev.org/c/openstack/releases/+/860125 ). We have intermediate bugfix releases as well, and I was hoping to get patch releases cut from these as well. As far as I can tell, there is no automation for performing these releases, or an official place to request them. If this is wrong; please correct me and I'm happy to go through the proper process. We know that the majority of consumers pull these from git directly; but checking pypi release notes, we had over 6000 downloads of the 21.0.0 and 20.2.0 releases during the 2/4 months of the Zed cycle they had respectively been released, so I do think there's value in releasing these even if it might be a small amount of manual effort. Below is a list of the Ironic projects, and associated bugfix/ branches I'd like to have a patch (bugfix) release cut for: ironic - bugfix/21.0 - bugfix/20.2 - bugfix/19.0 - bugfix/18.1 ironic-inspector - bugfix/11.0 - bugfix/10.12 - bugfix/10.9 - bugfix/10.7 ironic-python-agent - bugfix/9.0 - bugfix/8.6 - bugfix/8.3 - bugfix/8.1 Thanks, Jay Faulkner

5 8

[Swift][Ussuri] Erasure Coding Quarantines
by Reid Guyett 05 Oct '22

05 Oct '22

Hello, I'm not sure if it is related, but I am testing reimaging a node from Ubuntu 18.04 to 20.04 (Cloud Archive Ussuri 2.25.1 to Focal Repo Ussuri 2.25.2) in a 3-node cluster. I have a lot of servers to upgrade, and the environments will be mixed for a while, so I have left this mixed for a week. Now the 18.04 servers are starting to accumulate quarantined EC objects. The 20.04 server has log messages indicating that it is unable to get enough responses from the reconstructor. The 18.04 servers have a couple EC messages. "...liberasurecode[30807]: Invalid fragment header information!" followed by "...object-server: Quarantined object /srv/node/d9/objects-4/10321/b2e/50a3dce515aafc6f222824ec5c7dfb2e/1664002866.33100#8#d.data: Invalid EC metadata at offset 0x0 Is there any thing you can think of that would cause this issue? My steps to reproduce: 1. Create a container in an EC policy 2. Upload object to EC container 3. Wait a bit of time (It looks like the object-server is quarantining but not sure on the trigger) 4. Try to download the file and it will give a 504 Looking at python3-swift dependencies and the package versions I thought may affect this: 20.04 libjerasure2 = 2.0.0+2017.04.10.git.de1739cc84-1 python3-pyeclib = 1.6.0-6build1 python3-xattr = 0.9.6-1.1 18.04 libjerasure2 = 2.0.0+2017.04.10.git.de1739cc84-1 python3-pyeclib = 1.3.1-1ubuntu3 python3-xattr = 0.9.2-0ubuntu1 Thanks! Reid Important Notice: This email is intended to be received only by persons entitled to receive the confidential and legally privileged information it presumptively contains, and this notice constitutes identification as such. Any reading, disclosure, copying, distribution or use of this information by or to someone who is not the intended recipient, is prohibited. If you received this email in error, please notify us immediately at legal(a)kaseya.com, and then delete it. To opt-out of receiving emails Please click here<https://info.kaseya.com/email-subscription-center.html>. The term 'this e-mail' includes any and all attachments.

3 6

Bug Report - 10-05-2022
by Sofia Enriquez 05 Oct '22

05 Oct '22

This is a bug report from 09-28-2022 to 10-05-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1991634 "Toyou drivers report allocated_capacity_gb." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1991217 "[docs] Unsupported option in docs for cinder-manage quota check/sync." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1991154 "[docs] Service tokens documentation is misleading." Fix proposed to master. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[kolla-ansible] How to recover from unfinished upgrade
by wodel youchi 05 Oct '22

05 Oct '22

Hi, I am testing the upgrade from xena to yoga and I made a mistake in globals.yml, I forgot to specify the correct name of gnocchi ceph pool, so my deployment went wrong. I interrupted the deployment Ctrl+C I corrected the mistake, then I restarted the upgrade and it got stuck somewhere else, but I couldn't find where, I interrupted then restarted the deployment again and it got stuck at the same place. My questions : - Is there a way to rollback the upgrade in case of a problem, then start over? - What is the best way to restart a broken upgrade process? Regards.

2 2

[barbican] New team meeting time
by Grzegorz Grasza 05 Oct '22

05 Oct '22

Hi Team, At our last meeting, it was proposed to move the meeting forward 1 hour (an hour early), from 1300 to 1200 UTC. [1] If there are no objections, I'll be making the change by the end of the week, before the next meeting takes place. / Greg [1] https://meetings.opendev.org/meetings/barbican/2022/barbican.2022-10-04-13.…

1 0

[horizon] Cancelling Today's Weekly meeting
by vishal manchanda 04 Oct '22

04 Oct '22

Hello Team, Since there are no agenda items [1] to discuss for today's horizon weekly meeting. Also, Today is a holiday for me. So let's cancel today's weekly meeting. Thanks & regards, Vishal Manchanda(irc:vishalmanchanda) [1] https://etherpad.opendev.org/p/horizon-release-priorities#L38

1 0