- openstack-discuss - lists.openstack.org

[publiccloud-sig] Reminder - next meeting May 29th - 0700 UTC
by Felix Kronlage-Dammers 28 May '24

28 May '24

Hi everyone, This Wednesday (May 29th, tomorrow) the next meeting of the public cloud sig is going to happen. We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG Likely we will pick up the discussions from our Forum Session at OID Berlin. See my summary that I sent to this list[1]. See you tomorrow! felix [1] <url: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…> -- Felix Kronlage-Dammers 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

Re: [Octavia] octavia not setting up load balancers
by Jaime Ibar 28 May '24

28 May '24

Hi, I have set debug to true and I can see the following but not sure if they're related though Disabling service 'block-storage': Encountered an exception attempting to process config for project 'cinder' (service type 'block-storage'): no such option valid_interfaces in group [cinder]: oslo_config.cfg.NoSuchOptError: no such option valid_interfaces in group [cinder] Disabling service 'compute': Encountered an exception attempting to process config for project 'nova' (service type 'compute'): no such option valid_interfaces in group [nova]: oslo_config.cfg.NoSuchOptError: no such option valid_interfaces in group [nova] 2024-05-27 19:09:32.136 225246 WARNING openstack [None req-588327db-96d5-4377-ba72-b603731f9568 - c2270ba97baa40cbbb17f89d6980a2d6 - - default default] Disabling service 'image': Encountered an exception attempting to process config for project 'glance' (service type 'image'): no such option valid_interfaces in group [glance]: oslo_config.cfg.NoSuchOptError: no such option valid_interfaces in group [glance] Jaime On 27/05/2024 21:20, Winicius Allan wrote: > I understood. Is there any error log level message or anything like that? > > Em seg., 27 de mai. de 2024 às 15:19, Jaime Ibar <jim2k7(a)gmail.com> > escreveu: > > Hi Winicius, > > yes, I have the Octavia:health-mgr interface and it shows as > Active and up, in fact, I can ssh into the amphora from > the management network. > > Thanks > Jaime > > On Mon, 27 May 2024 at 18:54, Winicius Allan > <winiciusab12(a)gmail.com> wrote: > > Hi Jaime, > > In general, a load balancer stuck in the PENDING_CREATE state > could be a network problem. Do you have a network interface on > your control node that belongs to the same network as Amphora? > > Regards. > > Em seg., 27 de mai. de 2024 às 12:51, Jaime Ibar > <jim2k7(a)gmail.com> escreveu: > > Nope, I can't see anything. > > This is what I can see > > [...] > request url / request > /usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py:652 > request url https://172.16.4.56:9443// request > /usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py:655 > Connected to amphora. Response: <Response [200]> request > /usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py:677 > Amphora f3809732-80d8-4795-a5cb-cb36e63bc895 has API > version 1.0 _populate_amphora_api_version > /usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py:104 > > Update DB for loadbalancer id > Marking all listeners of loadbalancer > ce31155c-3484-4ff0-8740-fcd8c0915a1c ACTIVE execute > > Mark ACTIVE in DB for load balancer id: > [...] > > So all seems to be OK but nothing in the amphora. > > Thanks > Jaime > > On Mon, 27 May 2024 at 16:25, Oliver Weinmann > <oliver.weinmann(a)me.com> wrote: > > Ok, anything suspicious in the Octavia worker logs? > > Von meinem iPhone gesendet > >> Am 27.05.2024 um 17:17 schrieb Jaime Ibar >> <jim2k7(a)gmail.com>: >> >> >> Hi Oliver, >> >> thanks for the tip but after increasing the quotas, >> the problem persists :( >> >> Jaime >> >> On Mon, 27 May 2024 at 12:20, Oliver Weinmann >> <oliver.weinmann(a)me.com> wrote: >> >> Hi, >> >> Just a quick guess. Check the quotas for security >> groups of the service tenant. >> >> In our deployment we had a similar issue and saw >> errors indicating this in the logs. >> >> Cheers, >> Oliver >> >> Von meinem iPhone gesendet >> >> > Am 27.05.2024 um 13:16 schrieb Jaime Ibar >> <jim2k7(a)gmail.com>: >> > >> > >> > Hi all, >> > >> > I've been running Octavia with no issues so far >> and now it stopped working >> > with no reasons(no recent upgrades other that OS). >> > When I create a load balancer, sometimes the >> amphora is launched successfully >> > but some others is not. >> > When it's launched, no listeners, backends, >> pools are created and the load balancer >> > gets stuck in either, pending create or pending >> update state, and deleting all the >> > load balancer details from the database is the >> only option of getting rid of it. >> > >> > I can ssh into the amphora but I can't see any >> error, gunicorn is listening >> > on port 9443 but no haproxy instances are >> created(haproxy-<uuid>) on >> > /var/lib/octavia >> > >> > I'm running 2023.2 Bobcat version. >> > >> > Any ideas? >> > >> > TIA >> > Jaime >> > >> > -- >> > salu2 >> > >> > Jaime >> >> >> >> -- >> salu2 >> >> Jaime > > > > -- > salu2 > > Jaime > > > > -- > salu2 > > Jaime > -- Jaime

1 0

[Tempest] [Blazar] Connection Refused Error 111 on Blazar tempest plugin
by Tran, Kenny 28 May '24

28 May '24

First time asking a question on the mailing list, I am trying to set up tempest against a quick start yoga (kolla-ansible) deployment with Keystone, Zun, Heat, Blazar, and Nova (1 controller, 1 compute). Default tempest tests are behaving as expected but when I try to run the blazar plugin tests they fail with Errno 111 Connection Refused. I ran a tcpdump on the tempest server side and saw no issues. Tcpdump on controller showed a reset when trying to connect to keystone. Is this an issue with blazar not being able to authenticate against the openstack deployment? The default tempest tests succeed so I don't think my admin_password admin_username etc. are incorrect. Kenny Tran Iowa State University Student Computer Engineer 515-441-5237 | trantk(a)iastate.edu

2 1

[Octavia] octavia not setting up load balancers
by Jaime Ibar 27 May '24

27 May '24

Hi all, I've been running Octavia with no issues so far and now it stopped working with no reasons(no recent upgrades other that OS). When I create a load balancer, sometimes the amphora is launched successfully but some others is not. When it's launched, no listeners, backends, pools are created and the load balancer gets stuck in either, pending create or pending update state, and deleting all the load balancer details from the database is the only option of getting rid of it. I can ssh into the amphora but I can't see any error, gunicorn is listening on port 9443 but no haproxy instances are created(haproxy-<uuid>) on /var/lib/octavia I'm running 2023.2 Bobcat version. Any ideas? TIA Jaime -- salu2 Jaime

3 7

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-18)
by Goutham Pacha Ravi 27 May '24

27 May '24

Hello Stackers, We're 18 weeks away from the 2024.2 (Dalmatian) release [1]. The Call for Proposals for the upcoming Open Infra Summit is still open [2], but it will close in a couple of days (May 29th, 2024). If you're planning to attend, I encourage you to submit a talk! In the past week, the OpenStack Technical Committee continued its spring cleaning exercise – this time, the party was on PyPi. We also identified dates for the TC and PTL elections for the 2025.1 ("E") release cycle [3]. The nomination period for the TC and PTL elections will begin on 2024-08-14 at 23:45 UTC and will conclude on 2024-08-28 at 23:45 UTC. The elections will be held between 23:45 UTC on 2024-09-04 and 23:45 UTC on 2024-09-18. === Weekly Meeting === We identified 207 maintainers for removal across 146 PyPi packages [4]. The cleanup task is large and manual due to a lack of API. We've also identified packages where "openstackci" cannot remove maintainers due to a lack of ownership. This is likely a long-drawn effort. I'll keep you posted as we make progress. We had a few remaining project updates pending from the last release cycle, and one of them concerned the OpenStack Charms team. Since the TC didn't have context on the health of the team and its plans, we decided to gather some information on this mailing list. We're also excited to publish the first draft for the next election dates/process, courtesy of our Election Official, Ian Y. Choi (ianychoi). This election will be socialized with early and periodic notifications to address concerns expressed regarding the lack of visibility and poor voter turnout in past elections. This meeting, like all of our IRC meetings, was logged to eavesdrop [5]. Our next weekly IRC meeting is tomorrow! The agenda is pretty light [6], likely owing to the fact that a few TC members are returning from a long weekend holiday. === Governance Proposals === ==== Merged ==== Retire devstack-gate | https://review.opendev.org/c/openstack/governance/+/919629 ==== Open for review/discussion ==== Appoint ChunYang Wu as PTL of Trove | https://review.opendev.org/c/openstack/governance/+/920462 Clarify the project retirement vs. project's repository retirement | https://review.opendev.org/c/openstack/governance/+/919984 Simplifying house rules for project updates | https://review.opendev.org/c/openstack/governance/+/920318 Update to include docs and miscellaneous repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 Add DPL model & liaison reset policy | https://review.opendev.org/c/openstack/governance/+/916833 Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://2024.openinfraasia.org/ [3] https://review.opendev.org/c/openstack/election/+/920092 [4] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L52 [5] https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-21-18.00.log.html [6] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

How to assign an ip-address to a server on creation
by Nine, Harmon S 27 May '24

27 May '24

Hello. I'm using the openstack connection api in python to create a server. The server is getting created, but the "create_server" call is not assigning the ip-address to the server that is specified in the call. flavor_id = 'ed88b5d6-150d-4715-8de0-8a2df0a1746a' image_id = '399ae60e-7f73-476e-aad7-13aebcad84a1' networks = [{'uuid': '978ebb40-8ee4-4c0b-932e-83dce7e182dd'}] ip_addresses =[{'subnet_id': '978ebb40-8ee4-4c0b-932e-83dce7e182dd', 'ip_address': '10.0.0.153'}] # also tried ip_addresses = ['10.0.0.153'] instance = conn.compute.create_server( name='testmachine', flavor_id=flavor_id, image_id=image_id, ips=ip_addresses, networks=network_uuid_list, key_name='key_name' ) What is the format of the "ips" argument? Are there other arguments that need to be specified? Thanks for any help you can provide 🙂 -- Harmon

3 5

[kolla][OpenstackAnsible] 2024.1 Caracal cycle-trailing release deadline reminder
by Herve Beraud 27 May '24

27 May '24

Hello teams with trailing projects, The 2024.1 Caracal cycle-trailing release deadline is next week [1], and all projects following the cycle-trailing release model must release their 2024.1 Caracal deliverables by June 6th, 2024. The following trailing projects haven't been released yet for 2024.1 Caracal, convenience patches have been proposed: OSA team's deliverables: - https://review.opendev.org/c/openstack/releases/+/919484 - https://review.opendev.org/c/openstack/releases/+/919483 Kolla team's deliverables: - https://review.opendev.org/c/openstack/releases/+/919486 This is just a friendly reminder to allow you to release these projects in time. Please, ensure to provide feedback or to update these patches before the deadline. Do not hesitate to ping us if you have any questions or concerns. [1] https://releases.openstack.org/dalmatian/schedule.html#d-cycle-trail Thanks, -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[nova][scheduler] nova scheduler to balance vms more randomly
by Satish Patel 27 May '24

27 May '24

Folks, I have noticed when I spin up a bunch of vms then they all go to the same hypervisor until it runs out of resources. I can understand that it's trying to fill the hypervisor before it picks the next one. But it's kind of dangerous behavior. For example one customer created 3 vms to build a mysql galera cluster and all those 3 nodes endup on the same hypervisor (This is dangerous). I would like openstack to pick the hypervisor more randomly if resources are available in the pool instead of trying to fill the hypervisor. How do I change that behavior? ( There is a feature called affinity but again I would like nova to place vm more randomly instead shaving all to a single node). I am not an expert in scheduler logic so please educate me if I am missing something here.

5 5

Difficulty Create/Upload Images
by Cakra Wirabuana 24 May '24

24 May '24

Hi everyone, I have a difficulty when creating image. I have downloaded the file with both .img and .iso formats and I have tried various format options (QCOW2, RAW, ISO, etc) but it still fails and a notification appears as in the image I attached to this email. Does anyone know the cause of this and what is the solution? If it turns out that I have to create an image via CLI, how do I do it? I am using Ubuntu 22.04.4 LTS. Thank you, Cakra Wirabuana [image: image.png]

2 1

[openstack][magnum] Error with QueuePool limit of size
by Nguyễn Hữu Khôi 23 May '24

23 May '24

Hello. I am using Magnum 18.0.0.0rc2.dev2 in OPS 2024.01 with Magnum-Cluster-API(0.17.0) from Vexxhost. But I have these errors as: Ignore error [QueuePool limit of size 1 overflow 50 reached, connection timed out, timeout 30.00 (Background on this error at: https://sqlalche.me/e/14/3o7r) when syncing up cluster status.: sqlalchemy.exc.TimeoutError: QueuePool limit of size 1 overflow 50 reached, connection timed out, timeout 30.00 Full log is in: https://paste.sh/gWg28T2s#zctJBJsW34bX9pG705VR5PMP Thank you. Nguyen Huu Khoi

2 2