January 2023 - openstack-discuss - lists.openstack.org

Pulling plugins from my repository
by vincent lee 22 Jan '23

22 Jan '23

Hi everyone, I would like to know where exactly I can replace the path for the GitHub repository. For example, I want to pull some plugins, such as zun_ui, blazar_dashboard, etc., from my own GitHub repository instead of the default GitHub repository. I am currently using Kolla-ansible for deploying OpenStack in the yoga version. Best, Vincent

1 0

Pulling plugins from my repository
by vincent lee 20 Jan '23

20 Jan '23

Hi all, I would like to ask where exactly I can change the default path in which plugins such as zun_ui, blazar_dashboard, etc... can be pulled from my GitHub instead of the default repository. Best, Vincent

2 1

[all][tc] What's happening in Technical Committee: summary 2023 Jan 20: Reading: 5 min
by Ghanshyam Mann 20 Jan '23

20 Jan '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Jan 18. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-18-16.00.log.html * The next TC weekly meeting will be on Jan 25 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Jan 24. 2. What we completed this week: ========================= * Removed Adjutant from inactive project list[2] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[3]. Open Reviews ----------------- * Four open reviews for ongoing activities[4]. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The horizon team discussed the 'xstatic-font-awesome' repo PyPi maintainer topic[5] in their weekly meetings and decided to hand over the maintenance to additional external maintainers. The horizon team will retire the repo from OpenStack. To clean up other OpenStack packages, I have sent a separate email[6] to audit first and then we can cleanup based on the audit results. Requesting every PTL to look and do the required step. Project updates ------------------- * Add Cinder Huawei charm[7] * Add the woodpecker charm to Openstack charms[8] Less Active/Inactive projects: ~~~~~~~~~~~~~~~~~~~~~~ * Zaqar status TC discussed and set a deadline of Jan 25th (next week's TC meeting) to check the status and take a final call on Zaqar to be included in this cycle release or not. Zaqar PTL is trying to fix the gate[9]. * Mistral status: python-mistralclient gate is also green now and their beta releases are in progress[10][11]. 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[12]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [13] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://review.opendev.org/c/openstack/governance/+/869665 [3] https://etherpad.opendev.org/p/tc-2023.1-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://github.com/openstack/xstatic-font-awesome/pull/2 [6] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848… [7] https://review.opendev.org/c/openstack/governance/+/867588 [8] https://review.opendev.org/c/openstack/governance/+/869752 [9] https://review.opendev.org/c/openstack/zaqar/+/857924/ [10] https://review.opendev.org/c/openstack/releases/+/869470 [11] https://review.opendev.org/c/openstack/releases/+/869448 [12] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [13] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

upgrade from Yoda to Zed according to the documentation
by Kaiser Wassilij 20 Jan '23

20 Jan '23

Hallo, I'm trying the openstack system upgrade from Yoda to Zed according to the documentation https://docs.openstack.org/openstack-ansible/zed/admin/upgrades/major-upgra… But I get the following errors: TASK [Clone git repos (parallel)] *********************************************************************************************************************************************************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TypeError: Value of unknown type: <class 'multiprocessing.managers.ListProxy'>, [["Failed to fetch /etc/ansible/roles/etcd\nCmd('git') failed due to: exit code(128)\n cmdline: git fetch --force --shallow-since=2022-05-27\n stderr: 'fatal: error in object: unshallow 29996b0d15ebfaacb7626ce889e26b209ed53434\nfatal: the remote end hung up unexpectedly'"], ["Failed to fetch /etc/ansible/roles/etcd\nCmd('git') failed due to: exit code(128)\n cmdline: git fetch --force --shallow-since=2022-05-27\n stderr: 'fatal: error in object: unshallow 29996b0d15ebfaacb7626ce889e26b209ed53434\nfatal: the remote end hung up unexpectedly'"], ["Role {'name': 'etcd', 'scm': 'git', 'src': 'https://github.com/noonedeadpunk/ansible-etcd' https://github.com/noonedeadpunk/ansible-etcd' , 'version': 'master', 'trackbranch': 'master', 'shallow_since': '2022-05-27', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 20, 'dest': '/etc/ansible/roles/etcd'} failed after 2 retries\n"]] fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n File \"<stdin>\", line 107, in <module>\n File \"<stdin>\", line 99, in _ansiballz_main\n File \"<stdin>\", line 47, in invoke_module\n File \"/usr/lib/python3.8/runpy.py\", line 207, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib/python3.8/runpy.py\", line 97, in _run_module_code\n _run_code(code, mod_globals, init_globals,\n File \"/usr/lib/python3.8/runpy.py\", line 87, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/modules/openstack/osa/git_requirements.py\", line 333, in <module>\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/modules/openstack/osa/git_requirements.py\", line 329, in main\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/module_utils/basic.py\", line 1533, in fail_json\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/module_utils/basic.py\", line 1506, in _return_formatted\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/module_utils/common/parameters.py\", line 887, in remove_values\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/module_utils/common/parameters.py\", line 461, in _remove_values_conditions\nTypeError: Value of unknown type: <class 'multiprocessing.managers.ListProxy'>, [[\"Failed to fetch /etc/ansible/roles/etcd\\nCmd('git') failed due to: exit code(128)\\n cmdline: git fetch --force --shallow-since=2022-05-27\\n stderr: 'fatal: error in object: unshallow 29996b0d15ebfaacb7626ce889e26b209ed53434\\nfatal: the remote end hung up unexpectedly'\"], [\"Failed to fetch /etc/ansible/roles/etcd\\nCmd('git') failed due to: exit code(128)\\n cmdline: git fetch --force --shallow-since=2022-05-27\\n stderr: 'fatal: error in object: unshallow 29996b0d15ebfaacb7626ce889e26b209ed53434\\nfatal: the remote end hung up unexpectedly'\"], [\"Role {'name': 'etcd', 'scm': 'git', 'src': 'https://github.com/noonedeadpunk/ansible-etcd' https://github.com/noonedeadpunk/ansible-etcd' , 'version': 'master', 'trackbranch': 'master', 'shallow_since': '2022-05-27', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 20, 'dest': '/etc/ansible/roles/etcd'} failed after 2 retries\\n\"]]\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} TASK [Clone git repos (with git)]******** failed: [localhost] (item={'name': 'etcd', 'scm': 'git', 'src': 'https://github.com/noonedeadpunk/ansible-etcd' https://github.com/noonedeadpunk/ansible-etcd' , 'version': 'master', 'trackbranch': 'master', 'shallow_since': '2022-05-27'}) => {"ansible_loop_var": "item", "attempts": 2, "changed": false, "cmd": ["/usr/bin/git", "fetch", "--depth", "20", "--force", "origin", "+refs/heads/master:refs/remotes/origin/master"], "item": {"name": "etcd", "scm": "git", "shallow_since": "2022-05-27", "src": "https://github.com/noonedeadpunk/ansible-etcd", "trackbranch": "master", "version": "master"}, "msg": "Failed to download remote objects and refs: fatal: error in object: unshallow 29996b0d15ebfaacb7626ce889e26b209ed53434\nfatal: the remote end hung up unexpectedly\n"} Does anyone of you have the idea? What should I do? For this reason, no further playbooks will be released. Kind regards

3 2

[openstack-ansible] Installing OpenStack with Ansible fails during Keystone playbook on TASK openstack.osa.db_setup
by jmarcelo.alencar＠gmail.com 20 Jan '23

20 Jan '23

Hello Community, I am trying to create a two machine deployment following Openstack Ansible Deployment Guide (https://docs.openstack.org/project-deploy-guide/openstack-ansible/latest/) The two machines are named targethost01 and targethost02, and I am running Ansible from deploymenthost. Every machine has 4-Core CPUs, 8 GB of RAM, and 240 GB SSD. I am using Ubuntu 22.04.1 LTS. The machine targethost01 has the following network configuration: network: version: 2 ethernets: enp5s0: dhcp4: true enp6s0: {} enp7s0: {} enp8s0: {} enp9s0: {} vlans: vlan.10: id: 10 link: enp6s0 addresses: [ ] vlan.20: id: 20 link: enp7s0 addresses: [ ] vlan.30: id: 30 link: enp8s0 addresses: [ ] vlan.40: id: 40 link: enp9s0 addresses: [ ] bridges: br-mgmt: addresses: [ 172.29.236.101/22 ] mtu: 1500 interfaces: - vlan.10 br-storage: addresses: [ 172.29.244.101/22 ] mtu: 1500 interfaces: - vlan.20 br-vlan: addresses: [] mtu: 1500 interfaces: - vlan.30 br-vxlan: addresses: [ 172.29.240.101/22 ] mtu: 1500 interfaces: - vlan.40 And targethost02 has the following network configuration: network: version: 2 ethernets: enp5s0: dhcp4: true enp6s0: {} enp7s0: {} enp8s0: {} enp9s0: {} vlans: vlan.10: id: 10 link: enp6s0 addresses: [ ] vlan.20: id: 20 link: enp7s0 addresses: [ ] vlan.30: id: 30 link: enp8s0 addresses: [ ] vlan.40: id: 40 link: enp9s0 addresses: [ ] bridges: br-mgmt: addresses: [ 172.29.236.102/22 ] mtu: 1500 interfaces: - vlan.10 br-storage: addresses: [ 172.29.244.102/22 ] mtu: 1500 interfaces: - vlan.20 br-vlan: addresses: [] mtu: 1500 interfaces: - vlan.30 br-vxlan: addresses: [ 172.29.240.102/22 ] mtu: 1500 interfaces: - vlan.40 On the deploymenthost, /etc/openstack_deploy/openstack_user_config.yml has the following: --- cidr_networks: container: 172.29.236.0/22 tunnel: 172.29.240.0/22 storage: 172.29.244.0/22 used_ips: - 172.29.236.1 - "172.29.236.100,172.29.236.200" - "172.29.240.100,172.29.240.200" - "172.29.244.100,172.29.244.200" global_overrides: internal_lb_vip_address: 172.29.236.101 external_lb_vip_address: "{{ bootstrap_host_public_address | default(ansible_facts['default_ipv4']['address']) }}" management_bridge: "br-mgmt" provider_networks: - network: group_binds: - all_containers - hosts type: "raw" container_bridge: "br-mgmt" container_interface: "eth1" container_type: "veth" ip_from_q: "container" is_container_address: true - network: group_binds: - glance_api - cinder_api - cinder_volume - nova_compute type: "raw" container_bridge: "br-storage" container_type: "veth" container_interface: "eth2" container_mtu: "9000" ip_from_q: "storage" - network: group_binds: - neutron_linuxbridge_agent container_bridge: "br-vxlan" container_type: "veth" container_interface: "eth10" container_mtu: "9000" ip_from_q: "tunnel" type: "vxlan" range: "1:1000" net_name: "vxlan" - network: group_binds: - neutron_linuxbridge_agent container_bridge: "br-vlan" container_type: "veth" container_interface: "eth11" type: "vlan" range: "101:200,301:400" net_name: "vlan" - network: group_binds: - neutron_linuxbridge_agent container_bridge: "br-vlan" container_type: "veth" container_interface: "eth12" host_bind_override: "eth12" type: "flat" net_name: "flat" shared-infra_hosts: targethost01: ip: 172.29.236.101 repo-infra_hosts: targethost01: ip: 172.29.236.101 coordination_hosts: targethost01: ip: 172.29.236.101 os-infra_hosts: targethost01: ip: 172.29.236.101 identity_hosts: targethost01: ip: 172.29.236.101 network_hosts: targethost01: ip: 172.29.236.101 compute_hosts: targethost01: ip: 172.29.236.101 targethost02: ip: 172.29.236.102 storage-infra_hosts: targethost01: ip: 172.29.236.101 storage_hosts: targethost01: ip: 172.29.236.101 Also on the deploymenthost, /etc/openstack_deploy/conf.d/haproxy.yml has the following: haproxy_hosts: targethost01: ip: 172.29.236.101 At the Run Playbooks step of the guide, the following two Ansible commands return with unreachable=0 failed=0: # openstack-ansible setup-hosts.yml # openstack-ansible setup-infrastructure.yml And verifying the database also returns no error: root@deploymenthost:/opt/openstack-ansible/playbooks# ansible galera_container -m shell \ -a "mysql -h localhost -e 'show status like \"%wsrep_cluster_%\";'" Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml " [WARNING]: Unable to parse /etc/openstack_deploy/inventory.ini as an inventory source targethost01_galera_container-5aa8474a | CHANGED | rc=0 >> Variable_name Value wsrep_cluster_weight 1 wsrep_cluster_capabilities wsrep_cluster_conf_id 1 wsrep_cluster_size 1 wsrep_cluster_state_uuid e7a0c332-97fe-11ed-b0d4-26b30049826d wsrep_cluster_status Primary But when I execute openstack-ansible setup-openstack.yml, I get this: TASK [os_keystone : Fact for apache module mod_auth_openidc to be installed] *** ok: [targethost01_keystone_container-76e9b31b] TASK [include_role : openstack.osa.db_setup] *********************************** TASK [openstack.osa.db_setup : Create database for service] ******************** failed: [targethost01_keystone_container-76e9b31b -> targethost01_utility_container-dc05dc90(172.29.238.59)] (item=None) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false} fatal: [targethost01_keystone_container-76e9b31b -> {{ _oslodb_setup_host }}]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false} PLAY RECAP ********************************************************************* targethost01_keystone_container-76e9b31b : ok=33 changed=0 unreachable=0 failed=1 skipped=8 rescued=0 ignored=0 targethost01_utility_container-dc05dc90 : ok=3 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 EXIT NOTICE [Playbook execution failure] ************************************** =============================================================================== First, how can I disable the "censored" warning? I wonder if the uncensored running could give me more clues. Second, it appears to be a problem creating the database (keystone db sync?) How can I test the database execution inside the LXC containers? I tried to log into one of the containers and ping the hosts IP and it works, so they have connectivity. I set up the passwords with: # cd /opt/openstack-ansible # ./scripts/pw-token-gen.py --file /etc/openstack_deploy/user_secrets.yml Any help? Best Regards. -- __________________________________ João Marcelo Uchôa de Alencar jmarcelo.alencar(at)gmail.com __________________________________

2 3

[Kolla-ansible] upgrade from yoga to zed on Rocky Linux
by wodel youchi 20 Jan '23

20 Jan '23

Hi, Reading the kolla documentation, I saw that Yoga is supported on Rocky 8 only and Zed is supported on Rokcy 9 only, how to do the upgrade from Yoga to Zed since we have to do OS upgrade also??? Regards.

3 5

[cinder] [glance] Image certificate validation when booting from volume
by İzzettin Erdem 20 Jan '23

20 Jan '23

Hello everyone, I have a problem about booting signed images from cinder volumes. I am currently working on OpenStack Ussuri and I have Ceph storage as cinder backend. I have completed the necessary steps to enable glance image verification according to this document [1]. Now, I can create VMs from signed images -if I do not choose the *create new volume* option-. If I try to boot from volume, it throws an error message: "Image certificate validation is not supported when booting from volume". According to [2], Cinder already has an option to use signed images and it is enabled by default, but it seems it does not work. As opposed to this, [3] explains that Cinder has no ability to verify trusted images: *"As of the 18.0.0 Rocky release, trusted image certification validation is not supported with volume-backed (boot from volume) instances. The block storage service support may be available in a future release"* Is there any way to use trusted/signed images when booting from volume? Thanks. 1 - https://docs.openstack.org/nova/ussuri/user/certificate-validation.html 2 - https://docs.openstack.org/cinder/latest/configuration/block-storage/sample… 3 - https://docs.openstack.org/nova/ussuri/user/certificate-validation.html

2 1

[cinder] festival of XS reviews 20th January 2023
by Rajat Dhasmana 19 Jan '23

19 Jan '23

Hello Argonauts, We will be having our monthly festival of XS reviews today i.e. 20th January (Friday) from 1400-1600 UTC. Following are some additional details: Date: 20th January, 2023 Time: 1400-1600 UTC Meeting link: https://bluejeans.com/556681290 etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews See you there! Thanks Rajat Dhasmana

1 0

[neutron] Neutron drivers meeting
by Rodolfo Alonso Hernandez 19 Jan '23

19 Jan '23

Hello Neutrinos: Due to the lack of agenda [1], the drivers meeting is cancelled tomorrow. See you online. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

Proposed 2023.2 "Bobcat" release schedule
by Thierry Carrez 19 Jan '23

19 Jan '23

Hi everyone, Here is the proposed schedule for the 2023.2 "Bobcat" release: https://review.opendev.org/c/openstack/releases/+/869976 For easier review, you can access the HTML rendering at: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… It's a 28-week-long cycle that places final release on Oct 4, 2023. Please comment on the review if you have objections to this or would like to make a case for targeting another week for the 2023.2 release. Thanks! -- Thierry Carrez (ttx)

1 0

[cinder] Cinder Midcycle - 2 (R-9) Summary
by Rajat Dhasmana 19 Jan '23

19 Jan '23

Hello Argonauts, The summary for midcycle-2 held on 18th January, 2023 between 1400-1600 UTC is available here[1]. Please go through the etherpad and recordings for the discussion. [1] https://wiki.openstack.org/wiki/CinderAntelopeMidCycleSummary#Session_Two:_…

1 0

[neutron][ovn] Metadata service failed after creating k8s cluster with kops
by Gene Kuo 18 Jan '23

18 Jan '23

Hi all, I'm recently trying to create Kubernetes cluster on top of OpenStack with kops. However, I found out that instances created kops are unable to get metadata from ovn-metadata-agent. I've tried creating a private network and creating instances manually and the instances are able to get metadata. After I use the same private network for kops, the whole metadata service seems to fail on that network, and new instances created manually also couldn't get metadata. From ovn-metadata-agent logs I can see that the haproxy for serving metadata is created but didn't see any logs related to instances connecting and getting metadata. Any ideas on what may happened and directions for debugging/solving the issues? Thanks! Background: OpenStack Version: Zed Deployment Method: Kolla-Ansible, Ubuntu source build Regards, Gene Kuo

1 0

OpenInfra Live - Jan. 19 at 9am CT / 15:00 UTC
by Kristin Barrientos 18 Jan '23

18 Jan '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by members of the OpenInfra Triangle user group. Episode: Distributing OpenStack Architecture with BGP and Kubernetes Integration This episode will discuss the shortcomings of layer-2 networks and how layer-3 network protocols help address those. We will take a in depth look at Red Hat OpenStack Platform 17 and its integration with FRRouting (FRR) to implement dynamic routing using BGP protocol as well as use of BFD (Bidirectional Forwarding Detection) protocol which is used for detecting network failures. We will also take a look at how ECMP is used to provide both high availability and load balancing in OpenStack control and dataplane networks. Date and time: Jan. 19 at 9 a.m. CT (15:00 UTC) You can watch us live on: YouTube: https://youtu.be/r8WLM9TM6w4 LinkedIn: https://www.linkedin.com/video/event/urn:li:ugcPost:7004177126690017280/ Facebook: www.facebook.com/events/862505974941677 <http://www.facebook.com/events/862505974941677> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Emilien Macchi, Chris Janiszewski, Maciej Lecki, and Luis Bolivar Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[cinder] Bug Report from 01-18-2023
by Sofia Enriquez 18 Jan '23

18 Jan '23

This is a bug report from 01-11-2022 to 01-18-2023. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/2003179 "Dell PowerFlex: password appears in plain text when creating a volume from an image." Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/2002535 "[NFS] Server resize failed when image volume cache enabled." Assigned to Jean Pierre Roquesalane. - https://bugs.launchpad.net/cinder/+bug/2002996 "storpool driver: drop the image-to-volume-and-back overridden methods." Unassigned. - https://bugs.launchpad.net/cinder/+bug/2002995 "storpool driver: fix the retype volume flow." Fix proposed to master. Cheers, -- 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

[cinder] 2023.1 R-9 virtual mid cycle on 18th January, 2023
by Rajat Dhasmana 18 Jan '23

18 Jan '23

Hello Argonauts, As discussed in yesterday's cinder upstream meeting[1], we will be conducting our second mid cycle on 18th January, 2023 (R-9 week). Following are the details: Date: 18th January 2023 Time: 1400-1600 UTC Meeting link: https://bluejeans.com/556681290 Etherpad: https://etherpad.opendev.org/p/cinder-antelope-midcycles Don't forget to add topics and see you there! [1] https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-01-11-14.00.l… Thanks Rajat Dhasmana

1 1

[neutron] The meetings "ping list"
by Rodolfo Alonso Hernandez 18 Jan '23

18 Jan '23

Hello Neutrinos: As suggested by some community members, we now have a "ping list" for our Neutron meetings. If you want to be pinged just before the meeting starts, you can add your IRC nickname to the meeting agenda, in the "ping list" paragraph. As commented during the Neutron meeting, this is only a courtesy ping. Please check the meeting agendas: * Neutron meeting: https://wiki.openstack.org/wiki/Network/Meetings * CI meeting: https://etherpad.opendev.org/p/neutron-ci-meetings * Drivers meeting: https://wiki.openstack.org/wiki/Meetings/NeutronDrivers If you can't edit the agenda meetings, you can request that to any Neutron core in the #openstack-neutron channel. Regards.

2 1

[all][tc] Technical Committee next weekly meeting on 2023 Jan 18 at 1600 UTC
by Ghanshyam Mann 17 Jan '23

17 Jan '23

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2023 Jan 18, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Jan 17 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[DIB][diskimage-builder] Debian Testing boot issues
by Michael Still 17 Jan '23

17 Jan '23

Has anyone else tried building Debian Testing (bookworm) images with DIB? I'm having troubles with getting them to boot, with errors that look like missing components in the initrd to me. The command I am using to build is: export ELEMENTS_PATH=elements:diskimage-builder/diskimage_builder/elements export DIB_CLOUD_INIT_DATASOURCES="ConfigDrive, OpenStack, NoCloud" export DIB_APT_MINIMAL_CREATE_INTERFACES=0 export DIB_PYTHON_VERSION=3 export DIB_RELEASE=bookworm export DIB_SF_AGENT_PACKAGE=shakenfist-agent export build_args="cloud-init cloud-init-datasources sf-agent vm" disk-image-create utilities debian debian-systemd ${build_args} -o temp.qcow2 Where shakenfist-agent / sf-agent are a custom element not really relevant to this query (I've left it for completeness). When I boot the output image, I get this: ... [ 1.906949] virtio_blk virtio2: 2/0/0 default/read/poll queues [ 1.908318] virtio_blk virtio2: [vda] 104857600 512-byte logical blocks (53.7 GB/50.0 GiB) [ 1.916912] vda: vda1 [ 1.917646] virtio_blk virtio3: 2/0/0 default/read/poll queues [ 1.917676] virtio_net virtio1 ens11: renamed from eth0 [ 1.918965] virtio_blk virtio3: [vdb] 184 512-byte logical blocks (94.2 kB/92.0 KiB) Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Warning: fsck not present, so skipping root file system [ 2.024351] EXT4-fs (vda1): mounted filesystem with ordered data mode. Quota mode: none. done. Begin: Running /scripts/local-bottom ... [ 2.041352] EXT4-fs (vda1): unmounting filesystem. GROWROOT: WARNING: resize failed: failed [flock:127] flock -x 9 /sbin/growpart: line 714: flock: not found FAILED: Error while obtaining exclusive lock on /dev/vda [ 2.057556] vda: vda1 /scripts/local-bottom/growroot: line 97: wait-for-root: not found done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory BusyBox v1.35.0 (Debian 1:1.35.0-4+b1) multi-call binary. Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS] Free initramfs and switch to another root fs: chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /, execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint. -c DEV Reopen stdio to DEV after switch -d CAPS Drop capabilities -n Dry run Target filesystem doesn't have requested /sbin/init. BusyBox v1.35.0 (Debian 1:1.35.0-4+b1) multi-call binary. Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS] Free initramfs and switch to another root fs: chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /, execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint. ... Which looks to me like I am missing fsck, flock and wait-for-root, probably in the initrd? Adding cloud-init-growpart and growroot as elements did not help, neither did ensuring that the image contained cloud-guest-utils or util-linux. I wonder if anyone else has seen this and has some hints? Thanks, Michael

1 0

Difficulties Developing a Horizon Customization Module
by Adam Cooper 17 Jan '23

17 Jan '23

Hello! I sent a message to the #openstack IRC last week, but did not receive any replies. I am attempting to create a customization module for Horizon and having difficulties getting things to function. I'm on a fork of the Xena release, and following these docs: https://docs.openstack.org/horizon/9.1.1/topics/customizing.html. At the present, I'm trying to figure out some weird behavior where having the file `openstack_dashboard/local/local_settings.py` causes Horizon to respond to every request with a 400 error. There is no information regarding this in the logs or the HTTP response as far as I can see. It does this with an empty module, or if it just contains HORIZON_CONFIG = {...}. Is there something I'm missing? I would just like to be able to debug this issue so I can actually develop the module. If this is not the right way to ask for help, I would appreciate a pointer to the correct channels. Thanks! -- Adam Cooper Cloud Computing Engineer, Security Point of Contact Chameleon Cloud University of Chicago, Argonne National Laboratory

1 0

[OSSA-2023-001] Swift: Arbitrary file access through custom S3 XML entities (CVE-2022-47950)
by Jeremy Stanley 17 Jan '23

17 Jan '23

=================================================================== OSSA-2023-001: Arbitrary file access through custom S3 XML entities =================================================================== :Date: January 17, 2023 :CVE: CVE-2022-47950 Affects ~~~~~~~ - Swift: <2.28.1, >=2.29.0 <2.29.2, ==2.30.0 Description ~~~~~~~~~~~ Sébastien Meriot (OVH) reported a vulnerability in Swift's S3 XML parser. By supplying specially crafted XML files an authenticated user may coerce the S3 API into returning arbitrary file contents from the host server resulting in unauthorized read access to potentially sensitive data; this impacts both s3api deployments (Rocky or later), and swift3 deployments (Queens and earlier, no longer actively developed). Only deployments with S3 compatibility enabled are affected. Patches ~~~~~~~ - https://review.opendev.org/870823 (2023.1/antelope) - https://review.opendev.org/870828 (Wallaby) - https://review.opendev.org/870827 (Xena) - https://review.opendev.org/870826 (Yoga) - https://review.opendev.org/870825 (Zed) Credits ~~~~~~~ - Sébastien Meriot from OVH (CVE-2022-47950) References ~~~~~~~~~~ - https://launchpad.net/bugs/1998625 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-47950 Notes ~~~~~ - The stable/wallaby branch is under extended maintenance and will receive no new point releases, but a patch for it is provided as a courtesy. -- Jeremy Stanley OpenStack Vulnerability Management Team

1 0

Re: Experience with VGPUs (Tobias Urdin)
by Karl Kloppenborg 17 Jan '23

17 Jan '23

Hi Tobias, I saw your message, interesting method to get around the transient mdev issue. Have you looked into implementing cyborg as a method to alleviate this? We are currently assessing it for a different project using nvidia A40’s. Would be keen to swap war stories and see if we can make a better solution than the current vGPU mdev support going on. Kind Regards, Karl. You can book a 30-minute meeting with me by clicking this link.<https://calendly.com/karl_rwts/30min> -- Karl Kloppenborg, Systems Engineering (BCompSc, CNCF-[KCNA, CKA, CKAD], LFCE, CompTIA Linux+ XK0-004) Real World Technology Solutions - IT People you can trust Voice | Data | IT Procurement | Managed IT rwts.com.au<http://rwts.com.au> | 1300 798 718 [uc%3fexport=download&id=1M0bR7j1-rXl-e7k5f1Rhwot6K_vfuAvn&revid=0B4fBbZ0cwq-1WFdQSExlR28rOEtUanJjOGcvQnJjMFhEMlEwPQ] Real World is a DellEMC Gold Partner This document should be read only by those persons to whom it is addressed and its content is not intended for use by any other persons. If you have received this message in error, please notify us immediately. Please also destroy and delete the message from your computer. Any unauthorised form of reproduction of this message is strictly prohibited. We are not liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt. Please consider the environment before printing this e-mail. From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Date: Tuesday, 17 January 2023 at 9:06 pm To: openstack-discuss(a)lists.openstack.org <openstack-discuss(a)lists.openstack.org> Subject: openstack-discuss Digest, Vol 51, Issue 51 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: Enable fstrim automatically on cinder thin lvm provisioning (Rajat Dhasmana) 2. Re: Experience with VGPUs (Tobias Urdin) 3. Re: [designate] Proposal to deprecate the agent framework and agent based backends (Thomas Goirand) 4. Re: Experience with VGPUs (Sylvain Bauza) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Jan 2023 10:11:27 +0530 From: Rajat Dhasmana <rdhasman(a)redhat.com> To: A Monster <amonster369(a)gmail.com> Cc: openstack-discuss <openstack-discuss(a)lists.openstack.org> Subject: Re: Enable fstrim automatically on cinder thin lvm provisioning Message-ID: <CAARK8KQ3rM9KSQ9vFP+CAVPL_xAksxfXvFuvZj8gd7FeFT6LTw(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, We've a config option 'report_discard_supported'[1] which can be added to cinder.conf that will enable trim/unmap support. Also I would like to suggest not creating new openstack-discuss threads for the same issue and reuse the first one created. As I can see these are the 3 threads for the same issue[2][3][4]. [1] https://docs.openstack.org/cinder/latest/configuration/block-storage/config… [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031789… [3] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031797… [4] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031805… Thanks Rajat Dhasmana On Tue, Jan 17, 2023 at 8:57 AM A Monster <amonster369(a)gmail.com> wrote: > I deployed openstack using kolla ansible, and used LVM as storage backend > for my cinder service, however I noticed that the lvm thin pool size keeps > increasing even though the space used by instances volumes is the same, and > after a bit of investigating I found out that I had to enable fstrim > because the data deleted inside the logical volumes was still allocated > from the thin pool perspective and I had to do fstrim on those volumes, > > how can I enable this automatically in openstack? >

1 0

Enable fstrim automatically on cinder thin lvm provisioning
by A Monster 16 Jan '23

16 Jan '23

I deployed openstack using kolla ansible, and used LVM as storage backend for my cinder service, however I noticed that the lvm thin pool size keeps increasing even though the space used by instances volumes is the same, and after a bit of investigating I found out that I had to enable fstrim because the data deleted inside the logical volumes was still allocated from the thin pool perspective and I had to do fstrim on those volumes, how can I enable this automatically in openstack?

2 1

When is client-side modified being added?
by Adisa Nicholson aka Tynamite 16 Jan '23

16 Jan '23

Hello Openstack When is client-side modified being added as a new feature? Right now I'm paying for file hosting and when I upload a file, the "date modified" isn't respected for that file. It always takes the "date modified" for the file as the current date, not the one on the file I was uploading from my computer. I've contacted the company I brought it from, and they said that client-side modified isn't supported in the Openstack API <https://docs.openstack.org/swift/latest/s3_compat.html>. What API method would this be exactly? Would it be the "object tagging" method? Do you lot have any idea when this feature would be added in, so my file uploads will respect the "date modified" metadata?

1 0

[kolla] where to find docker compose files
by garcetto 16 Jan '23

16 Jan '23

good afternoon, where can i find docker compose files for quay,io docker images used in kolla-ansible? need to undestand how are build, thank you.

2 1

Cinder LVM backend shows 100% space usage
by A Monster 16 Jan '23

16 Jan '23

I deployed openstack using kolla ansible using LVM as a backend, but after using it for a while, I ended up creating multiple volume with different sizes, but now I can no longer create new volumes, after checking lvs I found out that the thin pool created by cinder displays a 100% space usage of 20TB , but the size used by the volumes created is less than 1TB. how can I fix this isse?

1 0