- openstack-discuss - lists.openstack.org

[kolla-ansible][2023.2] Need some information about using let's encrypt
by wodel youchi 18 Mar '24

18 Mar '24

Hi, I deployed openstack using a self-signed certificate generated by kolla. I am using the encryption both internally and externally. Then I tried to use let's encrypt on the same platform, and it seemed to work, but only on the external URL of openstack (horizon portal). Then I undeployed my openstack, and I tried to redeploy it again, this time Keystone couldn't be deployed, it complained about not being able to verify the self-signed certificate. I had to disable the let's encrypt lines on the globals.yml to be able to deploy openstack. My question is : - Does using let's encrypt cover both internal and external traffic of openstack on all ports or just the 443? - If it does, how to configure globals.yml , especially the lines concerning the certificates? - If it does not, it covers only Horizon on 443, how could someone combine the use of self-signed to let's encrypt use? is it even possible? Regards.

2 3

[Kolla-ansible][Trove][2023.2] Unable to create datastore when using self-signed certificate
by wodel youchi 18 Mar '24

18 Mar '24

Hi, I am trying to complete trove configuration, by creating a datastore. I am using a self-signed certificate in my deployment. When trying to create a datastore I got : ble but deprecated behaviour. Please set this to True. 2024-03-18 12:26:20.245 35 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2024-03-18 12:26:20.249 35 WARNING keystonemiddleware.auth_token [-] Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use memcache for the auth_token token cache by setting the memcached_servers option. 2024-03-18 12:26:20.685 35 INFO trove.extensions.mgmt.datastores.service [None req-ef8a2f03-8500-40e0-88fe-4fac6ac5c9cb 85c09dd86fc846f98c3b4add7f64d76f 54589053b612438ab9c4d3f800c75000 - - - -] Tenant: '54589053b612438ab9c4d3f800c75000' is adding the datastore version: '5.7.29' to datastore: 'mysql' *2024-03-18 12:26:20.719 35 WARNING keystoneauth.identity.generic.base [None req-ef8a2f03-8500-40e0-88fe-4fac6ac5c9cb 85c09dd86fc846f98c3b4add7f64d76f 54589053b612438ab9c4d3f800c75000 - - - -] Failed to discover available identity versions when contacting https://dashint.cdn.example.com:5000 <https://dashint.cdn.example.com:5000>. Attempting to parse version from URL.: keystoneauth1.exceptions.connection.SSLError: SSL exception connecting to https://dashint.cdn.example.com:5000 <https://dashint.cdn.example.com:5000>: HTTPSConnectionPool(host='dashint.cdn.example.com <http://dashint.cdn.example.com>', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)')))* *2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi [None req-ef8a2f03-8500-40e0-88fe-4fac6ac5c9cb 85c09dd86fc846f98c3b4add7f64d76f 54589053b612438ab9c4d3f800c75000 - - - -] e85a7be5-6d90-456e-8c24-4125098a6228: Could not find versioned identity endpoints when attempting to authenticate. Please check that your auth_url is correct. SSL exception connecting to https://dashint.cdn.example.com:5000 <https://dashint.cdn.example.com:5000>: HTTPSConnectionPool(host='dashint.cdn.example.com <http://dashint.cdn.example.com>', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))): keystoneauth1.exceptions.discovery.DiscoveryFailure: Could not find versioned identity endpoints when attempting to authenticate. Please check that your auth_url is correct. SSL exception connecting to https://dashint.cdn.example.com:5000 <https://dashint.cdn.example.com:5000>: HTTPSConnectionPool(host='dashint.cdn.example.com <http://dashint.cdn.example.com>', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)')))* 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi Traceback (most recent call last): 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/connectionpool.py", line 703, in urlopen 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi httplib_response = self._make_request( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/connectionpool.py", line 386, in _make_request 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi self._validate_conn(conn) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi conn.connect() 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/connection.py", line 419, in connect 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi self.sock = ssl_wrap_socket( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/util/ssl_.py", line 449, in ssl_wrap_socket 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi ssl_sock = _ssl_wrap_socket_impl( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return ssl_context.wrap_socket(sock, server_hostname=server_hostname) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/eventlet/green/ssl.py", line 446, in wrap_socket 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return GreenSSLSocket(sock, *a, _context=self, **kw) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/eventlet/green/ssl.py", line 140, in __init__ 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi self.do_handshake() 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/eventlet/green/ssl.py", line 312, in do_handshake 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return self._call_trampolining( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/eventlet/green/ssl.py", line 162, in _call_trampolining 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return func(*a, **kw) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/usr/lib64/python3.9/ssl.py", line 1343, in do_handshake 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi self._sslobj.do_handshake() 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi During handling of the above exception, another exception occurred: 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi Traceback (most recent call last): 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/requests/adapters.py", line 489, in send 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi resp = conn.urlopen( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/connectionpool.py", line 787, in urlopen 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi retries = retries.increment( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/util/retry.py", line 592, in increment 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi raise MaxRetryError(_pool, url, error or ResponseError(cause)) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host=' dashint.cdn.example.com', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi During handling of the above exception, another exception occurred: 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi Traceback (most recent call last): 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/session.py", line 1014, in _send_request 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi resp = self.session.request(method, url, **kwargs) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/requests/sessions.py", line 587, in request 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi resp = self.send(prep, **send_kwargs) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/requests/sessions.py", line 701, in send 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi r = adapter.send(request, **kwargs) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/requests/adapters.py", line 563, in send 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi raise SSLError(e, request=request) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi requests.exceptions.SSLError: HTTPSConnectionPool(host=' dashint.cdn.example.com', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi During handling of the above exception, another exception occurred: 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi Traceback (most recent call last): 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/identity/generic/base.py", line 133, in _do_create_plugin 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi disc = self.get_discovery(session, 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/identity/base.py", line 605, in get_discovery 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return discover.get_discovery(session=session, url=url, 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/discover.py", line 1459, in get_discovery 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi disc = Discover(session, url, authenticated=authenticated) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/discover.py", line 539, in __init__ 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi self._data = get_version_data(session, url, 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/discover.py", line 106, in get_version_data 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi resp = session.get(url, headers=headers, authenticated=authenticated) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/session.py", line 1133, in get 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return self.request(url, 'GET', **kwargs) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/session.py", line 923, in request 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi resp = send(**kwargs) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/session.py", line 1018, in _send_request 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi raise exceptions.SSLError(msg) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi keystoneauth1.exceptions.connection.SSLError: SSL exception connecting to https://dashint.cdn.example.com:5000: HTTPSConnectionPool(host=' dashint.cdn.example.com', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))) Regards.

1 0

Is direct upgrade from Yoga to Antelope supported?
by Michel Jouvin 18 Mar '24

18 Mar '24

Hi, We are in the process of upgrading our Yoga cloud to Antelope and I was wondering if, Antelope being a SLURP release, it was supported to do it in 1 step or if Antelope was the first release from which it will be possible to skip one release and to go directly to the next SLURP release (Caracal). I didn't find a clear answer in the documentation... Best regards, Michel

5 5

New instance, provider vlan network, network unpredictable
by Mika Saari 18 Mar '24

18 Mar '24

Hi, I am using latest kolla-ansible installation. Network is in openvswitch type. My question is related to my provider network with VLAN type (external HW router, external DHCP, ...). The network is directly connected to the hardware through HW switch <-tagged-> bond0 <-> br-ex1 <-> openvswitch. When I create a new instance (cirros) to this provider network the instance can not connect to the metadata server during the bootup. The dhcp is trying to fetch the address, and I can sniff the data in bond0, br-ex1, br-int and br-tun and the dhcp request leaves the hardware, DHCP server sends the reply, but the reply wont go through back to the instance. If I force a static IP to this cirros instance and try pinging the network, the ICMP doesn't leave the bond0. After around 15 minutes the network starts suddenly to work and dhcp reply goes through and the instance gets the dynamic IP. After this the whole network starts to work fluently. Any ideas what might be the problem? Thank you very much!

3 5

[neutron] Bug Deputy Report March 11 - March 17
by Nurmatov Mamatisa 18 Mar '24

18 Mar '24

Hi team, Below is the week summary of bug report for last week. 1 rfe was proposed. Undecided bugs needs further triage. Details: High ---- - https://bugs.launchpad.net/neutron/+bug/2057492 - [devstack-tobiko-neutron] periodic broken running on ubuntu focal - In progress: https://review.opendev.org/c/x/tobiko/+/912718 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/2057770 - [neutron-dynamic-routing] LBaaS constants still present in older versions of Neutron - Fix released: https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/912737 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2057914 - [neutron-vpnaas-dashboard] UT failing due to a change in Django - Fix released: https://review.opendev.org/c/openstack/neutron-vpnaas-dashboard/+/912911 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2057942 - external_gateways KeyError when running add_gw_port_info_to_logical_router_port - In progress: https://review.opendev.org/c/openstack/neutron/+/913408 - Assigned to Brian Haley Medium ------ - https://bugs.launchpad.net/neutron/+bug/2056778 - TestOVNMechanismDriver some ipv6 tests fails if host has ipv6 dns_names configured - Fix released: https://review.opendev.org/c/openstack/neutron/+/912475 (backported to stable/2023.1 , stable/2023.2) - Assigned to Arnau Verdaguer - https://bugs.launchpad.net/neutron/+bug/2057698 - Concurrent routerroute update fails on deletion with AttributeError - In progress: https://review.opendev.org/c/openstack/neutron/+/912629 - Assigned to Sebastian Lohff - https://bugs.launchpad.net/neutron/+bug/2057983 - The HA flag of user defined flavos routers is always set to true - In progress: https://review.opendev.org/c/openstack/neutron/+/913276 - Miguel Lavalle RFE --- - https://bugs.launchpad.net/neutron/+bug/2058006 - [RFE] Allow multiple segments per host in ML2/OVN Undecided --------- - https://bugs.launchpad.net/neutron/+bug/2058018 - AssertionError: do not call blocking functions from the mainloop Best regards, Mamatisa Nurmatov

1 0

[kuryr-libnetwork] Run with a service container or install on the compute node?
by Francesco Di Nucci 18 Mar '24

18 Mar '24

Hello, I am working to install Zun on a OpenStack instance, so I'm required to set up Docker with kuryr-libnetwork. I see that there are three possible approaches: * Running it inside a service container, using the Docker Engine on the compute nodes (https://opendev.org/openstack/kuryr-libnetwork#getting-it-running-with-a-se…) * Installing it directly on the compute nodes (https://opendev.org/openstack/kuryr-libnetwork#getting-it-running-with-a-se…) * Installing it as a Docker plugin (https://opendev.org/openstack/kuryr-libnetwork#getting-it-running-with-a-se…) Does anyone know the advantages/disadvantages of the three approaches? I've tried to find a comparison, but the OpenStack docs only include a procedure to install it on a Ubuntu Compute Node (https://docs.openstack.org/kuryr-libnetwork/latest/install/compute-install-…) Best regards Francesco Di Nucci

1 0

Neutron external connectivity to and from tenant VMs : Help
by KK CHN 16 Mar '24

16 Mar '24

Hi, Neutron external network connection to and from instances.. Problem statement. I have deployed AIO on a Virtual Machine. (Created the demo networks, flavors and images by init-runonce script.) I created a cirros instance with a demo-net instance, and the instance is spawning with 10.0.0.0/24 ips. *inside the cirros Vm I am able to ping its own ip(10.0.0.73) and 10.0.0.1 and the "public1" network gateway 10.176.17.63 .. But unable to ping the Base VM IP 10.176.17.61* Any hints how I can reach the Base VM IP 10.176.17.61 ? from 10.0.0.73 and vice versa .. What steps I missed or I am unaware of? To get the external connection/ping/access..? I have referred many documents and I am at the end of the rope, but couldn't find a solution or what the exact issue is , any guidance much appreciated... Krish. If more information is required : There are two networks by default created 1. public1. with gateway as 10.176.17.63 public1-subnet <http://10.220.0.24/project/networks/subnets/3b9e11ae-4595-4e4c-ba71-1fba209…> 10.176.16.0/23 IPv4 10.176.17.63 2. demo-net demo-subnet <http://10.220.0.24/project/networks/subnets/80e8d33e-6276-450b-bb46-76446dc…> 10.0.0.0/24 IPv4 10.0.0.1 These are the values given in the " kolla_ansible_venv3/share/kolla-ansible/init-runonce" script.. ################################################################################# DEMO_NET_CIDR=${DEMO_NET_CIDR:-'10.0.0.0/24'} DEMO_NET_GATEWAY=${DEMO_NET_GATEWAY:-'10.0.0.1'} DEMO_NET_DNS=${DEMO_NET_DNS:-'8.8.8.8'} ENABLE_EXT_NET=${ENABLE_EXT_NET:-1} EXT_NET_CIDR=${EXT_NET_CIDR:-'10.176.17.0/23'} EXT_NET_RANGE=${EXT_NET_RANGE:-'start=10.176.17.62,end=10.176.17.80'} EXT_NET_GATEWAY=${EXT_NET_GATEWAY:-'10.176.16.1'} ################################################################################ Demo Router: (ee6500a8-039c) <http://10.220.0.24/project/networks/ports/ee6500a8-039c-4ceb-8dc0-b37e2c3a2…> - 10.176.17.63 Active External Gateway UP (bb4c9437-82fa) <http://10.220.0.24/project/networks/ports/bb4c9437-82fa-4689-b125-9edc1987c…> - 10.0.0.1 Active Internal Interface UP (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml --- workaround_ansible_issue_8743: yes config_strategy: "COPY_ALWAYS" kolla_base_distro: "ubuntu" openstack_release: "2023.1" kolla_internal_vip_address: "10.220.0.24" // a free unused IP address in 10.220.0.0/24 segment. kolla_external_vip_address: "{{ kolla_internal_vip_address }}" kolla_container_engine: docker network_interface: "ens224" /// this vNIC is with ip 10.220.0.51 and without internet - a vlan segment for internal experiments. neutron_external_interface: "ens160" // this is the vNIC with my organization dhcp leased ip 10.176.17.61 assigned and up and running neutron_plugin_agent: "openvswitch" nova_compute_virt_type: "qemu" (kolla_ansible_venv3) ubuntu@ub Strange Behaviour: When I create another instance ( Cirros) with the network selected as " public1" network, the instance is spawning the horizon dashboard showing IP as 10.176.17.70 extTestVM <http://10.220.0.24/project/instances/9e744ab1-7a21-4d55-ad03-c01d5631657a/> cirros 10.176.17.70 But inside this VM $ ip a /// lists the IP address of this VM as 169.254.198.1/16 ?? why 169.254 .198.1/16 ? It should be 10.176.17.70 right ?? What's happening ?? Confused ..

3 4

[all][tc][policy] RBAC discussion in 2024.2 PTG
by Ghanshyam Mann 15 Mar '24

15 Mar '24

Hello Everyone, I have booked the Tuesday 15-16 UTC slot Folsom room for the RBAC discussion. Feel free to add the topics/queries to be discussed or your project-related RBAC session info in the below etherpad: - https://etherpad.opendev.org/p/rbac-2024.2-ptg -gmann

1 0

Enabling SNAT for Non-Private Addresses
by Jan Wasilewski 15 Mar '24

15 Mar '24

Hi everyone, I'd like to inquire about SNAT settings for non-private addresses. I've created a network with the subnet 100.70.0.0/24 (please note, it starts with 100, not 10). I'm wondering why all hosts attached to such a network cannot establish an internet connection when the network is connected to a router with an external gateway that has internet access. However, I found documentation here: https://docs.openstack.org/neutron/zed/admin/intro-nat.html, which states that SNAT works only for private addresses (so mine are not included). Is there a way to enable SNAT for my subnet as well, but in a different way than manually configuring iptables settings on top of Neutron nodes? If so, could anyone share it? Thanks in advance for your help. /Jan Wasilewski

2 3

[kolla-ansible][Antelope][Heat] Auto Scaling Group - Cancel Update
by Devin Patterson 15 Mar '24

15 Mar '24

Hello, We are working on a workflow to cancel in progress rolling updates for the resource OS::Heat::AutoScalingGroup When we run the command `openstack stack cancel <stack-id> it cancels the Heat stack update, but the Auto-Scaling group finishes updating all VMs in the group. We need a way to either rollback or completely cancel the Auto Scaling Group update and not replace any additional VMs. Any help would be appreciated. Devin

1 0