- openstack-discuss - lists.openstack.org

[neutron] Drivers meeting cancelled today
by Rodolfo Alonso Hernandez 13 Jan '23

13 Jan '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend! [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[horizon]
by Nguyễn Hữu Khôi 12 Jan '23

12 Jan '23

Hello guys. I use Openstack Xena which deployed by Kolla Ansible.My problem is when I launch instance from Horizon, Port selection won't show as below pictures: [image: image.png] [image: image.png] I try to change browser but this problem still persists Any suggestions for me? Thank you. Regards. Nguyen Huu Khoi

2 2

RuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml | Openstack wallaby | tripleo | centos 8 stream
by Swogat Pradhan 12 Jan '23

12 Jan '23

Hi, INFO: Openstack wallaby on centos 8 stream I am trying to deploy a DCN and during the ceph deploy command i am getting the following error: (undercloud) [stack@hkg2director dcn01]$ openstack overcloud ceph deploy dcn01_overcloud-baremetal-deployed.yaml --stack dcn01 --config initial-ceph.conf --output deployed_ceph.yaml --container-image-prepare containers-prepare-parameter.yaml --network-data custom_network_data.yaml --cluster dcn01 --roles-data dcn01_roles.yaml -vvv The full traceback is: Traceback (most recent call last): File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 241, in get_deployed_roles_to_hosts UnboundLocalError: local variable 'matching_hosts' referenced before assignment During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>", line 102, in <module> File "<stdin>", line 94, in _ansiballz_main File "<stdin>", line 40, in invoke_module File "/usr/lib64/python3.6/runpy.py", line 205, in run_module return _run_module_code(code, init_globals, run_name, mod_spec) File "/usr/lib64/python3.6/runpy.py", line 96, in _run_module_code mod_name, mod_spec, pkg_name, script_name) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 500, in <module> File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 471, in main File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 246, in get_deployed_roles_to_hosts RuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml 2023-01-13 01:27:15.811878 | 48d539a1-1679-ea57-d54d-000000000013 | FATAL | Create Ceph spec based on baremetal_deployed_path and tripleo_roles | undercloud | error={ "changed": false, "module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 241, in get_deployed_roles_to_hosts\nUnboundLocalError: local variable 'matching_hosts' referenced before assignment\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"<stdin>\", line 102, in <module>\n File \"<stdin>\", line 94, in _ansiballz_main\n File \"<stdin>\", line 40, in invoke_module\n File \"/usr/lib64/python3.6/runpy.py\", line 205, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib64/python3.6/runpy.py\", line 96, in _run_module_code\n mod_name, mod_spec, pkg_name, script_name)\n File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 500, in <module>\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 471, in main\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 246, in get_deployed_roles_to_hosts\nRuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1 } (undercloud) [stack@hkg2director dcn01]$ cat /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml parameter_defaults: DeployedServerPortMap: dcn01-hci-0-ctlplane: fixed_ips: - ip_address: 172.25.221.96 dcn01-hci-1-ctlplane: fixed_ips: - ip_address: 172.25.221.90 dcn01-hci-2-ctlplane: fixed_ips: - ip_address: 172.25.221.106 HCICount: 3 HCIHostnameFormat: '%stackname%-hci-%index%' HostnameMap: dcn01-hci-0: dcn01-hci-0 dcn01-hci-1: dcn01-hci-1 dcn01-hci-2: dcn01-hci-2 NodePortMap: dcn01-hci-0: ctlplane: ip_address: 172.25.221.96 ...> Can someone please tell me what could be the issue here?? Am I missing something? With regards, Swogat Pradhan

1 1

[ironic] Bugfix branches being EOL'd first week of Jan, 2023
by Jay Faulkner 12 Jan '23

12 Jan '23

OpenStack Community and Operators, As documented in https://specs.openstack.org/openstack/ironic-specs/specs/approved/new-relea…, Ironic performs bugfix releases in the middle of a cycle to permit downstream packagers to more rapidly deliver features to standalone Ironic users. However, we've neglected as a project to cleanup or EOL any of these branches -- until now. Please take notice that during the first week in January, we will be EOL-ing all old, unsupported Ironic bugfix branches. This will be handled similarly to an EOL of a stable branch; we will create a tag -- e.g. for bugfix/x.y branch, we would tag bugfix-x.y-eol -- then remove the branch. These branches have been out of support for months and should not be in use in your Ironic clusters. If you are using any branches slated for retirement, please immediately upgrade to a supported Ironic version. A full listing of projects and branches impacted: ironic branches being retired bugfix/15.1 bugfix/15.2 bugfix/16.1 bugfix/16.2 bugfix/18.0 bugfix/20.0 ironic-python-agent branches being retired bugfix/6.2 bugfix/6.3 bugfix/6.5 bugfix/6.6 bugfix/8.0 bugfix/8.4 ironic-inspector branches being retired bugfix/10.2 bugfix/10.3 bugfix/10.5 bugfix/10.10 Thank you, Jay Faulkner Ironic PTL

1 4

[ironic] Moving Aija to core-emeritus
by Jay Faulkner 12 Jan '23

12 Jan '23

Hi all, As many of you may already know, Aija is no longer actively working on OpenStack. She informed many Ironic cores over email of this last week. I asked her if she expected to contribute on her own time and she said no. In order to ensure we keep core reviewer lists up to date, I suggest we move Aija to core-emeritus status, removing core permissions from gerrit. If she decides to begin working on OpenStack again in the future, we'd obviously quickly return core permissions. What do you think? -- Jay Faulkner Ironic PTL TC Member P.S. A huge thanks to Aija for her hard work on the sushy project and the Dell driver in Ironic.

6 6

Overriding tox's install_command won't work for non-service projects
by Stephen Finucane 12 Jan '23

12 Jan '23

Another tox 4 PSA. It turns out the tox 3 was not using the command in '[tox] install_command' when installing the package under test. tox 4 does, which means overriding '[tox] install_command' to include a constraints file (-c) will prevent you installing any requirement that is listed in the upper-constraints file, even if said requirement is the thing you're currently working on. This applies to all libraries (e.g. oslo.db, python-cinderclient) but not the services (cinder, nova) since those aren't included in upper-constraints. The "correct" way to respect upper-constraints is to provide them in 'deps' alongside the requirements file(s), e.g. [testenv] deps = -c{env:UPPER_CONSTRAINTS_FILE:https://releases.openstack.org/constraints/upper/master} -r{toxinidir}/requirements.txt -r{toxinidir}/test-requirements.txt This will cause tox to install all of the package's dependencies first *with* constraints before installing the package itself *without constraints*. There is a bug report open against pip to change this behaviour [1], but it's been sat there for over two years with no activity so I wouldn't rely on this. Stephen [1] https://github.com/pypa/pip/issues/7839

2 3

Issue resizing volumes attached to running volume backed instances
by Jérôme BECOT 12 Jan '23

12 Jan '23

Hello Openstack, We have Ussuri deployed on a few clouds, and they're all plugged to PureStorage Arrays. We allow users to only use volumes for their servers. It means that each server disk is a LUN attached over ISCSI (with multipath) on the compute node hosting the server. Everything works quite fine, but we have a weird issue when extending volumes attached to running instances. The guests notice the new disk size .. of the last extent. Say I have a server with a 10gb disk. I add 5gb. On the guest, still 10gb. I add another 5gb, and on the guest I get 15, and so on. I've turned the debug mode on and I could see no error in the log. Looking closer at the log I could catch the culprit: 2022-12-08 17:35:13.998 46195 DEBUG os_brick.initiator.linuxscsi [] Starting size: *76235669504* 2022-12-08 17:35:14.028 46195 DEBUG os_brick.initiator.linuxscsi [] volume size after scsi device rescan *80530636800* extend_volume 2022-12-08 17:35:14.035 46195 DEBUG os_brick.initiator.linuxscsi [] Volume device info = {'device': '/dev/disk/by-path/ip-1...1:3260-iscsi-iqn.2010-06.com.purestorage:flasharray.x-lun-10', 'host': '5', 'channel': '0', 'id': '0', 'lun': '10'} extend_volume 2022-12-08 17:35:14.348 46195 INFO os_brick.initiator.linuxscsi [] Find Multipath device file for volume WWN 3624... 2022-12-08 17:35:14.349 46195 DEBUG os_brick.initiator.linuxscsi [] Checking to see if /dev/disk/by-id/dm-uuid-mpath-3624.. exists yet. wait_for_path 2022-12-08 17:35:14.349 46195 DEBUG os_brick.initiator.linuxscsi [] /dev/disk/by-id/dm-uuid-mpath-3624... has shown up. wait_for_path 2022-12-08 17:35:14.382 46195 INFO os_brick.initiator.linuxscsi [] mpath(/dev/disk/by-id/dm-uuid-mpath-3624) *current size 76235669504* 2022-12-08 17:35:14.412 46195 INFO os_brick.initiator.linuxscsi [] mpath(/dev/disk/by-id/dm-uuid-mpath-3624) *new size 76235669504* 2022-12-08 17:35:14.413 46195 DEBUG oslo_concurrency.lockutils [] Lock "extend_volume" released by "os_brick.initiator.connectors.iscsi.ISCSIConnector.extend_volume" :: held 2.062s inner 2022-12-08 17:35:14.459 46195 DEBUG os_brick.initiator.connectors.iscsi [] <== extend_volume: return (2217ms) *76235669504* trace_logging_wrapper 2022-12-08 17:35:14.461 46195 DEBUG nova.virt.libvirt.volume.iscsi [] Extend iSCSI Volume /dev/dm-28; new_size=*76235669504* extend_volume 2022-12-08 17:35:14.462 46195 DEBUG nova.virt.libvirt.driver [] Resizing target device /dev/dm-28 to *76235669504* _resize_attached_volume The logs clearly shows that the rescan confirm the new size but when interrogating multipath, it does not. But requesting multipath few seconds after on the command line shows the new size as well. It explains the behaviour. I'm running Ubuntu 18.04 with multipath 0.7.4-2ubuntu3.2. The os-brick code for multipath is far more basic than the one in master branch. Maybe the multipath version installed is too recent for os-brick. Thanks for the help Jerome

2 2

[CI][Tempest] Broken tempest-full-multinode-py3 job
by Lukas Piwowarski 12 Jan '23

12 Jan '23

Hi, I've got stuck trying to figure out why one of our tempest jobs is failing. I will be grateful for any kind of input regarding potential solutions. I did a little investigation of the failing job (tempest-multinode-full-py3 [1][2]) and this is what I found: - The failure is mostly caused by scenario tests. There was one occurrence of failure outside of the scenario tests ( test_create_servers_on_different_hosts_with_list_of_servers) - The failure is always connected to the creation of a VM. The reasons for the failure differ but most of the time it looks like the VM gets created but tempest is not able to access it ("Authentication (publickey) failed.") or the created instance can not be found ("Instance f4e582fe-52e6-40e3-b366-2b11ed589089 could not be found.") - The failure is not connected to one specific test. I am wondering why only the multinode job is failing as in other jobs the scenario tests are passing fine. Thanks for any kind of help Lukáš Piwowarsk [1] https://ca077a96786c794b51b6-8aab0ff599dd9fcfda722d0dee6871dd.ssl.cf5.rackc… [2] https://review.opendev.org/c/openstack/tempest/+/866692

1 0

[openstack][nova][kvm] numa
by Ignazio Cassano 11 Jan '23

11 Jan '23

Hello All, I would like to know if with numa in kvm hypervisor I must disable merge across nodes ? If yes, is there any metadata to do it ? Ignazio

2 2

[largescale-sig] Next meeting: Jan 11, 15utc
by Thierry Carrez 11 Jan '23

11 Jan '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230111T15 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1