- openstack-discuss - lists.openstack.org

[tripleo]] tripleo victoria rc1
by Marios Andreou 25 Sep '20

25 Sep '20

hello TripleO folks o/ we don't normally/aren't expected to cut release candidates. However after discussion with and guidance from Wes I decided to propose an rc1 as practice since I haven't used the new releases tool before [4]. The proposal is up at [1] but I've set -1 there on request from reviewers; we can't merge that until [2] merges first. If you are interested please check [1] and add any comments. In particular let me know if you want to include a release for one of the independent repos [3] (though for validations-common/libs we need to reach out to the validations team they are managing those AFAIK). thanks, hope you enjoy your weekend! [1] https://review.opendev.org/#/c/754346/ [2] https://review.opendev.org/754347 [3] https://releases.openstack.org/teams/tripleo.html#independent [4] https://releases.openstack.org/reference/using.html#using-new-release-comma…

1 0

[openstack][manila] GenericShareDriver on stein
by Ignazio Cassano 25 Sep '20

25 Sep '20

Hello Stackers, I am testing manila manila.share.drivers.generic.GenericShareDriver with manila.share.drivers.generic.GenericShareDriver. I created in my project an instance with nfs server and it is up and running. In my manila.conf I have specified the instance id, use and password: [locale] share_driver = manila.share.drivers.generic.GenericShareDriver driver_handles_share_servers = false share_backend_name= locale service_instance_user = manila service_instance_passwod = manila service_instance_name_or_id = 5b0fa246-e94b-4a84-b730-7066dfb31fb0 path_to_private_key=~/.ssh/id_rsa path_to_public_key=~/.ssh/id_rsa.pub I have also other backend with netapp drivers and they works fine. The generic drivers reports: 2020-09-25 13:56:13.955 4097174 WARNING manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] Waiting for the common service VM to become available. Driver is currently uninitialized. Share server: None Retry interval: 5 2020-09-25 13:56:14.143 4097174 ERROR manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] string indices must be integers 2020-09-25 13:56:19.144 4097174 WARNING manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] Waiting for the common service VM to become available. Driver is currently uninitialized. Share server: None Retry interval: 5 2020-09-25 13:56:19.340 4097174 ERROR manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] string indices must be integers Seems the instance I created is not available. Please, any help? Ignazio

2 2

[election][Kuryr] PTL candidacy for Wallaby
by Maysa De Macedo Souza 25 Sep '20

25 Sep '20

Hello, I would like to propose my candidacy to be the PTL of Kuryr for the Wallaby cycle. I have been a contributor to Kuryr since the Queens release and was appointed to the Kuryr core team in the Ussuri cycle. I see the following goals for the Kuryr project during the Wallaby cycle: * Improve stability and extend CI: we already included great improvements in our CI, but I believe we must continuously work on it to provide better and quicker feedback when developing new features. As part of that, we should start graduating experimental jobs like the ones using OVN-Octavia driver and Network Policy, and handle issues with jobs requiring more swap. * Address testing gaps for new and existing features: this would avoid regressions and find bugs. Also, improves stability. * Continue extending and improving Kuryr functionalities, such as dual stack, SCTP support and CRDs usage. * Grow the contributor base. I would like to contribute back to the community as a PTL while following great examples of previous PTLs. Thank you, Maysa.

1 0

[rpm-packaging] Proposing Hervé Beraud as new core reviewer
by Javier Pena 25 Sep '20

25 Sep '20

Hi, I would like to propose Hervé Beraud as a new core reviewer for the rpm-packaging project. Hervé has been providing consistently good reviews over the last few months, and I think he would be a great addition to the core reviewer team. Existing cores, please vote on the thread! Regards, Javier Peña

3 3

[tc] monthly meeting
by Mohammed Naser 25 Sep '20

25 Sep '20

Hi everyone, Our monthly TC meeting is scheduled for next Thursday, October 1st, at 1400 UTC. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, September 30th, at 1900 UTC. Thank you, Regards, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[tripleo] PTL candidacy for Wallaby
by Marios Andreou 25 Sep '20

25 Sep '20

I would like to nominate myself for the TripleO PTL role for the Wallaby cycle. I think it is obvious that the role of the PTL has changed significantly compared to the early days of TripleO. Most importantly we are (and have been for a while) now organised into self-contained topic squads (deployment, validations, upgrades, networking, storage, ci, etc). Typically technical decisions are driven exclusively within those squads (even if they are done 'in the open' on gerrit and launchpad and opendev-discuss). The role of the PTL then is more about coordination across the squads, ensuring we deliver release targets, keeping bug backlogs in order and facilitating the resolution of any conflicts that arise. I have worked on TripleO since before the Kilo release and have collaborated with many current and past members of the community including engineers and also users/operators. My contributions thus far have been in code/docs/bugs, originally working on upgrades and more recently working on CI. I haven't had the opportunity to work on the 'admin' side of TripleO (besides in the past cutting the occasional release). I am thus especially excited by the prospect of contributing in this new way as PTL, if TripleO will have me! I sincerely promise to give it my best and I am sure that together with the kind help of the current PTL Wes Hayutin we will have a smooth Wallaby cycle, meeting our responsibilities to the foundation and the community. There is (as ever!) a lot of exciting work coming in the Victoria release and continuing in Wallaby including the continued exploration of the removal of Heat as our configuration engine, the new validations repos and framework, the new container builds process, Fast Forward Upgrades II (back with a vengeance), ci component and dependency pipelines, ci parent/child jobs, and I'm sure many more that we will discuss at the coming Wallaby PTG. Two areas I would like to focus on as PTL should you give me the opportunity are: - improve our current documentation/deployment guides - at minimum they must be updated to recent releases and there are many items missing. I am hoping to rally support from the various squads for this. - improve visibility into the various TripleO squads - this may mean re-instating a 'new' weekly/bi-weekly (or other frequency) tripleo meeting or by some new way of collaborating. Again this is really dependent on support from the tripleo community. thank you for your consideration!

1 0

[Neutron] Not create .2 port
by Tony Liu 24 Sep '20

24 Sep '20

Hi, When create a subnet, by default, the first address is the gateway and Neutron also allocates an address for serving DHCP and DNS. Is there any way to NOT create such port when creating subnet? Thanks! Tony

3 4

[election][neutron] PTL candidacy for Wallaby
by Slawek Kaplonski 24 Sep '20

24 Sep '20

Hi, I want to propose my candidacy and continue serving as Neutron PTL in the Wallaby cycle. In the Victoria cycle I proposed a couple of major goals. We achieved most of them, like for example: * add support for metadata over IPv6 in Neutron, * continue adoption of the OVN driver as one of the in-tree Neutron drivers. * find new maintainers for the networking-midonet project so we keep it the * Neutron stadium. In the upcoming cycle I would like to continue work which we started already and focus mostly on: * implement old, unfinished Blueprints like adoption of new engine facade, * continue adoption of the OVN backend in Neutron, closing more feature parity * gaps * switch the OVN driver to be the default backend in Devstack, In addition to the goals mentioned above mentioned, I want to continue work to improve our CI stability and coverage. It is my continuing desire to do my best to help our outstanding team to deliver better software and to grow. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Drivers meeting agenda - 25.09.2020
by Slawek Kaplonski 24 Sep '20

24 Sep '20

Hi, For tomorrows drivers meeting we again don't have any new RFEs to discuss but I wanted to use this meeting to quickly discuss about 1 bug: https://bugs.launchpad.net/neutron/+bug/1895933 So see You on tomorrows meeting :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[all][election][TC] Candidacy
by Kendall Nelson 24 Sep '20

24 Sep '20

Hello Everyone! I am once again declaring my candidacy for the Technical Committee. This last year I have learned so much about OpenStack and our amazing community. There is never a shortage of work to be done and I feel there is still a lot I can do to help the community as a part of the TC. I served as TC Vice Chair during the second half of my term and I felt like I was able to do a lot to help support Mohammed, the chair and other members of the TC. My work in coordinating the new office hours and our time at the upcoming PTG will enable the future TC to be more accessible and productive. I also lead the community goal to improve the onboarding documentation, further lowering the barrier for new contributors. If elected, I will continue bridging our community with the kubernetes community. I am actively facilitating the conversations between the TC and the k8s Technical Steering Committee at the upcoming PTG meetings to share insight between both of our communities and generally share knowledge about keeping open source communities healthy. I would also like to take a more active role in pushing the unification of the community around a single CLI to simplify openstack operations to better support our users and lessen the load on developers. I think a good first step would be to work with the CLI/SDK team to build a list of items that are blocking project teams from fully implementing all their features in the openstack client. From there we can figure out what is missing from the list, which teams are affected by which blocking items and prioritize what needs to be worked on first. Thank you for your time and consideration. As I said in my platform last year, I love this community and all the awesome people in it, serving on the TC is a great experience and an honor. -Kendall Nelson (diablo_rojo)

1 0

[ironic] Recovering IPMI-type baremetal nodes in 'error' state
by Paul Browne 24 Sep '20

24 Sep '20

Hello all, I have a handful of baremetal nodes enrolled in Ironic that use the IPMI hardware type, whose motherboards were recently replaced in a hardware recall by the vendor. After the replacement, the BMC IPMI-over-LAN feature was accidentally left disabled on the nodes, and future attempts to control them with Ironic has put these nodes into the ERROR provisioning state. The IPMI-over-LAN feature on the boards has been enabled again as expected, but is there now any easy way to get the BM nodes back out of that ERROR state, without first deleting and re-enrolling them? -- ******************* Paul Browne Research Computing Platforms University Information Services Roger Needham Building JJ Thompson Avenue University of Cambridge Cambridge United Kingdom E-Mail: pfb29(a)cam.ac.uk Tel: 0044-1223-746548 *******************

2 3

LVM misconfiguration after openstack stackpack server hang and reboot
by Alan Davis 24 Sep '20

24 Sep '20

This morning my CentOS 7.7 RDO packstack installation of Rocky hung. On reboot some of the VMs won't start. This is a primary system and I need to find the most expedient way to recover without losing data. I'm not using LVM thin volumes. Any help is appreciated. Looking at nova-compute.log I see errors trying to find LUN 0 during the sysfs stage. Several machines won't boot because their root disk entries in LVM are seen as PV and booting them doesn't see them in the DM subsystem. Other machines boot but there attached disks throw LVM errors about duplicate PV and preferring the cinder-volumes VG version. LVM is showing LVs that have both "bare" entries as well as entries in cinder-volumes and it's complaining about duplicate PVs, not using lvmetad and preferring some entries because they are in the dm subsystem. I've verified that, so far, I haven't lost any data. The "bare" LV not being used as part of the DM subsystem because it's server won't boot can be mounted on the openstack host and all data on it is accessible. This host has rebooted cleanly multiple times in the past. This is the first time it's shown any problems. Am I missing an LVM filter? (unlikely since it wasn't neede before) How can I reset the LVM configuration and convince it that it's not seeing duplicate PV? How do I ensure that openstack sees the right UUID and volume ID? Excerpts from error log and output of lvs : --- nova-compute.log --- during VM start 2020-09-24 11:15:27.091 13953 INFO os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default default] Trying to connect to iSCSI portal 172.10.0.40:3260 2020-09-24 11:15:29.721 13953 WARNING nova.compute.manager [req-fd32e16f-c879-402f-a32c-6be45a943c34 48af9a366301467d9fec912fd1c072c6 f9fc7b412a8446d083da1356aa370eb4 - default d efault] [instance: de7d740c-786a-4aa2-aa09-d447ae7e14b6] Received unexpected event network-vif-unplugged-79aff403-d2e4-4266-bd88-d7bd19d501a9 for instance with vm_state stopped a nd task_state powering-on. 2020-09-24 11:16:21.361 13953 WARNING os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d 1c8 - default default] LUN 0 on iSCSI portal 172.10.0.40:3260 not found on sysfs after logging in. 2020-09-24 11:16:23.482 13953 INFO os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default default] Trying to connect to iSCSI portal 172.10.0.40:3260 2020-09-24 11:17:17.741 13953 WARNING os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d 1c8 - default default] LUN 0 on iSCSI portal 172.10.0.40:3260 not found on sysfs after logging in.: VolumeDeviceNotFound: Volume device not found at . 2020-09-24 11:17:21.864 13953 INFO os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default default] Trying to connect to iSCSI portal 172.10.0.40:3260 2020-09-24 11:18:16.113 13953 WARNING os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d 1c8 - default default] LUN 0 on iSCSI portal 172.10.0.40:3260 not found on sysfs after logging in.: VolumeDeviceNotFound: Volume device not found at . 2020-09-24 11:18:17.252 13953 INFO nova.compute.manager [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default defa ult] [instance: de7d740c-786a-4aa2-aa09-d447ae7e14b6] Successfully reverted task state from powering-on on failure for instance. 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - defaul t default] Exception during message handling: VolumeDeviceNotFound: Volume device not found at . 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) --- lvs output --- I've annotated 1 machine's disks to illustrate the relationship between the volume-*** cinder-volumes vg entries and the "bare" lv seen as directly accessible from the host. There are 3 servers that won't boot, they are the one's who's home/vg_home and encrypted_home/encrypted_vg entries are shown. WARNING: Not using lvmetad because duplicate PVs were found. WARNING: Use multipath or vgimportclone to resolve duplicate PVs? WARNING: After duplicates are resolved, run "pvscan --cache" to enable lvmetad. WARNING: Not using device /dev/sdu for PV yZy8Xk-foKT-ovjV-0EZv-VxEM-GqiP-WH7k53. == backup_lv/encrypted_vg WARNING: Not using device /dev/sdv for PV tHA9ui-eSIO-MDmI-RM3u-3Bf4-Dznb-Ha3XfP. == varoptgitlab/encrypted_vg WARNING: Not using device /dev/sdm for PV 5eoyCa-sMO4-b7O4-jIfh-byZE-L5pS-3lOu0D. WARNING: Not using device /dev/sdp for PV 3BI0nV-TP0k-rgPC-PrjH-FT7z-reMe-ec1spj. WARNING: Not using device /dev/sdt for PV ILdbcY-VFCm-fnH6-Y3jc-pdWZ-fnl8-PH3TPe. == storage_lv/encrypted_vg WARNING: Not using device /dev/sdr for PV zowU2N-oaBh-r4cO-cxgX-YYiq-Kf3q-mqlHfK. WARNING: PV yZy8Xk-foKT-ovjV-0EZv-VxEM-GqiP-WH7k53 prefers device /dev/cinder-volumes/volume-c8da1abf-7143-422c-9ee5-b2724a71c8ff because device is in dm subsystem. WARNING: PV tHA9ui-eSIO-MDmI-RM3u-3Bf4-Dznb-Ha3XfP prefers device /dev/cinder-volumes/volume-0a12012f-8c2e-41fb-aa0c-a7ae99c62487 because device is in dm subsystem. WARNING: PV 5eoyCa-sMO4-b7O4-jIfh-byZE-L5pS-3lOu0D prefers device /dev/cinder-volumes/volume-990a057c-46cc-4a81-ba02-28b72c34791d because device is in dm subsystem. WARNING: PV 3BI0nV-TP0k-rgPC-PrjH-FT7z-reMe-ec1spj prefers device /dev/cinder-volumes/volume-b6a9da6e-1958-46ea-90b4-ac1aebed8c04 because device is in dm subsystem. WARNING: PV ILdbcY-VFCm-fnH6-Y3jc-pdWZ-fnl8-PH3TPe prefers device /dev/cinder-volumes/volume-302dd53b-7d05-4f6d-9ada-8f2ed6e1d4c6 because device is in dm subsystem. WARNING: PV zowU2N-oaBh-r4cO-cxgX-YYiq-Kf3q-mqlHfK prefers device /dev/cinder-volumes/volume-df006472-be7a-4957-972a-1db4463f5d67 because device is in dm subsystem. LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert home centos_stack3 -wi-ao---- 4.00g root centos_stack3 -wi-ao---- 50.00g swap centos_stack3 -wi-ao---- 4.00g _snapshot-05b1e46b-1ae3-4cd0-9117-3fb53a6d94b0 cinder-volumes swi-a-s--- 20.00g volume-1d0ff5d5-93a3-44e8-8bfa-a9290765c8c6 0.00 lv_filestore cinder-volumes -wi-ao---- 1.00t ... volume-c8da1abf-7143-422c-9ee5-b2724a71c8ff cinder-volumes -wi-ao---- 100.00g volume-0a12012f-8c2e-41fb-aa0c-a7ae99c62487 cinder-volumes -wi-ao---- 60.00g volume-990a057c-46cc-4a81-ba02-28b72c34791d cinder-volumes -wi-ao---- 200.00g volume-b6a9da6e-1958-46ea-90b4-ac1aebed8c04 cinder-volumes -wi-ao---- 30.00g volume-302dd53b-7d05-4f6d-9ada-8f2ed6e1d4c6 cinder-volumes -wi-ao---- 60.00g volume-df006472-be7a-4957-972a-1db4463f5d67 cinder-volumes -wi-ao---- 250.00g ... volume-f3250e15-bb9c-43d1-989d-8a8f6635a416 cinder-volumes -wi-ao---- 20.00g volume-fc1d5fcb-fda1-456b-a89d-582b7f94fb04 cinder-volumes -wi-ao---- 300.00g volume-fc50a717-0857-4da3-93cb-a55292f7ed6d cinder-volumes -wi-ao---- 20.00g volume-ff94e2d6-449b-495d-82e6-0debd694c1dd cinder-volumes -wi-ao---- 20.00g data2 data2_vg -wi-a----- <300.00g data data_vg -wi-a----- 1.79t backup_lv encrypted_vg -wi------- <100.00g == ...WH7k53 storage_lv encrypted_vg -wi------- <60.00g == ...PH3TPe varoptgitlab_lv encrypted_vg -wi------- <200.00g varoptgitlab_lv encrypted_vg -wi------- <30.00g varoptgitlab_lv encrypted_vg -wi------- <60.00g == ...Ha3XfP encrypted_home home_vg -wi-a----- <40.00g encrypted_home home_vg -wi------- <60.00g pub pub_vg -wi-a----- <40.00g pub_lv pub_vg -wi------- <250.00g rpms repo -wi-a----- 499.99g home vg_home -wi-a----- <40.00g gtri_pub vg_pub -wi-a----- 20.00g pub vg_pub -wi-a----- <40.00g -- Alan Davis Principal System Administrator Apogee Research LLC

1 1

[Glance] PTL on Vacation
by Abhishek Kekane 24 Sep '20

24 Sep '20

Hi All, I'm starting my vacations from 28th September and will be back on October 5th. Please direct any issues to the rest of the core team. Also there will be no glance weekly meeting on 01 October [1]. [1] https://etherpad.opendev.org/p/glance-team-meeting-agenda Thanks, Abhishek

1 0

[all][tc][goals] Migrate CI/CD jobs to new Ubuntu LTS Focal: Week R-4 Update
by Ghanshyam Mann 24 Sep '20

24 Sep '20

Hello Everyone, Please find the week R-4 updates on 'Ubuntu Focal migration' community goal. Its time to force the base jobs migration which can break the projects gate if not yet taken care of. Read below for the plan. Tracking: https://storyboard.openstack.org/#!/story/2007865 Progress: ======= * We are close to V-3 release and this is time we have to complete this migration otherwise doing it in RC period can add unnecessary and last min delay. I am going to plan this migration in two-part. This will surely break some projects gate which is not yet finished the migration but we have to do at some time. Please let me know if any objection to the below plan. * Part1: Migrating tox base job tomorrow (8th Sept): ** I am going to open tox base jobs migration (doc, unit, functional, lower-constraints etc) to merge by tomorrow. which is this series (all base patches of this): https://review.opendev.org/#/c/738328/ . **There are few repos still failing on requirements lower-constraints job specifically which I tried my best to fix as many as possible. Many are ready to merge also. Please merge or work on your projects repo testing before that or fix on priority if failing. * Part2: Migrating devstack/tempest base job on 10th sept: * We have few open bugs for this which are not yet resolved, we will see how it goes but the current plan is to migrate by 10th Sept. ** Bug#1882521 ** DB migration issues, *** alembic and few on telemetry/gnocchi side https://github.com/sqlalchemy/alembic/issues/699, https://storyboard.openstack.org/#!/story/2008003 Testing Till now: ============ * ~200 repos gate have been tested or fixed till now. ** https://review.opendev.org/#/q/topic:migrate-to-focal+(status:abandoned+OR+… * ~100 repos are under test and failing. Debugging and fixing are in progress (If you would like to help, please check your project repos if I am late to fix them): ** https://review.opendev.org/#/q/topic:migrate-to-focal+status:open * ~30repos fixes ready to merge: ** https://review.opendev.org/#/q/topic:migrate-to-focal+status:open+label%3AV… Bugs Report: ========== 1. Bug#1882521. (IN-PROGRESS) There is open bug for nova/cinder where three tempest tests are failing for volume detach operation. There is no clear root cause found yet -https://bugs.launchpad.net/cinder/+bug/1882521 We have skipped the tests in tempest base patch to proceed with the other projects testing but this is blocking things for the migration. 2. DB migration issues (IN-PROGRESS) * alembic and few on telemetry/gnocchi side https://github.com/sqlalchemy/alembic/issues/699, https://storyboard.openstack.org/#!/story/2008003 3. We encountered the nodeset name conflict with x/tobiko. (FIXED) nodeset conflict is resolved now and devstack provides all focal nodes now. 4. Bug#1886296. (IN-PROGRESS) pyflakes till 2.1.0 is not compatible with python 3.8 which is the default python version on ubuntu focal[1]. With pep8 job running on focal faces the issue and fail. We need to bump the pyflakes to 2.1.1 as min version to run pep8 jobs on py3.8. As of now, many projects are using old hacking version so I am explicitly adding pyflakes>=2.1.1 on the project side[2] but for the long term easy maintenance, I am doing it in 'hacking' requirements.txt[3] nd will release a new hacking version. After that project can move to new hacking and do not need to maintain pyflakes version compatibility. 5. Bug#1886298. (IN-PROGRESS) 'Markupsafe' 1.0 is not compatible with the latest version of setuptools[4], We need to bump the lower-constraint for Markupsafe to 1.1.1 to make it work. There are a few more issues[5] with lower-constraint jobs which I am debugging. What work to be done on the project side: ================================ This goal is more of testing the jobs on focal and fixing bugs if any otherwise migrate jobs by switching the nodeset to focal node sets defined in devstack. 1. Start a patch in your repo by making depends-on on either of below: devstack base patch if you are using only devstack base jobs not tempest: Depends-on: https://review.opendev.org/#/c/731207/ OR tempest base patch if you are using the tempest base job (like devstack-tempest): Depends-on: https://review.opendev.org/#/c/734700/ Both have depends-on on the series where I am moving unit/functional/doc/cover/nodejs tox jobs to focal. So you can test the complete gate jobs(unit/functional/doc/integration) together. This and its base patches - https://review.opendev.org/#/c/738328/ Example: https://review.opendev.org/#/c/738126/ 2. If none of your project jobs override the nodeset then above patch will be testing patch(do not merge) otherwise change the nodeset to focal. Example: https://review.opendev.org/#/c/737370/ 3. If the jobs are defined in branchless repo and override the nodeset then you need to override the branches variant to adjust the nodeset so that those jobs run on Focal on victoria onwards only. If no nodeset is overridden then devstack being branched and stable base job using bionic/xenial will take care of this. Example: https://review.opendev.org/#/c/744056/2 4. If no updates need you can abandon the testing patch (https://review.opendev.org/#/c/744341/) If it need updates then modify the same patch with proper commit msg, once it pass the gate then remove the Depends-On so that you can merge your patch before base jobs are switched to focal. This way we make sure no gate downtime in this migration. Example: https://review.opendev.org/#/c/744056/1..2//COMMIT_MSG Once we finish the testing on projects side and no failure then we will merge the devstack and tempest base patches. Important things to note: =================== * Do not forgot to add the story and task link to your patch so that we can track it smoothly. * Use gerrit topic 'migrate-to-focal' * Do not backport any of the patches. References: ========= Goal doc: https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-j… Storyboard tracking: https://storyboard.openstack.org/#!/story/2007865 [1] https://github.com/PyCQA/pyflakes/issues/367 [2] https://review.opendev.org/#/c/739315/ [3] https://review.opendev.org/#/c/739334/ [4] https://github.com/pallets/markupsafe/issues/116 [5] https://zuul.opendev.org/t/openstack/build/7ecd9cf100194bc99b3b70fa1e6de032 -gmann

7 17

[tripleo] rdo infrastructure maintenance
by Wesley Hayutin 24 Sep '20

24 Sep '20

Greetings, There is some maintenance on the rdo infra that is causing check and gate jobs to fail upstream. The situation is actively being worked on at this time. You may find errors in your check / gate jobs.. like the following. TASK [oooci-build-images : Download TripleO source image] 2020-09-24 10:26:35.615996 | primary | ERROR 2020-09-24 10:26:35.617685 | primary | { 2020-09-24 10:26:35.617774 | primary | "attempts": 60, 2020-09-24 10:26:35.617850 | primary | "msg": "Failed to connect to images.rdoproject.org at port 443: [Errno 113] No route to host", 2020-09-24 10:26:35.617929 | primary | "status": -1, 2020-09-24 10:26:35.618001 | primary | "url": "https://images.rdoproject.org/CentOS-8-x86_64-GenericCloud.qcow2" 2020-09-24 10:26:35.618072 | primary | } https://5134c188955ee39fd51b-cd04c057bb6c1703504e41a1dbc31642.ssl.cf5.rackc… Sorry for the trouble, we'll update this email when we're clear. 0/

1 1

[manila] Doc-a-thon event coming up next Thursday (Aug 6th)
by Victoria Martínez de la Cruz 24 Sep '20

24 Sep '20

Hi folks, We will be organizing a doc-a-thon next Thursday, August 6th, with the main goal of improving our docs for the next release. We will be gathering on our Freenode channel #openstack-manila after our weekly meeting (3pm UTC) and also using a videoconference tool (exact details TBC) to go over a curated list of opened doc bugs we have here [0]. *Your* participation is truly valued, being you an already Manila contributor or if you are interested in contributing and you didn't know how, so looking forward to seeing you there :) Cheers, Victoria [0] https://ethercalc.openstack.org/ur17jprbprxx

2 3

[oslo] PTL Non-candidacy: I mean it this time :-P
by Ben Nemec 24 Sep '20

24 Sep '20

I'm eminently familiar with midwest goodbyes, but an entire cycle to actually leave is taking it a bit far, don't you think? :-) Seriously though, this is two cycles in a row that we've had to scramble late in a cycle to finish basic community goals, mostly because of my lack of attention. Now that we've all sort of adapted to the whole global pandemic thing I'm hoping my abdication will stick this time. I'll still be around and try to help out when I can, but it's past time for me to turn the leadership of Oslo over to someone else. We've got a great team and I'm sure any one of them will do a great job! Thanks. -Ben

5 4

[all][elections][tc] Stepping down from the TC
by Jean-Philippe Evrard 24 Sep '20

24 Sep '20

Hello everyone, This is probably not a surprise for most of you, but I think it's worth writing it down: I won't be a candidate for another term at the TC. It was a pleasure to work with all of you. I am not leaving because I don't find the TC interesting anymore, quite the opposite. I will probably still lurk and follow the channels and ML. I just have switched to (yet) another duty at my employer, keeping me away from OpenStack. Next to this, I believe it's good to have some fresh members in the TC, it's been a while I am part of this family now :) For those interested by running the TC: Don't hesitate to run! We need fresh ideas and motivated people. It's not by having always the same people at the helm that OpenStack will naturally or drastically evolve. If you want to change OpenStack, be the change! Thanks to all of you. It was nice. Regards, Jean-Philippe Evrard (evrardjp)

11 11

RE: [tacker] Propose Toshiaki Takahashi for tacker core
by TAKAHASHI TOSHIAKI(高橋　敏明) 24 Sep '20

24 Sep '20

Hi Yasufumi and Team, Thank you so much! I'm glad to join core team. I'll continue to contribute for Tacker community activation! Toshiaki > -----Original Message----- > From: Yasufumi Ogawa <yasufum.o(a)gmail.com> > Sent: Thursday, September 24, 2020 6:43 PM > To: openstack-discuss(a)lists.openstack.org; TAKAHASHI TOSHIAKI(高橋　敏明) > <ts-takahashi(a)nec.com> > Subject: ##freemail## Re: [tacker] Propose Toshiaki Takahashi for tacker core > > On 2020/09/17 4:06, yasufum wrote: > > Toshiaki Takahashi (takahashi-tsc) has been so active for reviewing, > > fixing bugs and answering questions in the recent releases [1][2] and > > had several sessions on summits for Tacker. In addition, he is now > > well distinguished as one of the responsibility from ETSI-NFV standard > > community as a contributor between the standard and implementation for > > the recent contributions for both of OpenStack and ETSI. > > > > I'd appreciate if we add Toshiaki to the core team. > > > > [1] https://www.stackalytics.com/?company=nec&module=tacker > > [2] > > https://www.stackalytics.com/?user_id=t-takahashi%40ig.jp.nec.com&metr > > ic=marks > > Thank you everyone! I've seen only positive responses, so I've added Toshiaki as a > new core of tacker team. > > Congratulations, Toshiaki! > > > > > > > Regards, > > Yasufumi > >

1 0

[tacker] Propose Toshiaki Takahashi for tacker core
by yasufum 24 Sep '20

24 Sep '20

Toshiaki Takahashi (takahashi-tsc) has been so active for reviewing, fixing bugs and answering questions in the recent releases [1][2] and had several sessions on summits for Tacker. In addition, he is now well distinguished as one of the responsibility from ETSI-NFV standard community as a contributor between the standard and implementation for the recent contributions for both of OpenStack and ETSI. I'd appreciate if we add Toshiaki to the core team. [1] https://www.stackalytics.com/?company=nec&module=tacker [2] https://www.stackalytics.com/?user_id=t-takahashi%40ig.jp.nec.com&metric=ma… Regards, Yasufumi

10 9

Error log
by Issac Chan 24 Sep '20

24 Sep '20

Hi all, May you have a look on this log file? I cannot start trove guest instance database normally. Best wishes, Issac

1 0

[neutron][ovn] N/S traffic that needs SNAT (without floating IPs) will always pass through the centralized gateway nodes
by Tony Liu 24 Sep '20

24 Sep '20

Hi, I read "N/S traffic that needs SNAT (without floating IPs) will always pass through the centralized gateway nodes," in [1]. Why is that? Is SNAT on each compute node not supported by OVN, or it's about ML2 driver or provisioning? [1] https://docs.openstack.org/networking-ovn/latest/admin/refarch/refarch.html Thanks! Tony

1 1

[neutron][ovn] enable_distributed_floating_ip
by Tony Liu 24 Sep '20

24 Sep '20

Hi, Could anyone elaborate what difference this option makes to Neutron OVN ML2 driver? I assume the driver will program OVN NB differently based on true or false? Any detail is appreciated. Thanks! Tony

1 0

[election][tc] TC Candidacy
by Ghanshyam Mann 23 Sep '20

23 Sep '20

Hello Everyone, I want to announce my candidacy for another term on the TC. First of all, thanks for giving me the opportunity as the technical committee in the previous terms. It's my 7th year in upstream developer activities and overall 9th year associated with OpenStack. I really enjoy my current role in the community. I've served as QA PTL for 2 years and currently a core developer in QA projects and Nova. Also, helping Tempest plugins for bug/Tempest compatible fixes and co-leader in the policy-popup team to make Openstack API policy more consistent and secure. With my QA, Nova, policy popup team role, I mainly target cross projects work as my TC responsibility; helping all projects team for the common work like Migrating the OpenStack CI/CD from Ubuntu Xenial to Bionic in Stein cycle and Ubuntu Bionic to Focal in Victoria, dropping python2.7 and, IPv6 deployment testing are the key activities in recent cycles. In my 3rd continuous cycle as community-wide goal champion, I tried my best to help in coding/investigation across many projects. I am actively involved in programs helping new contributors in OpenStack like a mentor in the Upstream Institute Training since Barcelona Summit (Oct 2016)[1] and an active member in FirstContact SIG [2]. It's always a great experience to introduce OpenStack upstream workflow to new contributors and encourage them to start contributing which is very much needed in OpenStack. TC direction has always been valuable and helps to keep the common standards in OpenStack. There is always room for improvement and so does in TC. I expect more involvement from the community and share what they expect from TC, and bring up discussions during TC office hours or meetings. In my next term, I would like to continue doing cross-project teams work for solving the common problem in OpenStack. In the next one or two-cycle, my main target is to make OpenStack API policy more consistent and secure as part of the policy popup team. Also, improving TC and team interaction. More interaction and involvement is the key to improve OpenStack. With the merging of UC into TC, it's a great opportunity to work together with the users/operators and collect valuable feedback to implement the required or priority things. Thank you for reading and considering my candidacy. Refernce: * Blogs: https://ghanshyammann.com * Review: http://stackalytics.com/?release=all&metric=marks&user_id=ghanshyammann&pro… * Commit: http://stackalytics.com/?release=all&metric=commits&user_id=ghanshyammann&p… * Foundation Profile: https://www.openstack.org/community/members/profile/6461 * IRC (Freenode): gmann [1] https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute [2] https://wiki.openstack.org/wiki/First_Contact_SIG - Ghanshyam Mann (gmann)

1 0

[ptl][release] RC1 Deadline Tomorrow
by Sean McGinnis 23 Sep '20

23 Sep '20

Hey everyone, Just a reminder that tomorrow, September 24, is the RC1 deadline for the Victoria cycle. If you have any cycle-based deliverables, there should have been a patch proposed earlier this week. If your project is ready, and if you've merged any final critical patches for Victoria, please +1 that patch so the release team knows it is safe to proceed. If you are working on any final patches, please update the release patch as soon as those merge to point to the commit hash for the tag and branch. After RC1 and the stable/victoria branch is created, any additional bugfixes will need to merge to the master branch first, then be backported to stable/victoria. Thanks, Sean

1 0

Community voting for the 2020 Open Infrastructure Summit Superuser Awards is now open!
by Ashlee Ferguson 23 Sep '20

23 Sep '20

Hi everyone, It’s time for the community to help determine the winner of the 2020 Open Infrastructure Summit <https://www.openstack.org/summit/2020/> Superuser Awards. The Superuser Editorial Advisory Board <https://superuser.openstack.org/about> will review the nominees and determine the finalists and overall winner after the community has had a chance to review and rate nominees. Now, it’s your turn. Review the nominees <https://superuser.openstack.org/articles/meet-the-2020-superuser-awards-nom…> and rate them <https://www.surveymonkey.com/r/Superuser2020> before the deadline September 28 at 11:59 p.m. PDT <http://www.thetimenow.com/worldclock.php>. Share your top pick for the Superuser Awards on Twitter <https://twitter.com/hashtag/OpenInfraSummit?src=hashtag_click>, Facebook <https://www.facebook.com/hashtag/openinfrasummit>, and LinkedIn <https://www.linkedin.com/feed/hashtag/?keywords=openinfrasummit> with #OpenInfraSummit! Cheers, Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation

1 0

Trove images for Cluster testing.
by ARUNKUMAR PALANISAMY 23 Sep '20

23 Sep '20

Hello Team, My name is ARUNKUMAR PALANISAMY, As part of our project requirement, we are evaluating trove components and need your support for experimental datastore Image for testing cluster. (Redis, Cassandra, MongoDB, Couchbase) 1.) We are running devstack enviorment with Victoria Openstack release and with this image (trove-master-guest-ubuntu-bionic-dev.qcow2<https://tarballs.opendev.org/openstack/trove/images/trove-master-guest-ubun…>), we are able to deploy mysql instance and and getting below error while creating mongoDB instances. "ModuleNotFoundError: No module named 'trove.guestagent.datastore.experimental' " 2.) While tried creating mongoDB image with diskimage-builder<https://opendev.org/openstack/diskimage-builder> tool, but we are getting "Block device " element error. Regards, Arunkumar Palanisamy Cell: +49 172 6972490 =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

2 4

Can't delete a vm
by Szabo, Istvan (Agoda) 23 Sep '20

23 Sep '20

Hello, I have vm which is stuck in the build phase: openstack server list --all-projects --long --limit -1 | grep 94ab55d3-3e39-48d3-a9b2-505838ceb6e7 | 94ab55d3-3e39-48d3-a9b2-505838ceb6e7 | hk-qaciapp-2020 | BUILD | scheduling | NOSTATE | | CentOS-7-x86_64-1511 (14.11.2017) | 2caaef01-e2f9-4e93-961a-c2b2d4a6be82 | QA_VLAN62 | None I've tried to delete with openstack server delete, nova delete force, restarted the nova services on all management nodes, restarted the nova compute service where it was originally spawned but still visible. I see in the database in couple of places either the id and either the hostname, like in instance mapping table, instances table, nova_cell0 database ... I have an idea how to delete, so I'd spawn just a vm and check which tables are created the entries, and I would go through all tables with the problematic one and delete 1 by 1 but this will takes me hours .... Any faster way you might suggest me please? Thank you ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 9

[election][nova] PTL Candidacy for Wallaby
by Balázs Gibizer 23 Sep '20

23 Sep '20

Hi, I would like to continue serving as a Nova PTL in the Wallaby cycle. In Victoria I helped keeping Nova alive and kicking: * The team merged 56% (9/16) of the blueprints we approved for Victoria. I think the renewed runway process helped making that achievement happen. * We was also managed to reduce Nova's non triaged bug backlog from more than 100 to less than 10. * We had a productive virtual PTG and the organization of the second PTG is already underway. I intend to continue what I have started. Cheers, gibi

1 0

[largescale-sig] Next meeting: September 23, 8utc
by Thierry Carrez 23 Sep '20

23 Sep '20

Hi everyone, Our next meeting will be a EU-APAC-friendly meeting, this Wednesday, September 23 at 8 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200923T08 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - all to describe briefly how you solved metrics/billing in your deployment in https://etherpad.openstack.org/p/large-scale-sig-documentation - ttx to look into a basic test framework for oslo.metrics - masahito to push latest patches to oslo.metrics - amorin to see if oslo.metrics could be tested at OVH - ttx to file Scaling Stories forum session, with amorin and someone from penick's team to help get it off the ground Talk to you all later, -- Thierry Carrez

1 1

[Kuryr] Stepping down as PTL
by Michał Dulko 23 Sep '20

23 Sep '20

Hi, Given that it's considered healthy to have rotation in the PTL role, after serving 2.5 cycle as Kuryr PTL, I won't be a candidating in Wallaby cycle. I'm not going anywhere and I will continue to work on Kuryr projects. Thanks, Michał

2 1

[kolla] Kolla klub meeting
by Mark Goddard 23 Sep '20

23 Sep '20

Hi, Tomorrow (Thursday) sees the return of the Kolla Klub! As usual, the meeting will be at 15:00 UTC. Lets kick off with the following topics: * Quick upstream update * Improving engagement with the community in non EU/US timezones * Operator feedback Look forward to seeing you there. https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… Thanks, Mark

1 0

[kolla] Ussuri -source images now use stable branches tarballs
by Michał Nasiadka 23 Sep '20

23 Sep '20

Hello, Since [1] was merged - Kolla source type images are using stable branch tarballs for OpenStack projects - compared to latest point releases - as previously. There are some projects though, that kolla-build uses point releases for those, the list can be found in version-check tool source [2]. Users that want to build source images using latest point releases - can run tools/version-check.py with --versioned-releases option (-v) - and it will adapt sources list accordingly. [1]: https://review.opendev.org/#/c/750297/ [2]: https://opendev.org/openstack/kolla/src/branch/master/tools/version-check.p… -- Michał Nasiadka mnasiadka(a)gmail.com

1 0

[storlets] Wallaby PTG planning
by Takashi Kajinami 23 Sep '20

23 Sep '20

Hello, After discussion in IRC I booked a slot for Storlets project in the Wallaby vPTG. I created a planning etherpad[1] so please put your name/nick if you are interested to join , and also put any topics you want to discuss there. [1] https://etherpad.opendev.org/p/storlets-ptg-wallaby Currently we have a slot from 13:00 UTC booked, but if we don't see attendance from EMEA/NA, we might reschedule it to "earlier" slots since current active cores are based in APAC. Please let me know if you have any questions. Thank you Takashi

1 1

[all][elections][ptl][tc] Combined PTL/TC Nominations Kickoff
by Jeremy Stanley 23 Sep '20

23 Sep '20

Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (4 positions) are now open and will remain open until Sep 29, 2020 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/wallaby/<Project_Name or "TC">/<email_address> (for example, "candidates/wallaby/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the Ussuri to Victoria timeframe, Sep 27, 2019 00:00 UTC - Sep 29, 2020 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Oct 06, 2020 23:45 UTC through to Oct 13, 2020 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the Ussuri to Victoria timeframe, Sep 27, 2019 00:00 UTC - Sep 29, 2020 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the Ussuri to Victoria timeframe, Sep 27, 2019 00:00 UTC - Sep 29, 2020 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: nomination starts @ Sep 22, 2020 23:45 UTC nomination ends @ Sep 29, 2020 23:45 UTC campaigning starts @ Sep 29, 2020 23:45 UTC campaigning ends @ Oct 06, 2020 23:45 UTC elections start @ Oct 06, 2020 23:45 UTC elections end @ Oct 13, 2020 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2020-09-29 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials -- Jeremy Stanley on behalf of the OpenStack Technical Election Officials

1 0

[all][elections][tc] Stepping down from the TC
by Nate Johnston 22 Sep '20

22 Sep '20

All, I have decided not to run for reelection to the TC. Although I remain a part of the OpenStack community my responsibilities have shifted away from engineering, and I strongly believe that the TC should be composed of people who are actively creating or operating OpenStack on a daily basis. I am deeply appreciative for all of the support I have recieved from current and former TC members. I also want to take this chance to tell my story a bit, in hopes that it will encourage others to participate more with the TC. A year ago when I joined the TC I did not have a clear idea what to expect. I had observed a few TC meetings and brought one issue to the TC's attention, but since I did not have background on the workstreams in progress, there was a lot that I did not understand or could not contextualize. So what I did was observe, gathering an understanding of the issues and initiatives and raising my hand to participate when I felt like my efforts could make a difference. I was pleasantly surprised how many times I was able to raise my hand and work on things like community goals or proposals like distributed project leadership. The fact that I have not been around since the beginning - my first significant code contributions were merged in the Mitaka cycle - and I did not already know all the names and histories did not matter much. What mattered was a willingness to actively engage, to participate in thoughtful discernment, and when the opportunity presented itself to put in the work. I feel like I made a difference. And if you don't feel the calling to join the TC, that is fine too. Be a part of the process - join the meetings, discuss the issues that cut across projects, and have your voice heard. If you are a part of creting or using OpenStack then you are a part of the TC's constituency and the meetings are to serve you. You don't have to be a member of the TC to participate in the process. Thanks so much, Nate Johnston

7 6

Re: Ussuri CentOS 8 add mptsas driver to introspection initramfs
by Oliver Weinmann 22 Sep '20

22 Sep '20

Hi, thanks a lot. That did the trick. Now it loads the module automatically. I even added another driver and it works like a charm. :) Best Regards, Oliver Am 15. September 2020 um 0:19 schrieb Donny Davis <donny(a)fortnebula.com>: On Fri, Sep 11, 2020 at 3:25 PM Oliver Weinmann <oliver.weinmann(a)icloud.com> wrote: Hi, I already asked this question on serverfault. But I guess here is a better place. I have a very ancient hardware with a MPTSAS controller. I use this for TripleO deployment testing. With the release of Ussuri which is running CentOS8, I can no longer provision my overcloud nodes as the MPTSAS driver has been removed in CentOS8: https://www.reddit.com/r/CentOS/comments/d93unk/centos8_and_removal_mpt2sas… I managed to include the driver provided from ELrepo in the introspection image but It is not loaded automatically: All commands are run as user "stack". Extract the introspection image: cd ~ mkdir imagesnew cd imagesnew tar xvf ../ironic-python-agent.tar mkdir ~/ipa-tmp cd ~/ipa-tmp /usr/lib/dracut/skipcpio ~/imagesnew/ironic-python-agent.initramfs | zcat | cpio -ivd | pax -r Extract the contents of the mptsas driver rpm: rpm2cpio ~/kmod-mptsas-3.04.20-3.el8_2.elrepo.x86_64.rpm | pax -r Put the kernel module in the right places. To figure out where the module has to reside I installed the rpm on a already deployed node and used find to locate it. xz -c ./usr/lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko > ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/kernel/drivers/message/fusion/mptsas.ko.xz mkdir ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko sudo chown root . -R find . 2>/dev/null | sudo cpio --quiet -c -o | gzip -8 > ~/images/ironic-python-agent.initramfs Upload the new image cd ~/images openstack overcloud image upload --update-existing --image-path /home/stack/images/ Now when I start the introspection and ssh into the host I see no disks: [root@localhost ~]# fdisk -l [root@localhost ~]# lsmod | grep mptsas Once i manually load the driver, I can see the disks: [root@localhost ~]# modprobe mptsas [root@localhost ~]# lsmod | grep mptsas mptsas 69632 0 mptscsih 45056 1 mptsas mptbase 98304 2 mptsas,mptscsih scsi_transport_sas 45056 1 mptsas [root@localhost ~]# fdisk -l Disk /dev/sda: 67.1 GiB, 71999422464 bytes, 140623872 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes But how can I make it so that it will automatically load on boot? Best Regards, Oliver I guess you could try using modules-load to load the module at boot. > sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko echo "mptsas" > ./etc/modules-load.d/mptsas.conf > sudo chown root . -R Also I would have a look see at these docs to build an image using ipa builder https://docs.openstack.org/ironic-python-agent-builder/latest/ -- ~/DonnyD C: 805 814 6800 "No mission too difficult. No sacrifice too great. Duty First"

1 0

Re: Ussuri CentOS 8 add mptsas driver to introspection initramfs
by Oliver Weinmann 22 Sep '20

22 Sep '20

Hi, thanks a lot. That did the trick. Now it loads the module automatically. I even added another driver and it works like a charm. :) Best Regards, Oliver Am 15. September 2020 um 0:19 schrieb Donny Davis <donny(a)fortnebula.com>: On Fri, Sep 11, 2020 at 3:25 PM Oliver Weinmann <oliver.weinmann(a)icloud.com> wrote: Hi, I already asked this question on serverfault. But I guess here is a better place. I have a very ancient hardware with a MPTSAS controller. I use this for TripleO deployment testing. With the release of Ussuri which is running CentOS8, I can no longer provision my overcloud nodes as the MPTSAS driver has been removed in CentOS8: https://www.reddit.com/r/CentOS/comments/d93unk/centos8_and_removal_mpt2sas… I managed to include the driver provided from ELrepo in the introspection image but It is not loaded automatically: All commands are run as user "stack". Extract the introspection image: cd ~ mkdir imagesnew cd imagesnew tar xvf ../ironic-python-agent.tar mkdir ~/ipa-tmp cd ~/ipa-tmp /usr/lib/dracut/skipcpio ~/imagesnew/ironic-python-agent.initramfs | zcat | cpio -ivd | pax -r Extract the contents of the mptsas driver rpm: rpm2cpio ~/kmod-mptsas-3.04.20-3.el8_2.elrepo.x86_64.rpm | pax -r Put the kernel module in the right places. To figure out where the module has to reside I installed the rpm on a already deployed node and used find to locate it. xz -c ./usr/lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko > ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/kernel/drivers/message/fusion/mptsas.ko.xz mkdir ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko sudo chown root . -R find . 2>/dev/null | sudo cpio --quiet -c -o | gzip -8 > ~/images/ironic-python-agent.initramfs Upload the new image cd ~/images openstack overcloud image upload --update-existing --image-path /home/stack/images/ Now when I start the introspection and ssh into the host I see no disks: [root@localhost ~]# fdisk -l [root@localhost ~]# lsmod | grep mptsas Once i manually load the driver, I can see the disks: [root@localhost ~]# modprobe mptsas [root@localhost ~]# lsmod | grep mptsas mptsas 69632 0 mptscsih 45056 1 mptsas mptbase 98304 2 mptsas,mptscsih scsi_transport_sas 45056 1 mptsas [root@localhost ~]# fdisk -l Disk /dev/sda: 67.1 GiB, 71999422464 bytes, 140623872 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes But how can I make it so that it will automatically load on boot? Best Regards, Oliver I guess you could try using modules-load to load the module at boot. > sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko echo "mptsas" > ./etc/modules-load.d/mptsas.conf > sudo chown root . -R Also I would have a look see at these docs to build an image using ipa builder https://docs.openstack.org/ironic-python-agent-builder/latest/ -- ~/DonnyD C: 805 814 6800 "No mission too difficult. No sacrifice too great. Duty First"

1 0

[openstack][cinder] volume_copy_bps_limit
by Ignazio Cassano 22 Sep '20

22 Sep '20

Hello stackers, I am using cinder netapp nfs driver and I have vm performances problems during the backup of volumes. My backup tool make snapshots of volumes, then, on compute notes, it use virt-convert for creating a volume backup on another nfs backend using a different vlan. But during the virt-convert a lot of read are done on netapp and my virtual machines become very slow. I am asking if volume_copy_bps_limit can help me to mitigate. Please, anyone could help me ? Ignazio

2 2

[Neutron][QoS] Meeting cancelled today
by Rodolfo Alonso Hernandez 22 Sep '20

22 Sep '20

Hello: Due to the lack of agenda, the Neutron QoS meeting will be cancelled today (22/9/2020). Regards.

1 0

[manila][FFE] Request for "User messages panel"
by Victoria Martínez de la Cruz 22 Sep '20

22 Sep '20

Hi, I would like to ask for an FFE for the RFE "User messages panel" [0] This feature adds support for manila's user messages API to the user interface. It's implemented by this single patch [1] that already has reviews. Thanks, Victoria [0] https://blueprints.launchpad.net/manila-ui/+spec/ui-user-messages [1] https://review.opendev.org/#/c/742550/

2 1

[ops][neutron]: Anyone using Calico with neutron in production?
by Imtiaz Chowdhury 22 Sep '20

22 Sep '20

Hi all, I have some Calico related questions and am wondering if any operators in this forum have experience in running Calico with OpenStack in production environment. Thanks and regards, Imtiaz

1 0

[nova] update field cpu_info.features value
by Alexander Usov 22 Sep '20

22 Sep '20

Hi guys, Several servers in the cluster have an older version of Intel microcode. I updated one of the servers and rebooted it. After reboot: root@xxx3:~# cat /proc/cpuinfo | grep flags | tail -1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap intel_pt xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts flush_l1d root@xxx3:~# cat /proc/cpuinfo | grep micro | tail -1 microcode : 0xb000038 But the value on the controller didn't update: ~$ nova hypervisor-show 99 | grep ssbd xxx@admin:~$ I updated the value in the database, but it was immediately reverted If the way to update cpu_info.features value without deleting and adding the hypervisor? Nova version: 2:16.1.0 Thanks

2 1

[all] Forum Schedule is now LIVE!
by Kendall Nelson 22 Sep '20

22 Sep '20

Hello Everyone! The forum schedule is now live: https://www.openstack.org/summit/2020/summit-schedule/global-search?t=forum Please let myself or Jimmy McArthur know as soon as possible if you see any conflicts. Speakers will be contacted shortly (if not already) with more details about the event and your sessions. Thanks! -Kendall Nelson (diablo_rojo)

1 0

[tc] weekly update
by Mohammed Naser 21 Sep '20

21 Sep '20

Hi everyone, Here's an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # Patches ## Open Reviews - Retire devstack-plugin-pika project https://review.opendev.org/748730 - Clarify impact on releases for SIGs https://review.opendev.org/752699 - Define TC-approved release in a resolution https://review.opendev.org/752256 - Add assert:supports-standalone https://review.opendev.org/722399 - Add election schedule exceptions in charter https://review.opendev.org/751941 - Remove tc:approved-release tag https://review.opendev.org/749363 ## Project Updates - Add openstack/osops to Ops Docs and Tooling SIG https://review.opendev.org/749835 - Add python-dracclient to be owned by Hardware Vendor SIG https://review.opendev.org/745564 - Retire the devstack-plugin-zmq project https://review.opendev.org/748731 - Migrate rpm-packaging to a SIG https://review.opendev.org/752661 ## General Changes - Reinstate weekly meetings https://review.opendev.org/749279 - Resolution to define distributed leadership for projects https://review.opendev.org/744995 - Add exception for Sept 2020 term election https://review.opendev.org/751936 # Other Reminders - PTG Brainstorming: https://etherpad.opendev.org/p/tc-wallaby-ptg Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[tripleo][ansible-ceph[ussuri][rdo][centos8] fails on ansible-ceph execution.
by Ruslanas Gžibovskis 21 Sep '20

21 Sep '20

Hi all, using tripleo 13.4.0-1.el8 and ceph-ansible 4.0.25-1.el8 on CentOS8 from @centos-openstack-ussuri repo. but get [1] error. I thought it was due to not found python exec, but I saw later, when added verbosity 4, that it is able to find python3. It looks like output in paste.openstack.org is too short, not sure what was an issue, but here is a second place [2] for same full output [1] http://paste.openstack.org/show/i2XpSBiSVjuL69Ahm1sl/ [2] https://proxy.qwq.lt/ceph-ansible.html -- Ruslanas Gžibovskis +370 6030 7030

2 12

Re: Re: [openstack-ansible] OpenStack Ansible deployment fails due to lxc containers not having network connection
by Oliver Wenz 21 Sep '20

21 Sep '20

Hi Jonathan, thank you for your reply! I probably should have specified that I already changed some default values in /etc/ansible/roles/lxc_hosts/defaults/main.yml to prevent a conflict with my storage network. Here's the part that I changed: ``` lxc_net_address: 10.255.255.1 lxc_net_netmask: 255.255.255.0 lxc_net_dhcp_range: 10.255.255.2,10.255.255.253 ``` Could there be some other reference to the original default address range which causes the error? I'm also confused about dnsmasq: Running 'apt-get install dnsmasq' I discovered that it wasn't installed on the infra host yet (though installing it also didn't solve the problem). Moreover, I couldn't find dnsmasq in the prerequisites in the OSA deployment guide. Kind regards, Oliver On 03/09/2020 18:38, openstack-discuss-request(a)lists.openstack.org wrote: > Message: 1 > Date: Thu, 3 Sep 2020 16:51:51 +0100 > From: Jonathan Rosser <jonathan.rosser(a)rd.bbc.co.uk> > To: openstack-discuss(a)lists.openstack.org > Subject: Re: [openstack-ansible] OpenStack Ansible deployment fails > due to lxc containers not having network connection > Message-ID: <e6746294-ada6-0f29-cdfb-59538396a0e0(a)rd.bbc.co.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Oliver, > > The default route would normally be via eth0 in the container, which I > suspect has some issue. > > This is given an address by dnsmasq/dhcp on the host and attached to > lxcbr0. This is where I would start to look. I am straight seeing that > the default address range used for eth0 is in conflict with your storage > network, so perhaps this is also something to look at. See > https://github.com/openstack/openstack-ansible-lxc_hosts/blob/master/defaul… > <https://github.com/openstack/openstack-ansible-lxc_hosts/blob/master/defaul…> > > You join us on irc at #openstack-ansible for some 'real-time' assistance > if necessary. > > Regards, > Jonathan. > > On 03/09/2020 16:18, Oliver Wenz wrote: >> I'm trying to deploy OpenStack Ansible. When running the first playbook >> ```openstack-ansible setup-hosts.yml```, there are errors for all >> containers during the task ```[openstack_hosts : Remove the blacklisted >> packages]``` (see below) and the playbook fails. >> >> ``` >> fatal: [infra1_repo_container-1f1565cd]: FAILED! => {"changed": false, >> "cmd": "apt-get update", "msg": "E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer has a >> Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> Release' no longer has a Release file.", "rc": 100, "stderr": "E: The >> repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer >> has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> Release' no longer has a Release file. >> ", "stderr_lines": ["E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer has a >> Release file.", "E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu >> bionic-updates Release' no longer has a Release file.", "E: The >> repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release' >> no longer has a Release file.", "E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release' no longer >> has a Release file."], "stdout": "Ign:1 >> http://ubuntu.mirror.lrz.de/ubuntu bionic InRelease >> Ign:2 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates InRelease >> Ign:3 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports InRelease >> Ign:4 http://ubuntu.mirror.lrz.de/ubuntu bionic-security InRelease >> Err:5 http://ubuntu.mirror.lrz.de/ubuntu bionic Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:6 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:7 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:8 http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Reading package lists... >> ", "stdout_lines": ["Ign:1 http://ubuntu.mirror.lrz.de/ubuntu bionic >> InRelease", "Ign:2 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> InRelease", "Ign:3 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> InRelease", "Ign:4 http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> InRelease", "Err:5 http://ubuntu.mirror.lrz.de/ubuntu bionic Release", >> " Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable)", "Err:6 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-updates Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Err:7 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Err:8 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Reading package lists..."]} >> >> ``` >> >> When I attach to any container and run ```ping 192.168.100.6``` (local >> DNS), I get the same error (```connect: Network is unreachable```). >> However, when I specify an interface by running ```ping -I eth1 >> 192.168.100.6``` there is a successful connection. >> Running ```ip r``` on the infra_cinder container yields: >> ``` >> 10.0.3.0/24 dev eth2 proto kernel scope link src 10.0.3.5 >> 192.168.110.0/24 dev eth1 proto kernel scope link src 192.168.110.232 >> ``` >> so there seems to be no default route which is why the connection fails >> (similar for the other infra containers). Shouldn't OSA automatically >> configure this? I didn't find anything regarding a default route on >> containers in the Docs. >> >> Here's my openstack_user_config.yml: >> >> ``` >> cidr_networks: >> container: 192.168.110.0/24 >> tunnel: 192.168.32.0/24 >> storage: 10.0.3.0/24 >> >> used_ips: >> - "192.168.110.1,192.168.110.2" >> - "192.168.110.111" >> - "192.168.110.115" >> - "192.168.110.117,192.168.110.118" >> - "192.168.110.131,192.168.110.140" >> - "192.168.110.201,192.168.110.207" >> - "192.168.32.1,192.168.32.2" >> - "192.168.32.201,192.168.32.207" >> - "10.0.3.1" >> - "10.0.3.11,10.0.3.14" >> - "10.0.3.21,10.0.3.24" >> - "10.0.3.31,10.0.3.42" >> - "10.0.3.201,10.0.3.207" >> >> global_overrides: >> # The internal and external VIP should be different IPs, however they >> # do not need to be on separate networks. >> external_lb_vip_address: 192.168.100.168 >> internal_lb_vip_address: 192.168.110.201 >> management_bridge: "br-mgmt" >> provider_networks: >> - network: >> container_bridge: "br-mgmt" >> container_type: "veth" >> container_interface: "eth1" >> ip_from_q: "container" >> type: "raw" >> group_binds: >> - all_containers >> - hosts >> is_container_address: true >> - network: >> container_bridge: "br-vxlan" >> container_type: "veth" >> container_interface: "eth10" >> ip_from_q: "tunnel" >> type: "vxlan" >> range: "1:1000" >> net_name: "vxlan" >> group_binds: >> - neutron_linuxbridge_agent >> - network: >> container_bridge: "br-ext1" >> container_type: "veth" >> container_interface: "eth12" >> host_bind_override: "eth12" >> type: "flat" >> net_name: "ext_net" >> group_binds: >> - neutron_linuxbridge_agent >> - network: >> container_bridge: "br-storage" >> container_type: "veth" >> container_interface: "eth2" >> ip_from_q: "storage" >> type: "raw" >> group_binds: >> - glance_api >> - cinder_api >> - cinder_volume >> - nova_compute >> - swift-proxy >> >> ### >> ### Infrastructure >> ### >> >> # galera, memcache, rabbitmq, utility >> shared-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> # repository (apt cache, python packages, etc) >> repo-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> # load balancer >> haproxy_hosts: >> infra1: >> ip: 192.168.110.201 >> >> ### >> ### OpenStack >> ### >> >> os-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> identity_hosts: >> infra1: >> ip: 192.168.110.201 >> >> network_hosts: >> infra1: >> ip: 192.168.110.201 >> >> compute_hosts: >> compute1: >> ip: 192.168.110.204 >> compute2: >> ip: 192.168.110.205 >> compute3: >> ip: 192.168.110.206 >> compute4: >> ip: 192.168.110.207 >> >> storage-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> storage_hosts: >> lvm-storage1: >> ip: 192.168.110.202 >> container_vars: >> cinder_backends: >> lvm: >> volume_backend_name: LVM_iSCSI >> volume_driver: cinder.volume.drivers.lvm.LVMVolumeDriver >> volume_group: cinder_volumes >> iscsi_ip_address: "{{ cinder_storage_address }}" >> limit_container_types: cinder_volume >> >> ``` >> >> I also asked this question on the server fault stackexchange: >> https://serverfault.com/questions/1032573/openstack-ansible-deployment-fail… >> >> >> Kind regards, >> Oliver >> >> >> >

2 1

Openstack version 18.04
by ops＠clustspace.com 21 Sep '20

21 Sep '20

Hello, We are decided to change Apache CloudStack to OpenStack. Trying to install, but only Stein....As you can see we have repositories ussuri root@ops:~# apt update Hit:1 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@ops:~# But after installation we got only Stein root@ops:~# openstack --version openstack 5.2.0 Do'es anyone have idea why we can install only Stein?

3 2

[tripleo][ansible-ceph][ussuri]ceph-ansiible fails at chown stack: /tmp/ceph_ansible_tmp on distributed compute HCI node
by Ruslanas Gžibovskis 21 Sep '20

21 Sep '20

Hi all, using tripleo 13.4.0-1.el8 and ceph-ansible 4.0.25-1.el8 on CentOS8 from @centos-openstack-ussuri repo. I get error [1]. When ansi playbook tries to chown to stack user dir: /tmp/ceph_ansible_tmp, but not able to find user stack. As I understand the deployment process, should it have tripleo-admin user? Also executed ansible.sh file with ansible-playbook -vvvv [2] it also has /home/stack/config-download/v3/ceph-ansible/create_ceph_ansible_remote_tmp.log I see in default file, it has the correct things set: owner: "{{ ansible_user | default('tripleo-admin', true) }}" In undercloud.conf I do not have deployment user set, that option is commented out. I have not set any in overcloud config files... [1] http://paste.openstack.org/show/798126/ [2] http://paste.openstack.org/show/798127 -- Ruslanas Gžibovskis +370 6030 7030

2 3

[tc] weekly meeting time
by Mohammed Naser 21 Sep '20

21 Sep '20

Hi folks: Given that we've landed the change to start having weekly meetings again, it's time to start picking a time: https://doodle.com/poll/xw2wiebm2ayqxvki A few people also mentioned they wouldn't mind taking the current office hours time towards that, I guess we can try and come to an agreement if we want to do that here (or simply by voting that time on the Doodle). Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 2