- openstack-discuss - lists.openstack.org

Subject: [tc][election] gouthamr's TC Candidacy for 2024.2
by Goutham Pacha Ravi 16 Feb '24

16 Feb '24

Hello Stackers, I'm expressing my interest to join the OpenStack Technical Committee with your acceptance. I have had a long and exciting stint with OpenStack; and can probably claim to have evolved along with it. I began my active contribution journey in the Liberty release, and have had the pleasure to build a community around the OpenStack Manila project for most of this time. In many ways, my efforts here were rooted in the core ideology of this community: the fervent desire for openness that drives each decision [1]. I coupled that with my own penchant for mentoring; the result of which is a vast number of new contributors in the form of Outreachy, Google Summer of Code, Grace Hopper Celebrations, and student projects with numerous universities. All of this was done with similarly motivated fellow conspirators. This experience has helped me foster the diversity of thought in our community, and provided sustained energy to a small group of people chopping wood and carrying water around software whose relevance transcends hype cycles. I now wish to employ this energy and experience in service as a member of the TC. I set out the following goals to drive within the team: * Sustain and improve collaboration: I wish to extend TC's charter on investment opportunities with the "formal" mentorship engagements we have had in the community, including but not limited to Outreachy, GSOC, GSOD, GHC and university projects. I've new ideas here, and feel like a TC member can add a ton of excitement to this niche area of people enthusiastic to do this year on year. * Commit to a closer collaboration with adjacent communities: I am inspired by our willingness to engage with maintainers of software that work with OpenStack. My pitch is for us to identify TC representation within projects like Ceph, Kubernetes and others for active and periodic communication. * Drive long running efforts to completion: prime examples here are efforts for coherence for operators and users: Unified CLI, Limits, and Secure RBAC defaults. Thank you for considering my candidacy. I look forward to the opportunity to serve our community and contribute to the continued success of OpenStack. Warm regards, Goutham Pacha Ravi (gouthamr) [1] https://openinfra.dev/four-opens/ [2] https://review.opendev.org/c/openstack/election/+/909239

1 0

[manila][ceph] Collab Review/design discussion for Cback Share Backup driver
by Goutham Pacha Ravi 16 Feb '24

16 Feb '24

Hello Zorillas and other interested stackers, Folks at CERN have been working with Manila's share backup feature and are authoring a new backup driver for CBack [1]. We are hosting a call to dive into the implementation and discuss how the feature works with CephFS shared file systems. If this is of interest to you, please join us on: Date: 22nd February 2024 Time: 1600 UTC Location: https://meetpad.opendev.org/manila-caracal-cback-driver Etherpad: https://etherpad.opendev.org/manila-caracal-cback-driver <https://meetpad.opendev.org/manila-caracal-cback-driver> [1] https://cds.cern.ch/record/2767135?ln=en Thanks, Goutham

1 0

[ironic] PTL non-candidacy
by Jay Faulkner 16 Feb '24

16 Feb '24

As I've mentioned in IRC, and various times throughout the cycle -- I do not intend to run for PTL of Ironic for Dalmation. I encourage Ironic contributors to run for PTL and will gladly offer any assistance to whomever is elected. Thanks, Jay Faulkner Ironic PTL

1 0

[release] Release countdown for week R-6, Feb 19-23
by Elõd Illés 16 Feb '24

16 Feb '24

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on February 22nd, 2024. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2024.1 branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (February 29th, 2024) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, February 29th, 2024. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/2024.1 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2024.1 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2024.1 Caracal will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 22nd, 2024 (R-6 week) Client library freeze: February 29th, 2024 (R-5 week) Caracal-3 milestone: February 29th, 2024 (R-5 week) Cycle Highlights Due: March 7th, 2024 (R-4 week) 2024.1 Caracal final release: April 3rd, 2024 Dalmatian PTG: April 8-12, 2024 Előd Illés irc: elodilles @ #openstack-release

1 0

[keystone] Reviewathon canceled
by Dave Wilde 16 Feb '24

16 Feb '24

I’m on PTO today and won’t be able to host the reviewathon so I’m cancelling it. Please reach out if you need anything. Thanks! /Dave

1 0

[Cinder] User visible information in Volume Types
by Josephine Seifert 16 Feb '24

16 Feb '24

Hi, as discussed in the Cinder midcycle meeting: I would like to add something to the volume types to be able to see certain information. I am also working out a spec for this, but here are the options I have in mind/we have discussed yesterday: Use Cases -------------- As a non-admin user creating a volume I would like to see various information about the volume type. Some of them are already available (e.g. multiattach). While others are either not available at all or not available for non-admin users. Two of those information are: 1. Whether a volume type can be used to create encrypted volumes 2. Whether a volume type creates replicated volumes, either through Cinder or through a configured backend like ceph The first information comes from the encryption type within the volume, that is only accessible for the admin role. The second information can either be set and directly seen in the volume type extra_specs or is indirectly a part of the configuration of the backend. There might be other use cases, where an operator wants to set certain information about the volume type. As there are more and more tools that automatically create IaaS resources, those information should be accessible in a uniform way. Possible changes ------------------------ Here are a few ways to solve this problem. 1. Using the already existing user facing "properties" field. Administrators can already set key,value pairs here and user visible extra_specs can be seen in this field. This would lead to a problem in the volume scheduler, as EVERY input is going into the extra_specs table and the scheduler will try to fulfill every key=value pair a volume type requests when looking for a fitting backend for the volume. 1.a) This could be solved in creating a whitelist or blacklist, so not every extra_spec is checked in the scheduler. Either all only informational extra_specs should be ignored or a list of extra_specs, that will be checked could be created. 1.b) Another option would be to create another database table: metadata and put every key=value pair in there at the time of their creation, that should not be used in the scheduling process. The "properties" field would then be build in the API from a merge of the extra_specs and the metadata table. (This may also prevent the volume type from getting unusable, when some adds a key=value pair to the "properties", that is not meant for the scheduler - right now this would break the volume creation process) 2. Creating a new "metadata" field, that will contain such user facing information. This would include API changes to address the new view of the volume type as well as a new API endpoint to set information as key value pairs for this metadata field. A new database table for those metadata is also necessary. The downside on this is, it might confuse people, as user facing information would be in two different fields: "propertied" for multiattach, replication_enabled and AZ, but "metadata" for some things like encryption_enabled and backend_replication, etc... It would also not solve the problem, that key-value pairs not meant for scheduling purposes can still be put into the properties/extra_specs and will only lead to Errors in the scheduling process later on. 3. Facing use cases individually: 3.a) Information about whether a volume type creates encrypted volumes or not could be calculated in the API calls for list/show volume types from the presence of an encryption type. The information would be shown in the "properties" field. This would be a very minimal patch, but will not solve other use cases, that would benefit from user facing information. 3.b) Creating an extra field for the encryption in the volume type table, that is automatically set when creating or deleting an encryption type. This would need a database change and a change of the view of the volume_types. 3.c) Looking into the different drivers and how they handle internal configurable replication and whether there are ways to let OpenStack know this and propagate it to users. This is very hard to achieve, maybe even impossible without input from an operator, who configured the backends and volume types. ----- If you have any other options in mind or want to state your opinion on this, please let me know. greetings Josephine (Luzi)

2 2

Reg cinder because Iscsi and TGT giving problems
by Rohit Sansiya 15 Feb '24

15 Feb '24

Hello all, i want a new cinder because iscsi and tgt giving some problem. tell me how to configure give some handouts. version: openstack yoga os: ubuntu 20.04 multi -node i m working please help its urgent Your message is ready to be sent with the following file or link attachments: Rohit Sansiya https://sites.google.com/view/rpgcloud/research-india Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled.

1 0

How to enable or disable a hypervisor via openstack python module
by Saeed 15 Feb '24

15 Feb '24

Hello, I use this module to find if any hypervisors are disabled: https://github.com/openstack/openstacksdk I can find and see if any hypervisor is disabled and see the reason, but I didn't find any docs about how to enable (or even disable) a hypervisor. This is my code to find disabled hypervisors: import openstack > regions = ['region1', 'region2', 'region3'] > openstack.enable_logging(debug=False)disabled_hypervisors = [] > for region in regions: > conn = openstack.connect(cloud=region) # clouds.yaml > for server in conn.compute.hypervisors(details=True): > a = server.to_dict() > if a['status'] == 'disabled' and > a['service_details']['disabled_reason'] != None: > disabled_hypervisors.append({'name': a['name'], 'ip': > a['host_ip'], 'disabled_reason': a['service_details']['disabled_reason']}) Regards, Saeed

1 0

OpenStack SAML Integration and Application Cred, CLI usage
by Nazan Cengiz 15 Feb '24

15 Feb '24

Hello I want to do SAML integration in OpenStack keystone. How can SAML integration be done? How can I use Application credential and OpenStack CLI with SAML-OpenStack integration? Environment version openstack:stein keystone: 15.0.1-0ubuntu1~cloud0 keystone federation: SAML Authentication Flows: SAML2.0 WebSSO Apache authentication method: Mellon

1 0

[neutron] qrouter namespace missing in controllers - opensack ussuri
by keshav bareja 15 Feb '24

15 Feb '24

Hi Team We are experiencing an issue of reachability in some of the projects, instances in the project are not reachable. It is a project specific issue. I tried to check router details and could observe . For the project having issues, I checked the router and could see that the qrouter namespace is not present in the command "ip netns" in any of the controllers. Problem started after a reboot of one controller. Do any one has faced a similar issue and any suggestions to recover this? Regards Keshav Bareja

2 2

[Kolla][Ironic] Ironic node validation failed
by Jayesh Chaudhari 15 Feb '24

15 Feb '24

Hi All, I am following the below document for implementing Ironic in my Kolla-Ansible Cloud which is on yoga version. https://docs.openstack.org/kolla-ansible/yoga/reference/bare-metal/ironic-g… I can add a baremetal node with this in the "baremetal node list" and make it available. But when I am trying to create a nova server it fails trying to find the host. I tried to troubleshoot and find that "openstack baremetal node validate <nodeid>" command shows 1. bios - Driver ipmi does not support bios (disabled or not implemented) 2. console - Driver ipmi does not support console (disabled or not implemented) 3. deploy - Node failed to validate deploy image info. Some parameters were missing. Missing are ['instance_info.image_source'] 4. inspect - Driver ipmi does not support inspect (disabled or not implemented) 5. raid - Driver ipmi does not support raid (disabled or not implemented) 6. rescue - Driver ipmi does not support rescue (disabled or not implemented) Can you please guide me with documentation for setting these options. Or correct me if I am missing anything. Also above documents show steps to create deploy-vmlinuz and deploy-initrd only. Please guide me for steps creating deploy_kernel and deploy_ramdisk. Thanks, Jayesh

3 4

Encountering a live migration issue on Kolla Ansible Deployment
by khurshidsx＠gmail.com 15 Feb '24

15 Feb '24

Hello all, I recently set up a cluster using Kolla Ansible, but I'm encountering a live migration issue. I would appreciate any advice or insights you can provide. Error Message is rule:create_port_binding is disallowed by policy Neutron server returns request_ids: ['req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee'] Here are some logs: 2024-01-25 04:55:51.599 23 INFO neutron.api.v2.resource [req-a380e1bc-a94b-4935-be0d-76fcc94becc4 req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee 636854b888d7441eafcd21255e1378f1 b07c4b6d7b2241c187ed84f30b163817 - - default default] create failed (client error): Access was denied to this resource. 2024-01-25 04:55:51.601 23 INFO neutron.wsgi [req-a380e1bc-a94b-4935-be0d-76fcc94becc4 req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee 636854b888d7441eafcd21255e1378f1 b07c4b6d7b2241c187ed84f30b163817 - - default default] 192.168.252.254,192.168.252.12 "POST /v2.0/ports/e70fab29-d0cd-4db4-8fbc-a572da1bff64/bindings HTTP/1.1" status: 403 len: 308 time: 0.0207033 Neutron server returns request_ids: ['req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee'] 2024-01-25 04:55:51.815 19 ERROR nova.conductor.manager Neutron server returns request_ids: ['req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee'] 2024-01-25 04:55:51.815 19 ERROR nova.conductor.manager Neutron server returns request_ids: ['req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee'] Neutron server returns request_ids: ['req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee']: nova.exception.Forbidden: rule:create_port_binding is disallowed by policy

3 5

The issue of not being able to create application credentials with federated users
by Nazan Cengiz 15 Feb '24

15 Feb '24

Hello, I implemented Cyberark integration in OpenStack. I used the SAML protocol during the integration. I created user groups in Active Directory and defined these groups in Openstack. I added users to the created groups. My goal is to send requests to the OpenStack API by creating application credentials. However, the federated user added to the groups created as a result of the Cyberark integration cannot create and use application credentials. It gives the following error: Unable to create application credential. Inventory openstack:stein keystone: 15.0.1-0ubuntu1~cloud0 Can you help me solve this problem? Thanks

1 0

[cinder] 2024.1 Caracal Midcycle-2 Summary
by Rajat Dhasmana 15 Feb '24

15 Feb '24

Hello Argonauts, Following is the summary of the 2024.1 Caracal Midcycle-2 held on 14th February, 2024. https://wiki.openstack.org/wiki/CinderCaracalMidCycleSummary#Session_Two:_R… Please go through the discussion points and action items assigned to you and let me know if any modification is required. Thanks Rajat Dhasmana

1 0

[elections][tc] Self-nomination for a TC seat
by Sylvain Bauza 15 Feb '24

15 Feb '24

Howdy folks, That's now been a long time I'm thinking about running for a TC seat but I never really thought about it until today. Now, I think this is the best time for me asking you to accept me as a TC member and I'll explain why below. First, in case you don't know me yet, I'm Sylvain Bauza (bauzas on IRC), working on OpenStack since... wow, 11 years already ? I first started to test OpenStack Diablo and Essex for a SME company but eventually moved to another (and then another) position and became contributor, first to the Blazar (that time named Climate) project and then Nova for 10 years now, eventually becoming nova-core and PTL. Time flies and now I'm still there, happy with what OpenStack became. Of course, it changed. But honestly, I haven't seen more operators using it previously than now, which means that we succeeded as a team to make OpenStack useful for our users. As a Nova PTL for the previous cycles, I know how important it is to get feedback from our operators and how much this is crucial to provide help for them. The last discussions I had with the community led to me think that this motto needs to be addressed as a whole and not only on a per-project basis, hence convincing myself that I should run for a TC seat. As someone evolving from a operations position in a SME company to a core developer working with large cloud deployments, I wish I could help the TC driving some efforts into shortening the feedback loop within the community. I'd also want to help the TC provide some guidance on the new SLURP release cadence model to all the projects so that we could really achieve a skip-release upgrade that would benefit to our operators. There are a couple of other stuff I do really care and I wish to help them. CI gate stability is one of them. Having transient failures close to a milestone is not a good experience for us and we need to really address those failures as top priorities when they occur. We should somehow recognize the very fews who dedicate time on chasing those issues and fixing them, as their contributors are mostly valuable, since not a single code of code can't merge when a gate is down. Maintaining our code is another important aspect to me. Recent experiences on not-so-well-maintained dependencies led us force to evaluate all the options and those decisions aren't easy to make. As someone caring about maintaining our code for stable releases, I wish I could help the TC to correctly identify risks and benefits of breaking changes and evaluate the impact it may have on our feature delivery. Enough talk, I'll end up here, saying that after those 10 years in the community, I'm still enjoying being part of it and how much I do love working with all of you. Cheers, -Sylvain

1 0

nova-compute error
by Rohit Sansiya 14 Feb '24

14 Feb '24

Hii Sir, my all 3 compute nodes are down. and error is shown " 2024-02-15 10:27:36.467 4154697 ERROR oslo.messaging._drivers.impl_rabbit [req-650474a9-f2f3-4e05-ade4-cbedf826d16e - - - - -] Connection failed: timed out (retrying in 5.0 seconds): socket.timeout: timed out" [image: image.png] Your message is ready to be sent with the following file or link attachments: Rohit Sansiya https://sites.google.com/view/rpgcloud/research-india Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled.

1 0

[qa][centos] devstack-platform-centos-9 jobs failing
by Martin Kopec 14 Feb '24

14 Feb '24

Hello, centos-9 jobs started failing a week ago for various reasons, most often I see that tempest tests failed with 'No valid host found' https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job… Any ideas what went wrong with centos? Thanks, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

4 3

Cinder-volume
by Rohit Sansiya 14 Feb '24

14 Feb '24

Hi sir, I am unable to attach and detach the volume through gui, When I tried so it was stuck and error shows that it is unable to attach or detach. help me how to attach and detach through gui. but I can attach and detach through cmd. Your message is ready to be sent with the following file or link attachments: Rohit Sansiya https://sites.google.com/view/rpgcloud/research-india Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled.

3 3

Can't see Orchestration menu from left side in the Horizon to build VDI
by Artemio Mendoza 14 Feb '24

14 Feb '24

Hello, I'm a bit new in OpenStack but really interested and wanted to build a VDI management system based on OpenStack. So I started setting up OpenStack on VirtualBox using devstack. I used Ubuntu22.04 jammy and configured local.conf like the attached file. I tried setting up Nova, cinder, neutron, swift, glance, ceph, heat, and ceilometer components. But even though I was able to run the stack.sh command successfully, when I logged in horizon dashboard, I couldn't see the Orchestration menu item from the left side. Here is a link that I referred. https://contactchanaka.medium.com/mastering-openstack-from-installation-to-… Anybody help me please to set up a work environment to see the Orchestration menu item? Also, I would be very appreciative if anyone could share the open source/reference link to develop VDI based on OpenStack. Regards, Artemio

1 0

[all][elections][ptl][tc] Combined PTL/TC 2024.2 cycle Election Season
by Ian Y. Choi 14 Feb '24

14 Feb '24

Election details: https://governance.openstack.org/election/ The nomination period officially begins Feb 14, 2024 23:45 UTC. Please read the stipulations and timelines for candidates and electorate contained in these governance documents[1][2][3]. Due to circumstances of timing, PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. Similarly, there will only be a TC poll if there are more than 5 candidates stepping forward the available TC positions. All members of the community are encouraged to confirm their email address as described at: https://governance.openstack.org/election/#electorate There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you wish to discuss in private please email any of the election officials[4] so that we may address your concerns. Thank you, /Ian [1] https://governance.openstack.org/tc/reference/charter.html [2] https://governance.openstack.org/tc/reference/role-of-the-tc.html [3] https://docs.openstack.org/project-team-guide/ptl.html [4] https://governance.openstack.org/election/#election-officials

1 0

[Octavia] today's weekly meeting cancelled
by Gregory Thiemonge 14 Feb '24

14 Feb '24

Hi Folks, Unfortunately, I'm not able to join the weekly meeting today, so we have to cancel it. Thanks.

1 0

[cinder] 2024.1 (Caracal) R-7 virtual mid cycle - 2 (14th Feb, 2024)
by Rajat Dhasmana 14 Feb '24

14 Feb '24

Hello Argonauts, We will be conducting the second midcycle of 2024.1 (Caracal) on 14th February, 2024. Following are the details: Date: 14th February, 2024 Time: 1400-1600 UTC Meeting link: https://meet.google.com/cqw-kbpn-sxx Etherpad: https://etherpad.opendev.org/p/cinder-caracal-midcycles We have 1 week so please add your topics timely. Thanks Rajat Dhasmana

1 1

Kolla-Ansible on Ubuntu 22.04 Fluentd Image peesnt for Label Check Error
by KK CHN 14 Feb '24

14 Feb '24

List, 1. I am trying kolla-ansible all-in-one on an Ubuntu VM on Esxi7.0 ( 22.04 Desktop OS. ) 2. Followed https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html *All went well upto here * * 3. Kolla-ansible -i ./all-in-one deploy * fails with message as follows.. Ensure Fluentd Image peesnt for Label Check *vNICs on this Ubuntu VM as follows* 1. "ens192" IP => 10.x.0.128 A DHCP IP of our organization's internal N/W) 2. "ens224 IP => 10.220.0.51 3. Added another interface ens160 without IP ( UP running) in globals.yml I have used 1. "ens224" for network_interface: "ens224" 2. "ens160" for neutron_external_interface: "ens160" 3. an unused 10.220.0.24 ip as kolla_internal_vip_address: "10.220.0.24" Hope I am right doing the interface configurations in globals.yml ? correct me if I am wrong. All went well up to * pre checks .*. *1. (kolla_ansible_venv) ubuntu@ubuntu-VM:~$ kolla-ansible -i ./all-in-one bootstrap-servers* Bootstrapping servers : ansible-playbook -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e kolla_action=bootstrap-servers /home/ubuntu/ PLAY RECAP ************************************************************ ********* localhost : ok=30 changed=2 unreachable=0 failed=0 skipped=24 rescued=0 ignored=0 2. (kolla_ansible_venv) ubuntu@ubuntu-VM:~$ kolla-ansible -i ./all-in-one prechecks PLAY RECAP ************************************************************ ********* localhost : ok=99 changed=0 unreachable=0 failed=0 skipped=158 rescued=0 ignored=0 *But * * 3. Kolla-ansible -i ./all-in-one deploy * fails with message as follows.. Ensure Fluentd Image peesnt for Label Check (kolla_ansible_venv) ubuntu@ubuntu-VM:~$ kolla-ansible -i ./all-in-one deploy TASK [common : Ensure fluentd image is present for label check] **************** fatal: [localhost]: FAILED! => {"changed": true, "msg": "'Traceback (most recent call last):\\n File \"/usr/local/lib/python3.10/dist-packages/docker/api/cli PLAY RECAP ********************************************************************* localhost : ok=6 changed=0 unreachable=0 failed=1 skipped=4 rescued=0 ignored=0 What went wrong? Any hints are much appreciated !!!! Full Error Report: Fatal: [localhost]: FAILED! => {"changed": true, "msg": "'Traceback (most recent call last):\\n File \"/usr/local/lib/python3.10/dist-packages/docker/api/client.py\", line 268, in _raise_for_status\\n response.raise_for_status()\\n File \"/usr/local/lib/python3.10/dist-packages/requests/models.py\", line 1021, in raise_for_status\\n raise HTTPError(http_error_msg, response=self)\\nrequests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.44/images/create?tag=master-ubuntu-jammy-aarch64&fromImage= quay.io%2Fopenstack.kolla%2Ffluentd\\n\\nThe above exception was the direct cause of the following exception:\\n\\nTraceback (most recent call last):\\n File \"/tmp/ansible_kolla_container_payload_fnpt9ldm/ansible_kolla_container_payload.zip/ansible/modules/kolla_container.py\", line 425, in main\\n File \"/tmp/ansible_kolla_container_payload_fnpt9ldm/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_docker_worker.py\", line 522, in ensure_image\\n self.pull_image()\\n File \"/tmp/ansible_kolla_container_payload_fnpt9ldm/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_docker_worker.py\", line 209, in pull_image\\n json.loads(line.strip().decode(\\'utf-8\\')) for line in self.dc.pull(\\n File \"/usr/local/lib/python3.10/dist-packages/docker/api/image.py\", line 429, in pull\\n self._raise_for_status(response)\\n File \"/usr/local/lib/python3.10/dist-packages/docker/api/client.py\", line 270, in _raise_for_status\\n raise create_api_error_from_http_exception(e) from e\\n File \"/usr/local/lib/python3.10/dist-packages/docker/errors.py\", line 39, in create_api_error_from_http_exception\\n raise cls(e, response=response, explanation=explanation) from e\\ndocker.errors.NotFound: 404 Client Error for http+docker://localhost/v1.44/images/create?tag=master-ubuntu-jammy-aarch64&fromImage= quay.io%2Fopenstack.kolla%2Ffluentd: Not Found (\"manifest for quay.io/openstack.kolla/fluentd:master-ubuntu-jammy-aarch64 not found: manifest unknown: manifest unknown\")\\n'"} While installing kolla I have executed this as in the doc. pip install git+https://opendev.org/openstack/kolla-ansible@master Is the error above related to this step ?? If so what the solution ?/ More details as follows.. globals.yml parameters enabled ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml --- workaround_ansible_issue_8743: yes kolla_base_distro: "ubuntu" openstack_tag_suffix: "-aarch64" kolla_internal_vip_address: "10.220.0.24" network_interface: "ens224" neutron_external_interface: "ens160" ubuntu@ubuntu-VM:~$ VM details *ubuntu@ubuntu-VM:~$ cat /etc/lsb-release* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS" *ubuntu@ubuntu-VM:~$ cat /etc/hosts* 127.0.0.1 localhost 10.220.0.51 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters # BEGIN ANSIBLE GENERATED HOSTS 10.220.0.51 ubuntu-VM # END ANSIBLE GENERATED HOSTS *Thanks in advance * *Krishane*

4 3

[tc][releases][ptl][all] you don't need your own unmaintained-core group!
by Brian Rosmaita 13 Feb '24

13 Feb '24

Hello Stackers, Thank you for your help in transitioning the Yoga series to Unmaintained status. We want to stress that there is a global openstack-unmaintained-core team that, by default, has merge permissions on *all* branches in the unmaintained/* namespace. Therefore, you do *not* need to create a specific core group for your project's unmaintained branches. The aim of Unmaintained status is to free up project teams from worrying about the maintenance of old branches. Thus, by design, project core teams do not have merge powers on these branches. Instead, the merry group of stalwart volunteers who have an interest in keeping legacy branches open have taken on this responsibility. If you are interested in helping to keep Unmaintained branches alive, reach out to the openstack-unmaintained-core team members [0] and let them know your interest. They will also be following up with an email, sometime this week, outlining how to join them. To summarize: you should only create your own separate group if you want to maintain the unmaintained branches yourself and don't want the larger group to do it for you. Otherwise you have no such obligation. If you are interested in helping with the unmaintained branches, it will help the community more if you join the global team instead creating your own. Finally, anyone can propose patches to an unmaintained branch, and can +1 or -1 reviews, just like for any other branch. So there's plenty you can do even without being part of an unmaintained-core team. Thanks for your attention to this email! [0] https://review.opendev.org/admin/groups/4d728691952c04b8b2ec828eabc96b98dc1…

1 0

[nova][nova-novncproxy] handler exception: Origin header protocol does not match this host.
by Satish Patel 13 Feb '24

13 Feb '24

Folks, Life was good till I restarted nova-novncproxy services on all controller nodes after that my vnc console stopped working. I can directly connect to the vm console using vnc viewer but not from Horizon. This is not a new setup or something. What could be wrong here and how do I debug this protocol issue? This is what I have on controller nodes [vnc] novncproxy_host = 192.168.8.14 novncproxy_port = 6080 server_listen = 192.168.8.14 server_proxyclient_address = 192.168.8.14 This is what I have on all computes nodes [vnc] novncproxy_host = 192.168.8.18 novncproxy_port = 6080 server_listen = 192.168.8.18 server_proxyclient_address = 192.168.8.18 novncproxy_base_url = https://os2.example.com:6080/vnc_lite.html 2024-02-13 20:08:16.315 7 INFO nova.console.websocketproxy [-] In exit 2024-02-13 20:08:30.402 7 INFO nova.console.websocketproxy [-] WebSocket server settings: 2024-02-13 20:08:30.403 7 INFO nova.console.websocketproxy [-] - Listen on 192.168.8.14:6080 2024-02-13 20:08:30.403 7 INFO nova.console.websocketproxy [-] - Web server (no directory listings). Web root: /usr/share/novnc 2024-02-13 20:08:30.404 7 INFO nova.console.websocketproxy [-] - No SSL/TLS support (no cert file) 2024-02-13 20:08:30.404 7 INFO nova.console.websocketproxy [-] - proxying from 192.168.8.14:6080 to None:None 2024-02-13 20:08:42.800 7 DEBUG nova.console.websocketproxy [-] 192.168.8.15: new handler Process vmsg /var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py:605 2024-02-13 20:08:42.810 71 INFO nova.console.websocketproxy [-] 192.168.8.15 - - [13/Feb/2024 20:08:42] 192.168.8.15: Plain non-SSL (ws://) WebSocket connection 2024-02-13 20:08:42.810 71 INFO nova.console.websocketproxy [-] 192.168.8.15 - - [13/Feb/2024 20:08:42] 192.168.8.15: Path: '/?token=03ad44a0-b876-4725-a71f-d383c15efb63' 2024-02-13 20:08:42.832 71 DEBUG oslo_db.sqlalchemy.engines [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] MySQL server mode set to STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,TRADITIONAL,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION _check_effective_sql_mode /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_db/sqlalchemy/engines.py:335 2024-02-13 20:08:42.923 71 DEBUG nova.objects.console_auth_token [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] Validated token - console connection is ConsoleAuthToken(access_url_base='https://os2.example.com:6080/vnc_lite.html',console_type='novnc',created_at=2024-02-13T20:08:41Z,host='192.168.8.18',id=3993,instance_uuid=7b6e0c71-ea3c-4314-9a4c-1fc86d5680f2,internal_access_path=None,port=5920,token='***',updated_at=None) validate /var/lib/kolla/venv/lib/python3.10/site-packages/nova/objects/console_auth_token.py:153 2024-02-13 20:08:42.961 71 DEBUG oslo_concurrency.lockutils [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] Acquiring lock "compute-rpcapi-router" lock /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/lockutils.py:312 2024-02-13 20:08:42.961 71 DEBUG oslo_concurrency.lockutils [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] Acquired lock "compute-rpcapi-router" lock /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/lockutils.py:315 2024-02-13 20:08:42.967 71 INFO nova.compute.rpcapi [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] Automatically selected compute RPC version 6.2 from minimum service version 66 2024-02-13 20:08:42.968 71 DEBUG oslo_concurrency.lockutils [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] Releasing lock "compute-rpcapi-router" lock /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/lockutils.py:333 2024-02-13 20:08:43.008 71 INFO nova.console.websocketproxy [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] handler exception: Origin header protocol does not match this host. 2024-02-13 20:08:43.008 71 DEBUG nova.console.websocketproxy [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] exception vmsg /var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py:605 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy Traceback (most recent call last): 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 662, in top_new_client 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy client = self.do_handshake(startsock, address) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 590, in do_handshake 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.RequestHandlerClass(retsock, address, self) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/console/websocketproxy.py", line 93, in __init__ 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy websockify.ProxyRequestHandler.__init__(self, *args, **kwargs) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 87, in __init__ 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy super().__init__(req, addr, server) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/usr/lib/python3.10/http/server.py", line 668, in __init__ 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy super().__init__(*args, **kwargs) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/usr/lib/python3.10/socketserver.py", line 747, in __init__ 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.handle() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 297, in handle 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy super().handle() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/usr/lib/python3.10/http/server.py", line 433, in handle 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.handle_one_request() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websocketserver.py", line 40, in handle_one_request 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy super().handle_one_request() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/usr/lib/python3.10/http/server.py", line 421, in handle_one_request 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy method() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websocketserver.py", line 50, in _websocket_do_GET 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.handle_upgrade() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 203, in handle_upgrade 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy super().handle_upgrade() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websocketserver.py", line 77, in handle_upgrade 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.handle_websocket() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 241, in handle_websocket 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.new_websocket_client() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/console/websocketproxy.py", line 215, in new_websocket_client 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy raise exception.ValidationError(detail=detail) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy nova.exception.ValidationError: Origin header protocol does not match this host. 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy

1 0