January 2025 - openstack-discuss - lists.openstack.org

openstack instances unable to reach the internet
by collinl＠churchofjesuschrist.org 04 Feb '25

04 Feb '25

I have been banging my head on this issue for quite some time now. I am hoping that somebody can help me see what I have misconfigured. Here is the situation. I have tried setting up several openstack installs, and in none of them am I able to reach the internet from the instances running inside of openstack. All of them are on Rocky Linux 9.5, running the dalmatian version of openstack, installed using packstack. (I have tried an all-in-one, with everything on a single node, and a cluster with the controller/networking on one node, and the compute running on separate nodes). I can get the cirros instances running on the backend network within openstack, and can ssh to them via the floating ip from the host without issues. The cirros instance can ping other cirros instances in the openstack controlled network (both on the backend network(subnet is in the 192.168.100.0/24 range, or on the external public network(subnet is in the 172.24.4.024 range) Even trying the simplest configuration, where everything is all on a single node (compute/networking/controller/etc), Everything from instance creation to VM migration/etc all seems to work just fine. However, the cirros instances cannot ping anything on the internet -- for example, I am unable to ping 8.8.8.8 or even the gateway that the host can reach (The host has an ip used to reach horizon on the 10.61.157.0/24 subnet on our internal lan) I can ping all interfaces from the cirros interface through the backend_network (192.168.100.0/24) through the public interface (172.24.4.0/24), and can even ping the host ip address (10.61.157.59) . . .However, I can't ping anything beyond that (i.e. the 10.61.147.1 gateway does not ping from the cirros instance) From the host commandline, it is able to reach everything external just fine (i.e. it can ping it's gateway 10.61.147.1 and 8.8.8.8 or anything else external) Here is the ip addr output from the host: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000 link/ether 00:1d:d8:b7:1e:df brd ff:ff:ff:ff:ff:ff inet6 fe80::21d:d8ff:feb7:1edf/64 scope link valid_lft forever preferred_lft forever 3: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 56:d8:51:53:10:b0 brd ff:ff:ff:ff:ff:ff 4: br-int: <BROADCAST,MULTICAST> mtu 1442 qdisc noop state DOWN group default qlen 1000 link/ether 62:8c:b0:c2:3e:5a brd ff:ff:ff:ff:ff:ff 5: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 00:1d:d8:b7:1e:df brd ff:ff:ff:ff:ff:ff inet 10.61.157.59/24 brd 10.61.157.255 scope global br-ex valid_lft forever preferred_lft forever inet 172.24.4.1/24 brd 172.24.4.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::2446:29ff:fe58:6541/64 scope link valid_lft forever preferred_lft forever 6: tapeffe7cc1-56: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc noqueue master ovs-system state UNKNOWN group default qlen 1000 link/ether fe:16:3e:e2:66:5d brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fee2:665d/64 scope link valid_lft forever preferred_lft forever 7: tap65170f1f-e0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master ovs-system state UP group default qlen 1000 link/ether 3a:26:09:cf:3d:4f brd ff:ff:ff:ff:ff:ff link-netns ovnmeta-65170f1f-e837-4b5e-a471-13e783e6b48e inet6 fe80::3826:9ff:fecf:3d4f/64 scope link valid_lft forever preferred_lft forever And the output from the ovs-vsctl show command: 46294eda-8a39-4775-875d-ef6ec9929346 Manager "ptcp:6640:127.0.0.1" is_connected: true Bridge br-int fail_mode: secure datapath_type: system Port tap65170f1f-e0 Interface tap65170f1f-e0 Port patch-br-int-to-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24 Interface patch-br-int-to-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24 type: patch options: {peer=patch-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24-to-br-int} Port tapeffe7cc1-56 Interface tapeffe7cc1-56 Port br-int Interface br-int type: internal Bridge br-ex fail_mode: standalone Port patch-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24-to-br-int Interface patch-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24-to-br-int type: patch options: {peer=patch-br-int-to-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24} Port br-ex Interface br-ex type: internal Port eth0 Interface eth0 ovs_version: "3.3.1" Here is the info for the networks/subnets currently configured: From "openstack network list --long" +------------------------+-----------------+--------+------------------------+-------+--------+------------------------+--------------+-------------+--------------------+------+ | ID | Name | Status | Project | State | Shared | Subnets | Network Type | Router Type | Availability Zones | Tags | +------------------------+-----------------+--------+------------------------+-------+--------+------------------------+--------------+-------------+--------------------+------+ | 65170f1f-e837-4b5e-a47 | backend_network | ACTIVE | c5f408c4daed4fb2afefa4 | UP | False | b1e5aef4-77da-4b0b-9b9 | geneve | Internal | | | | 1-13e783e6b48e | | | 4fa039fe26 | | | 4-5aaf395484e0 | | | | | | b8e7a305-65f0-44ea-93a | public | ACTIVE | c5f408c4daed4fb2afefa4 | UP | False | 6cff8f70-9dc8-4f17-b78 | flat | External | | | | a-cc6ec741d408 | | | 4fa039fe26 | | | 0-32cf2aedb017 | | | | | | c0c67da4-22bf-4dd2-b4c | private | ACTIVE | 2967b1fe70794fa88cbb3d | UP | False | caed16ae-22ff-427a-a37 | geneve | Internal | | | | 2-2edcb41ffb97 | | | e7227cec77 | | | 0-6b891755bfa7 | | | | | +------------------------+-----------------+--------+------------------------+-------+--------+------------------------+--------------+-------------+--------------------+------+ From "openstack subnet list --long" +---------------+---------------+---------------+---------------+---------------+-------+--------------+------------------+-------------+------------+---------------+---------------+------+ | ID | Name | Network | Subnet | Project | DHCP | Name Servers | Allocation Pools | Host Routes | IP Version | Gateway | Service Types | Tags | +---------------+---------------+---------------+---------------+---------------+-------+--------------+------------------+-------------+------------+---------------+---------------+------+ | 6cff8f70-9dc8 | public_subnet | b8e7a305-65f0 | 172.24.4.0/24 | c5f408c4daed4 | False | | 172.24.4.2-172.2 | | 4 | 172.24.4.1 | | | | -4f17-b780-32 | | -44ea-93aa- | | fb2afefa44fa0 | | | 4.4.254 | | | | | | | cf2aedb017 | | cc6ec741d408 | | 39fe26 | | | | | | | | | | b1e5aef4-77da | backend_subne | 65170f1f-e837 | 192.168.100.0 | c5f408c4daed4 | True | | 192.168.100.100- | | 4 | 192.168.100.1 | | | | -4b0b-9b94-5a | t | -4b5e-a471-13 | /24 | fb2afefa44fa0 | | | 192.168.100.250 | | | | | | | af395484e0 | | e783e6b48e | | 39fe26 | | | | | | | | | | caed16ae-22ff | private_subne | c0c67da4-22bf | 10.0.0.0/24 | 2967b1fe70794 | True | | 10.0.0.2-10.0.0. | | 4 | 10.0.0.1 | | | | -427a-a370-6b | t | -4dd2-b4c2-2e | | fa88cbb3de722 | | | 254 | | | | | | | 891755bfa7 | | dcb41ffb97 | | 7cec77 | | | | | | | | | +---------------+---------------+---------------+---------------+---------------+-------+--------------+------------------+-------------+------------+---------------+---------------+------+ From "openstack floating ip list" +------------------------------------+---------------------+------------------+------------------------------------+------------------------------------+----------------------------------+ | ID | Floating IP Address | Fixed IP Address | Port | Floating Network | Project | +------------------------------------+---------------------+------------------+------------------------------------+------------------------------------+----------------------------------+ | 61d98a1c-f19a-451f-9353-6cb8305a0c | 172.24.4.175 | 192.168.100.128 | effe7cc1-566d-4574-b4e3-d9f440b776 | b8e7a305-65f0-44ea-93aa- | c5f408c4daed4fb2afefa44fa039fe26 | | 2f | | | 5e | cc6ec741d408 | | +------------------------------------+---------------------+------------------+------------------------------------+------------------------------------+----------------------------------+ From "openstack server list" +--------------------------------------+-------+--------+-----------------------------------------------+--------------------------+---------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+-------+--------+-----------------------------------------------+--------------------------+---------+ | e42372d2-946d-4c90-bf2d-1e36cda80e2f | test3 | ACTIVE | backend_network=172.24.4.175, 192.168.100.128 | N/A (booted from volume) | m1.tiny | +--------------------------------------+-------+--------+-----------------------------------------------+--------------------------+---------+ Any assistance in helping me figure out what I am missing to get external access would be greatly appreciated. Thank you!

3 9

VPNaaS
by Vincent Godin 04 Feb '25

04 Feb '25

Hello, The VPNaaS provided with Openstack is a Site-to-Site VPN made to interconnect two tenants or an external gateway with a tenant network. I would like to know if there are plans to offer a VPNaaS more like a Remote VPN. This would allow Openstack users to administer their instances securely. A user could mount this VPN from a roaming device, be assigned a local IP address, and then administer the instances of his tenant. Regards Vincent

3 2

Discussion of OpenStack development getting Error.
by Kiran Raja 04 Feb '25

04 Feb '25

Hi Team, We have deployed Open stack and when we are trying to access Neutron Gateway from the Controller node we are unable to access, but It is access able from Namespace Created in neutron , please help me on neutron configuration we are using Self-provision Network Option. root@controller:~# openstack router list +--------------------------------------+--------------+--------+-------+----------------------------------+-------------+-------+ | ID | Name | Status | State | Project | Distributed | HA | +--------------------------------------+--------------+--------+-------+----------------------------------+-------------+-------+ | 16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 | Admin_Router | ACTIVE | UP | 523711770d5243dd9af5b2356b540b07 | False | False | +--------------------------------------+--------------+--------+-------+----------------------------------+-------------+-------+ root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 ip route default via 172.16.86.1 dev qg-afb1772f-2f proto static 172.16.86.0/24 dev qg-afb1772f-2f proto kernel scope link src 172.16.86.49 root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 172.16.86.1 0.0.0.0 UG 0 0 0 qg-afb1772f-2f 172.16.86.0 0.0.0.0 255.255.255.0 U 0 0 0 qg-afb1772f-2f root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 ping 172.16.86.1 PING 172.16.86.1 (172.16.86.1) 56(84) bytes of data. ^C --- 172.16.86.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2042ms root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 ip address 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 13: qg-afb1772f-2f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:d1:58:50 brd ff:ff:ff:ff:ff:ff inet 172.16.86.49/24 brd 172.16.86.255 scope global qg-afb1772f-2f valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fed1:5850/64 scope link valid_lft forever preferred_lft forever root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 ping 172.16.86.49 PING 172.16.86.49 (172.16.86.49) 56(84) bytes of data. 64 bytes from 172.16.86.49: icmp_seq=1 ttl=64 time=0.073 ms 64 bytes from 172.16.86.49: icmp_seq=2 ttl=64 time=0.113 ms ^C --- 172.16.86.49 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1003ms rtt min/avg/max/mdev = 0.073/0.093/0.113/0.020 ms root@controller:~# ping 172.16.86.49 PING 172.16.86.49 (172.16.86.49) 56(84) bytes of data. ^C --- 172.16.86.49 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1048ms root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 ip address 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 13: qg-afb1772f-2f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:d1:58:50 brd ff:ff:ff:ff:ff:ff inet 172.16.86.49/24 brd 172.16.86.255 scope global qg-afb1772f-2f valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fed1:5850/64 scope link valid_lft forever preferred_lft forever 15: qr-6be4aabd-b9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:df:a9:ad brd ff:ff:ff:ff:ff:ff inet 172.16.100.1/24 brd 172.16.100.255 scope global qr-6be4aabd-b9 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fedf:a9ad/64 scope link valid_lft forever preferred_lft forever root@controller:~# ping 172.16.86.1 PING 172.16.86.1 (172.16.86.1) 56(84) bytes of data. 64 bytes from 172.16.86.1: icmp_seq=1 ttl=64 time=0.204 ms ^C --- 172.16.86.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.204/0.204/0.204/0.000 ms root@controller:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0c:29:25:f8:21 brd ff:ff:ff:ff:ff:ff altname enp3s0 inet 172.16.85.11/24 brd 172.16.85.255 scope global ens160 valid_lft forever preferred_lft forever inet6 fe80::20c:29ff:fe25:f821/64 scope link valid_lft forever preferred_lft forever 3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000 link/ether 00:0c:29:25:f8:2b brd ff:ff:ff:ff:ff:ff altname enp11s0 inet6 fe80::20c:29ff:fe25:f82b/64 scope link valid_lft forever preferred_lft forever 4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 2e:14:3b:10:5d:42 brd ff:ff:ff:ff:ff:ff 5: br-tun: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 02:fb:f2:93:65:46 brd ff:ff:ff:ff:ff:ff inet6 fe80::fb:f2ff:fe93:6546/64 scope link valid_lft forever preferred_lft forever 6: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 00:0c:29:25:f8:2b brd ff:ff:ff:ff:ff:ff inet6 fe80::20c:29ff:fe25:f82b/64 scope link valid_lft forever preferred_lft forever 7: br-int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 72:cb:66:8a:21:4c brd ff:ff:ff:ff:ff:ff inet6 fe80::70cb:66ff:fe8a:214c/64 scope link valid_lft forever preferred_lft forever root@controller:~# ovs-vsctl show 77dc413c-c4a0-4c7a-b3e2-3ba8ecf5bee7 Manager "ptcp:6640:127.0.0.1" is_connected: true Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port br-int Interface br-int type: internal Port qg-afb1772f-2f tag: 2 Interface qg-afb1772f-2f type: internal Port qr-6be4aabd-b9 tag: 3 Interface qr-6be4aabd-b9 type: internal Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port tap93e5731e-d9 tag: 2 Interface tap93e5731e-d9 type: internal Port tap52dcef2e-c9 tag: 3 Interface tap52dcef2e-c9 type: internal Port int-br-ex Interface int-br-ex type: patch options: {peer=phy-br-ex} Bridge br-tun Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port br-tun Interface br-tun type: internal Bridge br-ex Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port phy-br-ex Interface phy-br-ex type: patch options: {peer=int-br-ex} Port br-ex Interface br-ex type: internal Port ens192 Interface ens192 ovs_version: "3.4.0" Thanks and Regards CH Kiran Raja M: +91 9959503256 [cid:1df6874c-4456-494d-9e7c-aa3aed63e7af]<https://pidatacenters.com/> [cid:693f6ef0-1ee9-4ea9-a345-8488a3aa8c2b]<https://harbour1.in/> kiran.raja(a)pidatacenters.com<mailto:kiran.raja@pidatacenters.com> [cid:0770d139-f2b6-424b-a451-6ad2a391a96b]

1 1

[openstack helm] [Glance] Glance showing OSError: unable to receive chunked part when uploading image
by daniel890723＠gmail.com 04 Feb '25

04 Feb '25

Hello i'm testing using Openstack-helm to install all component but after the installation complete i can't upload the OS image through both openstack CLI or Horizon it stuck at Queueing and when i checking Glance Api log it shows 2024-11-07 07:31:19.362 7 INFO glance.api.v2.image_data [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token. 2024-11-07 07:31:19.400 7 ERROR glance.api.v2.image_data [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Failed to upload image data due to internal error: OSError: unable to receive chunked part 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Caught error: unable to receive chunked part: OSError: unable to receive chunked part 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi Traceback (most recent call last): 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1302, in __call__ 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi action_result = self.dispatch(self.controller, action, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1345, in dispatch 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return method(*args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 415, in wrapped 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return func(self, req, *args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/api/v2/image_data.py", line 299, in upload 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi with excutils.save_and_reraise_exception(): 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.force_reraise() 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise self.value 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/api/v2/image_data.py", line 162, in upload 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi image.set_data(data, size, backend=backend) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/notifier.py", line 492, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi with excutils.save_and_reraise_exception(): 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.force_reraise() 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise self.value 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/notifier.py", line 443, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.repo.set_data(data, size, backend=backend, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/quota/__init__.py", line 322, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.image.set_data(data, size=size, backend=backend, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/location.py", line 596, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self._upload_to_store(data, verifier, backend, size) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/location.py", line 487, in _upload_to_store 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi multihash, loc_meta) = self.store_api.add_with_multihash( 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/multi_backend.py", line 397, in add_with_multihash 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return store_add_to_backend_with_multihash( 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/multi_backend.py", line 479, in store_add_to_backend_with_multihash 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi (location, size, checksum, multihash, metadata) = store.add( 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/driver.py", line 294, in add_adapter 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi metadata_dict) = store_add_fun(*args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/capabilities.py", line 176, in op_checker 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return store_op_fun(store, *args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/_drivers/filesystem.py", line 764, in add 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise errors.get(e.errno, e) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/_drivers/filesystem.py", line 746, in add 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi for buf in utils.chunkreadable(image_file, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/common/utils.py", line 73, in chunkiter 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi chunk = fp.read(chunk_size) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 294, in read 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi result = self.data.read(i) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 121, in readfn 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi result = fd.read(*args) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/format_inspector.py", line 956, in read 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi chunk = self._source.read(size) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1045, in read 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi data = uwsgi.chunked_read() 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi OSError: unable to receive chunked part 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi Ceph Cluster Status: NAME DATADIRHOSTPATH MONCOUNT AGE PHASE MESSAGE HEALTH EXTERNAL FSID ceph /var/lib/rook 3 82m Ready Cluster created successfully HEALTH_OK 5cf8b9bb-13e1-4c31-b47d-9e7d92c3c05d Ceph osd status: ID CLASS WEIGHT REWEIGHT SIZE RAW USE DATA OMAP META AVAIL %USE VAR PGS STATUS TYPE NAME -1 0.35156 - 360 GiB 3.3 GiB 493 MiB 0 B 2.8 GiB 357 GiB 0.91 1.00 - root default -5 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 964 MiB 119 GiB 0.92 1.01 - host instance-lu-1 2 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 964 MiB 119 GiB 0.92 1.01 195 up osd.2 -3 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 - host instance-lu-2 0 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 195 up osd.0 -7 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 - host instance-lu-3 1 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 197 up osd.1 TOTAL 360 GiB 3.3 GiB 493 MiB 0 B 2.8 GiB 357 GiB 0.91 MIN/MAX VAR: 1.00/1.01 STDDEV: 0.01 now i'm able to create Empty Volume using horizon(can't create volume using default cirros image ) and i can start an Instance without volume and mount the empty volume in(Ceph also can detect when i use that volume) is there something i need to set when starting glance? because i'm following the Openstack-helm installation document to install openstack with helm

3 5

[watcher] core team expansion
by Sean Mooney 04 Feb '25

04 Feb '25

Hi everyone, As you may be aware a number of us from Redhat have been trying to revitalize the Watcher project. To enable that one of the changes that we previously discussed on the mailing list and ptg was the expansion of the core team. https://etherpad.opendev.org/p/r.79644f8f3cd04686c4f45c10aa35d8ac#L46 https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… In November the initial phase of that proposal was completed and I took an action to follow up in Q1 to see what steps are needed to rebuild a healthy core team. based on the activity of the last 90 days and the progress of work I think it is time to expand the core teams once again to enable effective maintenance and development of watcher https://openstack.biterg.io/app/dashboards#/view/95487340-6762-11e9-a198-67…:'Gerrit%20Approvals%20panel%20by%20Bitergia',filters:!(('$state':(store:appState),meta:(alias:Bots,disabled:!f,index:gerrit,key:author_bot,negate:!t,params:(query:!t),type:phrase),query:(match:(author_bot:(query:!t,type:phrase)))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:gerrit,key:project,negate:!f,params:(query:watcher),type:phrase),query:(match_phrase:(project:watcher)))),fullScreenMode:!f,options:(darkTheme:!f,hidePanelTitles:!f,useMargins:!t),query:(language:lucene,query:''),timeRestore:!f,title:'Gerrit%20Approvals',viewMode:view) tiny url version of ^ https://tinyurl.com/439wzbdk https://www.stackalytics.io/?module=watcher-group the current core teams are as follows * watcher-core https://review.opendev.org/admin/groups/77cd139bd57514e98e5e694a82f7e261b47… * watcher-dashboard-core https://review.opendev.org/admin/groups/bcc8588732437ceea3533249313e6e96148… * watcher-specs-core https://review.opendev.org/admin/groups/747af616eb8748aee5b17d9493f9ebbc49e… * watcher-tempest-core https://review.opendev.org/admin/groups/09a91d8e24af9ce44b80062c4851a1d2fa3… starting in order watcher-core: https://tinyurl.com/2p8sr7u4 https://www.stackalytics.io/?module=opendev.org/openstack/watcher - add Marios Andreou - add Douglas Viroel Marios and Doug both have past experience as core reviews in other OpenStack projects (triple-o and Manilla), over the last 90 days, they have engaged in reviews of bug fixes and the development of the new Prometheus data source. watcher-dashboard-core: https://tinyurl.com/4259h8nz https://www.stackalytics.io/?module=opendev.org/openstack/watcher-dashboard - add Marios Andreou - add Douglas Viroel as with Watcher itself Doug and Marios have spent time looking at the open review for the watcher-dashboard. watcher-spec-core: is tricky as we have effective only had one spec this cycle that was written by Marios with some minor patches for ci. As watcher core is a member of watcher-spec-core, Marios and Doug will inherit review rights on the specs repo. At this time I do not see a need to make any other changes to the group membership. watcher-tempest-core: https://tinyurl.com/4nbctef8 https://www.stackalytics.io/?module=opendev.org/openstack/watcher-tempest-p… - add Chandan Kumar - add Douglas Viroel - remove Martin Kopec As many of you may know Martin has taken up a new role in Redhat outside of OpenStack and will no longer be working directly on OpenStack. Over the last 90 days, Martin and Gmann have modernized the tempest plugin significantly paying down much of the tech debt. I want to thank them for the efforts they put in to help revive Watcher this cycle and if they return to the OpenStack community in the future I will gladly welcome them back. In their stead, I am proposing adding Chandan and Doug to augment the existing core group. As agreed in the Watcher team meeting earlier today we will review this mail thread in the next Watcher IRC meeting next week. I would like to invite others to provide feedback on this proposal over the next week. In the next PTG, I will also raise the composition of the core teams for discussion. It is my hope that with these additions we will have at least 3 active reviews on all deliverables of the watcher project mitigating the current bus factor and accelerating development. Regards Sean.

1 1

[ironic]About the OS supported by Diskimage-builder
by Junya Noguchi (Fujitsu) 03 Feb '25

03 Feb '25

To whom it may concern. My name is Junya Noguchi. I have some questions about the supported OS for Diskimage-builder operation. Please respond. References https://docs.openstack.org/ironic-python-agent-builder/latest/admin/dib.html Does it mean that the OS that says "work but receive only limited testing and support" works but is not supported? References https://docs.openstack.org/diskimage-builder/latest/ This document describes RHEL and other operating systems that are not supported in the previous question. Are these operating systems supported? Also, are there any plans to support more operating systems in the future? Best regards, Junya Noguchi

5 7

[neutron] neutron-core/networking-ovn-core consolidation
by Brian Haley 03 Feb '25

03 Feb '25

Hello Neutrinos: I noticed the other day we still have the networking-ovn-core group [0] included in the neutron-core group [1], a left-over from when we merged the OVN code into the Neutron repo in Ussuri. Most people in the networking-ovn-core group no longer contribute to Neutron, except for one - Terry Wilson (otherwiseguy). In order to cleanup a little I'm going to consolidate things and add Terry as a member of the neutron-core group, and remove the import. Since he has basically been operating as a Neutron core reviewer already for years, I don't think we need to vote on this. So welcome officially Terry! -Brian, Neutron PTL [0] https://review.opendev.org/admin/groups/ecdeda6cb5657af51f20b282cd0525cb7e6… [1] https://review.opendev.org/admin/groups/38

6 5

OpenStack BoF at FOSDEM
by Amy Marrich 03 Feb '25

03 Feb '25

Hey all, Sorry for the late promotion but we will be having an OpenStack BoF at FOSDEM[0] on Saturday at 16:00 in room AW1.121. Hope to see you there! Amy 0 - https://fosdem.org/2025/schedule/event/fosdem-2025-4885-openstack-community…

3 3

[openstack][manila][cephfs]About access rule
by Nguyễn Hữu Khôi 31 Jan '25

31 Jan '25

Hello. I setup Manila with Cephfs driver-CephFS NFS shares and I use NFS-Ganesha based “ceph nfs” service. I can create a share and can mount after creating access rule: openstack share access create cephnfsshare ip 10.10.11.76 But I can mount my share from any ip. Is it a bug, or do I understand it wrong? My env: Openstack 2024 with Kolla-Ansible deployment Ceph Quincy Thank you. Regards Nguyen Huu Khoi

2 11

[glance][security][vmt] propose Cyril Roelandt for glance coresec
by Brian Rosmaita 31 Jan '25

31 Jan '25

I'd like to propose an update to the Glance Core Security Contacts team [0], which handles embargoed security issues for Glance project deliverables. The OpenStack Vulnerability Management Team prefers to keep the project core security teams small (because otherwise it kind of defeats the point of having embargoed private security issues). Thus, the changes I propose will keep the glance-coresec team at its current size: Add: Cyril Roelandt (croelandt on IRC). Cyril has been a Glance core since June 2021 and is a thorough and respected reviewer and developer; he also organizes the recurring Glance Review Party. Remove: Erno Kuvaja (jokke on IRC). Erno has been focusing his time away from Glance. On behalf of the Glance project team, I thank Erno for his past service on glance-coresec, and note that Erno continues to participate in the Glance project as a "regular" glance core. If you have any concerns about this change, please communicate them to me or Pranali Deore (Glance PTL) before 23:59 UTC on Wednesday, 29 January 2025. cheers, brian [0] https://launchpad.net/~glance-coresec

1 1

[manila] driver_handles_share_servers not recognized as boolean
by Francesco Di Nucci 31 Jan '25

31 Jan '25

Hi all, I'm running OpenStack 2024.1 Caracal, configured through Puppet, and I'm having an issue with Manila. /etc/manila/manila.conf contains the line "driver_handles_share_servers = True", but setup fails, "/var/log/manila/share.log" reports that "Config opt 'driver_handles_share_servers' has improper value - 'None'. Please define it as boolean." Has anyone encountered this? Where else should I define this? Thanks in advance -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci(a)na.infn.it

3 9

[all] Is oslo.vmware still relevant?
by Herve Beraud 31 Jan '25

31 Jan '25

Hey folks, I observed that oslo.vmware has not received any significant modifications since almost 4 years ago [1]. The only changes proposed to oslo.vmware since a while are just related to infra changes (python versions, tox versions, etc...). Due to the recent news about vmware [2], I wonder if oslo.vmware is still a relevant library in our context and I wonder if it is worth spending time on maintaining it. Do you think we should deprecate and retire this library? Thanks in advance for your opinions. [1] https://opendev.org/openstack/oslo.vmware/commits/branch/master [2] the broadcom story -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

5 6

[nova]Intel RDT CAT Support Missing from OpenStack
by Junya Noguchi (Fujitsu) 31 Jan '25

31 Jan '25

To whom it may concern I have a question regarding the lack of Intel RDT CAT implementation in OpenStack We are planning to commit Resource Monitoring functionality to Openstack for ARM, and are exploring the implementation of Intel RDT on Openstack. We found the following blueprint for the Intel RDT CAT implementation in nova. https://blueprints.launchpad.net/nova/+spec/cat-support However, the Intel RDT CAT feature is not currently implemented in OpenStack. Has the implementation of Intel RDT CAT functionality in Openstack been rejected? Or is it just a development delay? Best regards, Junya Noguchi.

5 8

[neutron] Drivers meeting agenda for Friday, January 31st
by Brian Haley 30 Jan '25

30 Jan '25

Hello Neutrinos: Sorry for the late notice but this is the agenda for tomorrow's drivers meeting: * [RFE] Allow rebalancing of OVN LRPs * https://bugs.launchpad.net/neutron/+bug/2096704 * We quickly discussed this in our weekly meeting and it seemed like a good idea See you then, -Brian

1 0

[manila] Feb 5th and 6th mid cycle
by Carlos Silva 30 Jan '25

30 Jan '25

Hello, zorillas and interested stackers, Manila's 2025.1 Epoxy mid cycle is right around the corner. We will meet next on February 5th and 6th, from 14 to 16 UTC on meetpad [1]. Please add your topics to the mid cycle etherpad [2]. We will use the second day of the mid cycle for collaborative review sessions, so in case you are proposing a feature or would like to have reviewers attention in a specific change, please bring it up and walk us through your change. [1] https://meetpad.opendev.org/manila-epoxy-mid-cycle [2] https://etherpad.opendev.org/p/manila-epoxy-mid-cycle Looking forward to it, carloss

1 0

OS-EXT-SRV-ATTR incomplete in compute api
by Jan 30 Jan '25

30 Jan '25

Hi, is there a reason why some member variables of the nova instance object are returned by the api and some not. For example the "os_type" value is not returned but the "kernel_id" (OS-EXT-SRV-ATTR:kernel_id) is. I have a use case where it would be very helpful to get the "os_type" via the api and python sdk. Is there a chance that a patch implementing this would be accepted? Regards, Jan

3 4

Skip upgrades
by engineer2024 29 Jan '25

29 Jan '25

Is there a way to upgrade openstack older versions like ussuri , victoria, by migrating just the nova, neutron dbs, schema to the latest version by skipping one level at once and then install the latest venvs against the latest migrated galera dbs. On the compute nodes, if we preserve just the var lib nova instances and on top of it reinstall the compute and neutron agents, will it work ? I am asking becos, I don't know what r the dependencies among the major nova versions. Are the db schema and data, the only diffs from one version to another, or is there any thing else ?

5 5

[keystone] Weekly meeting canceled 29-Jan-25
by Dave Wilde 29 Jan '25

29 Jan '25

Hi folks, Apologies for the late notice but I need to cancel the Keystone weekly meeting today due to a scheduling conflict. Please reach out either here or via IRC if you need anything. Thanks!! /Dave

1 0

[rabbitmq] Need help about RabbitMQ quorum HA mode
by İzzettin Erdem 29 Jan '25

29 Jan '25

Hi, In kolla-ansible yoga environment, rabbitmq queues are set to quorum by default instead of classical mirroring, as it seems they are not replicated (per queue has +0 quorum). We tried to find a solution to handle it in configs, but we couldn't find it and we set queues to be replicated by using CLI commands (rabbitmq-queues grow). Now, my questions are: 1- Why do all rabbitmq queues come as non-replicated by default? 2- How can we set HA mode to quorum queues?

5 5

Nova
by engineer2024 29 Jan '25

29 Jan '25

Does nova support flavors where vcpus of a single flavor can be in mixed modes where some of them are pinned and the rest dedicated ? Say, a flavor has 5 vcpus, I want 2 of them to be of dedicated type and the remaining 3 vcpus to be shared

2 2

[neutron][upgrades] IPv6 Prefix Delegation 'dibbler' driver removal
by Brian Haley 28 Jan '25

28 Jan '25

Hi again Stackers, In 2023, during the Bobcat cycle, the Neutron team changed the IPv6 Prefix Delegation (IPv6 PD) 'dibbler' driver to be an experimental feature [0]. The reason was due to it (dibbler) becoming unmaintained/retired upstream, as well as the low level of testing support we had in Neutron for the feature. So what does this mean? We (the neutron cores) have come to the conclusion that it is time to take the next step and remove the driver from the tree [1]. The framework to support IPv6 PD is *not* being removed, but as this is the only in-tree driver the functionality will no longer be available to end-users. We plan on doing this in the current Epoxy cycle. We realize that there may be deployments using IPv6 PD, although we have not to my knowledge ever received a bug against it, so we think any usage is very small. If there is desire to add an in-tree driver back to the code base, there is an open OVN-related bug for that at [2], we have just not had the interest from downstream customers to warrant the investment in this area. Thanks for reading, -Brian, Neutron PTL [0] https://review.opendev.org/c/openstack/neutron/+/879030 [1] https://review.opendev.org/c/openstack/neutron/+/934283 [2] https://bugs.launchpad.net/neutron/+bug/1895972

1 0

[Octavia][magnum] change timeout value
by Satish Patel 28 Jan '25

28 Jan '25

Folks, I am running magnum-cluster-api (mcapi) with openstack to spin up k8s but now I want to change octavia LB timeout. Is there a way to tell magnum to change the timeout value of LB? loadbalancer.openstack.org/timeout-client-data: "120000" loadbalancer.openstack.org/timeout-member-data: "120000"

1 0

[Nova] Nova-compute service flapping on Antelope
by Jakub Darmach 28 Jan '25

28 Jan '25

Hello, Recently I encountered an interesting issue - nova-compute service started to temporarily lose Rabbit connectivity to regain it after a few seconds on Antelope. The issue was replicated on the test environment, without specific steps to replicate though - it just starts to happen after some time. I pasted a log example in the bug I opened [1]. First we can see rabbit logging closing AMQP connection, followed by nova-compute reporting rabbit server being unreachable, with next message being successful reconnection. Restarting nova-compute services helps temporarily, the issue starts to manifest after a few days. Initially disconnects once every few hours, each time in shorter intervals, to the point it happens every minute or so. Did anyone encounter something similar? [1] https://bugs.launchpad.net/nova/+bug/2092297 Pozdrawiam / Best regards, *Jakub Darmach*

3 2

[administrivia] Bounce processing disabled for now
by Jeremy Stanley 28 Jan '25

28 Jan '25

Due to repeated challenges with random messages being rejected by subscribers' mail providers (from DMARC invalidations, lines too long to be forwarded, content misidentified as spam, et cetera), the time required for list administrators to manage the resulting extra work is greater than the benefit we get from Mailman being able to figure out when subscriber addresses become defunct. As such, I've disabled the "bounce processing" feature for the time being, until we can work out solutions to make it less of a burden on our list admins and less confusing/failure prone for the list subscribers. If we do decide to give it another try at some point in the future, after some of the current challenges with it get ironed out, I'll let the list know. -- Jeremy Stanley

1 0

openstack-discuss-owner mailbox
by Albert Braden 28 Jan '25

28 Jan '25

Is anyone manning the openstack-discuss-owner mailbox? I've been writing to that address about the recent glitch that deleted my list subscription and account (and according to the error message, hundreds of others), but I'm not getting a response.

2 3