- openstack-discuss - lists.openstack.org

[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

[openstack-ansible] Train deployment
by Danish Khan 14 Jun '24

14 Jun '24

Dear All, I am trying to install openstack-ansible train but I am unable to find any branch for it. I tried to clone *train-em* branch but my playbooks are failing at multiple places. I need to do POC for openstack upgrade from train to ussuri. Is there any way to deploy openstack train and upgrade it to latest upgradable version? Regards, Danish khan

2 2

[ironic][docs] Ironic docs audit draft report
by Jay Faulkner 14 Jun '24

14 Jun '24

Hi all, Dave from Expert Support has been doing a docs audit for Ironic, as some of you are aware. The preliminary draft of the report is ready for review: https://docs.google.com/document/d/1e9URuPHKNTx5QXdkCFAzsS0EAAxPJ-xQC4BEpDw… -- please add comments if you have them. I've added discussion of this as an agenda item for next Ironic meeting on Monday June 17. I anticipate the next steps will be as follows: - Ironic cores and other interested parties review -- now - ~June 24th - Revise report and action items as needed - Turn action items into documentation bugs against Ironic, tagged as docs-audit-2024, for completion by the community. Dave has spent some time interviewing Ironic operators and contributors, as well as looking over our docs from the perspective of a long-time tech writer with cloud, but not OpenStack, experience. I've found his insights very useful so far, and I think this document is worth a read even if you're not specifically invested in Ironic docs. Thanks, Jay Faulkner

1 0

[neutron] ovs: multiple rows in Manager patch
by stream_unpicked390＠simplelogin.com 14 Jun '24

14 Jun '24

Hi everyone! this is my first time on a mailing list, so please excuse any "obvious" mistakes and feel free to correct me :) I'm currently setting up a minimal OpenStack system manually on one server. The setup is nearly complete but I'm running into issues with neutron. After fully completing the neutron setup as mentioned in the docs, the neutron-ovs-service refuses to start, showing the error message multiple rows in Manager patch "ptcp:6640:127.0.0.0" I dumped the ovs database which only shows one row in the Manager table. After many days of debugging and googleing I'm out of ideas how this could be solved.. I already posted this issue on serverfault (https://serverfault.com/questions/1160418/openstack-ovs-multiple-rows-in-ma…) only after that post finding this mailing list! Best regards Talooola

2 3

[neutron] Drivers meeting cancelled tomorrow
by Brian Haley 14 Jun '24

14 Jun '24

Hello Neutrinos: Due to the lack of agenda, Friday's drivers meeting is cancelled. Have a nice weekend! I will also be offline and unavailable for a couple of days, back on June 18th. -Brian

1 0

Caracal Magnum: magnum-api-wsgi fails to start because of a problem retrieving the version
by Michel Jouvin 13 Jun '24

13 Jun '24

Hi, Moving forward with my current upgrades, I tried to upgrade our preprod Magnum to Caracal. Unfortunately, every components using the Magnum module fails with: ---- File "/usr/bin/magnum-api-wsgi", line 52, in <module> application = build_wsgi_app() File "/usr/lib/python3.9/site-packages/magnum/api/app.py", line 74, in build_wsgi_app service.prepare_service(sys.argv) File "/usr/lib/python3.9/site-packages/magnum/common/service.py", line 27, in prepare_service config.parse_args(argv) File "/usr/lib/python3.9/site-packages/magnum/common/config.py", line 32, in parse_args version=version.version_info.release_string(), File "/usr/lib/python3.9/site-packages/pbr/version.py", line 490, in release_string return self.semantic_version().release_string() File "/usr/lib/python3.9/site-packages/pbr/version.py", line 498, in semantic_version self._semantic = self._get_version_from_importlib_metadata() File "/usr/lib/python3.9/site-packages/pbr/version.py", line 483, in _get_version_from_importlib_metadata return SemanticVersion.from_pip_string(result_string) File "/usr/lib/python3.9/site-packages/pbr/version.py", line 156, in from_pip_string return klass._from_pip_string_unsafe(version_string) File "/usr/lib/python3.9/site-packages/pbr/version.py", line 163, in _from_pip_string_unsafe version_string = version_string.lstrip('vV') AttributeError: 'NoneType' object has no attribute 'lstrip' ---- It also affects magnum-db-manage where the traceback is litle bit different but the exception happens at the same place so I guess it is a common cause: ------ File "/usr/bin/magnum-db-manage", line 5, in <module> from magnum.cmd.db_manage import main File "/usr/lib/python3.9/site-packages/magnum/__init__.py", line 18, in <module> __version__ = pbr.version.VersionInfo( File "/usr/lib/python3.9/site-packages/pbr/version.py", line 505, in version_string return self.semantic_version().brief_string() File "/usr/lib/python3.9/site-packages/pbr/version.py", line 498, in semantic_version self._semantic = self._get_version_from_importlib_metadata() File "/usr/lib/python3.9/site-packages/pbr/version.py", line 483, in _get_version_from_importlib_metadata return SemanticVersion.from_pip_string(result_string) File "/usr/lib/python3.9/site-packages/pbr/version.py", line 156, in from_pip_string return klass._from_pip_string_unsafe(version_string) File "/usr/lib/python3.9/site-packages/pbr/version.py", line 163, in _from_pip_string_unsafe version_string = version_string.lstrip('vV') AttributeError: 'NoneType' object has no attribute 'lstrip' ------ For magnum-db-manage a workaround is to comment the __version__ line in __init__.but it doesn't help for the API. I wanted to check in the Magnum release notes if I missed some requirements but unfortunately they are not linked from https://releases.openstack.org/caracal/#caracal-magnum and I was not able to locate them elsewhere... Thanks in advance for any help/hint. Best regards, Michel

1 2