- openstack-discuss - lists.openstack.org

[manila] Cancelling Dec 29th weekly meeting
by Carlos Silva 23 Dec '22

23 Dec '22

Hello, Zorillas! As discussed in yesterday's weekly meeting, next week's IRC meeting (Dec 29th) is cancelled due to most of us being offline. The next weekly meeting is on January 5th. Happy holidays to those celebrating! Cheers, carloss

1 0

[neutron] bug deputy report December 19th -23th
by Miguel Lavalle 23 Dec '22

23 Dec '22

Hi, Here's this week's bugs deputy report: Under investigation at the moment of this report ==================================== https://bugs.launchpad.net/neutron/+bug/2000378 [OVN] orphaned virtual parent ports break new ports. Under investigation by ralonsoh Medium ====== https://bugs.launchpad.net/neutron/+bug/2000163 [FT] Error in "test_get_datapath_id". Proposed fix: https://review.opendev.org/c/openstack/neutron/+/868311 https://bugs.launchpad.net/neutron/+bug/2000164 [FT] Error in "test_dvr_update_gateway_port_with_no_gw_port_in_namespace". Needs owner https://bugs.launchpad.net/neutron/+bug/2000252 [OVN] "DBInconsistenciesPeriodics.check_for_inconsistencies" failing during port deletion. Needs owner https://bugs.launchpad.net/neutron/+bug/2000314 [OVS] Call to "driver.unregister" failing. Needs owner Low === https://bugs.launchpad.net/neutron/+bug/2000238 [FT] Remove the "Running command:" messages in the logs. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/868304

1 0

[nova] Isolating scheduler
by Dominik Danelski 23 Dec '22

23 Dec '22

Hello, I'd like to create and test some new filters and weights for the scheduler. Ideally, I would mimic an existing OpenStack deployment I have access to. I already installed placement component, to which the scheduler would connect and now I'd like to isolate it. I'm not sure how to approach it, as scheduler is part of Nova and not a stand-alone component as placement. My intention is to initially fill placement's database with information about the infrastructure, set up the scheduler and then query it for consecutive requests (linear, no need for locks if that changes anything) to log the decisions it would make with modified weights/filters and the state of the system in-between requests. What is, in your opinion, the best way to detach the scheduler as much as possible from the rest of Nova, in order to test it under configuration most resembling the real-world setup? Should I use the test framework and mimic how it is set up for the unit tests or is there a better way to go? Thank you for your time. Regards Dominik Danelski

1 0

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 23 Dec '22

23 Dec '22

Hello Neutrinos: Due to the lack of agenda, today's drivers meeting is cancelled. Please spend some time reviewing the active specs from the RFEs approved last week: https://review.opendev.org/q/project:openstack/neutron-specs+status:open+-a… . See you next year!

1 0

[all][tc] Canceling next week TC meetings
by Ghanshyam Mann 23 Dec '22

23 Dec '22

Hello Everyone, Due to the holidays, we are cancelling next week's (Dec 28) TC meeting. -gmann

1 0

[Glance] Cancelling Weekly meeting for Next 2 weeks
by Pranali Deore 22 Dec '22

22 Dec '22

Hello, Upstream glance weekly meeting for next 2 weeks is cancelled as most of the team members will be on New Year Holidays. The Next weekly meeting will be on Jan 12th ! Wishing everyone a Wonderful Holiday Season & a Joyful New Year. Thanks, Pranali

1 0

[Octavia] cancelling meeting Dec 28
by Gregory Thiemonge 22 Dec '22

22 Dec '22

Hi, Next week's meeting (Dec 28th) is cancelled, The next weekly meeting will be on Jan 4th! Gregory

1 0

Kolla ansible, add a service to a running openstack deployment
by A Monster 22 Dec '22

22 Dec '22

is there a way to add a service such as elasticsearch to an already done openstack deployment using kolla-ansible?

2 1

[cinder] Cancelling meeting on 28th December
by Rajat Dhasmana 22 Dec '22

22 Dec '22

Hello Argonauts, As discussed in today's meeting[1], we will be cancelling the upstream cinder meeting on 28st December, 2022 and will meet in the meeting on 4th January, 2023. Wishing everyone Merry Christmas and a happy new year! [1] https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-12-21-14.00.l… Thanks Rajat Dhasmana

1 0

[Openstack Heat] - Problems to find right Heat syntax to declare static route in a router template
by ddorra＠t-online.de 21 Dec '22

21 Dec '22

Hi Lajos, many thanks for your hints! Dieter > Hi, > > For adding extra/static routes for your routers you have 2 ways in Heat > (actually Neutron API has it, and you can use them in hot also): > > OS::Neutron::ExtraRoute https://docs.openstack.org/api-ref/network/v2/index.html#update-router > > OS::Neutron::ExtraRouteSethttps://docs.openstack.org/api-ref/network/v2/ind… > > The 1st one is the "old" set router attribute, and the 2nd is add_extraroutes & remove_extraroutes is optimized for concurrent > updates (see the API ref's > description for add_extraroutes). > So in hot template it will look something like this: > type: OS::Neutron::ExtraRouteSet > properties: > router: { get_resource: myrouter0 } > routes: > - destination: 179.24.2.0/24 > nexthop: 192.168.222.221 > > Lajos > > > ddorra(a)t-online.de <ddorra(a)t-online.de> ezt írta (időpont: 2022. dec. 19., H, 21:43): > > Hi, > > > > I want extend my router HOT template by adding a static route. > > > > In the Openstack cli this would be > > > > openstack router add route --route destination='1.2.3.4/17',gateway='10.0.0.66' myrouter > > > > From the OS::Neutron::Router resource description I guess this belongs into the value_specs > > section as a map, but all my attempts failed, e.g. > > > > router1: > > type: 'OS::Neutron::Router' > > properties: > > external_gateway_info: > > network: provider > > name: myrouter > > value_specs: > > route: > > destination: '0.0.0.0/0' > > gateway: '10.0.0.62' > > > > Can somebody help me with the correct syntax? > > > > > > Thanks & best regards, > > Dieter

1 0

[cinder] Bug Report from 12-21-2022
by Sofia Enriquez 21 Dec '22

21 Dec '22

This is a bug report from 12-14-2022 to 12-21-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/1999706 "Cinder fails to automatically map availability zones to volume types." Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/1999766 "Retype VM root Volume Cause VM failed to boot." Unassigned. Cheers, Sofia -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

Magnum private docker registry (insecure_registry) not working?
by Oliver Weinmann 21 Dec '22

21 Dec '22

Hi,I can't seem to get magnum (k8s) to accept my private docker registry. I wanted to have a central registry so not all hosts pull the images during deployment.For this I configured a registry:v2 docker container, pulled the images and pushed them to the local registry and added the following label to my k8s template:container_infra_prefix=172.28.7.140:4000/At first this seems to be working fine and when deploying a new k8s cluster using magnum I can see that it pulls the heat-container-agent image from my local registry:[core@k8s-admin-test-local-reg-6c4hx7gxbdhr-master-0 ~]$ sudo podman ps -aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES2d08559b9cdc 172.28.7.140:4000/heat-container-agent:wallaby-stable-1 /usr/bin/start-he... 1 second ago Up 1 second ago heat-container-agentBut then it fails to pull the next container:tail -f /var/log/heat-config/heat-config-script/64d35aad-5453-4da4-97c7-45abb640fc90-k8s-admin-test-local-reg-6c4hx7gxbdhr-kube_masters-h3wbcqgm6qv4-0-sfagopiu52se-master_config-2f5lhvr32z7j.logWARNING Attempt 8: Trying to install kubectl. Sleeping 5s+ ssh -F /srv/magnum/.ssh/config root@localhost '/usr/bin/podman run --entrypoint /bin/bash --name install-kubectl --net host --privileged --rm --user root --volume /srv/magnum/bin:/host/srv/magnum/bin 172.28.7.140:4000/hyperkube:v1.23.3-rancher1 -c '\''cp /usr/local/bin/kubectl /host/srv/magnum/bin/kubectl'\'''Trying to pull 172.28.7.140:4000/hyperkube:v1.23.3-rancher1...Error: initializing source docker://172.28.7.140:4000/hyperkube:v1.23.3-rancher1: pinging container registry 172.28.7.140:4000: Get "https://172.28.7.140:4000/v2/": http: server gave HTTP response to HTTPS clientI don't know why but there is no /etc/docker/daemon.json and the /etc/sysconfig/docker also doesn'T contain the line for my insecure registry:root@k8s-admin-test-local-reg-6c4hx7gxbdhr-master-0 ~]# cat /etc/sysconfig/docker# /etc/sysconfig/docker# Modify these options if you want to change the way the docker daemon runsOPTIONS="--selinux-enabled \ --log-driver=journald \ --live-restore \ --default-ulimit nofile=1024:1024 \ --init-path /usr/libexec/docker/docker-init \ --userland-proxy-path /usr/libexec/docker/docker-proxy \"As soon as I manually add my insecure registry here it works just fine. I looked at the magnum code and there is indeed some lines that should actually handle this, but it doesn't seem to be working. What is also weird is that while there is the Option in the Horizon WebUI to set an insecure registry, the openstack coe command doesn't offer this.Best Regards,Oliver

1 1

[kolla] Cancelling meetings on 21 and 28 Dec
by Michał Nasiadka 21 Dec '22

21 Dec '22

Hello Koalas, Cancelling this and next weekly meeting due to Christmas/New Year period. See you next year! Best regards, Michal

1 0

horizon policy
by Parsa Aminian 21 Dec '22

21 Dec '22

Hello is it possible to prevent access to delete instance on horizon for some users ? I want to access only admin user to delete instances from dashboard

1 0

Instance console works only if opened from one of the deployment nodes
by A Monster 21 Dec '22

21 Dec '22

I've deployed openstack yoga using kolla ansible, in three controller nodes, a storage cluster and multiple compute nodes. The deployment included using haproxy, keepalived and hacluster. everything seems to work fine, I can launch instances and networking is doing great, however I found out a problem that I didn't get in all the deployment tests that i've run before. I've combien openstack networks under the same network 10.10.10.0/24 and used the same ip address for both : *kolla_internal_vip_address* and *kolla_external_vip_interface *which is 10.10.10.254, and used an ip route to access to the openstack cluster from an external pc > ip route add 10.10.10.0/24 via 192.168.129.29 dev eth0 where *192.168.129.29* is the address of one of my controllers, however when I try to login to the horizon dashboard using *10.10.10.254 *i don't get a response from the web page, and when I log to the dashboard using the ip address of one of my controller nodes, I cannot use the instance console since it is under the ip address of 10.10.10.254 which is assigned to both *kolla_internal_vip_address* and *kolla_external_vip_interface.* although i can ping 10.10.10.254 from the external network using ip route.

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Dec 21 at 1600 UTC
by Ghanshyam Mann 21 Dec '22

21 Dec '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2022 Dec 21, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Dec 20 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[horizon] Cancelling next three weekly meetings
by vishal manchanda 21 Dec '22

21 Dec '22

Hello Team, As agreed, during the last weekly meeting, we are canceling our weekly meeting on 21st, 28th December and 4th January. The next weekly meeting will be on 11th January. Happy holidays and a happy new year in advance! Thanks & Regards, Vishal Manchanda

1 0

[neutron] Bug deputy report for week of December 12th
by Rodolfo Alonso Hernandez 20 Dec '22

20 Dec '22

Hello Neutrinos: This is the bug report from last week. * Critical: ** https://bugs.launchpad.net/neutron/+bug/2000150: "Fullstack dhcp test test_multiple_agents_for_network is failing intermittently". *Not assigned* * High: ** https://bugs.launchpad.net/neutron/+bug/1999558: "tox4 is breaking Neutron CI (most of the jobs)". To be discussed during the weekly Neutron meeting. ** https://bugs.launchpad.net/neutron/+bug/2000071: "[ovn-octavia-provider] Do not make the status of a newly HM conditional on the status of existing members". Patch: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/868092 * Medium: ** https://bugs.launchpad.net/neutron/+bug/1999392: "Some events which are supposed to be run AFTER changes are committed are performed BEFORE commit". Assigned ** https://bugs.launchpad.net/neutron/+bug/1999678: "Static route can get stuck in the router snat namespace". Patch: https://review.opendev.org/c/openstack/neutron/+/867678 ** https://bugs.launchpad.net/neutron/+bug/1999774: "SDK: Neutron stadiums use python bindings from python-neutronclient which will be deprecated". This bug is a container for any patch on any project deprecating "python-neutronclient". ** https://bugs.launchpad.net/neutron/+bug/1999813: "[ovn-octavia-provider] when a HM is created/deleted the listener remains in PENDING_UPDATE". Patch: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/867974. ** https://bugs.launchpad.net/neutron/+bug/2000078: "neutron-remove-duplicated-port-bindings doesn't remove binding_levels". Assigned/ * Low ** https://bugs.launchpad.net/neutron/+bug/1999390: "TypeError raised in neutron-dhcp-agent due to missing argument in clean_devices method". *Not assigned.* ** https://bugs.launchpad.net/neutron/+bug/1999391: "Attribute error in neutron-ovs-agent".* Not assigned.* * Incomplete: ** https://bugs.launchpad.net/neutron/+bug/1999400: "neutron-metadata-agent does not sometimes provide instance-id". The issue seems to be an error during the cloud-init route assignment. Must be confirmed first. ** https://bugs.launchpad.net/neutron/+bug/1999540: "Tempest test test_two_vms_fips failed due to port binding on instance failing". Missing logs (not accessible). ** https://bugs.launchpad.net/neutron/+bug/1999677: "Defunct nodes are reported as happy in network agent list". This issue is already solved in newer versions (latest Ussuri release 16.4.2). Also newer releases allow the removal of the OVN agents using the CLI. Regards.

1 0

[Openstack Heat] - Problems to find right Heat syntax to declare static route in a router template
by ddorra＠t-online.de 20 Dec '22

20 Dec '22

Hi, I want extend my router HOT template by adding a static route. In the Openstack cli this would be openstack router add route --route destination='1.2.3.4/17',gateway='10.0.0.66' myrouter >From the OS::Neutron::Router resource description I guess this belongs into the value_specs section as a map, but all my attempts failed, e.g. router1: type: 'OS::Neutron::Router' properties: external_gateway_info: network: provider name: myrouter value_specs: route: destination: '0.0.0.0/0' gateway: '10.0.0.62' Can somebody help me with the correct syntax? Thanks & best regards, Dieter

2 1

OpenStack Release Name Voting Now Open!
by Erin Disney 20 Dec '22

20 Dec '22

Hey everyone- It’s that time again to vote for the next OpenStack release name! Here are the finalists: 1. Bandicoot 2. Basalt 3. Bobcat 4. Boomerang Please submit your vote by January 3rd at 11:59pm PT (January 4th at 7:59 UTC). https://civs1.civs.us/cgi-bin/vote.pl?id=E_9c7f7a20a8871b09&akey=5b974247f9… <https://civs1.civs.us/cgi-bin/vote.pl?id=E_9c7f7a20a8871b09&akey=5b974247f9…> Happy voting! Thanks, Erin

2 1

Kolla-ansible openstack deployment with High Availability
by A Monster 18 Dec '22

18 Dec '22

Do I need to deploy and configure PaceMaker and HAproxy or something similar in order to get a HA kolla-ansible openstack deployment? or is it something done automatically? If so, what are the steps I should be taking?

3 2

[cinder] Extending specs deadline to 23rd December
by Rajat Dhasmana 17 Dec '22

17 Dec '22

Hello Argonauts, As per the schedule[1], cinder spec deadline was 16th December, 2022. However, due to unavailability of some core members, less review bandwidth throughout the week (including me) and other factors like bringing cinderlib to a release-able state, we couldn't get the sufficient reviews done and hence will be extending the deadline for all the open specs proposed for 2023.1 (Antelope) release. The new deadline for cinder specs will be 23rd December, 2022. Please make sure your specs are updated and in a reviewable state. [1] https://releases.openstack.org/antelope/schedule.html#a-cinder-spec-freeze Thanks Rajat Dhasmana

1 0

[all][TC] Bare rechecks stats week of 25.07
by Slawek Kaplonski 17 Dec '22

17 Dec '22

Hi, Here are fresh data about bare rechecks. +--------------------+---------------+--------------+-------------------+ | Team | Bare rechecks | All Rechecks | Bare rechecks [%] | +--------------------+---------------+--------------+-------------------+ | requirements | 2 | 2 | 100.0 | | keystone | 1 | 1 | 100.0 | | OpenStackSDK | 3 | 3 | 100.0 | | tacker | 3 | 3 | 100.0 | | freezer | 1 | 1 | 100.0 | | rally | 1 | 1 | 100.0 | | OpenStack-Helm | 14 | 15 | 93.33 | | cinder | 6 | 7 | 85.71 | | kolla | 20 | 25 | 80.0 | | neutron | 4 | 5 | 80.0 | | Puppet OpenStack | 10 | 13 | 76.92 | | OpenStack Charms | 3 | 6 | 50.0 | | nova | 11 | 22 | 50.0 | | tripleo | 8 | 19 | 42.11 | | ironic | 1 | 3 | 33.33 | | Quality Assurance | 1 | 3 | 33.33 | | octavia | 0 | 1 | 0.0 | | OpenStackAnsible | 0 | 1 | 0.0 | | designate | 0 | 1 | 0.0 | | Release Management | 0 | 1 | 0.0 | | horizon | 0 | 1 | 0.0 | +--------------------+---------------+--------------+-------------------+ Those data should be more accurate as my script now counts only comments from last 7 days, not all comments from patches updated in last 7 days. Reminder: "bare rechecks" are recheck comments without any reason given. If You need to do recheck for patch due to failed job(s), please first check such failed job and try to identify what was the issue there. Maybe there is already opened bug for that or maybe You can open new one and add it as explanation in the recheck comment. Or maybe it was some infra issue, in such case short explanation in the comment would also be enough. -- Slawek Kaplonski Principal Software Engineer Red Hat

6 10

[all][tc] What's happening in Technical Committee: summary 2022 Dec 16: Reading: 5 min
by Ghanshyam Mann 17 Dec '22

17 Dec '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Dec 14. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-14-16.00.log.html * Next TC weekly meeting will be on Dec 21 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Dec 20. 2. What we completed this week: ========================= * The technical elections dates for next cycle is finalized[2], please plan your nominations for open leaderships roles accordingly. 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[3]. Open Reviews ----------------- * Three open reviews for ongoing activities[4]. IMPORTANT: Tox 4 failure and time to fix them -------------------------------------------------------- You might know about Tox 4 failure and currently it is capped as <4 in ensure-tox role. This is going to be uncapped on Dec 21[5] and you might see tox based unit/functional tests job (or any job using ensure-role except devstack based) will start failing. Please plan the testing and fix accordingly. Calling out here as holiday seasons or fixing it in early cycle will help to plan the smooth development cycle and release. Change in Inactive project timeline ----------------------------------------- The proposal for this is under review[6] and positive response so far. Mistral release and more maintainers ------------------------------------------- avanzagh joined TC meeting and updates us that new maintainers from OVHCloud have been added as Core members to help maintaining Mistral. And we also discussed and agreed to continue Mistral in DPL model for this cycle. As next step, avanzagh will discuss the required work to release Mistral or what are the expectations from the release team to consider it as release item. This seems like good progress. We will keep monitor the situation until proposal for Mistral release deprecation is closed[7]. Renovate translation SIG i18 ---------------------------------- * No updates this week and we will track it in TC tracker and update on ML if there is any update. Project updates ------------------- * Add Cinder Huawei charm[8] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[9]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [10] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://governance.openstack.org/election/ [3] https://etherpad.opendev.org/p/tc-2023.1-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/03144… [6] https://review.opendev.org/c/openstack/governance/+/867062 [7] https://review.opendev.org/c/openstack/governance/+/866562 [8] https://review.opendev.org/c/openstack/governance/+/867588 [9] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [10] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[keystone] Holiday Meeting Schedule
by Dave Wilde 17 Dec '22

17 Dec '22

Hello, For the upcoming holidays I’m setting the Keystone meeting schedule as follows: 2022: - 20-Dec: Keystone weekly meeting on IRC - 23-Dec: Keystone Reviewathon on Google Meet - 27-Dec: Cancelled - Keystone weekly meeting - 30-Dec: Cancelled - Keystone Reviewathon on Google Meet 2023: - 03-Jan: Keystone weekly meeting on IRC as usual - 06-Jan: Keystone Reviewathon on Google Meet As always please let me know if you need anything. I hope you have a nice holiday and safe and happy new year! Thanks, /Dave

1 0