February 2023 - openstack-discuss

[mistral] lists and dict via CLI or dashboard not possible?
by Engelmann Florian 10 Feb '23

10 Feb '23

Hello, I spent 2 hours of testing the "example" workflow "create_instance" that was created by mistral-db-manage populate. Mistral 15.0.0 (including commit: 475c5cf34588fb88f2531883c957097ada5a5fb9 Fix sorting error when type is different) I tested with the CLI (python-mistralclient 4.5.0 as well as 3.7.0) and with the horizon mistral-dashboard (including this fix: mistraldashboard/workflows/forms.py @@ -56,7 +56,7 @@ class ExecuteForm(forms.SelfHandlingForm): def handle(self, request, data): try: - data['workflow_id'] = data.pop('workflow_name') + data['wf_identifier'] = data.pop('workflow_name') data['workflow_input'] = {} for param in self.workflow_parameters: value = data.pop(param) Now it looks like mistral and the mistral-dashboard are working. But: How to enter a list or a dict to any input field? The definition of "create_instance" looks like: --- version: '2.0' create_instance: type: direct description: | Creates VM and waits till VM OS is up and running. input: - name - image_id - flavor_id - ssh_username: null - ssh_password: null # Name of previously created keypair to inject into the instance. # Either ssh credentials or keypair must be provided. - key_name: null # Security_groups: A list of security group names - security_groups: null # An ordered list of nics to be added to this server, with information about connected networks, fixed IPs, port etc. # Example: nics: [{"net-id": "27aa8c1c-d6b8-4474-b7f7-6cdcf63ac856"}] - nics: null task-defaults: on-error: - delete_vm output: ip: <% $.vm_ip %> id: <% $.vm_id %> name: <% $.name %> status: <% $.status %> tasks: create_vm: description: Initial request to create a VM. action: nova.servers_create name=<% $.name %> image=<% $.image_id %> flavor=<% $.flavor_id %> input: key_name: <% $.key_name %> security_groups: <% $.security_groups %> nics: <% $.nics %> publish: vm_id: <% task(create_vm).result.id %> on-success: - search_for_ip ... But eg, "nics" (mandatory) expects a dict: https://docs.openstack.org/python-novaclient/rocky/reference/api/novaclient… nics – An ordered list of nics (dicts) to be added to this server, with information about connected networks, fixed IPs, port etc. Beginning in microversion 2.37 this field is required and also supports a single string value of ‘auto’ or ‘none’. The ‘auto’ value means the Compute service will automatically allocate a network for the project if one is not available. This is the same behavior as not passing anything for nics before microversion 2.37. The ‘none’ value tells the Compute service to not allocate any networking for the server. and "security_groups" a list: security_groups – A list of security group names I tried all possible notations... and gave up after 2 hours. Is it possible to use that workflow from the CLI and the mistral-dashboard? How? Could anybody please provide some examples for "nics" and "security_groups"? All the best, Florian

1 1

[magnum] Other Distro for k8s
by Nguyễn Hữu Khôi 09 Feb '23

09 Feb '23

Hello guys. I know that Magnum is using Fedora Coreos for k8s. Why don't we use a long-term distro such as Ubuntu for this project? I will be more stable. and this project seems obsolete with the old version for k8s. Nguyen Huu Khoi

3 6

[all][tc] Recap of Q1 OpenInfra Board Sync with OpenStack
by Jeremy Stanley 09 Feb '23

09 Feb '23

Interested members of the OpenStack community and OpenInfra Foundation board of directors met via conference call yesterday for an informal quarterly discussion. The call lasted one hour, and primary topics of discussion were an update on the replacement translation platform and the impact of contributor diversity on project sustainability. You can find brief notes here: https://etherpad.opendev.org/p/r.f3414b0bc2932c55376fbc1babde2192 We did not discuss a next time to meet, but since we've done the past three calls approximately three months apart, I propose we schedule 20:00 UTC on Wednesday, May 10. If there are no objections in the coming days, I'll distribute a placeholder calendar file for everyone's convenience. I've also created a new pad here for brainstorming topics for the upcoming discussion: https://etherpad.opendev.org/p/2023-05-board-openstack-sync -- Jeremy Stanley

1 0

Re: [TripleO] Last maintained release of TripleO is Wallaby
by Ümit Seren 09 Feb '23

09 Feb '23

What are the implications with regards to RDO and RHOSP which are based on TripleO ? Will they move to a different deployment method or will also development seize after Zed ? Best Ümit Seren From: James Slagle <james.slagle(a)gmail.com> Date: Wednesday, 8. February 2023 at 18:38 To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Subject: [TripleO] Last maintained release of TripleO is Wallaby The team of TripleO developers, reviewers, and community have no plans to do another release of TripleO, or to continue maintaining the Zed release. This means the last maintained release of TripleO is Wallaby. The plan is to continue to maintain the train and wallaby branches of TripleO repositories under the openstack namespace. We plan to continue to run existing CI on those branches, although we anticipate reducing to a minimal set of jobs in the future. Going forward, the TripleO team expects to continue involvement in other OpenStack projects, and focus on different approaches to OpenStack deployment. The team is not aware of enough other community interest to continue to maintain the zed, master, and future branches of TripleO. Eventually, we will empty commit these branches with a pointer to Wallaby being the last release. If other interests do exist to maintain TripleO going forward, then those plans can adjust. TripleO does not plan on nominating a PTL in the current Bobcat election cycle. If a PTL-like contact is needed for train and wallaby maintenance, then someone will be nominated. I am also not sure how to reflect this project structure change within openstack/governance, and am looking for guidance on how to do so. This type of change did not seem to exactly fit within the concepts of inactive or retired projects. I can work on the patches for governance with some direction, if anyone can provide it. Thanks, and please let us know any questions or feedback about this plan. -- -- James Slagle --

8 8

Re Error by Snapshot (Wassilij Kaiser)
by Wassilij Kaiser 09 Feb '23

09 Feb '23

Hi Linux version 5.4.0-135-generic (buildd@lcy02-amd64-066) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)) #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 iscsi storage Device Stack Cluster F UUID Label /dev/sdb o2cb ED9F270C8CC64F72B889A1154BE76F64 cluster-storage /dev/mapper/instances o2cb ED9F270C8CC64F72B889A1154BE76F64 cluster-storage /dev/sde o2cb ED9F270C8CC64F72B889A1154BE76F64 cluster-storage /dev/sdd o2cb ED9F270C8CC64F72B889A1154BE76F64 cluster-storage /dev/sdc o2cb ED9F270C8CC64F72B889A1154BE76F64 cluster-storage ||/ Name Version Architecture Description +++-==============-=================-============-====================================== ii apparmor 2.13.3-7ubuntu5.1 amd64 user-space parser utility for AppArmor Compiled against library: libvirt 8.0.0 Using library: libvirt 8.0.0 Using API: QEMU 8.0.0 Running hypervisor: QEMU 4.2.1 Best regards Wassilij Kaiser

1 0

Error by Snapshot
by Wassilij Kaiser 09 Feb '23

09 Feb '23

Hi, I take a snapshot of Running Instances. The following error occurs inLibvirtd: invalid argument: disk vda does not have an active block job Feb 09 07:42:07 bc1bl08 libvirtd[3860778]: internal error: Child process (LIBVIRT_LOG_OUTPUTS=3:stderr /usr/lib/libvirt/virt-aa-helper -r -u libvirt-12acd6a6-7e6b-405e-8760-7ccbac7d9d82) unexpected exit status 1: 2023-02-09 07:42:07.356+0000: 1763455: info : l> 2023-02-09 07:42:07.356+0000: 1763455: info : hostname: bc1bl08 2023-02-09 07:42:07.356+0000: 1763455: error : virDomainDiskDefMirrorParse:8800 : unsupported configuration: unknown mirror job type '' virt-aa-helper: error: could not parse XML virt-aa-helper: error: could not get VM definition Feb 09 07:42:07 bc1bl08 libvirtd[3860778]: internal error: cannot update AppArmor profile 'libvirt-12acd6a6-7e6b-405e-8760-7ccbac7d9d82' Feb 09 07:42:07 bc1bl08 libvirtd[3860778]: Unable to restore security label on /var/lib/nova/instances/snapshots/tmp13rvs6s5/2b0ec8c400634e5d937b5d6a9e0e26ef.delta # Ansible managed DISTRIB_ID="OSA" DISTRIB_RELEASE="25.2.0" DISTRIB_CODENAME="Yoga" DISTRIB_DESCRIPTION="OpenStack-Ansible" Did any of you have the same Error and how did you solve them? I think, For this reason, snapshots are not created. Wassilij Kaiser

2 2

[octavia] Octavia management IP fragment
by Nguyễn Hữu Khôi 08 Feb '23

08 Feb '23

Hello guys. I am using octavia but I see a problem with managing octavia instances, their name and their management ip are not useful to know which LB belongs to. I hope someone will give me some solutions. Nguyen Huu Khoi

2 2

Openstack TripleO Intergration with External Prometheus
by Lokendra Rathour 08 Feb '23

08 Feb '23

Hi team, TripleO Release: Wallaby Prometheus server version: 2.37.5 Node exporter version: 1.5.0 Grafana version: 8.5.20-1 *Query:* we need to integrate Prometheus with OpenStack TripleO, please help share any documents/links to validate this test case. -- ~ Lokendra skype: lokendrarathour

2 1

Zed OVN DPDK Support
by Lazuardi Nasution 08 Feb '23

08 Feb '23

Hi, Due to the depreciation of ovn/vif_type config, I'm still confused about how to implement OVN with DPDK in the proper way. In my experience, br-int datapath_type always returns to the "system" form "netdev" everytime VIF is plugged, even if it is from the first VM created on an empty compute node. My suspicion is related to the following debug log of nova-computer. 2023-02-09 04:34:42.395 1192435 DEBUG ovsdbapp.backend.ovs_idl.transaction [-] Running txn n=1 command(idx=0): AddBridgeCommand(name=br-int, may_exist=True, datapath_type=system) do_commit /usr/lib/python3/dist-packages/ovsdbapp/backend/ovs_idl/transaction.py:90 For information, following is the compute node OVS and Chassis configuration before any VIF is plugged. root@compute01:~# ovs-vsctl list Open_vSwitch _uuid : 799b3140-fe2e-48c6-9779-679152f2eb32 bridges : [6a3b363d-99c7-47b6-9c30-167fbf18cbd8, d2d5b32e-4089-493b-870a-aa056e311b92, ea68d505-bb91-4b15-a532-b942ea9c4e9f] cur_cfg : 440 datapath_types : [netdev, system] datapaths : {netdev=90cd281a-5890-4202-b7b2-ce2fe0bc538f, system=fa3dc7b5-929f-4cad-bdf0-36dbf9ddf78e} db_version : "8.3.0" dpdk_initialized : true dpdk_version : "DPDK 21.11.2" external_ids : {hostname=compute01, ovn-bridge-datapath-type=netdev, ovn-bridge-mappings="provider:br-provider", ovn-encap-ip="10.10.203.14", ovn-encap-type=geneve, ovn-nb="tcp:haproxy.internal:6641", ovn-openflow-probe-interval="60", ovn-remote="tcp:haproxy.internal:6642", ovn-remote-probe-interval="60000", rundir="/var/run/openvswitch", system-id="673c46a0-d9a1-40f8-a164-537693fabf95"} iface_types : [bareudp, dpdk, dpdkvhostuser, dpdkvhostuserclient, erspan, geneve, gre, gtpu, internal, ip6erspan, ip6gre, lisp, patch, stt, system, tap, vxlan] manager_options : [] next_cfg : 440 other_config : {dpdk-init="true", dpdk-socket-mem="1024,1024", pmd-cpu-mask="0x000200000002000200000002", vlan-limit="0"} ovs_version : "3.0.1" ssl : [] statistics : {} system_type : ubuntu system_version : "22.04" root@compute01:~# ovs-vsctl list Bridge _uuid : ea68d505-bb91-4b15-a532-b942ea9c4e9f auto_attach : [] controller : [] datapath_id : "000006d568ea154b" datapath_type : netdev datapath_version : "<built-in>" external_ids : {netplan="true", "netplan/global/set-fail-mode"=standalone, "netplan/mcast_snooping_enable"="false", "netplan/rstp_enable"="false"} fail_mode : standalone flood_vlans : [] flow_tables : {} ipfix : [] mcast_snooping_enable: false mirrors : [] name : br-tun netflow : [] other_config : {} ports : [167cf55f-d2be-48e2-b81c-fcaa0094125b, 2deee00a-86ca-4a4a-8466-682beb2da724, eba98d21-a6d8-4a17-9303-98eb760927ab] protocols : [] rstp_enable : false rstp_status : {} sflow : [] status : {} stp_enable : false _uuid : 6a3b363d-99c7-47b6-9c30-167fbf18cbd8 auto_attach : [] controller : [] datapath_id : "00005e94f53c221f" datapath_type : netdev datapath_version : "<built-in>" external_ids : {ct-zone-049ede3f-a6b8-4498-a278-aa50f69a9340="4", ct-zone-5ba9d829-5034-4f6e-9c50-84112d316eea="3", ct-zone-65177e75-c36c-44f8-b980-8d129bad6b05_dnat="7", ct-zone-65177e75-c36c-44f8-b980-8d129bad6b05_snat="8", ct-zone-7e87f5da-3510-42aa-85b3-b87e3ed53cbd_dnat="2", ct-zone-7e87f5da-3510-42aa-85b3-b87e3ed53cbd_snat="1", ct-zone-f12fcb10-d5f1-4b96-8787-bfc5b5dee282_dnat="6", ct-zone-f12fcb10-d5f1-4b96-8787-bfc5b5dee282_snat="5", netplan="true", "netplan/global/set-fail-mode"=standalone, "netplan/mcast_snooping_enable"="false", "netplan/rstp_enable"="false", ovn-nb-cfg="119", ovn-nb-cfg-ts="1675915566313", ovn-startup-ts="1675897357360"} fail_mode : secure flood_vlans : [] flow_tables : {} ipfix : [] mcast_snooping_enable: false mirrors : [] name : br-int netflow : [] other_config : {disable-in-band="true", hwaddr="5e:94:f5:3c:22:1f"} ports : [0e30606b-00ff-4202-83a7-57505987df79, 4bf11193-ac2f-4101-9eb9-102b5c5e8bf5, 5a20376a-6ec3-49b3-af74-4ecf04636fb2, 62ef10f0-0267-42f7-ac3a-49b8b9e6d816, 8d46690a-3ea8-420f-9bf3-d2aac5f22729, a6eb963a-c410-477c-b11c-4e02ecb17450, bbc9526a-836e-42d5-a2af-85f344eeba8a, cd7200a2-834e-4488-b8ed-3b61e881d6d0, d13d01ee-9fe8-4f21-ab12-831697870e34, d9fa4b5c-77ce-42af-8014-e1f21102f2c4, f6cb742a-2afa-4f00-87d5-8c07067573f3] protocols : [] rstp_enable : false rstp_status : {} sflow : [] status : {} stp_enable : false _uuid : d2d5b32e-4089-493b-870a-aa056e311b92 auto_attach : [] controller : [] datapath_id : "00002eb3d5d23b49" datapath_type : netdev datapath_version : "<built-in>" external_ids : {netplan="true", "netplan/global/set-fail-mode"=standalone, "netplan/mcast_snooping_enable"="false", "netplan/rstp_enable"="false"} fail_mode : standalone flood_vlans : [] flow_tables : {} ipfix : [] mcast_snooping_enable: false mirrors : [] name : br-provider netflow : [] other_config : {} ports : [43d1234c-7dfb-450f-90fb-80c67bac0a9b, 811af772-eac0-4985-8125-a65958bb8c20, 87123c6a-554f-4d51-90fe-14ed709a95a9] protocols : [] rstp_enable : false rstp_status : {} sflow : [] status : {} stp_enable : false root@controller03:~# ovn-sbctl list Chassis "673c46a0-d9a1-40f8-a164-537693fabf95" _uuid : d966cc0e-14cb-4779-b433-d681849f54cd encaps : [afc6b6bb-3698-42ec-a269-579fd4bfdf27] external_ids : {} hostname : compute01 name : "673c46a0-d9a1-40f8-a164-537693fabf95" nb_cfg : 0 other_config : {ct-no-masked-label="true", datapath-type=netdev, iface-types="bareudp,dpdk,dpdkvhostuser,dpdkvhostuserclient,erspan,geneve,gre,gtpu,internal,ip6erspan,ip6gre,lisp,patch,stt,system,tap,vxlan", is-interconn="false", mac-binding-timestamp="true", ovn-bridge-mappings="provider:br-provider", ovn-chassis-mac-mappings="", ovn-cms-options="", ovn-enable-lflow-cache="true", ovn-limit-lflow-cache="", ovn-memlimit-lflow-cache-kb="", ovn-monitor-all="false", ovn-trim-limit-lflow-cache="", ovn-trim-timeout-ms="", ovn-trim-wmark-perc-lflow-cache="", port-up-notif="true"} transport_zones : [] vtep_logical_switches: [] Any clue about this situation? Best regards.

1 0

[all][election][tc]Current election statistics/summary
by Tony Breeds 08 Feb '23

08 Feb '23

Hello all, We're just over halfway through the window for PTL and TC nominations and we're low on candidates. We have a single candidate, of 5, for the TC Yours Tony.

1 0

[all][elction][ptl] Current election statistics/summary
by Tony Breeds 08 Feb '23

08 Feb '23

Hello all, We're just over halfway through the window for PTL and TC nominations and we're low on candidates. Somewhere around 15% of projects have valid candidates --- Nominations started @ 2023-02-01 23:45:00 UTC Nominations end @ 2023-02-15 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 6 days, 22:40:20 Nominations progress : 50.40% --------------------------------------------------- Projects[1][2] : 52 Projects with candidates : 7 ( 13.46%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 45 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Designate Ec2_Api Freezer Glance Heat Horizon Keystone Kolla Kuryr Magnum Manila Masakari Mistral Monasca Neutron Nova Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms Openstack_Chef Oslo Puppet_OpenStack Quality_Assurance Rally Release_Management Requirements Sahara Senlin Skyline Storlets Swift Tacker Telemetry Tripleo Trove Venus Vitrage Winstackers) =================================================== Stats gathered @ 2023-02-09 01:04:40 UTC Yours Tony. [1] These numbers currently include the projects that are run under distributed project leadership mistral[3], oslo, release and requirements [2] These numbers currently include tripleo which is in an unclear state from a governance POV [3] Mistral is currently DPL, but has a PTL candidate and *may* switch models

1 0

Re: [trove] Stopped OpenStack Trove Guest Agent Service for Development.
by Hirotaka Wakabayashi 08 Feb '23

08 Feb '23

Hello Uday, > Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory When trovestack runs with dev_mode=true, guest-agent requires the environment file "/etc/trove/controller.conf", which is created by nova on boot time, but the error message above seems to say the file does not exist. https://opendev.org/openstack/trove/src/branch/master/integration/scripts/f… I think you should make sure your DIB_CLOUD_INIT_DATASOURCES environment contains "OpenStack" when creating your image to make cloud-init create the file by using metadata service. FYI: https://docs.openstack.org/trove/latest/admin/building_guest_images.html Thanks, Hirotaka On Monday, February 6, 2023 at 11:27:27 PM GMT+9, <openstack-discuss-request(a)lists.openstack.org> wrote: 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. [osprofiler] CI broken, looks like something related to ChangeLog not generated (Sahid Orentino Ferdjaoui) 2. Re: Experience with VGPUs (Jonathan Rosser) 3. [largescale-sig] Next meeting: Feb 8, 9utc (!) (Thierry Carrez) 4. Stopped OpenStack Trove Guest Agent Service for Development. (Uday Dikshit) ---------------------------------------------------------------------- Message: 1 Date: Mon, 06 Feb 2023 12:37:39 +0000 From: Sahid Orentino Ferdjaoui <sahid.ferdjaoui(a)industrialdiscipline.com> To: openstack-discuss(a)lists.openstack.org Subject: [osprofiler] CI broken, looks like something related to ChangeLog not generated Message-ID: <Y+D0j/GDzLNh0MsX(a)system76-pc.localdomain> Content-Type: text/plain; charset=utf-8 Hello, There is a change here that is fixing functional test issues on CI. But we still have an issue with ChangeLog. https://review.opendev.org/c/openstack/osprofiler/+/840711 Looks like pbr should generate it, then we include it on history.rst. But for some reason it seems that the file is not generated or got deleted at some point. Locally that is working right. Any idea what may be the problem here? https://zuul.opendev.org/t/openstack/build/a6df711e249c4666a1a26ca6b25d6f42 Thanks, s. ------------------------------ Message: 2 Date: Mon, 6 Feb 2023 13:15:44 +0000 From: Jonathan Rosser <jonathan.rosser(a)rd.bbc.co.uk> To: openstack-discuss(a)lists.openstack.org Subject: Re: Experience with VGPUs Message-ID: <b840ea48-f19e-0b5a-b01a-b0692059f1da(a)rd.bbc.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Hi Tobias, Thankyou for posting the scripts to recreate the mdev, those are very useful and have worked OK in our environment. Managing the race conditions between the nvidia gpu manager starting, re-creating the mdev and holding off nova-compute starting until that is all complete seems quite tricky. I see the comments on https://review.opendev.org/c/openstack/nova/+/864418 and I'm also interested to know how the ordering between udev rules execution and the nvidia driver being sufficiently initialised to create mdev can be expressed. Thanks again for the scripts, Jonathan. On 17/01/2023 08:54, Tobias Urdin wrote: > Hello, > > We are using vGPUs with Nova on OpenStack Xena release and we?ve had a > fairly good experience integration > NVIDIA A10 GPUs into our cloud. > > As we see it there is some painpoints that just goes with mantaining > the GPU feature. > > - There is a very tight coupling of the NVIDIA driver in the guest > (instance) and on the compute node that needs to > ? be managed. > > - Doing maintainance need more planning i.e powering off instances, > NVIDIA driver on compute node needs to be > ? rebuilt on hypervisor if kernel is upgraded unless you?ve > implemented DKMS for that. > > - Because we?ve different flavor of GPU (we split the A10 cards into > different flavors for maximum utilization of > ? other compute resources) we added custom traits in the Placement > service to handle that, handling that with > ? a script since doing anything manually related to GPUs you will get > confused quickly. [1] > > - Since Nova does not handle recreation of mdevs (or use the new > libvirt autostart feature for mdevs) we have > ? a systemd unit that executes before the nova-compute service that > walks all the libvirt domains and does lookups > ? in Placement to recreate the mdevs before nova-compute start. [2] > [3] [4] > > Best regards > Tobias > > DISCLAIMER: Below is provided without any warranty of actually working > for you or your setup and does > very specific things that we need and is only provided to give you > some insight and help. Use at your own risk. > > [1] https://paste.opendev.org/show/b6FdfwDHnyJXR0G3XarE/ > [2] https://paste.opendev.org/show/bGtO6aIE519uysvytWv0/ > [3] https://paste.opendev.org/show/bftOEIPxlpLptkosxlL6/ > [4] https://paste.opendev.org/show/bOYBV6lhRON4ntQKYPkb/ ------------------------------ Message: 3 Date: Mon, 6 Feb 2023 14:20:50 +0100 From: Thierry Carrez <thierry(a)openstack.org> To: "openstack-discuss(a)lists.openstack.org" <openstack-discuss(a)lists.openstack.org> Subject: [largescale-sig] Next meeting: Feb 8, 9utc (!) Message-ID: <55a6e03d-3bd5-8b9d-8361-f3d54127a421(a)openstack.org> Content-Type: text/plain; charset=UTF-8; format=flowed Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC. This is a new hour, as we decided to rotate meetings between an APAC+EU time and a EU+US time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230208T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez ------------------------------ Message: 4 Date: Mon, 6 Feb 2023 07:58:30 +0000 From: Uday Dikshit <uday.dikshit(a)myrealdata.in> To: "openstack-discuss(a)lists.openstack.org" <openstack-discuss(a)lists.openstack.org> Subject: Stopped OpenStack Trove Guest Agent Service for Development. Message-ID: <BMXPR01MB2424696CCA24F08C85CDB88D8ADA9(a)BMXPR01MB2424.INDPRD01.PROD.OUTLOOK.COM> Content-Type: text/plain; charset="iso-8859-1" Hello Team We are trying to use Openstack Trove in kolla-ansible Openstack Wallaby release. We created an image using tarball as well as trovestack, we created a datastore for mysql and added version using these images. But every time we create a database instance the instance in service projects runs successfully and shows active status. But when the database instance gets stuck in build state and after the timeout it logs error in trove taskmanager of polling time out. We created a customized image with the trovestack image and configured ssh in it. Then we used this customized image to check if the guestagent was running in the instance. Here are the logs mysql-instance-1:~# journalctl -u guest-agent.service | less Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 1. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 2. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 3. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 4. Feb 04 18:10:58 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:58 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 5. Feb 04 18:10:58 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. It will be really helpful if anybody did had any idea on running trove in kolla ansible wallaby release Thanks in advance Uday Dikshit

1 0

[charms] Team Delegation proposal
by Chris MacNaughton 08 Feb '23

08 Feb '23

Hello All, <tl;dr> I would like to propose some new ACLs in Gerrit for the openstack-charms project: - openstack-core-charms - ceph-charms - network-charms - stable-maintenance </tl;dr> With an increasing focus split among the openstack-charmers team, I'm observing that people are focused on more specific subsets of the charms, and would like to propose that new ACLs are created to allow us to recognize that officially. I've chosen the breakdown above as it aligns neatly with where the focus lines are at this point, letting developers work on their specific focus areas. This proposal would not reduce permissions for anybody who is currently a core on the openstack-charms project and, in fact, future subteam core members could aspire to full openstack-charmers core as well. Ideally, this approach will let us escalate developers to "core" developers for the subteam(s) where they have demonstrated the expertise we expect in a core-charmer. It also allows a more gradual escalation to being a core in the openstack-charms project, making it a progression rather than a single destination. As a related addition, I'm appending to this proposal the creation of a stable-maintenance ACL which would allow members to manage backports without a full core-charmer grant. --- Chris MacNaughton

5 7

[cinder] Bug Report - 02-08-2023
by Sofia Enriquez 08 Feb '23

08 Feb '23

This is a bug report from 02-01-2023 to 02-08-2023. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/2004565 "non-exploitable resource exhaustion with malicious vmdk." Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/2004484 "list dependencies with tox4." Unassigned. - https://bugs.launchpad.net/cinder/+bug/2004537 "[storwize] Invalid Exception raised due to Invalid port set value." Assigned to Kumar Kanishka. Low - https://bugs.launchpad.net/cinder/+bug/2004630 "Dell PowerFlex: Unnecessary login happens." Assigned to Jean Pierre Roquesalane. - [outreachy possible first contribution] https://bugs.launchpad.net/cinder-tempest-plugin/+bug/2006594 "Inaccurate docstring test_boot_cloned_encrypted_volume." Unassigned. Cheers,

1 1

[ALL] Why we dont have an official forum?
by Nguyễn Hữu Khôi 08 Feb '23

08 Feb '23

Hello guys. Openstack is a very interesting project, many questions from users will make it grow more and more but I see that people, including me, still ask the same question. It is hard to sort or find knowledge by this way. If we hope this project spreads for people, we need a new way to share knowledge and skills, we are in the modern world but the way to access and exchange information in this project is too obsolete. This is a wall to slow down this project. Nguyen Huu Khoi

13 19

[largescale-sig] Next meeting: Feb 8, 9utc (!)
by Thierry Carrez 08 Feb '23

08 Feb '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC. This is a new hour, as we decided to rotate meetings between an APAC+EU time and a EU+US time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230208T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

slow server list
by Parsa Aminian 08 Feb '23

08 Feb '23

3 2

[ironic]Could I use x86 ironic to deploy arm bare metal node?
by 韩光宇 08 Feb '23

08 Feb '23

Hi, I deploy ironic in x86 env, could I use it to deploy arm bare metal node? My concern is mainly whether the files transferred in the tftp phase of PXE cannot be cross-architecture. Do I need to deploy a dedicated arm-architecture ironic-conductor node for arm-architecture bare metal nodes? Thanks

3 3

[TripleO] what option to enable restart compute node if it becomes unavailable/not pingable
by Ruslanas Gžibovskis 08 Feb '23

08 Feb '23

Hi all, Since TripleO is Openstack Over Openstack, and overcloud is able to recover instances if they become unavailable, how to enable/force undercloud to launch reset over redfish/idrac? Any suggestions? If that is relevant, I use ussuri, but I think this should not be relevant to the question for the option since I would like to have same enabled in latest release also. -- Ruslanas Gžibovskis +370 6030 7030

2 1

[QA] openstack-tox-py27 failures PSA
by Dariusz Smigiel 07 Feb '23

07 Feb '23

Hi Team, Recent change [1] to remove python27 from images caused issues across jobs still using python 2.7 There are a lot of projects failing due to that. [2] The solution is to update bindep.txt [3] The fix was discussed with the #opendev team and can be summarized as follows. [4] ``` 15:37 <clarkb> I think we have ~3 options: A) revert/or readd python2-dev installs B) ask projects to fix their broken bindep.txts (something we've asked for for years at this point) or C) update -py27 jobs to explicitly install python2 for you ``` I hope it helps. Best regards, Dariusz [1]: https://review.opendev.org/c/openstack/project-config/+/872476/ [2]: https://zuul.opendev.org/t/openstack/builds?job_name=openstack-tox-py27&ski… [3]: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/872983 [4]: https://meetings.opendev.org/irclogs/%23opendev/%23opendev.2023-02-07.log.h…

4 4

Updating copyConditions for Gerrit 3.7
by Ian Wienand 07 Feb '23

07 Feb '23

Hello, Change [1] modifies our Gerrit ACL files to move from the deprecated copy conditionals flags. In simpler terms, these are the flags that set rules for labels about "+2/-2 votes aren't removed when new changesets are updated" or "keep votes when a trivial rebase is made". Projects that have made custom labels (things like "Review-Priority", "Backport-Candidate", etc.) will have specified these as part of the label configuration. There should be no change to the rules applied to labels from this transition; the old rules have been translated into the new format. However, a double check is always welcome; if you project uses custom labels you might like to quickly look at [1]. We plan to merge this change in a few days. In going through all projects, I did notice that projects have perhaps copy-pasted the label/rules and possibly they are not always working as intended. If you use custom labels, it might be an idea to just again double-check the rules are what you want for your project. The new format is quite simple; described at [2] -- basically if the query matches on the new changeset, using standard Gerrit searching rules, then the votes will be copied forward to the new changeset. We are aware that Gerrit 3.6 changed the UI for showing custom labels, and the custom labels are less visible by default. We have raised some of the issues upstream [3]. So far there hasn't been a lot of community engagement with this, but we will keep the discussion going. It is good to remember that Gerrit does have a quite powerful ability to make customised dashboards, and we have gerrit-dash-creator (see samples at [4]) to help as well. Thanks, -i [1] https://review.opendev.org/c/openstack/project-config/+/867931 [2] https://gerrit-review.googlesource.com/Documentation/config-labels.html#lab… [3] https://groups.google.com/g/repo-discuss/c/gYVD-iBR9Ow [4] https://gerrit-dash-creator.readthedocs.io/en/latest/dashboards/index.html

1 0

[all][tc] Technical Committee next weekly meeting on 2023 Feb 8 at 1600 UTC
by Ghanshyam Mann 07 Feb '23

07 Feb '23

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

1 1

Hi, I am watcher ptl chenker. Could you help analyze watcher py38 error？thanks!
by 陈克 07 Feb '23

07 Feb '23

On the surface, the py38 unit test error. But after further analysis, I found that the use cases of failure are all because stevedore cannot be loaded. Here's what I do: 1、Analyzed the version of stevedore 4.1.1 looks like there is no problem. 2、Searched the merged code in watcher history, and found no suspicious points The gerrit link: 871531 Looking forward to your reply. Thanks!

1 1

[keystone] Weekly Meeting Cancelled
by Dave Wilde 07 Feb '23

07 Feb '23

Due to unforeseen circumstances I have to cancel the Keystone meeting this week. Sorry for the late notice, please reach out if you need anything. /Dave

1 0

[kolla][kolla-ansible][skyline] skyline kolla-ansible patches need review
by 朱博祥 07 Feb '23

07 Feb '23

Hi, Now the kolla patch[0] of skyline has been merged. And still two kolla-ansible patches[1][2] of skyline need review. All patches have been ready for review. And the CI has been passed. If you have some questions about them, welcome to review and write your comments. :) Thanks, Boxiang [0] https://review.opendev.org/c/openstack/kolla/+/826948 <https://review.opendev.org/c/openstack/kolla/+/826948> [1] https://review.opendev.org/c/openstack/kolla-ansible/+/828464 <https://review.opendev.org/c/openstack/kolla-ansible/+/828464> [2] https://review.opendev.org/c/openstack/kolla-ansible/+/861687 <https://review.opendev.org/c/openstack/kolla-ansible/+/861687>

1 0

[TripleO] Integrating external Prometheus with openstack TripleO wallaby
by Kushagra Gupta 07 Feb '23

07 Feb '23

Hi team, We have a tripleO environment. Our tripleO environment consists of 2 compute nodes, 3 controller nodes, and 1 undercloud node. TripleO Release: Wallaby We have also deployed an external Prometheus server along with a node exporter on a separate node. On this node, we have also installed Grafana. Prometheus server version: 2.37.5 Node exporter version: 1.5.0 Grafana version: 8.5.20-1 Goal: We need to monitor the instances launched on the compute nodes using Prometheus and visualize the metrics using Grafana. Could anyone help us integrate an external Prometheus server with a tripleO environment? Thanks and Regards Kushagra Gupta DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

1 0

[qa][gate][stable] stable/wallaby gate is broken
by Ghanshyam Mann 07 Feb '23

07 Feb '23

Hello Everyone, You might know stable/wallaby which is in the EM phase is broken because of the Tempest master incompatibility. As this is in EM phase, Tempest master does support it and the fix is to use the old compatible Tempest. I have pushed the fix on devstack to pin Tempest 29.0.0 to test stable/wallaby, do not recheck until that is merged: - https://review.opendev.org/c/openstack/devstack/+/871782 This depends on a few other fixes which are in the gate. Like the Tempest pin, we need to pin tempest plugins also on stable/wallaby. I have pushed a few projects fix for that, please review those if the devstack patch alone does not fix the gate - https://review.opendev.org/q/topic:wallaby-pin-tempest+status:open - https://review.opendev.org/q/topic:bug%252F2003993 -gmann

2 4

[OSSA-2023-002] Cinder, Glance, Nova: Arbitrary file access through custom VMDK flat descriptor (CVE-2022-47951)
by Jeremy Stanley 06 Feb '23

06 Feb '23

======================================================================== OSSA-2023-002: Arbitrary file access through custom VMDK flat descriptor ======================================================================== :Date: January 24, 2023 :CVE: CVE-2022-47951 Affects ~~~~~~~ - Cinder, glance, nova: Cinder <19.1.2, >=20.0.0 <20.0.2, ==21.0.0; Glance <23.0.1, >=24.0.0 <24.1.1, ==25.0.0; Nova <24.1.2, >=25.0.0 <25.0.2, ==26.0.0 Description ~~~~~~~~~~~ Guillaume Espanel, Pierre Libeau, Arnaud Morin and Damien Rannou (OVH) reported a vulnerability in VMDK image processing for Cinder, Glance and Nova. By supplying a specially created VMDK flat image which references a specific backing file path, an authenticated user may convince systems to return a copy of that file's contents from the server resulting in unauthorized access to potentially sensitive data. All Cinder deployments are affected; only Glance deployments with image conversion enabled are affected; all Nova deployments are affected. Patches ~~~~~~~ - https://review.opendev.org/871631 (Train(cinder)) - https://review.opendev.org/871630 (Train(glance)) - https://review.opendev.org/871629 (Ussuri(cinder)) - https://review.opendev.org/871626 (Ussuri(glance)) - https://review.opendev.org/871628 (Victoria(cinder)) - https://review.opendev.org/871623 (Victoria(glance)) - https://review.opendev.org/871627 (Wallaby(cinder)) - https://review.opendev.org/871621 (Wallaby(glance)) - https://review.opendev.org/871625 (Xena(cinder)) - https://review.opendev.org/871619 (Xena(glance)) - https://review.opendev.org/871622 (Xena(nova)) - https://review.opendev.org/871620 (Yoga(cinder)) - https://review.opendev.org/871617 (Yoga(glance)) - https://review.opendev.org/871624 (Yoga(nova)) - https://review.opendev.org/871618 (Zed(cinder)) - https://review.opendev.org/871614 (Zed(glance)) - https://review.opendev.org/871616 (Zed(nova)) - https://review.opendev.org/871615 (2023.1/antelope(cinder)) - https://review.opendev.org/871613 (2023.1/antelope(glance)) - https://review.opendev.org/871612 (2023.1/antelope(nova)) Credits ~~~~~~~ - Guillaume Espanel from OVH (CVE-2022-47951) - Pierre Libeau from OVH (CVE-2022-47951) - Arnaud Morin from OVH (CVE-2022-47951) - Damien Rannou from OVH (CVE-2022-47951) References ~~~~~~~~~~ - https://launchpad.net/bugs/1996188 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-47951 Notes ~~~~~ - The stable/wallaby, stable/victoria, stable/ussuri, and stable/train branches are under extended maintenance and will receive no new point releases, but patches for them are provided as a courtesy where possible. -- Jeremy Stanley OpenStack Vulnerability Management Team

3 3

[kolla][HAProxy] Insert custom vip in HAProxy
by Satish Patel 06 Feb '23

06 Feb '23

Folks, We have multi-node openstack running and recently i have deployed ceph storage which is in an internal network and i would like to access ceph dashboard on public. I was thinking if there is a way to insert custom vip configuration in the Kolla HAProxy role then I can expose the 8443 port of the ceph-dashboard to the public network. Is it possible in kolla to add custom config in haproxy for extra vip?

2 2

[election][ptl][openstack-helm] PTL Non-candidacy
by Gage Hugo 06 Feb '23

06 Feb '23

Hey folks, With the next election approaching, I want to announce that I will not be running for PTL this upcoming cycle. I've served as PTL for the last 3 years (6 cycles!?) now and I believe it's time for a change that can only be introduced by new leadership. I believe the OpenStack-Helm project is currently in good standing, but it will be healthy for the project to have someone with a fresh perspective step in. The current project team has been excellent and I believe whoever steps up will have plenty of support from the OpenStack-Helm community. I still plan on being around when I can so I can provide help whenever it's needed. Thanks everyone, it's been great! Gage

3 2

[qa][dev] Support for `sudo pip install` going away soon (PEP 668)
by Jeremy Stanley 06 Feb '23

06 Feb '23

Debian 12 (bookworm) and non-LTS Ubuntu 23.04 (lunar) are going to disallow `sudo pip install` so anything you install with pip for use by their packaged Python interpreter will need to go into venvs. Here's the upcoming readme about it: https://salsa.debian.org/cpython-team/python3/-/blob/master/debian/README.v… This has obvious implications for DevStack and Grenade, which currently install OpenStack services into the system environment for the distribution-packaged interpreter. Both bookworm and lunar will be released in a few months and people are going to end up using them for development systems, but at a minimum we're going to be forced to address this before we make Debian 12 or Ubuntu 24.04 LTS a targeted test platform for a release. There was an attempt to implement a solution 5 years ago when the writing was clearly on the wall that this would eventually happen. It may need some updates, but probably could serve as a good starting point: https://review.opendev.org/558930 -- Jeremy Stanley

1 0

[osprofiler] CI broken, looks like something related to ChangeLog not generated
by Sahid Orentino Ferdjaoui 06 Feb '23

06 Feb '23

Hello, There is a change here that is fixing functional test issues on CI. But we still have an issue with ChangeLog. https://review.opendev.org/c/openstack/osprofiler/+/840711 Looks like pbr should generate it, then we include it on history.rst. But for some reason it seems that the file is not generated or got deleted at some point. Locally that is working right. Any idea what may be the problem here? https://zuul.opendev.org/t/openstack/build/a6df711e249c4666a1a26ca6b25d6f42 Thanks, s.

1 0

Stopped OpenStack Trove Guest Agent Service for Development.
by Uday Dikshit 05 Feb '23

05 Feb '23

Hello Team We are trying to use Openstack Trove in kolla-ansible Openstack Wallaby release. We created an image using tarball as well as trovestack, we created a datastore for mysql and added version using these images. But every time we create a database instance the instance in service projects runs successfully and shows active status. But when the database instance gets stuck in build state and after the timeout it logs error in trove taskmanager of polling time out. We created a customized image with the trovestack image and configured ssh in it. Then we used this customized image to check if the guestagent was running in the instance. Here are the logs mysql-instance-1:~# journalctl -u guest-agent.service | less Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 1. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 2. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 3. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 4. Feb 04 18:10:58 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:58 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 5. Feb 04 18:10:58 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. It will be really helpful if anybody did had any idea on running trove in kolla ansible wallaby release Thanks in advance Uday Dikshit

1 0

[neutron] Bug Deputy Report January 30 - February 6
by Nurmatov Mamatisa 05 Feb '23

05 Feb '23

Hi, Below is the week summary of bug deputy report for last week. Undecided bugs needs further triage. Details: Critical -------- - https://bugs.launchpad.net/neutron/+bug/2004184 - [neutron-lib] SQLAlchemy 2.0: ASSOCIATION_PROXY import error - Fix released: https://review.opendev.org/c/openstack/neutron-lib/+/872198 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2004258 - [sqlalchemy-20] ORM "relation" deprecated since v1.4 - Fix released: https://review.opendev.org/c/openstack/neutron/+/872271 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2004538 - [neutron-lib] Gate pep8 errors - Fix released: https://review.opendev.org/c/openstack/neutron-lib/+/872513 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2004656 - "rpc_workers" config variable needs to be registered in stadium projects - In progress: https://bugs.launchpad.net/neutron/+bug/2004656 - Assigned to Rodolfo Alonso High ---- - https://bugs.launchpad.net/neutron/+bug/2004265 - [sqlalchemy-20] Add SQLAlchemy CI jobs using master branch - Fix released: https://review.opendev.org/c/openstack/neutron/+/872273 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2004263 - [sqlalchemy-20] Remove ORM "from_self" - Fix released: https://review.opendev.org/c/openstack/neutron/+/744512 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2004260 - [neutron-lib][sqlalchemy-20] ``Session.transaction`` is no longer a public member - Fix released: https://review.opendev.org/c/openstack/neutron-lib/+/872272 - Assigned to Rodolfo Alonso Medium ------ - https://bugs.launchpad.net/neutron/+bug/2004186 - [ovsdbapp] "LbAddIpPortMappingCommand" C letter is a non-ascii character - In progress: https://review.opendev.org/c/openstack/ovsdbapp/+/872200 - Assigned to Rodolfo Alonso Undecided --------- - https://bugs.launchpad.net/neutron/+bug/2004238 - OVN metadata use the same IP as LB health monitor - Incomplete - https://bugs.launchpad.net/neutron/+bug/1988574 - vpnaas not working on centos8-stream on xena - Originally it was kola-ansible bug. Now updated to neutron - https://bugs.launchpad.net/neutron/+bug/2004581 - Neutron API query error, implicit cast does not exist in postgresql - Incomplete - https://bugs.launchpad.net/neutron/+bug/2005111 - Batch creating VM failed because of timeout error Best regards, Isa Advanced Software Technology Lab / Cloud Technologies Research

1 0

[neutron] Bumping of requirements on RDO before bumping them on Neutron
by Elvira Garcia Ruiz 04 Feb '23

04 Feb '23

Hi Neutrinos! RDO folks proposed that, in order to be able to correctly build CI gates for testing, it would be nice if we tried to update the neutron-distgit requirement file when we want to update the minimal version of a dependency before merging it on our repository. This would allow them to realize whether they need or not to update any Fedora package. In order to do that, we just need to send a small commit to their repository [0]. You can use your GitHub account for the login. Here you can find an example for pyroute2 in RDO [1] and the respective pyroute2 bump in Neutron [2]. Regards! Elvira García (elvira) [0] https://review.rdoproject.org/r/openstack/neutron-distgit [1] https://review.rdoproject.org/r/c/openstack/neutron-distgit/+/46809 [2] https://review.opendev.org/c/openstack/neutron/+/870963

7 9

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

03 Feb '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Feb 1. Most of the meeting discussions are summarized in this email. This was a monthly video call and the recording is available @ https://www.youtube.com/watch?v=SU4CKkz2Fkc and summary logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-02-01-16.00.log.html * The next TC weekly meeting will be on Feb 8 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Feb 7. 2. What we completed this week: ========================= * None for this week 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[2]. Open Reviews ----------------- * Four open reviews for ongoing activities[3]. PTG/Forum planning ------------------------- The TC started the etherpad[4] to collect the topics for next vPTG in March, feel free to add the topics there. Defining 2023.2 cycle testing runtime --------------------------------------------- It's time to define the testing runtime for the next cycle (2023.2). I have pushed the patch[5], feel free to review and add feedback. For quick ref: below are the changes from the 2023.1 cycle testing runtime: * Remove the additional ubuntu version 20.04 from testing which was added in the 2023.1 testing runtime because we bumped the testing version from 20.04 to 22.04 in the 2023.1 cycle. From 2023.1 to 2023.2, there is no major version change in testing so we do not need to do any additional version testing. * Add Rocky Linux 9 in Best Effort testing * With that bumping the python minversion to py3.9 which is Debian 11 default. Defining 2023 upstream investment opportunities ------------------------------------------------------------ Every calendar year, TC defines the upstream investment opportunities where we need help and the organization can help. I have pushed the patch[6] to define it for the 2023 calendar year which is nothing but continuing last year's opportunities. Feel free to let TC know if any of the areas/projects you think need help and should be added to this list. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The audit process is going on and a few projects have been completed [7]. There is a discussion also going on in ML[8]. In this weekly call, TC discussed it further and there is some improvement in the cleanup process. To do this cleanup smoothly, instead of removing them directly, it is better to notify them first. As PyPi does not tell about the email addresses of additional maintainers, the PTL/team is the best person to know their email addresses (if they are old contributors). JayF will be documenting[9] the 'how to remove PyPI maintainers/owner access' and what additional steps to be done by PTL. Basically In step#1, along with the audit, PTL needs to reach out to their additional maintainers and ask them to i) remove themself as PyPi maintainers ii) transfer the ownership to 'openstackci' if they are 'owner' in PyPi. The process to find the less active projects early in the cycle: ------------------------------------------------------------------------ No update this week. JayF started the etherpad to collect the data and define the criteria to help in this process[10]. Project updates ------------------- * Add Cinder Huawei charm[11] * Add the woodpecker charm to Openstack charms[12] 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://etherpad.opendev.org/p/tc-2023.1-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://etherpad.opendev.org/p/tc-2023-2-ptg [5] https://review.opendev.org/c/openstack/governance/+/872232 [6] https://review.opendev.org/c/openstack/governance/+/872233 [7] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [8] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848… [9] https://meetings.opendev.org/meetings/tc/2023/tc.2023-02-01-16.00.log.html#… [10] https://etherpad.opendev.org/p/project-health-check [11] https://review.opendev.org/c/openstack/governance/+/867588 [12] https://review.opendev.org/c/openstack/governance/+/869752 [13] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[nova] instance not recoverable when its image backend got deleted
by hai wu 03 Feb '23

03 Feb '23

For an Openstack VM instance, if its backing image got deleted already, and this VM instance was already hard rebooted, and went into `Error` state due to `Image not found` error. Is it possible to recover this VM stucking in this bad state? I tried to create a vm snapshot, and then try to rebuild this VM using the newly created vm snapshot, and it kept failing. Regards, Hai

2 2

[ironic] [baremetal] [ops] Mark the date: new bare metal SIG meetup on Feb 8th
by Dmitry Tantsur 03 Feb '23

03 Feb '23

Hi stackers! The bare metal SIG will start with a new format of meetings this year: quarterly and with more content. Please read the announcement: https://ironicbaremetal.org/blog/baremetal-sig-2023q1/ Let me know if you have any questions. Otherwise, we'll be looking forward to talking to you. Zoom link will be posted later. Dmitry P.S. Please help to spread the word! -- Red Hat GmbH <https://www.redhat.com/de/global/dach>, Registered seat: Werner von Siemens Ring 12, D-85630 Grasbrunn, Germany Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross

2 1

[all][stable][ptl] Propose to EOL Rocky series
by Elõd Illés 03 Feb '23

03 Feb '23

Hi, Similarly like the Queens branch EOL proposal [1] I would like to propose to transition every project's stable/rocky to End of Life: - gates are mostly broken - minimal number of activity can be seen on this branch - some core projects already transitioned their stable/rocky to EOL recently (like ironic, neutron, nova) - gate job definitions are still using the old, legacy zuul syntax - gate jobs are based on Ubuntu Xenial, which is also beyond its public maintenance window date and hard to maintain Based on the above, if there won't be any project who wants to keep open their stable/rocky, then I'll start the process of EOL'ing Rocky stable series as a whole. If anyone has any objection then please respond to this mail. Thanks, Előd Illés irc: elodilles @ #openstack-stable / #openstack-release [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-October/031030…

6 7

[release] Release countdown for week R-6, Feb 06 - 10
by Herve Beraud 03 Feb '23

03 Feb '23

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 Feb 09. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2023.1 branching request with the review (as examples, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… https://opendev.org/openstack/releases/src/branch/master/deliverables/antel… 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 16) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, February 16. 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/2023.1 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2023.1 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2023.1 Antelope 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 (and ping elodilles). Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 09 (R-6 week) Client library freeze: February 16 (R-5 week) Antelope-3 milestone: February 16 (R-5 week) Cycle Highlights Due: February 23 (R-4 week) 2023.1 Antelope final release: March 22 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 03 Feb '23

03 Feb '23

Hello Neutrinos: Due to the lack of agenda, today's meeting is cancelled. If you have any topic to be discussed, please add it in [1]. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[all][tc] 2023.2 cycle TC PTG Planning
by Ghanshyam Mann 02 Feb '23

02 Feb '23

Hello Everyone, As you already know that the 2023.2 cycle virtual PTG will be held between Mar 27th - 31[1]. The Technical Committee will meet in this PTG. I have prepared the below etherpad to add the topics for discussion: - https://etherpad.opendev.org/p/tc-2023-2-ptg NOTE: This is not limited to TC members only; any community members feel free to add the topics you would like or want TC members to discuss. [1] https://openinfra.dev/ptg/ -gmann

1 0

[security-sig] Virtual PTG in March
by Jeremy Stanley 02 Feb '23

02 Feb '23

Just a quick heads up for anyone who missed the minutes[0] from today's meeting, I've signed us up for the upcoming virtual PTG (March 27-31) and created a pad[1] for brainstorming discussion topics. If you plan to join us, or participate in the PTG more generally, don't forget to register[2]! Also, a reminder, please don't forget to fill out the surveys[3] about rescheduling our IRC meeting. I'll be reviewing the results and determining next steps after 2023-02-09 (one week from today). [0] https://meetings.opendev.org/meetings/security/2023/security.2023-02-02-15.… [1] https://etherpad.opendev.org/p/mar2023-ptg-openstack-security [2] https://openinfra.dev/ptg [3] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031908… -- Jeremy Stanley

1 0

[osprofiler] who is maintaining osprofiler?
by Sahid Orentino Ferdjaoui 02 Feb '23

02 Feb '23

Hello, We would like to make some improvements on OSProfiler but don’t see a lot of activity on it. Actually it looks like the CI has been broken for a while now. I’m currently working on fixing it, any help would be gratefully appreciated but I will tackle that for sure ;) Besides that I wanted to understand the current status of the project? Thanks, s.

2 1

Masakari PTL non-candidacy
by Radosław Piliszek 02 Feb '23

02 Feb '23

Dears, I am writing this to confirm my non-candidacy for the Masakari PTL role for the next cycle. It has been a great adventure with OpenStack projects in general but my career is calling me in another direction. That said, <fingers crossed>, I might have some ties to the broader OpenDev ecosystem in the long run. Kind regards, Radek -yoctozepto

2 1

[all] Supporting SQLAlchemy 2.0 in OpenStack
by Thomas Goirand 02 Feb '23

02 Feb '23

Hi, SQLAlchemy 2.0 was released 5 days ago. IMO, we should start drawing a plan to support it for Bobcat, and possibly backport patches for Antelope. Note that I have no clue what his implies. Maybe Mike, you could write about it? Has a lot of things changed? Cheers, Thomas Goirand (zigo)

6 6

Winstackers PTL non-candidacy
by Lucian Petrut 02 Feb '23

02 Feb '23

Hi, As mentioned a few months ago [1], Cloudbase Solutions is no longer in a position to support Openstack on Windows. That being considered, I will no longer candidate for the Winstackers PTL role. We'll gladly provide any required assistance if there is anyone interested in taking over. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03104… Regards, Lucian Petrut Cloudbase Solutions

1 0

[kolla] local registry setup issue
by Satish Patel 02 Feb '23

02 Feb '23

Folks, I have set up a local registry using the following method as per official doc. docker run -d \ --network host \ --name registry \ --restart=always \ -e REGISTRY_HTTP_ADDR=0.0.0.0:4000 \ -v registry:/var/lib/registry \ registry:2 After that I ran the following command to import all images to the local registry. docker images | grep kolla | grep -v local | awk '{print $1,$2}' | while read -r image tag; do new_image_name=${image#"quay.io/"} docker tag ${image}:${tag} "localhost:4000"/${new_image_name}:${tag} docker push localhost:4000/${new_image_name}:${tag} done Now i can see images in local registry using docker images command (venv-kolla) root@kolla-infra-1:/etc/kolla# docker images | grep localhost localhost:4000/openstack.kolla/ubuntu-source-nova-novncproxy yoga 01dc100dc65a 2 days ago 1.2GB localhost:4000/openstack.kolla/ubuntu-source-horizon yoga a016e1f5b9af 2 days ago 1.1GB localhost:4000/openstack.kolla/ubuntu-source-nova-conductor yoga 381a64a368bd 2 days ago 1.11GB localhost:4000/openstack.kolla/ubuntu-source-nova-api yoga f90a15a09142 2 days ago 1.11GB .... .... I have added it in global.yml docker_registry: 10.73.0.181:4000 docker_registry_insecure: yes Now when i am trying to add compute nodes then I get a registry error like the following. Not sure why its trying to use https://10.73.0.181:4000/v2 instead of http;// TASK [common : include_tasks] **************************************************************************************************************************************************** included: /root/venv-kolla/share/kolla-ansible/ansible/roles/common/tasks/pull.yml for kolla-comp-2 TASK [service-images-pull : common | Pull images] ******************************************************************************************************************************** FAILED - RETRYING: common | Pull images (3 retries left). FAILED - RETRYING: common | Pull images (2 retries left). FAILED - RETRYING: common | Pull images (1 retries left). failed: [kolla-comp-2] (item=fluentd) => {"ansible_loop_var": "item", "attempts": 3, "changed": true, "item": {"key": "fluentd", "value": {"container_name": "fluentd", "dimensions": {}, "enabled": true, "environment": {"KOLLA_CONFIG_STRATEGY": "COPY_ALWAYS"}, "group": "fluentd", "image": " 10.73.0.181:4000/openstack.kolla/ubuntu-source-fluentd:yoga", "volumes": ["/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro", "/etc/localtime:/etc/localtime:ro", "/etc/timezone:/etc/timezone:ro", "kolla_logs:/var/log/kolla/", "fluentd_data:/var/lib/fluentd/data/"]}}, "msg": "'Traceback (most recent call last):\\n File \"/usr/lib/python3/dist-packages/docker/api/client.py\", line 261, in _raise_for_status\\n response.raise_for_status()\\n File \"/usr/lib/python3/dist-packages/requests/models.py\", line 940, in raise_for_status\\n raise HTTPError(http_error_msg, response=self)\\nrequests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.41/images/create?tag=yoga&fromImage=10.73.0.181%3A4000%2Fopenstack.kolla%2Fubuntu-source-fluentd\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n File \"/tmp/ansible_kolla_docker_payload_6o9nw9xd/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 381, in main\\n File \"/tmp/ansible_kolla_docker_payload_6o9nw9xd/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", line 450, in pull_image\\n json.loads(line.strip().decode(\\'utf-8\\')) for line in self.dc.pull(\\n File \"/usr/lib/python3/dist-packages/docker/api/image.py\", line 415, in pull\\n self._raise_for_status(response)\\n File \"/usr/lib/python3/dist-packages/docker/api/client.py\", line 263, in _raise_for_status\\n raise create_api_error_from_http_exception(e)\\n File \"/usr/lib/python3/dist-packages/docker/errors.py\", line 31, in create_api_error_from_http_exception\\n raise cls(e, response=response, explanation=explanation)\\ndocker.errors.APIError: 500 Server Error: Internal Server Error (\"Get \"https://10.73.0.181:4000/v2/\": http: server gave HTTP response to HTTPS client\")\\n'"} FAILED - RETRYING: common | Pull images (3 retries left).

3 5

Reddit query for openstack magnum for enterprise core component maker
by Gajendra D Ambi 02 Feb '23

02 Feb '23

https://www.reddit.com/r/openstack/comments/10hu68s/container_orchestrator_… . Hi team, request anyone of you from this project to please help us out. We also mean to contribute to the project because we know that we will need to add a lot more features to it that what api endpoints are already providing to us. When we do, it will all be contributed to the project after it is being tested for months in production. I am leaning towards openstack magnum and I do not have a lot of time to convince others of the same. Thanks and Regards, https://ambig.one/2/

2 3

[neutron] New pylint 2.16.0 version
by Rodolfo Alonso Hernandez 02 Feb '23

02 Feb '23

Hello Neutrinos: There is a new pylint version released that is breaking some pep8 CI jobs (so far [1]). If you find any error, please do not recheck and report a launchpad bug or ping us in #openstack-neutron channel. Thanks! [1]https://bugs.launchpad.net/neutron/+bug/2004538

1 0