March 2021 - openstack-discuss - lists.openstack.org

[PTLs][All] vPTG April 2021 Team Signup
by Kendall Nelson 26 Mar '21

26 Mar '21

Greetings! As you hopefully already know, our next PTG will be virtual again, and held from Monday, April 19 to Friday, April 23. We will have the same schedule set up available as last time with three windows of time spread across the day to cover all timezones with breaks in between. *To signup your team, you must complete **BOTH** the survey[1] AND reserve time in the ethercalc[2] by March 25 at 7:00 UTC.* We ask that the PTL/SIG Chair/Team lead sign up for time to have their discussions in with 4 rules/guidelines. 1. Cross project discussions (like SIGs or support project teams) should be scheduled towards the start of the week so that any discussions that might shape those of other teams happen first. 2. No team should sign up for more than 4 hours per UTC day to help keep participants actively engaged. 3. No team should sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. Again, you need to fill out BOTH the ethercalc AND the survey to complete your team's sign up. If you have any issues with signing up your team, due to conflict or otherwise, please let me know! While we are trying to empower you to make your own decisions as to when you meet and for how long (after all, you know your needs and teams timezones better than we do), we are here to help! Once your team is signed up, please register! And remind your team to register! Registration is free, but since it will be how we contact you with passwords, event details, etc. it is still important! Continue to check back for updates at openstack.org/ptg. -the Kendalls (diablo_rojo & wendallkaters) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/april2021_vptg_survey [2] Ethercalc Signup: https://ethercalc.net/oz7q0gds9zfi [3] PTG Registration: https://april2021-ptg.eventbrite.com

4 7

Cannot specify host in availability zone
by Mauricio Tavares 26 Mar '21

26 Mar '21

Easy peasy question: According to https://docs.openstack.org/nova/rocky/admin/availability-zones.html, I can specify the host I want to use by following the format --availability-zone ZONE:HOST So, let's get the hostnames for the compute nodes. [raub@test-hn ~(keystone_admin)]$ openstack compute service list --service nova-compute +----+--------------+-----------------------+------+---------+-------+----------------------------+ | ID | Binary | Host | Zone | Status | State | Updated At | +----+--------------+-----------------------+------+---------+-------+----------------------------+ | 11 | nova-compute | compute02.example.com | nova | enabled | up | 2021-02-03T17:25:53.000000 | | 12 | nova-compute | compute03.example.com | nova | enabled | up | 2021-02-03T17:25:53.000000 | | 13 | nova-compute | compute01.example.com | nova | enabled | up | 2021-02-03T17:25:52.000000 | +----+--------------+-----------------------+------+---------+-------+----------------------------+ [raub@test-hn ~(keystone_admin)]$ I want to use compute01.example.com, which I can resolve to 10.1.1.11. But, when I try to create server with (running as admin): openstack server create \ --image default_centos_8 \ --flavor m1.small \ --key-name raubkey \ --availability-zone nova:compute01.example.com \ --nic net-id=LONG_BORING-ID \ raub-netest I get the error message (from openstack server show raub-netest|grep fault): 'message': 'No valid host was found. No such host - host: compute01.example.com node: None ' What am I doing wrong here?

3 4

[cinder] review priorities for week of 29 march
by Brian Rosmaita 26 Mar '21

26 Mar '21

We're keeping track of release-critical patches here: https://etherpad.opendev.org/p/cinder-wallaby-release-critical-bug-nominati… The stable/wallaby branch was cut yesterday when RC-1 was released. So these must be reviewed and merged to master and then proposed as backports to stable/wallaby and reviewed and approved again. The week of 29 March is a short week for people in various parts of the world, and Monday the week after (which is final RC week) is also a holiday for some people. So even though it seems like there's a lot of time to prepare RC-2, there really isn't. Please schedule some time to do reviews early in the week. cheers, brian

1 0

[cinder] critical os-brick fix needs immediate review
by Brian Rosmaita 26 Mar '21

26 Mar '21

Gorka has a patch up to address a possible data loss situation: https://review.opendev.org/c/openstack/os-brick/+/782992 I spoke with the release team today, and if we can get the patch reviewed and merged to master and then backported to stable/wallaby by MONDAY (29 March), we can apply for a Requirements Freeze Exception so that os-brick with this fix will be included in the OpenStack coordinated wallaby release. (It's a data loss issue, of course we want the fix in the wallaby release.) So please review at your earliest convenience. thanks, brian

1 1

[manila] RC1 is available, No IRC meeting on 1st April 2021
by Goutham Pacha Ravi 26 Mar '21

26 Mar '21

Hello Zorillas, RC1 builds have now shipped for both manila and manila-ui, thank you all for your hard work on getting these out on time. It's now time to test these builds and learn of any release blocking bugs and fix them. Some down time is also in order between now and the PTG! In order to let folks to plan for that, I'd like to skip the IRC meeting on 1st April. In the meantime, please feel free to post your issues to #openstack-manila and to this email list. Thanks, Goutham

1 0

[TripleO] next irc meeting Tuesday Mar 30 @ 1400 UTC in #tripleo
by Marios Andreou 26 Mar '21

26 Mar '21

Reminder that the next TripleO irc meeting is: ** Tuesday 30 March at 1400 UTC in #tripleo ** ** https://wiki.openstack.org/wiki/Meetings/TripleO ** ** https://etherpad.opendev.org/p/tripleo-meeting-items ** Please add anything you want to highlight at https://etherpad.opendev.org/p/tripleo-meeting-items This can be recently completed things, ongoing review requests, blocking issues, or anything else tripleo you want to share. Our last meeting was on Mar 16 - you can find the logs there http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-03-16-14.… Hope you can make it on Tuesday, regards, marios

1 0

[kolla] Train Centos7 -> Centos8 upgrade fails on masakari
by Braden, Albert 26 Mar '21

26 Mar '21

I've created a heat stack and installed Openstack Train to test the Centos7->8 upgrade following the document here: https://docs.openstack.org/kolla-ansible/train/user/centos8.html#migrating-… Everything seems to work fine until I try to deploy the first replacement controller into the cluster. I upgrade RMQ, ES and Kibana, then follow the "remove existing controller" process to remove control0, create a Centos 8 VM, bootstrap the cluster, pull containers to the new control0, and everything is still working. Then I type the last command "kolla-ansible -i multinode deploy --limit control" The RMQ install works and I see all 3 nodes up in the RMQ admin, but it takes a long time to complete "TASK [service-ks-register : masakari | Creating users] " and then hangs on "TASK [service-ks-register : masakari | Creating roles]". At this time the new control0 becomes unreachable and drops out of the RMQ cluster. I can still ping it but console hangs along with new and existing ssh sessions. It appears that the CPU may be maxed out and not allowing interrupts. Eventually I see error "fatal: [control0]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}" RMQ seems fine on the 2 old controllers; they just don't see the new control0 active: (rabbitmq)[root@chrnc-void-testupgrade-control-2 /]# rabbitmqctl cluster_status Cluster status of node rabbit@chrnc-void-testupgrade-control-2 ... [{nodes,[{disc,['rabbit@chrnc-void-testupgrade-control-0', 'rabbit@chrnc-void-testupgrade-control-0-replace', 'rabbit@chrnc-void-testupgrade-control-1', 'rabbit@chrnc-void-testupgrade-control-2']}]}, {running_nodes,['rabbit@chrnc-void-testupgrade-control-1', 'rabbit@chrnc-void-testupgrade-control-2']}, {cluster_name,<<"rabbit(a)chrnc-void-testupgrade-control-0.dev.chtrse.com">>}, {partitions,[]}, {alarms,[{'rabbit@chrnc-void-testupgrade-control-1',[]}, {'rabbit@chrnc-void-testupgrade-control-2',[]}]}] After this the HAProxy IP is pingable but openstack commands are failing: (openstack) [root@chrnc-void-testupgrade-build openstack]# osl Failed to discover available identity versions when contacting http://172.16.0.100:35357/v3. Attempting to parse version from URL. Gateway Timeout (HTTP 504) After about an hour my open ssh session on the new control0 responded and confirmed that the CPU is maxed out: [root@chrnc-void-testupgrade-control-0-replace /]# uptime 17:41:55 up 1:55, 0 users, load average: 157.87, 299.75, 388.69 I built new heat stacks and tried it a few times, and it consistently fails on masakari. Do I need to change something in my masakari config before upgrading Train from Centos 7 to Centos 8? I apologize for the nonsense below. I have not been able to stop it from being attached to my external emails. E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

4 5

[release] Release countdown for week R-2 Mar 29 - Apr 02
by Herve Beraud 26 Mar '21

26 Mar '21

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the Wallaby deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/wallaby branch creation for all deliverables that have not branched yet, using the latest available Wallaby release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/wallaby branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/wallaby branch before releasing out of the stable/wallaby branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for Xena development, though the focus should still be on finishing up Wallaby until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final Wallaby release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targetted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the Wallaby version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: 08 April, 2021 (R-1 week) Final Wallaby release: 14 April, 2021 Xena virtual PTG: 19 - 23 April, 2021 Thank you for your attention -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[nova][placement] Wallaby release
by Balazs Gibizer 26 Mar '21

26 Mar '21

Hi, We are getting close to the Wallaby release. So I create a tracking etherpad[1] with the schedule and TODOs. One thing that I want to highlight is that we will hit Feature Freeze on 11th of March. As the timeframe between FF and RC1 is short I'm not plannig with FFEs. Patches that are approved before 11 March EOB can be rechecked or rebased if needed and then re-approved. If you have a patch that is really close but not approved before the deadline, and you think there are two cores that willing to review it before RC1, then please send a mail to the ML with [nova][FFE] subject prefix not later than 16th of March EOB. Cheers, gibi [1] https://etherpad.opendev.org/p/nova-wallaby-rc-potential

2 3

[glance] [ops] Glance deployed on 2 nodes with rbd. Do I need a shared filesystem for the reserved stores ?
by Massimo Sgaravatto 26 Mar '21

26 Mar '21

We are using OpenStack Train but we plan to migrate soon to something newer The glance-api service is deployed on 2 nodes. We used to have 2 backends for glance (file and rbd) but now we want to use only ceph. So I guess the configuration for the stores can be simply something like this [*] Reading: https://docs.openstack.org/glance/train/admin/multistores.html is not too clear to me if I have to configure somewhere filesystem_store_datadir. In particular do I have to configure the [os_glance_tasks_store] and [os_glance_staging_store] reserved stores ? If so, do I still need shared (between the 2 glance-api nodes )filesystems for them ? Thanks, Massimo [*] [DEFAULT] enabled_backends = rbd:rbd [glance_store] default_backend = rbd [rbd] store_description = Ceph in replica 3 rbd_store_pool = glance-cloudtest rbd_store_user = glance-cloudtest rbd_store_ceph_conf = /etc/ceph/ceph.conf rbd_store_chunk_size = 8

2 3