August 2022 - openstack-discuss - lists.openstack.org

[Wallaby] Deployment getting failed Randomly
by Lokendra Rathour 27 Aug '22

27 Aug '22

Hi Team, we were trying to deploy OpenStack wallaby, and we see that 4 out of 5 runs deployment is getting failed for mentioned below reasons: *Error:* 2022-08-25 17:34:29.036371 | 5254004d-021e-d4db-067d-000000007b1a | TASK | Create identity internal endpoint 2022-08-25 17:34:31.176105 | 5254004d-021e-d4db-067d-000000007b1a | FATAL | Create identity internal endpoint | undercloud | error={"changed": false, "extra_data": {"data": null, "details": "The request you have made requires authentication.", "response": "{\"error\":{\"code\":401,\"message\":\"The request you have made requires authentication.\",\"title\":\"Unauthorized\"} }\n"}, "msg": "Failed to list services: Client Error for url: overcloud-public.myhsc.com <https://overcloud-public.myhsc.com:13000/v3/services> :13000/v3/services <https://overcloud-public.myhsc.com:13000/v3/services>, The request you have made requires authentication."} Debug logs: pending results.... The full traceback is: File "/tmp/ansible_openstack.cloud.endpoint_payload_qhlqb_qw/ansible_openstack.cloud.endpoint_payload.zip/ansible_collections/open stack/cloud/plugins/module_utils/openstack.py", line 407, in __call__ results = self.run() File "/tmp/ansible_openstack.cloud.endpoint_payload_qhlqb_qw/ansible_openstack.cloud.endpoint_payload.zip/ansible_collections/open stack/cloud/plugins/modules/endpoint.py", line 150, in run File "/usr/lib/python3.6/site-packages/openstack/cloud/_identity.py", line 537, in get_service return _utils._get_entity(self, 'service', name_or_id, filters) File "/usr/lib/python3.6/site-packages/openstack/cloud/_utils.py", line 197, in _get_entity entities = search(name_or_id, filters, **kwargs) File "/usr/lib/python3.6/site-packages/openstack/cloud/_identity.py", line 517, in search_services services = self.list_services() File "/usr/lib/python3.6/site-packages/openstack/cloud/_identity.py", line 501, in list_services error_message="Failed to list services") File "/usr/lib/python3.6/site-packages/keystoneauth1/adapter.py", line 395, in get return self.request(url, 'GET', **kwargs) File "/usr/lib/python3.6/site-packages/openstack/proxy.py", line 668, in request return _json_response(response, error_message=error_message) File "/usr/lib/python3.6/site-packages/openstack/proxy.py", line 646, in _json_response exceptions.raise_from_response(response, error_message=error_message) File "/usr/lib/python3.6/site-packages/openstack/exceptions.py", line 238, in raise_from_response http_status=http_status, request_id=request_id 2022-08-25 19:38:03.201899 | 5254004d-021e-7578-cd65-000000007ad6 | FATAL | Create identity internal endpoint | undercloud | er ror={ "changed": false, "extra_data": { "data": null, "details": "The request you have made requires authentication.", "response": "{\"error\":{\"code\":401,\"message\":\"The request you have made requires authentication.\",\"title\":\"Unautho rized\"}}\n" }, "invocation": { "module_args": { "api_timeout": null, "auth": null, "auth_type": null, "availability_zone": null, "ca_cert": null, "client_cert": null, "client_key": null, "enabled": true, "endpoint_interface": "internal", "interface": "public", "region": "regionOne", "region_name": null, "service": "keystone", "state": "present", "timeout": 180, "url": "http://[fd00:fd00:fd00:2000::368]:5000", "validate_certs": null, "wait": true } }, "msg": "Failed to list services: Client Error for url: https://overcloud-public.myhsc.com:13000/v3/services, The request you have made requires authentication." } DeployCommand that was used: openstack overcloud deploy --templates \ -r /home/stack/templates/roles_data.yaml \ -n /home/stack/templates/custom_network_data.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-conductor.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-overcloud.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ptp.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/tls-endpoints-public-dns.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/inject-trust-anchor-hiera.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/external-ceph.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/templates/overcloud-baremetal-deployed.yaml \ -e /home/stack/templates/networks-deployed-environment.yaml \ -e /home/stack/templates/vip-deployed-environment.yaml \ -e /home/stack/templates/environment.yaml \ -e /home/stack/templates/ironic-config.yaml \ -e /home/stack/templates/enable-tls.yaml \ -e /home/stack/templates/cloudname.yaml \ -e /home/stack/templates/my-additional-ceph-settings.yaml \ -e /home/stack/containers-prepare-parameter.yaml [Issue] we are seeing the deployment is working perfectly once and the same setting is not working perfectly in the second run. the failure rate is high. what can be the reasons behind this? *Note:* Before this, we were deploying with DNS and SSL and it was perfectly working fine in multiple reruns. But after SSL we have seen this random failure. -- ~ Lokendra skype: lokendrarathour

1 1

question about skyline apiserver and console
by mahdi n 27 Aug '22

27 Aug '22

Hello, I want to install ui skyline but I don't know how to install Does the first install the skyline api server next console? or only install skyline console ui? where must I set the keystone url ? skyline have not docs fir develop please help

3 3

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

26 Aug '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 25. Most of the meeting discussions are summarized in this email. Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-08-25-15.00.log.html * Next TC weekly meeting will be on Sept 1 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 31. 2. What we completed this week: ========================= * Retired openstack-helm-addons[2] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], Two are completed and others items are in-progress. Open Reviews ----------------- * Six open reviews for ongoing activities[4]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- Nomination for the technical election (PTL and Technical Committee) are open now[5]. We are 1 week delay in election so as per TC charter we are adding this delay as exception[6]. Request you to add your nomination before Aug 31 and also ping anyone you know is interested in the PTL or TC position. Define 2023.1 cycle testing runtime ------------------------------------------- I have proposed the testing runtime for the 2023.1 cycle[7], please review and feedback if any. 2023.1 cycle TC PTG planning ------------------------------------ I have started the PTG planning for the TC sessions. * Similar to last coupe of PTG, we are planning "TC + Leader interaction" sessions[8], please vote your available day/time in poll[8]. * I have created the etherpad[10] to collect the TC slots topics and poll to select the TC slot timing[11]. * As you know, we are planning 'Operator Hours' in this PTG where developer and operator and meet for an hour to discuss/feedback. There is a poll to know if operator want to join developer PTG slot of interested to have their own space and let developer jump in there for discussion[12] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [14] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15]16]. Project updates ------------------- * Switch requirements to distributed leadership[17] 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[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/851859 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030094.… [6] https://review.opendev.org/c/openstack/governance/+/854624 [7] https://review.opendev.org/c/openstack/governance/+/854375 [8] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030108.… [9] https://framadate.org/zsOqRxfVcmtjaPBC [10] https://etherpad.opendev.org/p/tc-2023-1-ptg [11] https://framadate.org/yi8LNQaph5wrirks [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030114.… [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] https://review.opendev.org/c/openstack/governance/+/849606 [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [17] https://review.opendev.org/c/openstack/governance/+/854685 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-5, Aug 29 - Sep 02
by Előd Illés 26 Aug '22

26 Aug '22

Development Focus ----------------- We are getting close to the end of the Zed cycle! Next week on September 1st, 2022 is the Zed-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2023.1 Antelope cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on September 1st, 2022. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/zed branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… September 1st, 2022 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also the deadline for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Zed-3 milestone (feature freeze): September 1st, 2022 (R-5 week) RC1 deadline: September 15th, 2022 (R-3 week) Final RC deadline: September 29th, 2022 (R-1 week) Final Zed release: October 5th, 2022 Next PTG: October 17-21, 2022 (virtual PTG!!!) Előd Illés irc: elodilles

1 0

[Nova] Can't Attach An Encrypted NFS (luksv1) Volume
by Sofia Enriquez 26 Aug '22

26 Aug '22

Hello Nova Team, eharney and I are working on NFS encrypted volume support [1] and [2]. I'm trying to attach an encrypted volume to a nova instance. However, this fails with "libvirt.libvirtError: internal error: unable to execute QEMU command 'blockdev-add': Image is not in qcow2 format" error. I'm using a Devstack environment (nova/cinder master branch). Last week I opened a bug report [3] and I'd like to raise some attention to it. I've proposed a WIP patch [4] with a possible solution that I'd like to get some feedback on or know if should follow a different approach. The problem is that is_luks() returns false for the NFS case, because NFS is using LUKS inside of qcow2 and not regular LUKS. Let me know what you think Thank you Sofia [1] https://review.opendev.org/c/openstack/cinder/+/597148 [2] https://review.opendev.org/c/openstack/cinder/+/749155 [3] https://bugs.launchpad.net/nova/+bug/1987311 [4] https://review.opendev.org/c/openstack/nova/+/854030 -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[charms][elections] PTL candidacy for Antelope cycle
by Alex Kavanagh 26 Aug '22

26 Aug '22

Hi All I would like to put myself forward for another cycle for the Charms PTL for the Antelope cycle. I've been a contributor to OpenStack and Charms since 2016 and a core member since mid 2016. I've also been the PTL for the last 2 cycles. Why do I want to be PTL again? The team has again achieved a huge amount, testing and supporting the charms and packages across multiple Ubuntu LTS releases (bionic, focal and now, jammy) with Charms and OpenStack support back to queens. We've (almost) transitioned to the new Charmhub ( charmhub.io) and will continue to support Queens through to the upcoming Zed release, and onto Antelope. I'd like to continue to support the team as we march forward with the responsibilities of the PTL to smooth the processes. Thanks Alex (tinwood) -- Alex Kavanagh - Software Engineer OpenStack Engineering - Data Centre Development - Canonical Ltd

1 0

[Glance] PTL non-candidacy
by Abhishek Kekane 26 Aug '22

26 Aug '22

Hi all, I'm writing this email to let you know that I'm not going to run for Glance PTL for the Antelope dev cycle, I think it's time for some new ideas and new approaches so it's a good idea to hand over the hat of PTL to a new member of the team. I've been serving Glance PTL since Ussuri, tried my best to keep Glance stable, lots of changes have been made since then, my initial focus was to improve glance-tempest coverage which we managed to do in past cycles. I would like to thank all the members of the Glance team and others for supporting me during this period. My plan is to stick around, attend to my duties as a glance core contributor, and support my successor in whatever way I can to make for a smooth transition. Thank you once again! Cheers, Abhishek Kekane

4 3

[kuryr][elections] PTL candidacy for Antelope cycle
by Roman Dobosz 26 Aug '22

26 Aug '22

Hello, I would like to announce my candidacy to be the Kuryr PTL for the next Antelope cycle. I've been Kuryr contributor since the Ussuri release and became core reviewers member at the end of Victoria cycle. In the upcoming Antelope cycle, I'd like to focus on Kuryr stability and compatibility with upcoming Kubernetes release. Another thing which I'd like to move forward is to eliminate Kuryr services restarts. Thanks, Roman Dobosz (gryf)

1 0

[election][heat][ptl] PTL non-candidacy
by Rico Lin 26 Aug '22

26 Aug '22

Hi all, As the PTL election will soon start, I would like to share my statement on not planning to run another term of Heat PTL. And instead, I encourage anyone (core reviewer or not) who is interested to put their name on. I will definitely still stay around and help with reviews and patches. *Rico Lin*

2 1

Regarding Designate Installation in ansible Playbook
by Adivya Singh 25 Aug '22

25 Aug '22

hi Team, I have made under conf.d a designate. yml file, and rerunning the setup of Openstack-setuphost but still it is not installing a Designate Container in OpenStack. Is there any Reason for this, Something i am doing right Regards Adivya Singh

2 1