June 2024 - openstack-discuss - lists.openstack.org

[operations][nova] Mi grate to shared /var/lib/nova/instances
by Francesco Di Nucci 18 Jun '24

18 Jun '24

Hello, AFAIK live migration requires to have /var/lib/nova/instances shared between the compute nodes (eg. through a NFS export)- If this has not been configured initially and each compute node has its own folder, is it possible to merge them somehow without disruptive effects? Regards Francesco Di Nucci

2 4

[neutron] Neutron server WSGI module, plugin workers
by Rodolfo Alonso Hernandez 18 Jun '24

18 Jun '24

Hello Neutrinos: I would like to highlight something I found during the implementation of [1]. The periodic workers are currently not executed when the WSGI module is configured when using the ML2/OVS mechanism driver (ML2/OVS is still under development). In order to fix that, I've pushed the following patches: * Set the Neutron server workers name: https://review.opendev.org/c/openstack/neutron/+/922090/ * Add a new process to spawn the plugin services in the Neutron server: https://review.opendev.org/c/openstack/neutron/+/922110 * (devstack) [Neutron] Add a new Neutron service: neutron-services-server: https://review.opendev.org/c/openstack/devstack/+/922125 Now we have periodic and experimental jobs using WSGI, I've pushed https://review.opendev.org/c/openstack/neutron/+/922182 to test both the Neutron and the devstack patches. Regards. [1] [OVN] Add support for WSGI mod: https://bugs.launchpad.net/neutron/+bug/1912359

1 0

[openstack-ansible][release] Delayed 2024.1 (Caracal) Trailing release
by Dmitriy Rabotyagov 18 Jun '24

18 Jun '24

Hi folks, As you might have noticed, the final release for 2024.1 (Caracal) is being delayed now for over a week. This has happened due to finding a couple of nasty bugs during more thorough testing of the upgrade path from Antelope by our community members, which happened after RC1 was published. Currently we are on track and known issues was fixed. We are waiting now for SHA bumps to land for the final RC3 which will be used as a 29.0.0 tag. I do hope that it will be done by the end of this week. Sorry for the inconveniences.

1 1

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-15)
by Goutham Pacha Ravi 18 Jun '24

18 Jun '24

Hello Stackers, We're two weeks away from milestone-2 of the 2024.2 (Dalmatian) release cycle [1]. Milestone-2 is a checkpoint to assess the status of inactive project teams and the release worthiness of their deliverables. As I shared with you last week, Dr. Jens Harbott (frickler) made progress on cleaning up maintainers for OpenStack packages on PyPI. He dropped 207 human maintainers across 146 PyPI packages [2]. I'll follow up in the next few weeks about other progress we'll make in this area. === Weekly Meeting === The last weekly IRC meeting was well attended. We chatted about making changes to our PyPI audit scripts. With as much as we're able to automate around the interface, there are some packages we have identified where we need OpenStack CI to assume ownership/maintenance from individuals. We also highlighted Zuul configuration errors [3]; we'll focus on addressing these and gate stability in the coming weeks. If you are a project maintainer, your help in fixing these broken CI job configurations in your project is most welcome! We then briefly touched upon the extensive discussions on removing Eventlet from OpenStack and migration efforts. These discussions have prompted a rewrite of the goal, and we should hear more about this soon. Jay Faulkner (JayF) provided an update on the successful OpenInfra Days event at CERN. He encouraged folks to participate in local OpenInfra events if they are able. Our next weekly meeting is today (Tuesday, June 18th 2024) at 1800 UTC on OFTC's #openstack-tc channel. The agenda is at [4]. Your participation is always appreciated! === Governance Proposals === ==== Merged ==== Add retired-on date for a few missing projects | https://review.opendev.org/c/openstack/governance/+/920855 ==== Open for review/discussion ==== Show TC and SIG repos under reference | https://review.opendev.org/c/openstack/governance/+/918488 Update to include docs and miscellaneous repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 Fix the validate-legacy script | https://review.opendev.org/c/openstack/governance/+/920848 Update criteria for inactive projects to become active again | https://review.opendev.org/c/openstack/governance/+/921500 Appoint James Page as OpenStack Charms PTL | https://review.opendev.org/c/openstack/governance/+/921731 Add TC liaison in DPL model implementation | https://review.opendev.org/c/openstack/governance/+/917516 Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L52 [3] https://zuul.opendev.org/t/openstack/config-errors [4] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Tripleo Heat Templates
by Faillace Christian 17 Jun '24

17 Jun '24

Hi, i am from Leonardo Italy and we use OpenStack. We see that this repository https://github.com/openstack-archive/tripleo-heat-templates is retired. What we should use to installo os-*-config packages? In particular we are tryiing to create an ubuntu 22.04 image and we notice that openstack-heat-agents package doesnt exists in official repository. The same package exists intead for red hat. Thank you very much c. [logo] Christian Faillace Land & Naval Defence Electronics / Engineering Combat Systems Simulators SW Leonardo S.p.A. Via Puccini, 2 - Genova - 16154 - Italy Tel: +39 010 6584438 christian.faillace(a)leonardo.com<mailto:christian.faillace@leonardo.com> ________________________________ HELICOPTERS / AERONAUTICS / ELECTRONICS, DEFENCE AND SECURITY SYSTEMS / SPACE ________________________________ Company General Use Il presente messaggio e-mail e ogni suo allegato devono intendersi indirizzati esclusivamente al destinatario indicato e considerarsi dal contenuto strettamente riservato e confidenziale. Se non siete l'effettivo destinatario o avete ricevuto il messaggio e-mail per errore, siete pregati di avvertire immediatamente il mittente e di cancellare il suddetto messaggio e ogni suo allegato dal vostro sistema informatico. Qualsiasi utilizzo, diffusione, copia o archiviazione del presente messaggio da parte di chi non ne è il destinatario è strettamente proibito e può dar luogo a responsabilità di carattere civile e penale punibili ai sensi di legge. Questa e-mail ha valore legale solo se firmata digitalmente ai sensi della normativa vigente. ________________________________ The contents of this email message and any attachments are intended solely for the addressee(s) and contain confidential and/or privileged information. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately notify the sender and then delete this message and any attachments from your system. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Unauthorized disclosure and/or use of information contained in this email message may result in civil and criminal liability. “ This e-mail has legal value according to the applicable laws only if it is digitally signed by the sender

1 0

[Neutron] Bug deputy report: week of June 10th
by Oleg Bondarev 17 Jun '24

17 Jun '24

Hello Neutron Team, Please see the bug report for the week of June 10th. Some are looking for an assignee, some wait for the authors' response, the one marked as "opinion" might need a second pair of eyes to review. High: ***** - https://bugs.launchpad.net/neutron/+bug/2069482 - [OVN] VMs cannot access metadata when connected to a network with only IPv6 subnets - triaged - assigned to Miguel Lavalle Medium: ***** - https://bugs.launchpad.net/neutron/+bug/2069061 - Investigate 'selectin' relation optimization with newer SQLAlchemy - triaged - unassigned - https://bugs.launchpad.net/neutron/+bug/2069201 - [ovn-octavia-provider] Issues with creating LBs on VLAN networks - triaged - unassigned - https://bugs.launchpad.net/neutron/+bug/2069442 - Deleting a VM may produce a traceback because of a race - in progress: https://review.opendev.org/c/openstack/neutron/+/922043 - assigned to Jakub Libosvar - https://bugs.launchpad.net/neutron/+bug/2069543 - instance tap port has dead vlan when parent port for trunk - triaged - unassigned Undecided: ***** - https://bugs.launchpad.net/neutron/+bug/2069071 - address pair not working with oslo policy http check - Incomplete - https://bugs.launchpad.net/neutron/+bug/2069409 - Addding route in qrouter namesapce failing as Nexthop has invalid gateway. - Incomplete - https://bugs.launchpad.net/neutron/+bug/2069149 - Designate DNS and SSLError 524297 - Opinion Thanks, Oleg

1 0

[ironic] Writing image to device /dev/sda failed
by James Leong 17 Jun '24

17 Jun '24

Hi all, I have been playing around with ironic. However, I am not able to get the deploy of an image to write to the whole disk. It has been complaining about the same error of "Writing image to device /dev/sda failed with exit code 32. stdout: . stderr: lsblk: /dev/sda2: not a block device." Apart from that, I have tried to attached a physical pendrive to it and it's showing me another error stating "Installing GRUB2 boot loader to device /dev/sda failed with Unexpected error while running command.\nCommand: mount -o bind /dev /tmp/tmp5q03tchw/dev\nExit code: 32\nStdout: ''\nStderr: 'mount: /tmp/tmp5q03tchw/dev: mount point does not exist.\\n'." Any help or directly is greatly appreciated. Best, James

2 2

[release] Release countdown for week R-15
by Thierry Carrez 14 Jun '24

14 Jun '24

Development Focus ----------------- The Dalmatian-2 milestone will happen next month, on July 4th, 2024. 2024.2 Dalmatian-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/dalmatian/schedule.html for details. General Information ------------------- Please remember that libraries need to be released at least once per milestone period. At milestone-2, the release team will propose releases for any library that has not been otherwise released since milestone-1. Other non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/dalma… You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/dalmatian/schedule.html#membership-freeze Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates -------------------------- Dalmatian-2 Milestone: July 4th, 2024 -- Thierry Carrez (ttx)

1 0

How to update and set or unset a QOS Policy by python module
by Saeed 14 Jun '24

14 Jun '24

Hello, By using the following commands I can set/unset a port: openstack port set --qos-policy qos_policy_name "network_id" openstack port unset --qos-policy "network_id" But the issue is I cannot find the proper way to set/unset a port. I see this document: https://docs.openstack.org/openstacksdk/latest/user/proxies/network.html And I see the module has this method: *conn.network.update_port* But I don't see any more documents to see how to do that and what parameters are required. Can you help me?

1 1

Issue in Stack.sh
by Lohit S 14 Jun '24

14 Jun '24

How to fix this issue while stack.sh is executed +functions-common:_run_under_systemd:1655 sudo systemctl start devstack(a)q-svc.service +functions-common:run_process:1687 time_stop run_process +functions-common:time_stop:2421 local name +functions-common:time_stop:2422 local end_time +functions-common:time_stop:2423 local elapsed_time +functions-common:time_stop:2424 local total +functions-common:time_stop:2425 local start_time +functions-common:time_stop:2427 name=run_process +functions-common:time_stop:2428 start_time=1716869530330 +functions-common:time_stop:2430 [[ -z 1716869530330 ]] ++functions-common:time_stop:2433 date +%s%3N +functions-common:time_stop:2433 end_time=1716869534546 +functions-common:time_stop:2434 elapsed_time=4216 +functions-common:time_stop:2435 total=16163 +functions-common:time_stop:2437 _TIME_START[$name]= +functions-common:time_stop:2438 _TIME_TOTAL[$name]=20379 +lib/neutron:start_neutron_service_and_check:640 neutron_url= http://192.168.122.150:9696/ +lib/neutron:start_neutron_service_and_check:642 is_service_enabled tls-proxy +functions-common:is_service_enabled:2077 return 1 +lib/neutron:start_neutron_service_and_check:646 '[' '!' -z networking ']' +lib/neutron:start_neutron_service_and_check:647 neutron_url= http://192.168.122.150:9696/networking +lib/neutron:start_neutron_service_and_check:649 echo 'Waiting for Neutron to start...' Waiting for Neutron to start... +lib/neutron:start_neutron_service_and_check:651 local 'testcmd=wget --no-proxy -q -O- http://192.168.122.150:9696/networking' +lib/neutron:start_neutron_service_and_check:652 test_with_retry 'wget --no-proxy -q -O- http://192.168.122.150:9696/networking' 'Neutron did not start' 60 +functions-common:test_with_retry:2359 local 'testcmd=wget --no-proxy -q -O- http://192.168.122.150:9696/networking' +functions-common:test_with_retry:2360 local 'failmsg=Neutron did not start' +functions-common:test_with_retry:2361 local until=60 +functions-common:test_with_retry:2362 local sleep=0.5 +functions-common:test_with_retry:2364 time_start test_with_retry +functions-common:time_start:2407 local name=test_with_retry +functions-common:time_start:2408 local start_time= +functions-common:time_start:2409 [[ -n '' ]] ++functions-common:time_start:2412 date +%s%3N +functions-common:time_start:2412 _TIME_START[$name]=1716869535329 +functions-common:test_with_retry:2365 timeout 60 sh -c 'while ! wget --no-proxy -q -O- http://192.168.122.150:9696/networking; do sleep 0.5; done' +functions-common:test_with_retry:2366 die 2366 'Neutron did not start' +functions-common:die:285 local exitcode=0 [Call Trace] ./stack.sh:1322:start_neutron_service_and_check /home/lohit22/opensource/openstack/devstack/Org/devstack/lib/neutron:652:test_with_retry /home/lohit22/opensource/openstack/devstack/Org/devstack/functions-common:2366:die [ERROR] /home/lohit22/opensource/openstack/devstack/Org/devstack/functions-common:2366 Neutron did not start exit_trap: cleaning up child processes Error on exit

2 2