January 2022 - openstack-discuss - lists.openstack.org

[sdk] R1 branch merged into master
by Artem Goncharov 25 Jan '22

25 Jan '22

Hi everybody, Just wanted to give a hint that feature/r1 branch of the OpenStackSDK is now merged into the master. While most of the challenging things are now completed the work is not finished yet, but will soon be. Most important: most of the work is backward compatible, but few things were not. I took care on keeping things working and testing, but there might be side effects that I have not expected. Please let me know if jobs in your projects start failing. Regards, Artem

2 2

[ops][nova][victoria] Power State = Suspended?
by DHilsbos＠performair.com 25 Jan '22

25 Jan '22

All; I had something unusual happen this morning; one of my VMs was showing "Suspended" under the Power State in the Horizon dashboard. I've never seen that. What does it mean? Any search that I do points me to a bunch of resources for Status Suspended. Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

4 8

[TripleO] Horizon login failed with Something went wrong error in IPv6
by Anirudh Gupta 24 Jan '22

24 Jan '22

Hi Team, We are trying to deploy the Tripleo Train with IPv6. All the overcloud control plane networks - internal, management etc are also on the IPv6 subnet. Upon successful completion of overcloud, when I am trying to open the page, it does open. But when I enter the correct login credentials, it says something went wrong. [image: image.png] Upon looking into error logs, I found 2022-01-21 12:33:34.825 324 WARNING keystone.server.flask.application [req-0660e62c-dff7-4609-89fe-225e177a84f8 f908417368a24cc685818bb5fc54fe12 - - default -] *Authorization failed. The request you have made requires authentication. from fd00:fd00:fd00:2000::359: keystone.exception.Unauthorized: The request you have made requires authentication.* where *fd00:fd00:fd00:2000::359 is my internal IP address which is reachable.* Regards Anirudh Gupta

3 2

[xena][nova] Libvirt Live Migration Lock
by Ammad Syed 24 Jan '22

24 Jan '22

Hi, I have a weird error while performing live migration of trove instances. The instance has a root disk residing on a local compute node and a second a second disk is attached from shared storage via cinder. There are two networks attached with the instance, one is vlan backed and other one is geneve. When I try to perform its live migration, it fails. I see below errors in libvirt logs and the same in nova-compute logs. Jan 19 15:56:54 host03.cloud.com libvirtd[731030]: Cannot start job (query, none, none) for domain instance-00000819; current job is (none, none, migration in) owned by (0 <null>, 0 <null>, 0 remoteDispatchDomainMigratePrepare3Params (flags=0x9b)) for (0s, 0s, 61s) Jan 19 15:56:54 host03.cloud.com libvirtd[731030]: Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainMigratePrepare3Params) Jan 19 15:36:30 host03.cloud.com libvirtd[731030]: migration successfully aborted Any advise how to fix it ? I am using below libvirt version. libvirt 6.0 qemu-kvm 4.2 kernel 5.4 nova 24.0 Ammad

1 1

[neutron] Welcome Oleg Bondarev in the drivers team
by Lajos Katona 24 Jan '22

24 Jan '22

Hi, Oleg is one of the most active and experienced developers around Neutron, and long served to be a member of the Drivers team (see: [0]). We all agreed that Oleg deserves to be part of the team and he will be a great member (see [1]), so I just added him to the neutron-drivers group. Welcome to the team Oleg! [0]: https://review.opendev.org/admin/groups/5b063c96511f090638652067cf0939da1cb… [1]: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026690.… Lajos Katona (lajoskatona)

3 2

[all][tc] What's happening in Technical Committee: summary 21st Jan, 21: Reading: 5 min
by Ghanshyam Mann 22 Jan '22

22 Jan '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-20-15.00.log.html * Next week's meeting is on 27th Jan Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 26th Jan. 2. What we completed this week: ========================= * [masakari] Transfer PTL role to suzhengwei[2] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[3]. 2 out of 9 items are completed. Open Reviews ----------------- * 4 open reviews for ongoing activities[4]. Z release cycle name ------------------------- Z release cycle naming process schedule is merged[5]. Follow the ML thread for updates[6]. Z release cycle Technical Election --------------------------------------- Its time for Z release Technical Election, I have proposed the election dates (combined PTL + TC) [7], please review and add your feedback. Remove the tags framework --------------------------------- yoctozepto has proposed the WIP patch to remove the tag framework, feel free to review and provide early feedback[8]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[9] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- No updates on this. Discussion is in-progress in ML thread[10]. No other updates from TC on this and we will set up a separate call to continue the discussion. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[12], we discussed it in this week TC meeting and there is blocker for Yoga release. We will leave this item from monitoring now and check the situation at the time of Z release election. I hope till that time, we will have more maintainer/leaders to lead this project. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [13] 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[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. Welcome back from the holidays and stay safe! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/824509 [3] https://etherpad.opendev.org/p/tc-yoga-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://review.opendev.org/c/openstack/governance/+/824201 [6] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026810.… [7] https://review.opendev.org/c/openstack/election/+/825017 [8] https://review.opendev.org/c/openstack/governance/+/822900 [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [10] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [13] https://review.opendev.org/c/openstack/governance/+/798540 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all] Nomination open for OpenStack "Z" Release Naming
by Ghanshyam Mann 22 Jan '22

22 Jan '22

Hello Everyone, We are now starting the process for the OpenStack 'Z' release name. We are a little late to start it, sorry for that. I have proposed to close the nomination on 24th Jan[1]. I am hoping that is enough time to collect the names, If not please reply to this thread or in gerrit review[1]. Once the governance patch is merged I will update the final dates of nomination close and polls here, meanwhile in parallel please start proposing the name on the wiki page. Criteria: ====== - Refer to the below governance page for the naming criteria: https://governance.openstack.org/tc/reference/release-naming.html#release-n… - Any community members can propose the name to the below wiki page: https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals We encourage all community members to participate in this process. [1] https://review.opendev.org/c/openstack/governance/+/824201 -gmann

1 2

Bug Fix - openstack-archive/syntribos
by Abdullah Zaman Babar 22 Jan '22

22 Jan '22

Dear Sir/Madam, I hope this email finds you well. Recently I was working with syntribos and I found a bug in the code which I wanted to report but the repository is archived and I'm unable to generate a pull request. Could you please guide me to contribute to the repository? It will be my first ever contribution to open-source. Regards Abdullah Zaman Babar

3 2

[gate][nova][qa] tempest-*-centos-8-stream job failing consistently since yesterday
by Ghanshyam Mann 22 Jan '22

22 Jan '22

Hello Everyone, You might have noticed that 'tempest-integrated-compute-centos-8-stream' and 'tempest tempest-full-py3-centos-8-stream' job started failing the below two tests consistently since yesterday (~7 PM CST) - https://169dddc67bd535a0361f-0632fd6194b48b475d9eb0d8f7720c6c.ssl.cf2.rackc… I have filed the bug and to unblock the gate (nova & tempest), I have pushed patch to make these job non voting until bug is fixed. - https://review.opendev.org/c/openstack/tempest/+/824740 Please hold the recheck on nova or tempest (or any other effected project). ralonsoh mentioned that this is not the same issue which is raised in - http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026682.… or may be triggered due to same root cause? -gmann

4 6

[magnum][tc] Proposing Jake Yip for core-reviewer
by Spyros Trigazis 22 Jan '22

22 Jan '22

Dear all, I would like to nominate Jake Yip for core reviewer in the magnum project. Jake has been doing code reviews for the past years in magnum at a steady rate and is running magnum as well in their organization. With very good knowledge of the magnum codebase, I am confident that Jake will help increase the pace of development in the project. Cheers, Spyros

4 3