March 2024 - openstack-discuss - lists.openstack.org

Yoga Magnum: csi-cinder-controllerplugin-0 fails to initialize properly because of obsolete API
by Michel Jouvin 19 Mar '24

19 Mar '24

Hi, We recently upgraded our cluster to Yoga and since then we cannot successfully start pods in clusters using K8s 1.23 that require a volume. The volume is properly created but attachment fails because it is trying to use v1beta1.CSINode and v1beta1.VolumeAttachment that no longer exists. I found a reference to this in https://github.com/kubernetes/cloud-provider-openstack/issues/1845 but the way to fix it is unclear. I tried to use last version of CSI-related stuff from registry.k8s.io (playing with labels and source), but I then got another problem which may be related (it is my guess) to the fact that I'm using too recent versions. Is somebody using sucessfully Magnum Yoga/K8bs 1.23 combination sucessfully and what is the trick to do it? Thanks in advance for any help. Best regards, Michel

3 12

[skyline] Running a Skyline in "subdirectory"
by Dmitriy Rabotyagov 19 Mar '24

19 Mar '24

Hey folks, I was looking into a way to make both Horizon and Skyline work at the same time, and found out that I'm not really able to make Skyline to run in sub-URL. So for instance the plan was to place Horizon under /horizon (which is easily doable) and then Skyline under /skyline. However so far I haven't found any setting or anything that would allow me to do so. Basically, I've realized that static content is _really_ static, which means it does have hardcoded URIs: https://opendev.org/openstack/skyline-console/src/branch/master/skyline_con… So either I'm just not realizing the very simple technique which allows to overcome hardcoded in static files URIs (like some rewrite?), or just serving Skyline from a subdirectory is not possible by design... Would be great if someone could share their experience about Skyline and if anyone managed to do what I'm looking for. Thanks in advance

2 1

[Freezer] Is Freezer dead?
by pi3.14＠tuta.io 18 Mar '24

18 Mar '24

Hi folks, is Freezer still supported? I don't see any real development going on with it. Is it recommended to use in a production Cloud environment? Are there other free and open source alternatives to Freezer? Thanks Roby

8 19

[publiccloud-sig] Reminder - next meeting March 20th - 0800 UTC
by Felix Kronlage-Dammers 18 Mar '24

18 Mar '24

Hi everyone, This Wednesday (March 20th) the next meeting of the public cloud sig is going to happen. We’ll be meeting at 0800 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG See you Wednesday! felix -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[manila] Docs bugsquash: March 19th - 22nd
by Carlos Silva 18 Mar '24

18 Mar '24

Hello, Zorillas! As mentioned in last week's meeting, we are having a bugsquash/hack-a-thon focused on reducing our documentation backlog. I have created an ethercalc with some of the bugs we intend to work on [1]. - We will have the kick-off meeting on March 19th, 15 UTC and we will use meetpad [2] - We will use the Manila upstream meeting slot (March 21st, 15 UTC) as a checkpoint. In case you are planning to join and the bug you intend to work on is not in the ethercalc, please add it. [1] https://ethercalc.net/c9z5705xdeui [2] https://meetpad.opendev.org/ManilaCaracalBugsquash Looking forward to closing some docs bugs with you! Regards, carloss

1 0

[tc] Next Meeting Tomorrow, Tues March 19, 1800 UTC
by Jay Faulkner 18 Mar '24

18 Mar '24

Hi all, The next meeting of the Technical Committee is tomorrow, March 19, at 1800 UTC in #openstack-tc in OFTC. The proposed agenda is: Agenda - Roll call - Follow up on tracked action items - Gate health check - Implementation of Unmaintained branch statuses - TC vPTG 2024.2 / TC Tracker 2024.1 - https://etherpad.opendev.org/p/tc-2024.1-tracker - https://etherpad.opendev.org/p/apr2024-ptg-os-tc - Open Discussion and Reviews Thank you, Jay Faulkner OpenStack TC Chair

1 0

Survey to schedule i18n SIG 2024.04 PTG
by Seongsoo Cho 18 Mar '24

18 Mar '24

Hi i18n SIG I create a survey to schedule i18n SIG 2024.04 PTG. Please let me know, what time and day works best for you. survey: https://framadate.org/tY49ETqtFD9R4LPt Best Regards Seongsoo -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

1 0

[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