April 2024 - openstack-discuss - lists.openstack.org

[kolla-ansible][horizon]Create instance default parameters
by Franck VEDEL 10 Apr '24

10 Apr '24

Hi, With horizon, is it possible de have this default parameter when you create an instance: in source, create a new volume: « No ». And.. if it’s possible, how configure this with kolla-ansible ? Thank’s for your help. Franck

2 4

[keystone] Weekly meeting canceled 10-April-2024
by Dave Wilde 10 Apr '24

10 Apr '24

Hello all, I'm canceling this weeks keystone meeting in lieu of the PTG sessions we're holding today and tomorrow. Hope to see you there! /Dave

1 0

[kolla][kolla-ansible] How to debug container crashing or restarting
by Satish Patel 10 Apr '24

10 Apr '24

Folks, As soon as I deployed opensearch on the Zed release of openstack and found the opensearch_dashborad container kept restarting. So my question is how do I troubleshoot this kind of container crashing issue. Are there any guides to follow like stop container restart tasks and then get inside container check logs etc? I have checked docker logs <container_name> but didn't find any strange issue and logs are empty in /var/log/kolla/opensearch_dashborad/ In short I am clueless and I would like to change restart policy in docker so I can manually restart daemon to debug my issue. This is what logs showing in docker logs opensearch_dashboard INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2020-12/index.js INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2020-12/meta/meta-data.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2020-12/meta/core.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2020-12/meta/unevaluated.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2020-12/meta/content.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2020-12/meta/applicator.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2020-12/meta/format-annotation.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2020-12/meta/validation.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2019-09/meta INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2019-09/schema.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2019-09/index.js INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2019-09/meta/meta-data.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2019-09/meta/core.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2019-09/meta/content.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2019-09/meta/applicator.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2019-09/meta/validation.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/refs/json-schema-2019-09/meta/format.json INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/vocabularies/core INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/vocabularies/format INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/vocabularies/discriminator INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/vocabularies/jtd INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/vocabularies/validation INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/vocabularies/applicator INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_modules/ajv/dist/vocabularies/dynamic INFO:__main__:Setting permission for /usr/share/opensearch-dashboards/node_mo

2 1

[ironic] PTG schedula
by Riccardo Pittau 10 Apr '24

10 Apr '24

Hello ironicers! A quick reminder on the Ironic PTG schedule for this week: Tuesday 09/04 13-17 UTC Wednesday 10/04 13-17 UTC Thursday 11/04 13-16 UTC You can find the full schedule and topics here https://etherpad.opendev.org/p/ironic-ptg-april-2024 Ciao Riccardo

1 2

[Glance] Cancelling Weekly Meeting for this Week
by Pranali Deore 09 Apr '24

09 Apr '24

Hello, As discussed during last week's meeting, cancelling the meeting for this week(11th April) since we all are meeting in PTG. See you all at PTG ! Thanks & Regards, Pranali

1 0

[Octavia] weekly meeting cancelled
by Gregory Thiemonge 09 Apr '24

09 Apr '24

Hi Folks, Tomorrow's weekly meeting is cancelled because of the PTG. Thanks, Greg

1 0

[kolla] cancelling weekly meeting on 10th April
by Michał Nasiadka 09 Apr '24

09 Apr '24

Hello, Since we all met on PTG sessions - let’s cancel weekly meeting this week. See you on 17th April Michał Nasiadka mnasiadka(a)gmail.com

1 0

[all] Package reproducibility: shall we hard-wire our CI to avoid it in the future?
by Thomas Goirand 09 Apr '24

09 Apr '24

Hi, It used to be that a number of packages were not reproducible. If you do not know why reproducibility of packages is important, please read on: https://reproducible-builds.org/ This has been patched numerous times in numerous packages. However, it looks like the community is still not aware of the problem, and how to avoid it. One of the very common pitfall, is adding a default in an oslo.config string, that leaks properties of the build host, like for example the hostname, the number of CPU cores, and so on. Here's a very common example that was commited last summer: https://review.opendev.org/c/openstack/oslo.messaging/+/889425/9/oslo_messa… Yet the fix is super simple, thanks to oslo.messaging sample_default: https://review.opendev.org/c/openstack/oslo.messaging/+/915314 If I'm writing this, it is *not* to point at anyone, especially *not* the commiter of the above patch. it just happen to be the latest occurrence I noticed thanks to the Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068377 This message is only to raise awareness of the problem, and avoid having it happen again. I also wonder: would it be possible to have our CI avoid this type of mistake? It wouldn't be so hard to have the doc build twice, with different hostname, CPUs, etc. configuration, would it? (note: I'm not volunteering, just pushing for the idea...) Cheers, Thomas Goirand (zigo)

2 1

[openstack-helm] PTG schedule
by Vladimir Kozhukalov 09 Apr '24

09 Apr '24

Hey team, This is just a reminder that we booked two hours on Wednesday 04/10/2024 at 13:00 UTC and 14:00 UTC in the Cactus meeting room. Etherpad is here [1]. Feel free to add your topics for the discussion. Booking table is here [2]. [1] https://etherpad.opendev.org/p/apr2024-ptg-os-helm [2] https://ptg.opendev.org/ptg.html -- Best regards, Kozhukalov Vladimir

1 0

OpenStack OVN add secondary external network
by damage.alders-0j＠icloud.com 08 Apr '24

08 Apr '24

I've setup OpenStack version 2023.2 with with devstack on a Ubuntu 22.04 baremetal. I originally had one NIC (eth1, 192.XX.XX.XX) that works fine. Now I added a second NIC (eth2, 10.XX.XX.XX) to my machine and tried to add a secondary external network through: sudo ovs-vsctl add-br br-ex2 sudo ovs-vsctl add-port br-ex2 eth2 sudo ovs-vsctl set open . external-ids:ovn-bridge-mappings=public2:br-ex2 sudo ovs-vsctl set open . external-ids:ovn-cms-options="enable-chassis-as-gw" then my whole machine (including host and all instances) lost dns service, I can only ping ip addresses such as 8.8.8.8 instead of google.com. To be precise, I found out I lose dns service after `sudo ovs-vsctl add-port br-ex2 eth2` command. (Yes, I've moved ip from eth2 to br-ex2, but didn't help) I kept on creating a network and a router: openstack network create public2 --provider-network-type flat --provider-physical-network public2 --external openstack subnet create public2-subnet --network public2 --subnet-range 10.XX.XX.0/24 --no-dhcp --gateway 10.XX.XX.1 --allocation-pool start=10.XX.XX.10,end=10.XX.XX.30 openstack router create bridge-router --external-gateway public2 openstack router add subnet bridge-router shared-public2-subnet At this point, the router is accessible from eth2 after `sudo ovs-vsctl set open . external-ids:ovn-bridge-mappings=public2:br-ex2` command, but after I tried to allocate a floating ip from public2 to any instance, the instance is just not accessible from that ip. My ultimate goal is to be able to allocate floating ip to instances from eth2, so I can access instances from both eth1 and eth2 networks, but now I lost dns service and I'm unable to access instances from the allocated eth2 floating ip. Any suggestions?

1 0