- openstack-discuss - lists.openstack.org

[heat][horizon] heat-dashboard-core maintenance
by Akihiro Motoki 09 Jul '22

09 Jul '22

Hi, I added heat-core gerrit group to heat-dashboard-core [1]. Heat team and horizon team agreed to maintain heat-dashboard together a while ago and horizon-core was added to heat-dashboard-core. At that time heat-dashboard had active contributors so head-dashboard-core did not include heat-core team. The active contributors in heat-dashboard-core have gone and Rico is the only person from the heat team, so it is time to add heat-core to heat-dashboard-core. In addition, I would like to drop the following folks from heat-dashboard-core. They were active in heat-dashboard but they had no activities for over three years. If there is no objection, I will drop them next week. - Kazunori Shinohara - Keiichi Hikita - Xinni Ge [1] https://review.opendev.org/admin/groups/8803fcad46b4bce76ed436861474878f36e… Thanks, Akihiro Motoki (amotoki)

1 1

[all][tc] What's happening in Technical Committee: summary 08 July 2022: Reading: 5 min
by Ghanshyam Mann 08 Jul '22

08 Jul '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on 07 July. Most of the meeting discussions are summarized in this email. As it was video meeting, full recording is available @https://www.youtube.com/watch?v=zeJG6Mujalo&t=29s and brief logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-07-07-15.00.log.html * Next TC weekly meeting will be on 14 July Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by 13 July. 2. What we completed this week: ========================= * Nothing specific in this week. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[2], Two are completed and others items are in-progress. Open Reviews ----------------- * Three open reviews for ongoing activities[3]. CentOS-stream-9 testing stability and collaboration with centos-stream maintainers --------------------------------------------------------------------------------------------------- We discussed this topic in the TC meeting and I summarized the discussion in separate ML[4]. Create the Environmental Sustainability SIG --------------------------------------------------- Not much update on this except what we discussed last time, feel free to add your feedback in review[5]. Consistent and Secure Default RBAC ------------------------------------------- We have a good amount of discussion and review in the goal document updates[6] and I have updated the patch by resolving the review comments. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[7]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's the situation again on ML and hope Braden will be ready with their company side permission[8]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[9][10]. Project updates ------------------- * None 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[11]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [12] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/847413 [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029468.ht… [5] https://review.opendev.org/c/openstack/governance-sigs/+/845336 [6] https://review.opendev.org/c/openstack/governance/+/847418 [7] https://review.opendev.org/c/openstack/governance/+/836888 [8] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [9] https://etherpad.opendev.org/p/zuul-config-error-openstack [10] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [11] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [12] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[tc][qa][centos stream] CentOS-stream-9 testing stability and collaboration with CentOS-stream maintainers
by Ghanshyam Mann 08 Jul '22

08 Jul '22

Hello Everyone, As you know, CentOS-stream-9 is in Zed cycle testing runtime and we are facing some stability issues to make its testing voting (detach volume, qemu issues are some known ones). Currently, it is a non-voting job which is not good for the long term as non-voting job failures are mostly ignored. We called CentOS stream folks to discuss how to make it stable testing or a better way to improve the communication between both communities as well as coordinated debugging. Alan, Brian, and Aleksandra from the CentOS stream team joined the TC call on 7 July. With the CentOS stream model of having the latest packages version like libvirt etc it is good to test and capture the potential issues in advance but at the same time, there will more failure than other distros like ubuntu etc. Knowing the failure in the early stage is good but we have a few challenges to triage such failure. OpenStack or CentOS team alone might not be able to know the root cause of the issue at first glance, whether it is in OpenStack component or in CentOS stream. CentOS team has less experience in debugging devstack or tempest tests. And if such failures are more frequent (current case) then having it as a voting testing on every patch is another challenge for OpenStack smooth development cycle. We could not find any best solution to solve all these challenges but we all agree that we need some coordinated debugging. We need some of the initial level of failure debugging in OpenStack and pass the information to CentOS team for further debugging. That is one possible step forward and we will see how it goes. Basically doing the following : * If OpenStack members see failure in CentOS stream then do some initial level of debugging to know which OpenStack component is failing and collect some log information. * Report the bug with all those information at https://bugzilla.redhat.com/ * Contact CenntOS Stream team (you can address/ping Alan, Brian or Aleksandra ) via ** ML: https://lists.centos.org/mailman/listinfo/centos-devel ** IRC channel on Libera chat #centos-devel and #centos-stream Alan, Brian, Aleksandra, or any TC members feel free to add the things if I missed something. -gmann

1 0

[all][tc][gerrit] Ownership of *-stable-maint groups
by Stephen Finucane 08 Jul '22

08 Jul '22

tl;dr: Who should be able project-specific stable-maint groups on Gerrit: members of the projects-specific stable-maint group itself or members of stable- maint-core? A recent discussion on #openstack-sdks highlighted some discrepancies in the ownership of various project-specific "stable-maint" groups on Gerrit. As a reminder, any project that specifies "stable:follows-policy" is required to follow the stable branch policy (suprise!). This is documented rather well at [1]. We expect people who have the ability to merge patches to stable branches to understand and apply this policy. Initially the only people that could do this were peopled added to a central Gerrit group called "stable-maint-core" group, however, in recent years this responsibility has been devolved to the projects themselves. Each project with a stable branch now has a project- specific stable maintenance Gerrit group called PROJECTNAME-stable-maint (e.g. nova-stable-maint [2]. The issue here is who should *own* these groups. The owner of a Gerrit group is the only one that's able to modify it. In general, the owner of a Gerrit group is the group itself so for example the owner of python-openstackclient-core is python-openstackclient-core [3]. This means that if you're a member of the group then you can add or remove members, rename the group, set a description etc. However, _most_ PROJECTNAmE-stable-maint groups are owned by the old 'stable- maint-core' group, meaning only members of this global group can modify the project-specific groups. I say _most_ because this isn't applied across the board. The following projects are owned by 'stable-maint-core': * barbican-stable-maint * ceilometer-stable-maint * cinder-stable-maint * designate-stable-maint * glance-stable-maint * heat-stable-maint * horizon-stable-maint * ironic-stable-maint * keystone-stable-maint * manila-stable-maint * neutron-stable-maint * nova-stable-maint * oslo-stable-maint * python-openstackclient-stable-maint * sahara-stable-maint * swift-stable-maint * trove-stable-maint * zaqar-stable-maint However, the following stable groups "own themselves": * ansible-collections-openstack-stable-maint * aodh-stable-maint * congress-stable-maint * freezer-stable-maint * karbor-stable-maint * mistral-stable-maint * neutron-dynamic-routing-stable-maint * neutron-lib-stable-maint * neutron-vpnaas-stable-maint * octavia-stable-maint * openstacksdk-stable-maint * oslo-vmware-stable-maint * ovn-octavia-provider-stable-maint * panko-stable-maint * placement-stable-maint * sahara-dashboard-stable-maint * senlin-dashboard-stable-maint * senlin-stable-maint * telemetry-stable-maint This brings me to my question (finally!): do we want to resolve this discrepancy, and if so, how? Personally, I would lean towards delegating this entirely to the projects but I don't know if this requires TC involvement to do. If we want to insist on the stable-maint group owning all PROJECT-stable-maint branches then we have a lot of cleanup to do! Cheers, Stephen PS: This might be a good moment to do a cleanup of members of various stable branches that have since moved on... [1] https://docs.openstack.org/project-team-guide/stable-branches.html [2] https://review.opendev.org/admin/groups/21ce6c287ea33809980b2dec53915b07830… [3] https://review.opendev.org/admin/groups/aa0f197fcfbd4fcebeff921567ed3b48cd3…

4 6

[TripleO] PTL outage
by James Slagle 08 Jul '22

08 Jul '22

Hello TripleO, I'll be out on PTO for the next 2 weeks. Not that I'm typically needed :), but If anything urgent requires attention, please reach out to the kind folks directly in #tripleo. -- -- James Slagle --

1 0

[release] Release countdown for week R-12, Jul 11 - 15
by Előd Illés 08 Jul '22

08 Jul '22

Development Focus ----------------- The Zed-2 milestone is next week, on July 14th, 2022! Zed-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/zed/schedule.html for details. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library that has not been otherwise released since milestone 1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. Next week is also the deadline to freeze the contents of the final release. All new 'Zed' deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables and need to have done a release by milestone-2. Changes proposing those deliverables for inclusion in Zed have been posted, please update them with an actual release request before the milestone-2 deadline if you plan on including that deliverable in Zed, or -1 if you need one more cycle to be ready. Upcoming Deadlines & Dates -------------------------- Zed-2 Milestone: July 14th, 2022 Next PTG: October 17-20, 2022 (Columbus, Ohio) Előd Illés irc: elodilles

1 0

[cinder] Spec Freeze Exception Request
by Gorka Eguileor 08 Jul '22

08 Jul '22

Hi, I would like to request a spec freeze exception for the new Cinder Quota System spec [1]. Analysis of the required spec changes needed to implement the second quota driver, as agreed in the PTG/mid-cycle, were non trivial. In the latest spec update I just pushed there are considerable changes: - General improvements to existing sections to increase readability. - Description of the additional driver and reasons why we decided to implement it. - Spell out through the entire spec the similarities and differences of both drivers. - Change in tracking of the reservations to accommodate the new driver. - Description on how switching from one driver to the other would work. - Updated the driver interface to accommodate the particularities of the new driver. - Updated the performance section with a very brief summary of the performance tests done with some code prototipe. - Updating the phases of the effort as well as the work items. Cheers, Gorka. [1]: https://review.opendev.org/c/openstack/cinder-specs/+/819693

2 2

[neutron] CI meeting on Tuesday 12.07.2022 cancelled
by Slawek Kaplonski 08 Jul '22

08 Jul '22

Hi, I will be on PTO next week. As there is nothing really critical to our CI currently, lets cancel next week's meeting. See You on CI meeting on Tuesday 19th of July. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[baremetal-sig][ironic] Tue July 12, 2022, 2pm UTC: "Bare metal Kubernetes at G-Research"
by Arne Wiebalck 08 Jul '22

08 Jul '22

Dear all, The Bare Metal SIG will meet next week on Tue July 12, 2022, 2pm UTC featuring a topic of the day presentation by Scott Solkhon & Jamie Poole: "Bare metal Kubernetes at G-Research" Everyone is welcome, all details on how to join can be found on the SIG's etherpad: https://etherpad.opendev.org/p/bare-metal-sig Hope to see you there! Arne -- Arne Wiebalck CERN IT

1 0

[nova][neutron] do not recheck failing nova-next or nova-ovs-hybird-plug failures.
by Sean Mooney 08 Jul '22

08 Jul '22

hi o/ it looks like neutron recently moved linuxbridge to be experimental Jul 06 16:21:46.640517 ubuntu-focal-rax-ord-0030301377 neutron-server[90491]: ERROR neutron.common.experimental [-] Feature 'linuxbridge' is experimental and has to be explicitly enabled in 'cfg.CONF.experimental' we do not actully deploy it in nova-next or nova-ovs-hybrid-plug but it is enabeld in our job config as one of the configured mech drivers even if we dont install the agent. i have not looked up what change in neutron change this yet but im going to propose a patch to nova to disable it and i likely need to fix os-vif too so if you see a post fialure in either the nova-next of novs hybrid plug jobs (and or look into it and see " die 2385 'Neutron did not start'" in the Run devstack task summery that is why this is failing. ill update this thread once we have fixed the issue.

2 3

Cluster management tool for Openstack
by KK CHN 08 Jul '22

08 Jul '22

List, 1. Is there any specific tool or project component available to maintain multiple OpenStack Clusters 2. Is there any concept of Supervisory cluster ? Regards, Krish

1 0

Nova-conductor is having trouble with AMQP authentication
by Airamek 08 Jul '22

08 Jul '22

Hello everyone! I've installed OpenStack Ussuri on my home servers (one controller and one compute node, both running OpenSuse Leap 15.3) based on the instructions in the docs(https://docs.openstack.org/install-guide/openstack-services.html#minim… Everything works until I launch an instance in Horizon. The instance gets stuck on "Scheduling". Looking trough the logs I've came across nova-conductor.log(on the controller), which contained the following error log(full log in the attachments): 2022-07-08 00:48:08.846 25886 ERROR oslo_messaging.rpc.server [req-eb225ffd-9b12-4e80-987b-34f0317082c6 741cb0b6280cb6fbedf1d8c6df4fc854b3e177e331441e019b961839089154d6 9b41f3e228984401a7642f94cd47dc73 - 4596c7f3b97740b3adfa8f82b6240654 4596c7f3b97740b3adfa8f82b6240654] Exception during message handling: amqp.exceptions.AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN. For details see the broker logfile. I'm 100% sure my RabbitMQ username and password are set correctly in nova.conf. I've included my nova.conf too, with the passwords removed. I would be really thankful, if someone could point me in the right direction! P.S: Please excuse me for any grammatical or spelling mistakes, English is not my first language.

1 0

[neutron] Drivers meeting agenda - 08.07.2022.
by Lajos Katona 08 Jul '22

08 Jul '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * [RFE] Adding the "rekey" parameter to the api for strongswan like "dpd_action" (#link https://bugs.launchpad.net/neutron/+bug/1979044) * [RFE] Firewall Group Ordering on Port Association (#link https://bugs.launchpad.net/neutron/+bug/1979816) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[tc] Reminder: August 2022 OpenInfra Board Sync
by Jeremy Stanley 07 Jul '22

07 Jul '22

If you're interested in participating in an informal discussion between the OpenStack TC, OpenInfra board members, and other interested community collaborators, don't forget to mark your preferred dates and times by Friday, 2022-07-15, so that I can let the board members know what our collective availability looks like: https://framadate.org/atdFRM8YeUtauSgC If you don't know what this is about, see my earlier post for details (I intentionally avoided replying to it in order to increase visibility for the reminder): https://lists.openstack.org/pipermail/openstack-discuss/2022-June/029352.ht… -- Jeremy Stanley

1 0

[manila] Stepping down from manila core
by Rodrigo Barbieri 07 Jul '22

07 Jul '22

Hello fellow zorillas, It has been a long time since I started to hope every day I'd able to dedicate more time to manila core activities and so far that hasn't happened and I don't see it happening in the near foreseeable future. I had been following the meetings notes weekly until ~2 months ago but I recently ended up dropping those as well. Therefore I am stepping down from the manila core role. I would like to thank everyone that I worked closely with from 2014 to 2019 on this project. I hold this project and all of you dear to my heart and I am extremely glad and grateful to have worked with you and met you on summits/PTGs, as the life memories around Manila are among the best I have from that period. If someday circumstances change, the manila project and its community will be ones I will be very happy to go back to working closely with again. Kind regards, -- Rodrigo Barbieri MSc Computer Scientist

3 2

Openstack instance is unreachable
by GEORGIOS PAPATHANAIL 07 Jul '22

07 Jul '22

I am facing the following issue with my new Openstack installation. The installation is a little bit weird and to elaborate more, I have a controller and a compute node running as VMs in XenServer. The compute node has nested virtualization enabled and uses qemu in order to provision VMs. I have a provider flat network that has a public range of IPs and VMs use this network. I am able to create instances and access them via console, but I can't ping them or ssh even if they have public IPs. I am not very familiar with Xen Server, is there any configuration that is needed (bridges, promisc mode, etc)? -- *George Papathanail* *Associate Researcher* *Department of Applied Informatics* *University of Macedonia*

3 5

Poor I/O performance on OpenStack block device (OpenStack Centos8:Ussuri)
by Vinh Nguyen Duc 07 Jul '22

07 Jul '22

I have a problem with I/O performance on Openstack block device HDD. *Environment:**Openstack version: Ussuri* - OS: CentOS8 - Kernel: 4.18.0-240.15.1.el8_3.x86_64 - KVM: qemu-kvm-5.1.0-20.el8 *CEPH version: Octopus * *15.2.8-0.el8.x84_64* - OS: CentOS8 - Kernel: 4.18.0-240.15.1.el8_3.x86_64 In CEPH Cluster we have 2 class: - Bluestore - HDD (only for cinder volume) - SSD (images, cinder volume) *Hardware:* - Ceph-client: 2x10Gbps (bond) MTU 9000 - Ceph-replicate: 2x10Gbps (bond) MTU 9000 *VM:* - Swapoff - non LVM *Issue*When create VM on Openstack using cinder volume HDD, have really poor performance: 60-85 MB/s writes. And when tests with ioping have high latency. *Diagnostic* 1. I have checked the performance between Compute Host (Openstack) and CEPH, and created an RBD (HDD class) mounted on Compute Host. And the performance is 300-400 MB/s. => So i think the problem is in the hypervisor But when I check performance on VM using cinder Volume SSD, the result equals performance when test RBD (SSD) mounted on a Compute host. 2. I already have to configure disk_cachemodes="network=writeback"(and enable rbd cache client) or test with disk_cachemodes="none" but nothing different. 3. Push iperf3 from compute host to random ceph host still has 20Gb traffic. 4. Compute Host and CEPH host connected to the same switch (layer2). Where else can I look for issues? Please help me in this case. Thank you.

3 4

[large-scale][cinder] backend_native_threads_pool_size option with rbd backend
by Arnaud Morin 07 Jul '22

07 Jul '22

Hey all, Is there any recommendation on the number of threads to use when using RBD backend (option backend_native_threads_pool_size)? The doc is saying that 20 is the default but it should be increased, specially for the RBD driver, but up to which value? Is there anyone tuning this parameter in their openstack deployments? If yes, maybe we can add some recommendations on openstack large-scale doc about it? Cheers, Arnaud.

4 6

[all][TC] Bare rechecks stats update
by Slawek Kaplonski 07 Jul '22

07 Jul '22

Hi, New stats from last 7 days about bare rechecks in each team are available in [1]: +--------------------+---------------+--------------+-------------------+ | Team | Bare rechecks | All Rechecks | Bare rechecks [%] | +--------------------+---------------+--------------+-------------------+ | skyline | 1 | 1 | 100.0 | | OpenStack Charms | 10 | 10 | 100.0 | | kolla | 92 | 92 | 100.0 (was 76.19%)| | sahara | 21 | 21 | 100.0 | | tacker | 5 | 5 | 100.0 | | keystone | 17 | 17 | 100.0 | | OpenStack-Helm | 15 | 15 | 100.0 (was 70%) | | rally | 1 | 1 | 100.0 | | barbican | 2 | 2 | 100.0 | | Telemetry | 3 | 3 | 100.0 | | ec2-api | 5 | 5 | 100.0 | | zun | 2 | 2 | 100.0 | | kuryr | 30 | 32 | 93.75 (was 92.5%) | | cinder | 89 | 102 | 87.25 (was 81.33%)| | Puppet OpenStack | 13 | 15 | 86.67 (was 85.29%)| | horizon | 17 | 20 | 85.0 (was 100%) | | Quality Assurance | 26 | 32 | 81.25 (was 64.44%)| | manila | 70 | 89 | 78.65 (was 74%) | | ironic | 77 | 101 | 76.24 (was 79.66%)| | tripleo | 230 | 318 | 72.33 (was 87.19%)| | swift | 5 | 7 | 71.43 (was 75%) | | glance | 8 | 12 | 66.67 (was 50%) | | designate | 9 | 14 | 64.29 (was 64.71%)| | nova | 10 | 18 | 55.56 (was 84.21%)| | octavia | 6 | 11 | 54.55 (was 16.67%)| | OpenStackSDK | 13 | 25 | 52.0 (was 74.19%) | | neutron | 26 | 54 | 48.15 (was 73.68%)| | heat | 3 | 8 | 37.5 (was 25%) | | requirements | 1 | 3 | 33.33 (was 87.5) | | oslo | 1 | 3 | 33.33 (was 0%) | | Release Management | 0 | 2 | 0.0 | | OpenStackAnsible | 0 | 34 | 0.0 (was 13.64%) | +--------------------+---------------+--------------+-------------------+ There are some teams which made progress since last check (especially *OpenStackAnsible* which had all rechecks done with given some comment at least - thx a lot for that :)) [1] https://etherpad.opendev.org/p/recheck-weekly-summary[1] -- Slawek Kaplonski Principal Software Engineer Red Hat -------- [1] https://etherpad.opendev.org/p/recheck-weekly-summary

1 0

[all][tc] Technical Committee next weekly meeting on 7 July 2022 at 1500 UTC
by Ghanshyam Mann 07 Jul '22

07 Jul '22

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

1 1

openstackclient: booting from image-created volume w/ delete_on_termination
by Kurt Garloff 07 Jul '22

07 Jul '22

Hi openstack CLI wizards, Having flavors without disks, I want volumes to be created from images on the fly that I can boot from. But I don't want to do bookkeeping for these volumes; they should disappear once the server disappears. On the command line with nova, I can do this: nova boot --nic net-name=$MYNET --key-name $MYKEY --flavor $MYFLAVOR \ --block-device "id=$MYIMGIFD,source=image,dest=volume,size=$MYSIZE,shutdown=remove,bootindex=0" $MYNAME I did not find a way to do this with openstack server create. Is there one? Here's what I tried: --image $MYIMGID --boot-from-volume $MYSIZE works, except that there is no way to specify delete_on_termination --block-device-mapping "sda=$MYIMGID:image:$MYSIZE:true" does complain that no --image or --volume have been passed. The option does not appear to be used for bootable volumes. I have seen a BP (merged with Ussuri) that would allow a PUT call to update delete_on_termination, but I don't see it usable with the openstackclient ... https://specs.openstack.org/openstack/nova-specs/specs/ussuri/implemented/d… Anything obvious I missed? Thanks, -- Kurt Garloff <kurt(a)garloff.de> Cologne, Germany

2 2

Re: Regarding Policy.json entries for glance image update not working for a user
by Adivya Singh 07 Jul '22

07 Jul '22

Hi Brian, Please find the response > 1> i am using Xena release version 24.0.1 > > Now the scenario is line below, my customer wants to have their login > access on setting up the properties of an image to the public. now what i > did is > > 1> i created a role in openstack using the admin credential name as "user" > 2> i assigned that user to a role user. > 3> i assigned those user to those project id, which they want to access as > a user role > > Then i went to Glance container which is controller by lxc and made a > policy.yaml file as below > > root@aio1-glance-container-724aa778:/etc/glance# cat policy.yaml > > "modify_image": "role:user" > > then i went to utility container and try to set the properties of a image > using openstack command > > openstack image set --public <image id> > > and then i got this error > > HTTP 403 Forbidden: You are not authorized to complete publicize_image > action. > > Even when i am trying the upload image with this user , i get the above > error only > > export OS_ENDPOINT_TYPE=internalURL > export OS_INTERFACE=internalURL > export OS_USERNAME=adsingh > export OS_PASSWORD='adsingh' > export OS_PROJECT_NAME=adsingh > export OS_TENANT_NAME=adsingh > export OS_AUTH_TYPE=password > export OS_AUTH_URL=https://<Internal IP of horizon>:5000/v3 > export OS_NO_CACHE=1 > export OS_USER_DOMAIN_NAME=Default > export OS_PROJECT_DOMAIN_NAME=Default > export OS_REGION_NAME=RegionOne > > Regards > Adivya Singh > > > > > On Mon, Jun 13, 2022 at 6:41 PM Alan Bishop <abishop(a)redhat.com> wrote: > >> >> >> On Mon, Jun 13, 2022 at 6:00 AM Brian Rosmaita < >> rosmaita.fossdev(a)gmail.com> wrote: >> >>> On 6/13/22 8:29 AM, Adivya Singh wrote: >>> > hi Team, >>> > >>> > Any thoughts on this >>> >>> H Adivya, >>> >>> Please supply some more information, for example: >>> >>> - which openstack release you are using >>> - the full API request you are making to modify the image >>> - the full API response you receive >>> - whether the user with "role:user" is in the same project that owns the >>> image >>> - debug level log extract for this call if you have it >>> - anything else that could be relevant, for example, have you modified >>> any other policies, and if so, what values are you using now? >>> >> >> Also bear in mind that the default policy_file name is "policy.yaml" (not >> .json). You either >> need to provide a policy.yaml file, or override the policy_file setting >> if you really want to >> use policy.json. >> >> Alan >> >> cheers, >>> brian >>> >>> > >>> > Regards >>> > Adivya Singh >>> > >>> > On Sat, Jun 11, 2022 at 12:40 AM Adivya Singh <adivya1.singh(a)gmail.com >>> > <mailto:adivya1.singh@gmail.com>> wrote: >>> > >>> > Hi Team, >>> > >>> > I have a use case where I have to give a user restriction on >>> > updating the image properties as a member. >>> > >>> > I have created a policy Json file and give the modify_image rule to >>> > the particular role, but still it is not working >>> > >>> > "modify_image": "role:user", This role is created in OpenStack. >>> > >>> > but still it is failing while updating properties with a >>> > particular user assigned to a role as "access denied" and >>> > unauthorized access >>> > >>> > Regards >>> > Adivya Singh >>> > >>> >>> >>>

3 5

[largescale-sig] Next meeting: July 6th, 15utc
by Thierry Carrez 06 Jul '22

06 Jul '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC, before taking a break for July and most of August. You can check how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220706T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[Octavia] Proposing Tom Weininger as core reviewer
by Gregory Thiemonge 06 Jul '22

06 Jul '22

Hi Folks, I would like to propose Tom Weininger as a core reviewer for the Octavia project. Since he joined the project, Tom has been a major contributor to Octavia, and he is an excellent reviewer. Please send your feedback in this thread, if there is no objection until next week, we will add him to the list of core reviewers. Thanks Gregory

4 4

[cinder] Bug deputy report for week of 07-06-2022
by Sofia Enriquez 06 Jul '22

06 Jul '22

This is a bug report from 06-29-2022 to 07-06-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1980268 "creating a bootable volume fails async when vol_size < virtual_size of image." Fix proposed to master. Cheers, Sofia -- 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

Re: Problem while launching an instance directly from an image "Volume did not finish being created even after we waited 203 seconds or 61 attempts"
by A Monster 06 Jul '22

06 Jul '22

Hello, I talking about launching instance from persistent volume ( cinder ), I've checked cinder logs but I've found no errors, the only error I could find is in nova compute log which says Build of instance 4cf01ba2-05b3-44e9-a685-8875d8c96b4e aborted: Volume 01739e82-9e66-41f7-be74-dfbbdcd6746e did not finish being created even after we waited 203 seconds or 61 attempts. And its status is creating. I am using openstack xena deployed with kolla ansible on centos 8 stream.

1 0

QoS Cinder, Zed Release
by Sergey Drozdov 06 Jul '22

06 Jul '22

To whom it may concern, I am helping a colleague of mine with the following pieces of work: 820027 (https://review.opendev.org/c/openstack/cinder/+/820027 <https://review.opendev.org/c/openstack/cinder/+/820027>), 820030 (https://review.opendev.org/c/openstack/cinder-specs/+/820030 <https://review.opendev.org/c/openstack/cinder-specs/+/820030>). I was wondering whether it is not too late to include the aforementioned within the Zed release? Is there anyone who can advise on this matter? Best Regards, Sergey

3 2

October 2022 PTG Dates & Registration
by Kendall Nelson 06 Jul '22

06 Jul '22

Hello Everyone! As you may have seen, we announced the next PTG[1] which will take place October 17-20, 2022 in Columbus, Ohio! Registration is now open[2]. We have also secured a limited, discounted hotel block for PTG attendees [3]. If your organization is interested in sponsoring the event, information on packages and pricing are now available on the PTG website [1] or feel free to reach out directly to ptg(a)openinfra.dev. Can't wait to SEE you all there! -Kendall Nelson (diablo_rojo) [1] https://openinfra.dev/ptg/ [2] https://openinfra-ptg.eventbrite.com/ [3] https://www.hyatt.com/en-US/group-booking/CMHRC/G-L0RT

1 0

Listing instances that use a security group
by Derek O keeffe 05 Jul '22

05 Jul '22

Hi all, Is there a cli command to list all the VM's that have a specific security group attached, I need to delete some groups as a tidy up but I only get a warning that it's in use by an instance (of which there's 200) so I'd rather not go through them 1 by 1 in Horizon or show each one on the cli separately. An sql query would be acceptable also but nova db, select * from security_groups; select * from instances; & select * from security_group_instance_association; doesn't give me the required results that I can refine to search deeper. Thanks in advance for any info. Regards,Derek

2 2

Re: Issues With trove guest agent
by Hirotaka Wakabayashi 05 Jul '22

05 Jul '22

Hello, Hernando! I think Trove calls nova to inject files here: https://opendev.org/openstack/trove/src/branch/master/trove/taskmanager/mod… When cloud-init fails to inject Trove's configuration files, I think you should check the following parameters. 1. `use_nova_server_config_drive` configuration on trove.conf. This value should be True if you use config_drive to inject files. 2. `DIB_CLOUD_INIT_DATASOURCES` environment when buiding your own image. This value should contains `OpenStack` if you set `use_nova_server_config_drive` as False. and I think you should also check cloud-init log using journalctl. Thanks, Hirotaka On Tuesday, June 28, 2022, 09:55:24 PM GMT+9, <openstack-discuss-request(a)lists.openstack.org> wrote: Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: Regarding Floating IP is existing Setup (Adivya Singh) 2. Issues With trove guest agent (Hernando Ariza Perez) 3. Openstack keystone LDAP integration | openstack user list --domain domain.com | Internal server error (HTTP 500) (Swogat Pradhan) ---------------------------------------------------------------------- Message: 1 Date: Tue, 28 Jun 2022 18:12:51 +0530 From: Adivya Singh <adivya1.singh(a)gmail.com> To: Slawek Kaplonski <skaplons(a)redhat.com>, OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Subject: Re: Regarding Floating IP is existing Setup Message-ID: <CA+ykd61rKBam86Avut-7g+8EOS4snnzgTmMu5GvAETR3p5EuPg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" hi Slawek, it happens with a given router namespace at a time Regards Adivya Singh On Fri, Jun 24, 2022 at 10:13 PM Adivya Singh <adivya1.singh(a)gmail.com> wrote: > Hi, > > Thanks for the advice and the link, > > What i saw when i do testing using tcpdump was "ARP" was not working, and > it is not able to associate the FLoating IP with the MAC address of the > interface in the VM, When i do the associate and disassociate the VM , it > works fine > > But the Router NameSpace got changed. > > Regards > Adivya Singh > > On Thu, Jun 23, 2022 at 1:22 PM Slawek Kaplonski <skaplons(a)redhat.com> > wrote: > >> Hi, >> >> Dnia wtorek, 21 czerwca 2022 13:55:51 CEST Adivya Singh pisze: >> > hi Eugen, >> > >> > The current setup is 3 controller nodes, The Load is not much on each >> > controller and the number of DHCP agent is always set to 2 as per the >> > standard in the neutron.conf, The L3 agent seems to be stables as other >> > router namespace works fine under it, Only few router Namespace get >> > affected under the agent. >> >> Is it that problem happens for new floating IPs or for the FIPs which >> were working fine and then suddenly stopped working? If the latter, was >> there any action which triggered the issue to happen? >> Is there e.g. only one FIP broken in the router or maybe when it happens, >> then all FIPs which uses same router are broken? >> >> Can You also try to analyze with e.g. tcpdump where traffic is dropped >> exactly? You can check >> http://kaplonski.pl/blog/neutron-where-is-my-packet-2/ for some more >> detailed description how traffic should go from the external network to >> Your instance. >> >> > >> > Most of the template having issue , Have all instance having FLoating >> IP, a >> > Stack with a single floating IP have chance of issue very less >> > >> > Regards >> > Adivya Singh >> > >> > On Tue, Jun 21, 2022 at 1:18 PM Eugen Block <eblock(a)nde.ag> wrote: >> > >> > > Hi, >> > > >> > > this sounds very familiar to me, I had to deal with something similar >> > > a couple of times in a heavily used cluster with 2 control nodes. What >> > > does your setup look like, is it a HA setup? I would start checking >> > > the DHCP and L3 agents. After increasing dhcp_agents_per_network to 2 >> > > in neutron.conf and restarting the services this didn't occur again >> > > (yet). This would impact floating IPs as well, sometimes I had to >> > > disable and enable the affected router(s). If you only have one >> > > control node a different approach is necessary. Do you see a high load >> > > on the control node? >> > > >> > > >> > > Zitat von Adivya Singh <adivya1.singh(a)gmail.com>: >> > > >> > > > hi Team, >> > > > >> > > > We got a issue in Xena release, where we set the environment in >> Ubuntu >> > > > Platform, But later we get some issues in Floating IP not reachable. >> > > > >> > > > In a Network node, not all router namespace are Impacted and only >> few of >> > > > them get affected, So we can not comment Network node has a issue. >> > > > >> > > > The L3 agent where the Router is tied up, Worked just fine, as other >> > > > routers work Fine. >> > > > >> > > > and the one having issue in Floating IP, if i unassigned and >> assigned it >> > > > starts working most of the time. >> > > > >> > > > Any thoughts on this >> > > > >> > > > Regards >> > > > Adivya Singh >> > > >> > > >> > > >> > > >> > > >> > >> >> >> -- >> Slawek Kaplonski >> Principal Software Engineer >> Red Hat > >

1 0

import external compute
by Parsa Aminian 05 Jul '22

05 Jul '22

hello is there any way that i can import an already existing kolla-ansible compute to my openstack ? migrating instances manually take a lot of time from me

2 1

Ironic pxe tftp service failed | Tripleo wallaby
by Swogat Pradhan 05 Jul '22

05 Jul '22

Hi, I am trying to setup openstack wallaby using the repo : centos-release-openstack-wallaby on top of centos 8 stream. I have deployed undercloud but the service ironic_pxe_tftp is not starting up. Previously the undercloud was failing but now the undercloud is deployed successfully but the service is not coming up. Error log from ironic_pxe_tftp: [root@undercloud ~]# podman logs 23427d845098 /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory /bin/bash: /usr/sbin/in.tftpd: No such file or directory My undercloud config: [DEFAULT] undercloud_hostname = undercloud.taashee.com container_images_file = containers-prepare-parameter.yaml local_ip = 192.168.30.50/24 undercloud_public_host = 192.168.30.39 undercloud_admin_host = 192.168.30.41 undercloud_nameservers = 8.8.8.8 pxe_enabled = true #undercloud_ntp_servers = overcloud_domain_name = taashee.com subnets = ctlplane-subnet local_subnet = ctlplane-subnet #undercloud_service_certificate = generate_service_certificate = true certificate_generation_ca = local local_interface = eno3 inspection_extras = false undercloud_debug = false enable_tempest = false enable_ui = false [auth] [ctlplane-subnet] cidr = 192.168.30.0/24 dhcp_start = 192.168.30.60 dhcp_end = 192.168.30.100 inspection_iprange = 192.168.30.110,192.168.30.150 gateway = 192.168.30.1 With regards, Swogat Pradhan

4 9

[all][tc][policy][operator] RBAC discussion policy pop-up next meeting: Tuesday 5 July (biweekly meeting)
by Ghanshyam Mann 05 Jul '22

05 Jul '22

Hello Everyone, RBAC policy popup next meeting is schedule tomorrow on 5th July at 14:00 UTC Meeting details: https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… Feel free to add the topic you would to discuss in this etherpad: https://etherpad.opendev.org/p/rbac-zed-ptg#L213 -gmann

1 0

A centralized list of usable vs unusable projects?
by Vince Mulhollon 04 Jul '22

04 Jul '22

Hi, Can anyone point me to a status board or other format identifying which projects are uninstallable or unusable perhaps organized by release? Specifically for Yoga on Kolla-Ansible although "in general" would also be useful. I have a test cluster, and I'm exercising Yoga using Ubuntu hosts and Kolla-Ansible, and the online docs imply every project is up and installable and usable. However, from my notes so far: "everyone knows" Freezer hasn't been installable for many years and requires an ElasticSearch version from last decade (Every project that uses ElasticSearch needs a different and incompatible version of ES, honestly just in general, that's not just an OpenStack phenomena), Murano has been uninstallable for years AND hard crashes all of Horizon if you try to install it, Monasca has been uninstallable for around a year, as near as I can tell, due to a crash loop in the log persister, every Watcher container crash loops for no apparent reason after every Kolla-Ansible installation, although I recently hand installed Watcher on a separate Yoga cluster and it "worked" or at least didn't crash loop, I will research this in more detail and add/update issues and storyboards. The docs claim Magnum works great with Docker Swarm and I have a specific enduser application for Swarm so I set up Magnum successfully, then learned "everyone knows" that Magnum doesn't actually work for Docker Swarm, so I was very annoyed at that. I haven't even tried Ceilometer-and-related on Yoga, although if Monasca is dead maybe I should add it to the testing plan. The vast majority of projects do "just work" which is super awesome of course. My point is, I can't find a status board type of page, or any sort of centralized list, it seems like it would be incredibly useful, so I'm making my own list of what works, and what does not work, for my own use, and I'd feel silly if there's already some service or page or dashboard implementing this effort that I couldn't find. I'd certainly contribute data toward such a status page, as I'm running tests on my test cluster anyway, may as well share the results. Thanks!

2 1

[nova][placement] Spec review day tomorrow
by Sylvain Bauza 04 Jul '22

04 Jul '22

Hey members, Just a reminder we'll have a nova/placement spec review day happening on tomorrow July 5th. Sharpen your pens and prepare your specs for review, it would be greatly appreciated. -Sylvain

1 0

[glance][ops] [nova] Disabling an image
by Massimo Sgaravatto 04 Jul '22

04 Jul '22

Dear all What is the blessed method to avoid using an image for new virtual machines without causing problems for existing instances using that image ? If I deactivate the image, I then have problems resizing instances using that image [*]: it claims that image download is forbidden since the image was deactivated Thanks, Massimo [*] | fault | {'code': 500, 'created': '2022-06-30T07:57:30Z', 'message': 'Not authorized for image dd1492d5-17a2-4dc2-a4e3-ec6c99255e4b.', 'details': 'Traceback (most recent call last):\n File "/usr/lib/python3.6/site-packages/nova/image/glance.py", line 377, in download\n context, 2, \'data\', args=(image_id,))\n File "/usr/lib/python3.6/site-packages/nova/image/glance.py", line 191, in call\n result = getattr(controller, method)(*args, **kwargs)\n File "/usr/lib/python3.6/site-packages/glanceclient/common/utils.py", line 670, in inner\n return RequestIdProxy(wrapped(*args, **kwargs))\n File "/usr/lib/python3.6/site-packages/glanceclient/v2/images.py", line 255, in data\n resp, body = self.http_client.get(url)\n File "/usr/lib/python3.6/site-packages/keystoneauth1/adapter.py", line 395, in get\n return self.request(url, \'GET\', **kwargs)\n File "/usr/lib/python3.6/site-packages/glanceclient/common/http.py", line 380, in request\n return self._handle_response(resp)\n File "/usr/lib/python3.6/site-packages/glanceclient/common/http.py", line 120, in _handle_response\n raise exc.from_response(resp, resp.content)\nglanceclient.exc.HTTPForbidden: HTTP 403 Forbidden: The requested image has been deactivated. Image data download is forbidden.\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 201, in decorated_function\n return function(self, context, *args, **kwargs)\n File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 5950, in finish_resize\n context, instance, migration)\n File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__\n self.force_reraise()\n File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise\n raise self.value\n File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 5932, in finish_resize\n migration, request_spec)\n File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 5966, in _finish_resize_helper\n request_spec)\n File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 5902, in _finish_resize\n self._set_instance_info(instance, old_flavor)\n File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__\n self.force_reraise()\n File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise\n raise self.value\n File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 5890, in _finish_resize\n block_device_info, power_on)\n File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 11343, in finish_migration\n fallback_from_host=migration.source_compute)\n File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 4703, in _create_image\n injection_info, fallback_from_host)\n File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 4831, in _create_and_inject_local_root\n instance, size, fallback_from_host)\n File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 10625, in _try_fetch_image_cache\n trusted_certs=instance.trusted_certs)\n File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/imagebackend.py", line 275, in cache\n *args, **kwargs)\n File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/imagebackend.py", line 638, in create_image\n prepare_template(target=base, *args, **kwargs)\n File "/usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py", line 391, in inner\n return f(*args, **kwargs)\n File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/imagebackend.py", line 271, in fetch_func_sync\n fetch_func(target=target, *args, **kwargs)\n File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/utils.py", line 395, in fetch_image\n images.fetch_to_raw(context, image_id, target, trusted_certs)\n File "/usr/lib/python3.6/site-packages/nova/virt/images.py", line 115, in fetch_to_raw\n fetch(context, image_href, path_tmp, trusted_certs)\n File "/usr/lib/python3.6/site-packages/nova/virt/images.py", line 106, in fetch\n trusted_certs=trusted_certs)\n File "/usr/lib/python3.6/site-packages/nova/image/glance.py", line 1300, in download\n trusted_certs=trusted_certs)\n File "/usr/lib/python3.6/site-packages/nova/image/glance.py", line 379, in download\n _reraise_translated_image_exception(image_id)\n File "/usr/lib/python3.6/site-packages/nova/image/glance.py", line 1031, in _reraise_translated_image_exception\n raise new_exc.with_traceback(exc_trace)\n File "/usr/lib/python3.6/site-packages/nova/image/glance.py", line 377, in download\n context, 2, \'data\', args=(image_id,))\n File "/usr/lib/python3.6/site-packages/nova/image/glance.py", line 191, in call\n result = getattr(controller, method)(*args, **kwargs)\n File "/usr/lib/python3.6/site-packages/glanceclient/common/utils.py", line 670, in inner\n return RequestIdProxy(wrapped(*args, **kwargs))\n File "/usr/lib/python3.6/site-packages/glanceclient/v2/images.py", line 255, in data\n resp, body = self.http_client.get(url)\n File "/usr/lib/python3.6/site-packages/keystoneauth1/adapter.py", line 395, in get\n return self.request(url, \'GET\', **kwargs)\n File "/usr/lib/python3.6/site-packages/glanceclient/common/http.py", line 380, in request\n return self._handle_response(resp)\n File "/usr/lib/python3.6/site-packages/glanceclient/common/http.py", line 120, in _handle_response\n raise exc.from_response(resp, resp.content)\nnova.exception.ImageNotAuthorized: Not authorized for image dd1492d5-17a2-4dc2-a4e3-ec6c99255e4b.\n'} |

3 5

[neutron] Bug deputy Jun 27 to Jul 3
by Rodolfo Alonso Hernandez 04 Jul '22

04 Jul '22

1 0

Problem while launching an instance directly from an image "Volume did not finish being created even after we waited 203 seconds or 61 attempts"
by A Monster 04 Jul '22

04 Jul '22

I've deployed openstack using kolla, when I try to launch an instance directly from any image, after some time waiting for Block Device Mapping I get the following error : Build of instance 4cf01ba2-05b3-44e9-a685-8875d8c96b4e aborted: Volume > 01739e82-9e66-41f7-be74-dfbbdcd6746e did not finish being created even > after we waited 203 seconds or 61 attempts. And its status is creating. I've tried increasing *block_device_allocate_retries=400 *and *block_device_allocate_retries_interval=3 *, however I keep getting the same error. But when I create a volume from an image, then launch an instance from that same volume, it works just fine. Any suggestions for this issue?

2 1

[kolla-ansible][centos][yoga] Problems VpnaaS and containers
by Franck VEDEL 02 Jul '22

02 Jul '22

Hello I hope to have some help on a point that was bothering me last year, and which still does not work. I was a year ago on Wallaby, after 2 updates, I'm currently on Yoga. I use kolla-ansible, and openstack-kolla/centos-source images. Last year, I found the following ebug: https://bugs.launchpad.net/neutron/+bug/1938571 I tried with the Yoga update: exactly the same problem "Command: ['ipsec', 'whack', '--status'] Exit code: 33 Stdout: Stderr: whack: Pluto is not running (no "/run/pluto/pluto.ctl") ; Stderr: » Should I conclude that this bug will never be fixed and that it is impossible to have vpnaas functionality with centos images? Second question: let's imagine that I change the line kolla_base_distro: "centos" in kolla_base_distro: "ubuntu" Does this have a chance of working? I can't see all the possible problems. Thanks for your help. Franck

1 0

[all][tc] What's happening in Technical Committee: summary 01 July 2022: Reading: 5 min
by Ghanshyam Mann 01 Jul '22

01 Jul '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on 30 June. Most of the meeting discussions are summarized in this email. Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-06-30-15.00.log.html * Next TC weekly meeting will be on 7 July Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by 6 July. 2. What we completed this week: ========================= * Retired openstack-helm-deployments[2]. * Added Cinder Dell EMC PowerStore charm[3] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[4], Two are completed and others items are in-progress. Open Reviews ----------------- * Three open reviews for ongoing activities[5]. Create the Environmental Sustainability SIG --------------------------------------------------- We discussed it in TC meeting but did not conclude anything as Kendal would like to wait for more feedback in review[6]. New ELK service dashboard: e-r service ----------------------------------------------- There are good progress on brining elastic-recheck back. From no onwards, we can track the progress in TacT SIG. Feel free to ping dpawlik on #openstack-infra for any query or help. Consistent and Secure Default RBAC ------------------------------------------- We have a good amount of discussion and review in the goal document updates[7] and I have updated the patch by resolving the review comments. We will have policy popup meeting on 5 July[8]. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[9]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's the situation again on ML and hope Braden will be ready with their company side permission[10]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11][12]. Project updates ------------------- * None 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/847413 [3] https://review.opendev.org/c/openstack/governance/+/846890 [4] https://etherpad.opendev.org/p/tc-zed-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://review.opendev.org/c/openstack/governance-sigs/+/845336 [7] https://review.opendev.org/c/openstack/governance/+/847418 [8] https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… [9] https://review.opendev.org/c/openstack/governance/+/836888 [10] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all][TC] Stats about rechecking patches without reason given
by Slawek Kaplonski 01 Jul '22

01 Jul '22

Hi, During the last PTG and after it, in the TC we were discussing about CI resources usage and about "rechecks" of the CI jobs (I know, it's again the same topic). One of the things we would like to limit, or even avoid is to do "no reason rechecks" which means writing quick comment "recheck" without checking what really was wrong in the previous run. We know that putting some hard rules that only comments with "recheck" with given reason will trigger new CI jobs run will not work fine as people may simply start writing any random things there. But we want to encourage all teams to at least to investigate failures and do as many rechecks with explanation as possible. For now I prepared simple script [1] which counts how much of all rechecks are "bare rechecks". It can be checked by project (like openstack/neutron) or give summary for all projects or teams (like Quality Assurance for example). I prepared some stats for all teams listed in the https://opendev.org/openstack/governance/src/branch/master/reference/projec… from last 30 days: +-------------------+---------------+--------------+-------------------+ | Team | Bare rechecks | All Rechecks | Bare rechecks [%] | +-------------------+---------------+--------------+-------------------+ | skyline | 20 | 20 | 100.0 | | magnum | 2 | 2 | 100.0 | | zun | 1 | 1 | 100.0 | | mistral | 9 | 9 | 100.0 | | ec2-api | 1 | 1 | 100.0 | | barbican | 15 | 15 | 100.0 | | venus | 2 | 2 | 100.0 | | solum | 1 | 1 | 100.0 | | tacker | 30 | 30 | 100.0 | | trove | 4 | 4 | 100.0 | | rally | 2 | 2 | 100.0 | | storlets | 5 | 5 | 100.0 | | winstackers | 3 | 3 | 100.0 | | OpenStack Charms | 32 | 33 | 96.97 | | sahara | 27 | 28 | 96.43 | | keystone | 24 | 25 | 96.0 | | kuryr | 120 | 126 | 95.24 | | kolla | 134 | 142 | 94.37 | | Puppet OpenStack | 94 | 103 | 91.26 | | cloudkitty | 10 | 11 | 90.91 | | OpenStack-Helm | 29 | 32 | 90.62 | | blazar | 8 | 9 | 88.89 | | tripleo | 563 | 646 | 87.15 | | requirements | 20 | 23 | 86.96 | | Telemetry | 30 | 35 | 85.71 | | horizon | 55 | 67 | 82.09 | | ironic | 131 | 164 | 79.88 | | oslo | 11 | 14 | 78.57 | | heat | 25 | 33 | 75.76 | | cinder | 221 | 294 | 75.17 | | cyborg | 6 | 8 | 75.0 | | murano | 3 | 4 | 75.0 | | glance | 20 | 27 | 74.07 | | OpenStackSDK | 47 | 64 | 73.44 | | manila | 108 | 160 | 67.5 | | neutron | 149 | 221 | 67.42 | | senlin | 2 | 3 | 66.67 | | swift | 16 | 25 | 64.0 | | Quality Assurance | 106 | 167 | 63.47 | | nova | 41 | 71 | 57.75 | | octavia | 32 | 60 | 53.33 | | designate | 19 | 39 | 48.72 | | OpenStackAnsible | 41 | 226 | 18.14 | +-------------------+---------------+--------------+-------------------+ As You can see from that list above, there is much to improve there. I hope that if teams will be checking more reasons of the CI failures, and reporting bugs found there, we may make our CI more stable and as a result have less rechecks which will save our infra resources :) [1] https://github.com/slawqo/rechecks-stats/blob/main/rechecks_stats/bare_rech… -- Slawek Kaplonski Principal Software Engineer Red Hat -------- [1] https://opendev.org/openstack/governance/src/branch/master/reference/projec… [2] https://github.com/slawqo/rechecks-stats/blob/main/rechecks_stats/bare_rech…

8 10

[Openstack--Ansible] Playbook for Host Prep
by Dave Hall 30 Jun '22

30 Jun '22

Hello, I am wondering if there is any sort of playbook or script for setting up the networking on a new physical host prior to adding it to a cluster. It is a bit cumbersome to do it by hand, especially given that bridges on one type of host need an IP while the same bridge on another type of host should not have an IP. Seeding the /etc/hosts file would be nice as well. Going a bit further, it would be awfully nice if a given host could have the same 4th octet for all host interfaces, or at least for the important ones. I believe that since the 172.29 subnets are /22 this should be possible at least for smaller clusters. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

3 2

[sdk] renaming a volume with the SDK
by jdratlif＠globalnoc.iu.edu 30 Jun '22

30 Jun '22

I'm trying to set a property on a volume, specifically the name. But when I try to do this, it tells me the Session object has no default_microversion. I have all my auth in environment variables. Using TOKEN authentication. What am I doing wrong here? import openstack from openstack.block_storage.v3._proxy import Proxy as BlockStorageService from openstack.block_storage.v3.volume import Volume # enable openstack debug logging openstack.enable_logging(debug=True) conn = openstack.connect() cinder: BlockStorageService = conn.block_storage volume: Volume = cinder.get_volume("b3a70014-1cf0-4fd1-bdc4-183dbfd33e79") volume.name = "test_rename" volume.commit(conn.session) Thanks, --- John Ratliff Systems Automation Engineer GlobalNOC @ Indiana University

2 3

[neutron] Drivers meeting agenda - 01.07.2022.
by Lajos Katona 30 Jun '22

30 Jun '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * [RFE] Adding the "rekey" parameter to the api for strongswan like "dpd_action" (#link https://bugs.launchpad.net/neutron/+bug/1979044) * [RFE] Firewall Group Ordering on Port Association (#link https://bugs.launchpad.net/neutron/+bug/1979816) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[all][tc] Technical Committee next weekly meeting on 30 June 2022 at 1500 UTC
by Ghanshyam Mann 30 Jun '22

30 Jun '22

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

1 1

[tc][policy][ptl][operator] OpenSatck RBAC goal is to focus on project personas first (postpone the 'scope' implementation)
by Ghanshyam Mann 30 Jun '22

30 Jun '22

Hello Everyone, We have received a good amount of feedback from the operator. In ops meetup Berlin as well as from KDDI (Japanese telco). I have summarized the feedback in etherpad[1]. From feedback, it is clear that 'scope' enable will break heat so do NFV operators and even other operators are also confused with the 'scope' concept. Most operators want legacy admin to work as it is (able to do everything in deployment). We discussed this feedback in the policy popup meeting[2] and based on feedback and our outstanding issue of 'scope enable break heat create_stack', we decided to postpone the `scope` implementation. That is the way forward to at least implement the project personas which is asked by many operators. Basically the below direction: * Finish delivering project personas This is to introduce the `member` and `reader` roles to operate things within their project. By default, any other project role like `foo` will not be allowed to do anything in the project. * Postpone the `scope` implementation for later Some standalone services like Ironic can still have the `scope` implementation as long as it does not break any cross-service communication. Other services will make sure they work for project scope personas even with enforce_scope enabled. We are not saying 'scope' things are not good or we will never do it but at the same time, I am not sure when we will do it in future. At least moving this giant goal to focus on the project personas first will help us to deliver one good feature (project personas) for operators otherwise we are stuck. Complete details about the reason to postpone the 'scope' implementation and projects persons detail are proposed in community-wide goal, please review there. - https://review.opendev.org/c/openstack/governance/+/847418 [1] https://etherpad.opendev.org/p/rbac-operator-feedback#L45 [2] https://etherpad.opendev.org/p/rbac-zed-ptg#L171

4 5

Rocky? Stream?
by Ken D'Ambrosio 29 Jun '22

29 Jun '22

Hey, all. My company's looking for the path forward, after the switcheroo with CentOS, and we're wondering what seems to be solidly supported now and in the future. Any ideas? Thanks! -Ken

1 0

[PTG] [All] [Ops] [PTL] October 2022 Team Signup
by Kendall Nelson 29 Jun '22

29 Jun '22

Hi Everyone, At the Berlin Summit, we announced the next PTG will be held from Monday, October 17th to Thursday, October 20th, 2022 in Columbus, OH! To signup your team, you must complete the survey[1] by August 12th at 7:00 UTC. We NEED accurate contact information for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule signups which will be done via the PTGBot. If you are not on IRC, please get setup[2] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[3] as well. If you have any questions, please reach out! Information about signing up for timeslots will be sent to moderators mid to late August. Registration will open soon! A discounted room block at the PTG venue will be available. Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [3] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 0

Kolla Train deliverables are going EOL
by Radosław Piliszek 29 Jun '22

29 Jun '22

Dear Fellow OpenStackers, Kolla Train deliverables (Kolla, Kolla-Ansible, Kayobe) are going EOL. [1] Ussuri and Victoria remain in extended maintenance. Wallaby, Xena and Yoga are our current stable releases. The primary reason for EOLing is that the branch's CI is badly broken by Python2 and CentOS7 issues and there is no interest in fixing the issues. [1] https://review.opendev.org/c/openstack/releases/+/848148 Kind regards, -yoctozepto

1 0

Glance folder to store images
by A Monster 29 Jun '22

29 Jun '22

I noticied in the glance configuration file after deploying openstack that filesystem_store_datadir=/var/lib/glance/images/ however, upon inspection, I found that images weren't stored in that folder, instead all images where located in this folder */var/lib/docker/volumes/glance/_data/images/.* So I'm thinking if actually filesystem_store_datadir is not used to store images but maybe something else.

3 2