- openstack-discuss - lists.openstack.org

[TripleO] Gate blockers - C8 Wallaby & C9 Master|Wallaby
by Dariusz Smigiel 07 Apr '22

07 Apr '22

Hey! TripleO team noticed two separate issues which hit gates about 5h ago: * C8 Wallaby https://bugs.launchpad.net/tripleo/+bug/1967943 * C9 Master|Wallaby: https://bugs.launchpad.net/tripleo/+bug/1967945 Please withhold rechecking until further notice. Thanks, Dariusz

2 3

plain text config parameters encryption feature
by Alexander Yeremko 07 Apr '22

07 Apr '22

Dear OpenStack community, we are developing plain text config secrets encryption feature according to the next specification: https://specs.openstack.org/openstack/openstack-ansible-specs/specs/xena/pr… We started from Glance OS service and submitted two patchsets already: https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/814865 Now we have two questions that we need to clarify to proceed our work on that feature and finish our development: 1. Is it correct that we need to develop more patchsets to rework some logic of encryption mechanism according to comment to 'files/encypt_secrets.py' script that arised at the second patchset (PatchSet 2) dated Nov/30/2021 ? Comment is by Dmitry Rabotyagov: "We _really_ should make it as an ansible plugin and re-work logic" 2. We wish to have such feature in previous releases also, not just in upcoming Yoga or Zed. Stein, Train and Victoria - it would be excellent to have plain text secrets encryption with these releases also. So question is how is it possible to use our feature in those releases also? Can we push some backports to those releases openstack-ansible repo? Could someone be so kind and give us answers? Best regards and wishes, Alex Yeremko This E-Mail (including any attachments) may contain privileged or confidential information. It is intended only for the addressee(s) indicated above. The sender does not waive any of its rights, privileges or other protections respecting this information. Any distribution, copying or other use of this E-Mail or the information it contains, by other than an intended recipient, is not sanctioned and is prohibited. If you received this E-Mail in error, please delete it and advise the sender (by return E-Mail or otherwise) immediately. Any calls held by you with Connectria may be recorded by an automated note taking system to ensure prompt follow up and for information collection purposes, and your attendance on any calls with Connectria confirms your consent to this. Any E-mail received by or sent from Connectria is subject to review by Connectria supervisory personnel.

4 6

[swift][ptg] Ops feedback session - Apr 7 at 13:00 UTC
by Timothy Burke 06 Apr '22

06 Apr '22

As in PTGs past, we're getting devs and ops together to talk about Swift: what's working, what isn't, and what would be most helpful to improve. We're meeting in Havana (https://www.openstack.org/ptg/rooms/havana) on Apr 7 at 13:00UTC -- if you run a Swift cluster, we hope to see you there! Even if you can't make it, I'd appreciate if you can offer some feedback on this PTG's etherpad (https://etherpad.opendev.org/p/swift-zed-ops-feedback) Tim

3 2

[ptg][ptl][largescale-sig][all] PTG session: "The Scaling Journey" - Wednesday, April 6 15utc - kilo room
by Belmiro Moreira 06 Apr '22

06 Apr '22

Hi, the Large Scale SIG is organizing a PTG session to discuss "The Scaling Journey". The SIG worked in a "scaling journey" to guide and help operators to scale their OpenStack deployments. Definitely, there are different ways to scale OpenStack! and the challenges to move from a few hundreds cores to thousands or now millions cores are completely different. Based on the experience of several operators, we tried to answer different common questions and identify the pain points. https://wiki.openstack.org/wiki/Large_Scale_SIG If you are interested in scalability it would be great to have your feedback. Also, it's important that PTLs join because they can give the project vision for scalability and advise on how to overcome possible bottlenecks. To discuss all of this we will have a "zoom" session on Wednesday, April 6 15utc - "kilo room". See you there! cheers, Belmiro on behalf of the Large Scale SIG

2 1

Upgrading Openstack nodes
by Marc-Antoine Godde 06 Apr '22

06 Apr '22

Hello, We are running an Openstack cloud composed of 3 controller nodes and 4 compute nodes. Our deployment was realized with OpenStack-ansible and we are running OpenStack Ussuri on Ubuntu 18.04. Our plan is to upgrade nodes to Ubuntu 20.04, that way we would be able to update to OpenStack Victoria and further. We would like to withdraw each node from the cluster, reinstall a clean linux and redeploy the nodes. There is garbage remaining from previous upgrades. We figured out the way in the documentation to remove a compute node from the cluster with Openstack-ansible but we can’t find any related documentation for controller nodes. Any help would be very much appreciated. By the way, if you’d have any other suggestions on how to perform that upgrade, fell free to help. Best, Marc-Antoine Godde

2 2

[dev][infra][qa][tact-sig] Zuul behavior change with Depends-On across queues
by Jeremy Stanley 06 Apr '22

06 Apr '22

For those who haven't seen the more detailed announcement[*] about it, just a quick note that if you get a sudden -2 back from Zuul when approving a change with a Depends-On to a change in a different project which hasn't merged yet, that's likely an indication those projects don't share a dependent queue. It's not a bug, but an intentional clarification of Zuul's enqueuing behavior. For most other Zuul deployments (and even our other Zuul tenants in OpenDev) this is purely cosmetic, but since OpenStack's Zuul tenant is configured to require a positive Verified vote before enqueuing into the gate pipeline, it means some changes may end up unexpectedly needing another pass through check first. It's worth re-evaluating whether or not this "clean check" rule remains a useful requirement for gating. It was added some years ago because a number of gate breaking bugs were traced back to unstable changes being rechecked enough times that eventually they got lucky and were able to merge, and then their instability contributed to destabilizing the integrated gate as a whole. Similarly, changes were being approved without reviewers confirming their jobs were passing first, and this led to additional resource waste. There is a bit of discussion around "blind rechecks" at the PTG this week, and so this topic is related; it might be a good idea to consider it in conjunction with the greater recheck conversation. [*] http://lists.opendev.org/pipermail/service-announce/2022-April/000033.html -- Jeremy Stanley

2 2

[openstack-ansible][PTG] Session on 6th of April is cancelled
by Dmitriy Rabotyagov 06 Apr '22

06 Apr '22

1 0

[Oslo] IRC meeting.
by Daniel Mats Niklas Bengtsson 06 Apr '22

06 Apr '22

Hi there, I would like to know if you agree that we have the meeting once a week? Instead of the first and third Monday of the month. It will be easier to manage and if sometimes it is canceled it does not matter Even if the meetings each week are short, this way we will have regular follow-up.

2 1

Metadata service {devices list}
by Ahmed Abdelhamid 06 Apr '22

06 Apr '22

Hi All, I am running into a strange issue with the metadata service. Per metadata-service manual <https://docs.openstack.org/nova/latest/user/metadata.html>, the devices attached to a VM should be visible in $ curl http://169.254.169.254/openstack/2018-08-27/meta_data.json However, whenever i execute it from a VM , the devices array is empty and looks like this, any idea why ? Thanks { "random_seed": "yu5ZnkqF2CqnDZVAfZgarG...", "availability_zone": "nova", "keys": [ { "data": "ssh-rsa AAAAB3NzaC1y...== Generated by Nova\n", "type": "ssh", "name": "mykey" } ], "hostname": "test.novalocal", "launch_index": 0, "meta": { "priority": "low", "role": "webserver" }, "devices": [ ], "project_id": "f7ac731cc11f40efbc03a9f9e1d1d21f", "public_keys": { "mykey": "ssh-rsa AAAAB3NzaC1y...== Generated by Nova\n" }, "name": "test"}

3 10

wireguard - ? - puzzle
by lejeczek 06 Apr '22

06 Apr '22

Hi guys. Has anybody solved that puzzle? Or perhaps it's not a puzzle at all, I'd imagine might be trivial to experts. First I thought - and only thought so far thus asking here - 'allowed_address_pairs' I'd need but that obviously does not do anything as 'wireguard' creates its own ifaces. So.. how do you get your 'wireguard' in openstack to route (no NAT) to instances' local network(s)? many thanks, L.

3 3

[Octavia] Weekly meeting cancelled
by Gregory Thiemonge 06 Apr '22

06 Apr '22

Hi, As this is the PTG week, the Octavia weekly meeting is cancelled. Thanks, Gregory

1 0

[tripleo][RDO] Tags for Yoga GA version in tripleo projects
by Alfredo Moralejo Alonso 05 Apr '22

05 Apr '22

Hi, As we are doing builds for RDO Yoga release, I'd like to know what we should include in yoga release. In Xena, tags were created with the commits for the most recent promotion at around GA and shipped rpm packages for them. Additionally, we pinned RDO Trunk Xena to those versions. Will we get similar tags for Yoga? Best regards, Alfredo

2 3

Problems running Watcher on DevStack
by Christian Rohmann 05 Apr '22

05 Apr '22

Hello there, I am trying to setup devstack which is running Watcher. But I am running always into problems with setup not finishing and throwing errors (see below). To clarify: I am trying to setup the devstack with multiple nodes (three nodes to be exactly, one control/compute and two compute) following the instructions at https://docs.openstack.org/watcher/latest/contributor/devstack.html which leads to this configuration control / first compute node: > [[local|localrc]] > ADMIN_PASSWORD="<password>" > DATABASE_PASSWORD=$ADMIN_PASSWORD > RABBIT_PASSWORD=$ADMIN_PASSWORD > SERVICE_PASSWORD=$ADMIN_PASSWORD > SERVICE_HOST="<ip of the control node>" > HOST_IP="<ip of host>" > FIXED_RANGE="10.4.128.0/20" > FLOATING_RANGE="subnet range" > > DEVSTACK_RELEASE="stable/yoga" > > LOGFILE=/opt/stack/logs/stack.sh.log > LOGDAYS=7 > LOG_COLOR=False > > enable_plugin watcher https://opendev.org/openstack/watcher > $DEVSTACK_RELEASE > > enable_plugin watcher-dashboard > https://opendev.org/openstack/watcher-dashboard $DEVSTACK_RELEASE > > enable_plugin ceilometer https://opendev.org/openstack/ceilometer.git > $DEVSTACK_RELEASE > CEILOMETER_BACKEND=gnocchi > > enable_service ceilometer-api > enable_service ceilometer-acompute > > enable_plugin gnocchi https://github.com/gnocchixyz/gnocchi > > # OpenStack Telemetry (Ceilometer) Alarming > # enable_plugin aodh https://opendev.org/openstack/aodh $DEVSTACK_RELEASE > > # I did not use the panko project which is mentioned in the > documentation because it is deprecated > > [[post-config|$NOVA_CONF]] > [DEFAULT] > compute_monitors=cpu.virt_driver > [scheduler] > discover_hosts_in_cells_interval=2 additional compute node(s): > [[local|localrc]] > HOST_IP="<host ip>" > FIXED_RANGE=10.4.128.0/20 > FLOATING_RANGE="<floating range" > ADMIN_PASSWORD="<password>" > DATABASE_PASSWORD=$ADMIN_PASSWORD > RABBIT_PASSWORD=$ADMIN_PASSWORD > SERVICE_PASSWORD=$ADMIN_PASSWORD > DATABASE_TYPE=mysql > SERVICE_HOST="<ip of control node>" > MYSQL_HOST=$SERVICE_HOST > RABBIT_HOST=$SERVICE_HOST > GLANCE_HOSTPORT=$SERVICE_HOST:9292 > Q_HOST=$SERVICE_HOST > OVN_SB_REMOTE=tcp:$SERVICE_HOST:6642 > disable_all_services > ENABLED_SERVICES=n-cpu,placement-client,ovn-controller,q-ovn-metadata-agent > NOVA_VNC_ENABLED=True > NOVNCPROXY_URL="http://$SERVICE_HOST:6080/vnc_lite.html" > VNCSERVER_LISTEN=$HOST_IP > VNCSERVER_PROXYCLIENT_ADDRESS=$VNCSERVER_LISTEN > > DEVSTACK_RELEASE="stable/yoga" > > LOGFILE=/opt/stack/logs/stack.sh.log > LOGDAYS=7 > LOG_COLOR=False > > enable_plugin ceilometer https://opendev.org/openstack/ceilometer > $DEVSTACK_RELEASE > disable_service ceilometer-acentral > disable_service ceilometer-collector > disable_service ceilometer-api > > [[post-config|$NOVA_CONF]] > [DEFAULT] > compute_monitors=cpu.virt_driver In addition I have tried to use the configuration that can be found in the repository of the watcher-project at https://opendev.org/openstack/watcher/src/branch/master/devstack. The error is always the same with setup.sh ending in: > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:244 > : cp /opt/stack/ceilometer/etc/ceilometer/polling_all.yaml > /etc/ceilometer/polling.yaml > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:246 > : cp > /opt/stack/ceilometer/ceilometer/pipeline/data/event_definitions.yaml > /opt/stack/ceilometer/ceilometer/pipeline/data/event_pipeline.yaml > /opt/stack/ceilometer/ceilometer/pipeline/data/pipeline.yaml > /etc/ceilometer > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:248 > : '[' '' ']' > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:251 > : '[' False == True ']' > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:259 > : iniset /etc/ceilometer/ceilometer.conf service_credentials > auth_type password > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:260 > : iniset /etc/ceilometer/ceilometer.conf service_credentials > user_domain_id default > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:261 > : iniset /etc/ceilometer/ceilometer.conf service_credentials > project_domain_id default > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:262 > : iniset /etc/ceilometer/ceilometer.conf service_credentials > project_name service > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:263 > : iniset /etc/ceilometer/ceilometer.conf service_credentials > username ceilometer > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:264 > : iniset /etc/ceilometer/ceilometer.conf service_credentials > password <password> > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:265 > : iniset /etc/ceilometer/ceilometer.conf service_credentials > region_name RegionOne > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:266 > : iniset /etc/ceilometer/ceilometer.conf service_credentials > auth_url http://192.168.0.100/identity > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:268 > : configure_auth_token_middleware /etc/ceilometer/ceilometer.conf > ceilometer /var/cache/ceilometer > ++ lib/keystone:configure_auth_token_middleware:467 : echo 'WARNING: > configure_auth_token_middleware is deprecated, use > configure_keystone_authtoken_middleware instead' > WARNING: configure_auth_token_middleware is deprecated, use > configure_keystone_authtoken_middleware instead > ++ lib/keystone:configure_auth_token_middleware:468 : > configure_keystone_authtoken_middleware > /etc/ceilometer/ceilometer.conf ceilometer > ++ lib/keystone:configure_keystone_authtoken_middleware:447 : local > conf_file=/etc/ceilometer/ceilometer.conf > ++ lib/keystone:configure_keystone_authtoken_middleware:448 : local > admin_user=ceilometer > ++ lib/keystone:configure_keystone_authtoken_middleware:449 : local > section=keystone_authtoken > ++ lib/keystone:configure_keystone_authtoken_middleware:451 : iniset > /etc/ceilometer/ceilometer.conf keystone_authtoken auth_type password > ++ lib/keystone:configure_keystone_authtoken_middleware:452 : iniset > /etc/ceilometer/ceilometer.conf keystone_authtoken interface public > ++ lib/keystone:configure_keystone_authtoken_middleware:453 : iniset > /etc/ceilometer/ceilometer.conf keystone_authtoken auth_url > http://192.168.0.100/identity > ++ lib/keystone:configure_keystone_authtoken_middleware:454 : iniset > /etc/ceilometer/ceilometer.conf keystone_authtoken username ceilometer > ++ lib/keystone:configure_keystone_authtoken_middleware:455 : iniset > /etc/ceilometer/ceilometer.conf keystone_authtoken password <password> > ++ lib/keystone:configure_keystone_authtoken_middleware:456 : iniset > /etc/ceilometer/ceilometer.conf keystone_authtoken user_domain_name > Default > ++ lib/keystone:configure_keystone_authtoken_middleware:457 : iniset > /etc/ceilometer/ceilometer.conf keystone_authtoken project_name service > ++ lib/keystone:configure_keystone_authtoken_middleware:458 : iniset > /etc/ceilometer/ceilometer.conf keystone_authtoken project_domain_name > Default > ++ lib/keystone:configure_keystone_authtoken_middleware:460 : iniset > /etc/ceilometer/ceilometer.conf keystone_authtoken cafile > /opt/stack/data/ca-bundle.pem > ++ lib/keystone:configure_keystone_authtoken_middleware:461 : iniset > /etc/ceilometer/ceilometer.conf keystone_authtoken memcached_servers > localhost:11211 > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:270 > : [[ libvirt = \v\s\p\h\e\r\e ]] > ++ /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:277 > : _ceilometer_configure_storage_backend > ++ > /opt/stack/ceilometer/devstack/plugin.sh:_ceilometer_configure_storage_backend:208 > : '[' gnocchi = none ']' > ++ > /opt/stack/ceilometer/devstack/plugin.sh:_ceilometer_configure_storage_backend:210 > : '[' gnocchi = gnocchi ']' > ++ > /opt/stack/ceilometer/devstack/plugin.sh:_ceilometer_configure_storage_backend:211 > : sed -i > 's/gnocchi:\/\//gnocchi:\/\/?archive_policy=ceilometer-low\&filter_project=gnocchi_swift/' > /etc/ceilometer/event_pipeline.yaml /etc/ceilometer/pipeline.yaml > ++ > /opt/stack/ceilometer/devstack/plugin.sh:_ceilometer_configure_storage_backend:212 > : [[ ,watcher,watcher-dashboard,ceilometer,gnocchi =~ gnocchi ]] > + /opt/stack/ceilometer/devstack/plugin.sh:configure_ceilometer:1 : > exit_trap What am I missing? Any configuration parameter? Thanks in advance Christian

2 1

[TripleO] Move tripleo repos stable/ussuri to End Of Life OK?
by Marios Andreou 05 Apr '22

05 Apr '22

Hello TripleO o/ The tripleo-ci team proposes that we move the stable/ussuri branch for all tripleo repos [1] to End of Life [2]. The branch was moved to extended maintenance with [3] so we can already no longer make any new releases for ussuri/tripleo repos. Are there any objections or concerns about this? If so please speak up here or directly on the patch. I think that any patches posted to ussuri nowadays are mainly about cherrypicking back to train, rather than merging something to ussuri specifically. I have posted the proposal to move to EOL at [4] and have WF-1 to wait for this discussion. If there are no objections then once we move to EOL the tripleo-ci team will remove all Ussuri related CI, check/gate/promotions. regards, marios [1] https://releases.openstack.org/teams/tripleo.html#ussuri [2] https://docs.openstack.org/project-team-guide/stable-branches.html#maintena… [3] https://review.opendev.org/c/openstack/releases/+/817623 [4] https://review.opendev.org/c/openstack/releases/+/834049

2 5

Kubernetes cluster fails with timed out error
by Karera Tony 05 Apr '22

05 Apr '22

Hello Team, I deployed Openstack Wallaby using kolla-ansible and enabled Magnum. The Installation was Ok but when I try to deploy a k8s cluster with fedora-coreos-32.20200601.3.0 image, it fails with a timeout error. When I check the /var/log/heat-config/heat-config-script logs on the master node, I get the error below. ++ kubectl get --raw=/healthz The connection to the server localhost:8080 was refused - did you specify the right host or port? + '[' ok = '' ']' + sleep 5 ++ kubectl get --raw=/healthz The connection to the server localhost:8080 was refused - did you specify the right host or port? + '[' ok = '' ']' + sleep 5 ++ kubectl get --raw=/healthz Any idea on what could be the issue. Regards Regards Tony Karera

2 4

[cinder] Zed PTG schedule
by Rajat Dhasmana 05 Apr '22

05 Apr '22

Hello Argonauts, Zed PTG is going to start from next week i.e. 4th April, 2022 to 8th April, 2022. Kindly register if you haven't already[1]. The registration is free and acts as a count of the people participating. The Cinder team will be meeting from 5th April (Tuesday) till 8th April (Friday) in the 1300-1700 UTC time slot. I've arranged the topics as per participants availability and in the following manner[2]. The connection details are on the etherpad along with the day wise schedule of topics. I've also arranged them in a tabular structure[3] (the time allotted to each topic here might vary). Hope to see everyone next week! [1] https://openinfra-ptg.eventbrite.com/ [2] https://etherpad.opendev.org/p/zed-ptg-cinder [3] https://ethercalc.openstack.org/crz6qdm7fq0v Thanks and regards Rajat Dhasmana

1 1

[tacker] No IRC meeting on Apr 5th
by Yasufumi Ogawa 05 Apr '22

05 Apr '22

Hi, I'd like to skip IRC meeting today since it's PTG week. Cheers, Yasufumi

1 0

Constraints and docs requirements
by Michael Johnson 05 Apr '22

05 Apr '22

Hello, The Designate project recently discovered that Wallaby docs builds were failing. This started happening because jinja2 newer than is specified in the constraints file was being installed, and there was a non backward compatible change that broke the doc builds. After some debugging we have determined the reason for this is that `tox -e docs` has two steps in its installation process. The first is the dependency installation which respects constraints and then after that is the installation of the package itself (in this case Designate). This second step does not supply constraints info, and it is expected that all dependencies of the package have been preinstalled by the first step. Where we get in trouble is that the docs requirements for projects like Designate (and we suspect others) are a subset of the package requirements necessary to install the packages. This means the second step in this install process discovers that many dependencies need to be installed and this happens without constraints allowing unexpected versions to be pulled in. To resolve this issue, make sure you are including the project requirements along with the doc requirements in your tox environment dependencies section[1]. This will allow pip to install all of the required dependencies, those required for the documentation generation and those for the project, to be all installed using the upper constraints. Thanks to clarkb and fungi for helping track down this issue and composing this email. [1] https://review.opendev.org/c/openstack/designate/+/836410/1/tox.ini

2 1

Support to allow only boot from cinder volumes
by Laurent Dumont 05 Apr '22

05 Apr '22

Hey folks, I am trying to see if there are any ways to instruct Openstack to prevent the usage of local storage/ephemeral disks. There are cases where : - I don't want the added complexity of Ceph. - I don't want the added hassle of using local volumes/nfs/shared storage on the computes directly. In an ideal world, creating a VM would mean that you always have a boot-from-volume with the volume being in your chosen backend. I've seen this spec : https://blueprints.launchpad.net/nova/+spec/flavor-root-disk-none But it doesn't seem to have survived the Ocata cycle. Any thoughts? Thanks!

3 7

[CloudKitty] April 2022 - PTG Summary
by Rafael Weingärtner 05 Apr '22

05 Apr '22

Hello, CloudKitty community, Below is my summary of the CloudKitty session during the PTG meeting in April. More details registered can be found at [1]. - CloudKitty Yoga release: we started a discussion reviewing the Yoga release, where we had major interesting new features introduced, such as the reprocessing API, V2 API for the already existing V1 endpoints, and so on. Moreover, we reviewed the reviewing process of patches, and it seems to be working nicely for everybody and producing results for CloudKitty; therefore, we will maintain it. - Create scope API: there is no blueprint yet, but this is one of the requests we got. The idea is that one can create the scope (project) in CloudKitty before it is discovered by CloudKitty. Therefore, one could mark test/ignored projects for the rating before they start to be used and are picked up by CloudKitty. - ElasticSearch improvements: there are some improvements already going on, and Pierre's team is the one conducting it. - Expand the "custom_fields" in the Summary GET API to support Elastic search backends. As we discussed, this feature might be interesting to be expanded and added for other backends such as ElasticSearch. However, we still need to evaluate if that would be feasible. - Where do we go from here?: And last, but not least, we discussed the future of CloudKitty and where we want to go from our current state. The consensus is that we need to improve the default configurations to other systems such as Monasca and Prometheus to facilitate for newcomers to use it; keep users happy; continue innovating and improving CloudKitty. And, as the next step for that, we will propose a Forum panel for CloudKitty at the OpenStack summit to see if we can help people's onboarding and to have a broader discussion regarding the next big developments we will be doing in CloudKitty. Those are the main topics we covered during the PTG. If I forgot something, please let me know. Now, we just gotta work to keep evolving this awesome billing stack :) Link for the PTG Etherpad: [1] [1] https://etherpad.opendev.org/p/cloudkitty-ptg-zed -- Rafael Weingärtner

1 0

[ptl][release][stable][EM] Extended Maintenance - Victoria
by Előd Illés 05 Apr '22

05 Apr '22

Hi, As Yoga was released last week and we are in a less busy period (except the PTG :)), now it is a good time to call your attention to the following: In a month Victoria is planned to transition to Extended Maintenance phase [1] (planned date: /2022-04-27/). I have generated the list of the current *open* and *unreleased* changes in stable/victoria for every repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Victoria before moving stable/victoria branches to Extended Maintenance. Feel free to edit and extend these lists to track your progress! * next week the Release Team will tag the *latest* Victoria *releases* of repositories with *victoria-em* tag. * at the planned deadline (April 27th)//the Release Team will merge all the transition patches (even the ones without any response!) * After the transition stable/victoria will be still open for bug fixes, but there won't be official releases anymore. *NOTE*: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken (final!) releases! Thanks, Előd [1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/victoria-final-release-before-em

1 0

[openstack-helm] No Meeting This Week
by Gage Hugo 05 Apr '22

05 Apr '22

Hey team, Since the PTG is this week, the weekly meeting has been cancelled. We will meet for the PTG session on April 6th 1500-1700 UTC, hope to see you there!

1 0

PTG -Kickstart with Mistral Worflow review by eOTF/CoreStack teams
by prakash RAMCHANDRAN 05 Apr '22

05 Apr '22

Hi all, It's a great pleasure to kickstart PTG event by "eMerging Open Tech Foundation" (eOTF) having become Associate Member to promote and Collaborate with Open Infrastructure Foundation. https://meetpad.opendev.org/eotf Here is the link to today's Mistral - Workflow Engine presentation with Q&A. https://us02web.zoom.us/rec/share/lhcRPhpQYGbR_0QjizgOnPhozW2VOZlSBkhXjkLEs… (Passcode: H=Tx2KdN) We like interested community members to join in our efforts to revive maintenance and development for Mistral for CSPs for Hybrid Cloud usage. Next meeting is scheduled for Friday April 8th 7.30 PM IST / 7.00 AM Pacific Daylight Time when we will focus on KupeStack as well follow up on plans for maitenance and development for Mistral in Zed and future releases. ThanksFor eOTF teamhttps://eotf.infoR.Prakash

1 0

[Ironic][Bare Metal SIG] Community Feedback Survey (1 minute)
by Arne Wiebalck 05 Apr '22

05 Apr '22

Dear all, As input for the PTG and to align priorities for the next cycle, the Ironic team is looking for feedback from the community (users, operators, admins, deployers ... everyone interested in bare metal really!). So, if you have 1 minute, we would greatly appreciate your input by filling: https://de.surveymonkey.com/r/XCR2TN5 If you have any additional input for the Ironic team, do not hesitate to reach out (via mail, on IRC, or come along to the PTG!). Thanks! Arne

1 1

[glance] import RBD image
by Tony Liu 04 Apr '22

04 Apr '22

Hi, There used to be a way to import RBD image with API v1, but not any more with v2. Is there any other way to do that? In case given QCOW2 image, It would be much faster and easier to convert it directly to RBD image with RAW format, than convert it to RAW format on local file system and upload the RAW image to Glance. Thanks! Tony

2 3

[TripleO] gate blocker - impacting all quickstart-based jobs - openstack-ansible-os_tempest
by Ronelle Landy 04 Apr '22

04 Apr '22

Hello All, We have a check/gate blocker on all TripleO quickstart-based jobs, as described in: https://bugs.launchpad.net/tripleo/+bug/1967430 [1] commit to openstack-ansible-os_tempest removed setup.py and is causing failings in all quickstart jobs. A revert was proposed but will not be workable - we are waiting on another fix. Please hold rechecks until this is resolved. [1] https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/835969 Thank you!

5 12

[neutron] Bug deputy March 28 to April 3
by Rodolfo Alonso Hernandez 04 Apr '22

04 Apr '22

Hello Neutrinos: This is the bug list of week 13 (March 28 to April 3). Critical: - https://bugs.launchpad.net/neutron/+bug/1967472: [OVN] OVN compilation is failing in "neutron-tempest-plugin-scenario-ovn" job - Fixed Medium: - https://bugs.launchpad.net/neutron/+bug/1967142: No way to set quotas for neutron-vpnaas resources using openstack CLI tool. - Not assigned. - This bug affects OSC. Neutron API provides the needed information. - https://bugs.launchpad.net/neutron/+bug/1967144: [OVN] Live migration can fail due to wrong revision id during setting requested chassis in ovn. - Assigned to Slawek. Invalid/opinion/incomplete: - https://bugs.launchpad.net/neutron/+bug/1966858: `ovn-metadata-agent` not starting due to missing module `neutron.privileged.agent` - Most probably this is a problem with the installation of OpenStack and the Python version used (3.10). The recommendation is to use v3.8 or v3.9 as default binary. - The python version used to install the libraries must be the same running the services. Regards.

1 0

[security-sig] No meeting this week
by Gage Hugo 04 Apr '22

04 Apr '22

Since this week is the PTG, there will not be a security SIG meeting. Hope to see you all at the session! - Gage

1 0

Openstack Xena: error deleting image and snapshot via dashboard (as user and as admin)
by federica fanzago 03 Apr '22

03 Apr '22

Hi all, we have installed Openstack Xena in our cloud infrastructure (OS Centos-Stream 8) and we find a problem with the delete of images and snapshots via dashboard. The delete command returns "Error: Unable to delete Image:xxx" Via command line the delete works well. Looking in glance logs I don't find any error message. Did you experienced this problem? Have you suggestions about it? Thanks, cheers Federica -- Federica Fanzago INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy Tel: +39 049.967.7367 --

3 4

OPS Meetup - next meeting at the PTG
by Amy Marrich 03 Apr '22

03 Apr '22

The OPS Meetup team will be meeting this week during the PTG on Tuesday at 13:00 UTC in the Austin <https://zoom.us/j/96906327910?pwd=aE51d1FtM0R3dDY1Vk0xUTJKaEZtUT09#success> room. We will be planning[0] the meetup to be held in Berlin on June 10th]. See you there, Amy(spotz) 0 - https://etherpad.opendev.org/p/april2022-ptg-openstack-ops

1 0

[all][tc] What's happening in Technical Committee: summary April 1st, 21: Reading: 10 min
by Ghanshyam Mann 02 Apr '22

02 Apr '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We canceled this week meeting. * Next TC weekly meeting will be after PTG on April 14th Thursday 15:00 UTC, feel free to add the topic on the agenda[1] by April 13th. 2. What we completed this week: ========================= * Removed the tags framework[2]. * Defined 2022 upstream investment opportunities[3]. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 6 out of 9 items are completed and many are in progress. Open Reviews ----------------- * Seven open reviews for ongoing activities[5]. Consistent and Secure Default RBAC -------------------------------------------- I collected few of the RBAC related topic in RBAC PTG etherpad[6], also please add the questions or discussion point in that etherpad if you would like to discuss with TC on Thursday 14 UTC. Community-wide goals readiness checklist -------------------------------------------------- As we received the feedback in Yoga PTG TC+PTL interaction session, I have proposed the checklist which can help us to check if the goal is ready to start or not[7], please review and let us know if more items need to be added. Zed cycle Leaderless projects ---------------------------------- No updates on this. I am still waiting for Zaqar PTL +1 on the PTL appointment patch[8] and we will discuss Adjutant in PTG, hoping Braden will be ready with their company side permission[9]. PTG Preparation -------------------- I have prepared the schedule and updated in etherpad[10], please check and see you all next week. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]. Project updates ------------------- * Add Ganesha based Ceph NFS Charm[12] 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/834798 [3] https://governance.openstack.org/tc/reference/upstream-investment-opportuni… [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://etherpad.opendev.org/p/rbac-zed-ptg [7] https://review.opendev.org/c/openstack/governance/+/835102 [8] https://review.opendev.org/c/openstack/governance/+/831123 [9] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [10] https://etherpad.opendev.org/p/tc-zed-ptg [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] https://review.opendev.org/c/openstack/governance/+/835429 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all][tc] Zed TC-PTG Planning
by Ghanshyam Mann 02 Apr '22

02 Apr '22

Hello Everyone, As you already know that the Zed cycle virtual PTG will be held between 4th - 8th April[1]. I have started the preparation for the Technical Committee PTG sessions. Please do the following: 1. Fill the below doodle poll as per your availability. Please fill it in soon as the deadline to book the slot is March 11th. - https://doodle.com/poll/gz4dy67vmew5wmn9 2. Add the topics you would like to discuss to the below etherpad. - https://etherpad.opendev.org/p/tc-zed-ptg NOTE: this is not limited to TC members only; I would like all community members to fill the doodle poll and, add the topics you would like or want TC members to discuss in PTG. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027051… -gmann

1 2

[all][tc][goal][rbac] RBAC goal discussion in Zed PTG
by Ghanshyam Mann 02 Apr '22

02 Apr '22

Hello Everyone, I have collected few of the RBAC related sessions planned in Zed PTG. Please add related sessions in below etherpad if you are planning in your project PTG. - https://etherpad.opendev.org/p/rbac-zed-ptg Also, if you have or come up with questions/discussion points during PTG, feel free to add it in same etherpad (section "Open Questions") and we will discuss it in TC PTG slot on Thursday 14-15 UTC - https://etherpad.opendev.org/p/tc-zed-ptg#L71 -gmann

1 0

[neutron] [kolla] Static routes added to subnets after upgrading from Queens to Train
by Albert Braden 02 Apr '22

02 Apr '22

After upgrading our kolla-ansible clusters from Queens to Train, we are seeing static routes when we create subnets. We didn’t see this in Queens. For example, in our de6 region we have a network called “trust” with 3 subnets: Subnet CIDR Gateway trust-az1: 10.52.160.0/22 10.52.160.1 trust-az2: 10.52.164.0/22 10.52.164.1 trust-az3: 10.52.168.0/22 10.52.168.1 Each of these subnets has 2 entries under “host_routes:” that point to the other two subnets. For example, subnet trust-az1 has these two routes: host_routes | destination='10.52.164.0/22', gateway='10.52.160.1' | | | destination='10.52.168.0/22', gateway='10.52.160.1' | How can we prevent these host routes from being created in Train? Do we need to change something in our config?

2 6

[ironic] Ironic Zed PTG Schedule
by Iury Gregory 02 Apr '22

02 Apr '22

Hello Ironicers and Stackers! I've split the topics we had in our etherpad [1] in the booked slots. You can find the proposed schedule in [2], please provide feedback till Thursday so I can make changes and provide the official schedule by Friday morning =). If you haven't registered yourself for the PTG, please do [3]. [1] https://etherpad.opendev.org/p/ironic-zed-ptg [2] https://paste.opendev.org/show/bosAputU90U8RNKUbvKd/ [3] https://openinfra-ptg.eventbrite.com/ -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 1

[Kuryr] Zed PTG schedule
by Maysa De Macedo Souza 02 Apr '22

02 Apr '22

Hello, The Kuryr agenda[1] with the topics to be discussed on the PTG is up. Feel free to include any topics you're interested in discussing. See you at the PTG! Cheers, Maysa Macedo [1] https://etherpad.opendev.org/p/april2022-ptg-kuryr

1 0

[monasca][neutron][venus][release][kolla] Missing yoga tarballs
by Mark Goddard 02 Apr '22

02 Apr '22

Hi, In kolla we are trying to switch to the yoga branch tarballs in our images as part of our release process. The following projects lack these: * monasca-api: stable/yoga exists, but no additional commits yet, so no tarball. Could someone merge the release bot patches for stable/yoga? * neutron-vpnaas-dashboard: stable/yoga exists, but no additional commits yet, so no tarball. Could someone merge the release bot patches for stable/yoga? * venus: no stable/yoga branch yet. Looks like the review for the deliverable files is still open: https://review.opendev.org/c/openstack/releases/+/824394 Thanks, Mark

3 3

[horizon] [glance] [ops] Openstack Xena: error deleting image and snapshot via dashboard (as user and as admin)"
by federica fanzago 01 Apr '22

01 Apr '22

Hi all, we have installed Openstack Xena in our cloud infrastructure (OS Centos-Stream 8) and we find a problem with the delete of images and snapshots via dashboard. The delete command returns "Error: Unable to delete Image:xxx". Via command line the delete works well. Looking in glance logs I don't find any error message. The only error message is in a httpd log "ssl_error_log:[Thu Mar 31 09:54:28.857689 2022] [wsgi:error] [pid 315710:tid 140368604612352] [remote 192.168.60.229:59240] Internal Server Error: /dashboard/api/glance/images/9d519edb-5690-4660-a6e0-e44f9e2ab58f/" but it doesn't provide useful info for the debug. The creation of images via dashboard works well. Did you experienced this problem? Have you suggestions about it? Thanks, cheers Federica

1 0

[nova][placement] PTG schedule attempt
by Sylvain Bauza 01 Apr '22

01 Apr '22

Hi Compute-rs (lollilol), Before the PTG, I started to group all related topics into sections and I tried to allocate time against those. Feel free to take a look at the first schedule attempt https://etherpad.opendev.org/p/nova-zed-ptg#L45 As you will see in the etherpad, I added for every topic a courtesy ping list. Add your IRC nick in there if you are interested in attending this session, I'll ping folks at the start of the related session so people who can't be around for 3 hours can know when we discuss. Of course, I at least added the speaker ;-) -Sylvain

1 0

[nova][os-brick] Yoga - native nvmeof multipath support
by bartosz.rabiega＠ovhcloud.com 01 Apr '22

01 Apr '22

Hello, I'm trying to figure out how the new feature of Yoga works: "The libvirt driver now allows using Native NVMeoF multipathing for NVMeoF connector, via the configuration attribute in nova-cpu.conf [libvirt]/volume_use_multipath, defaulting to False (disabled)." https://review.opendev.org/c/openstack/nova/+/823941 It's said that this config value enables native NVMeoF multipathing, but I can't see any support for such configuration in os-brick connector. https://github.com/openstack/os-brick/blob/master/os_brick/initiator/connec… Am I missing something? BR BR

2 3

[release] Release Team's Zed PTG schedule & topics
by Előd Illés 01 Apr '22

01 Apr '22

Hi, Release team decided to hold our Zed PTG session at the usual weekly Release Team meeting timeframe, so @ Friday 14:00 UTC, April 8th, (Liberty Room). Please see the proposed topics (and add yours if you have any!) to our PTG etherpad: https://etherpad.opendev.org/p/april2022-ptg-rel-mgt Reminder: today's weekly meeting is cancelled, see you next week at the PTG! Cheers, Előd

1 0

[Glance] No weekly meeting On April 7th
by Pranali Deore 01 Apr '22

01 Apr '22

Hello, We won't be having our weekly meeting on 7th April since it's the PTG week. Thanks, Pranali Deore

1 0

No weekly meeting On April 7th
by Pranali Deore 01 Apr '22

01 Apr '22

Hello, We won't be having our weekly meeting on 7th April since it's the PTG week. Thanks, Pranali Deore

1 0

[cinder] Cancelling cinder meeting on 6th April
by Rajat Dhasmana 01 Apr '22

01 Apr '22

Hi, We will be cancelling the cinder meeting on 6th April as it is the PTG week. Thanks and regards Rajat Dhasmana

2 1

[kolla] RDP access to openstack instances
by A Monster 01 Apr '22

01 Apr '22

I can ssh into instances after attributing floating ips but whenever I try to access using remote desktop I fail, although I've enabled RDP traffic in security groups, is there a problem with my configuration or do I have to do extra work to successfully do a remote access.

2 1

[neutron] PTG schedule
by Lajos Katona 01 Apr '22

01 Apr '22

Hi Neutrinos, Please check the PTG schedule: https://etherpad.opendev.org/p/neutron-zed-ptg#L83 Please check it, and raise your hand if - a time slot is not suitable for you - or if you have any more topics to discuss next week. We have one full free day (Friday) and for Thursday I just added a theoretical Nova-Neutron cross project discussion, so we have space to shuffle slots. I added a slot for Edge, perhaps Designate folks can join us, that can also move in the schedule. See you next week during the PTG :-) Lajos Katona (lajoskatona)

1 0

[nova][placement] Nova meeting on Apr 5th CANCELLED
by Sylvain Bauza 01 Apr '22

01 Apr '22

Forgot to send this email before, but obviously let's cancel next week's Nova meeting as we'll see us virtually at the PTG. -Sylvain

1 0

[manila] Cancelling weekly meetings on the 7th and 14th
by Carlos Silva 01 Apr '22

01 Apr '22

Hello, zorillas! During today's meeting we agreed that we would cancel the next week's weekly meeting, as well as the meeting in the week after that. So we will be getting back to the regular manila meetings on April 21st. Thank you! carloss

1 0

[yoga][horizon] Broken Horizon plugins UT: murano-dashboard, magnum-ui, heat-dashboard
by Thomas Goirand 31 Mar '22

31 Mar '22

Hi, Building Horizon plugins for yoga after upgrading to Horizon 22.1.0 lead me to broken unit tests. I haven't filed separate bugs yet, as I'd like to have the opinion of upstream about what's going on first. I've pushed the build logs over here: http://shade.infomaniak.ch/yoga-dashboard-plugins-build-logs/ So, what's going on? :) Cheers, Thomas Goirand (zigo) P.S: These are the last remaining failed to build issues I have for Yoga, everything else has been uploaded already.

2 2

[Ironic]After deleting server on bare metal node, baremetal node clean failed because pxe dhcp no reply
by 韩光宇 31 Mar '22

31 Mar '22

Hi all, I have a OpenStack Victoria All-in-One environment, and I can deploy os to bare metal by Ironic. I use `openstack server create --flavor my-baremetal-flavor --nic net-id=$PROVISION_UUID --image $whiole-disk-image BM-server-01` to get a server successfully. But if I delete server by "openstack server delete BM-server-01", baremetal node will be clean. When baremetal node performs the clean process, it enters the PXE phase, but its DHCP request cannot be replied. The log of ironic-conductor: 2022-03-31 11:40:42.572 63976 INFO ironic.conductor.task_manager [req-9e92ea87-d48c-42ed-83fd-2f7f14a20984 8763be6de0434240803f305c895fced5 a1758405f9c24ae191543248ad65a447 - default default] Node 4b243894-d651-4700-9a69-28ca3c60446f moved to provision state "clean wait" from state "cleaning"; target provision state is "available" 2022-03-31 12:11:06.694 63976 ERROR ironic.conductor.task_manager [req-3ff5cebf-0895-4e85-bf75-4ac1d20b30f4 - - - - -] Node 4b243894-d651-4700-9a69-28ca3c60446f moved to provision state "clean failed" from state "clean wait"; target provision state is "available" 2022-03-31 12:11:07.676 63976 INFO ironic.drivers.modules.network.flat [-] Removing ports from cleaning network for node 4b243894-d651-4700-9a69-28ca3c60446f 2022-03-31 12:11:08.218 63976 INFO ironic.common.neutron [-] Successfully removed node 4b243894-d651-4700-9a69-28ca3c60446f neutron ports. 2022-03-31 12:11:08.222 63976 ERROR ironic.conductor.utils [-] Timeout reached while cleaning the node. Please check if the ramdisk responsible for the cleaning is running on the node. Failed on step {}. The log of tcpdump in openstack: # tcpdump -n -S -i br-ex port 67 or port 68 or port 69 11:44:43.358657 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:46.550963 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:51.558266 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:57.374583 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:57.375096 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:57.691646 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:57.807714 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:57.907428 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:58.027351 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 The log of /var/log/neutron/dhcp-agent.log: 2022-03-31 11:40:18.373 47489 INFO neutron.agent.dhcp.agent [-] Trigger reload_allocations for port admin_state_up=True, allowed_address_pairs=[], binding:host_id=, binding:profile=, binding:vif_details=, binding:vif_type=unbound, binding:vnic_type=baremetal, created_at=2022-03-31T03:40:18Z, description=, device_id=4b243894-d651-4700-9a69-28ca3c60446f, device_owner=, extra_dhcp_opts=[], fixed_ips=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d29aeeb8>], id=20e8d806-f976-4415-85f5-ed2df55978dc, mac_address=fa:16:3e:f1:b3:aa, name=, network=admin_state_up=True, availability_zone_hints=[], availability_zones=['nova'], created_at=2022-03-28T08:39:24Z, description=, id=faa2b805-7898-4fb2-ad51-49251da6e35e, ipv4_address_scope=None, ipv6_address_scope=None, is_default=False, mtu=1500, name=provider1, port_security_enabled=True, project_id=a1758405f9c24ae191543248ad65a447, provider:network_type=flat, provider:physical_network=provider, provider:segmentation_id=None, revision_number=2, router:external=True, shared=True, status=ACTIVE, subnets=['2d5d4c2c-8c8c-44ef-92b4-a124ed52030f'], tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-28T08:39:29Z, vlan_transparent=None, network_id=faa2b805-7898-4fb2-ad51-49251da6e35e, port_security_enabled=True, project_id=a1758405f9c24ae191543248ad65a447, revision_number=1, security_groups=['f574b5d0-8308-40f4-a8e5-81126b920e8f'], status=DOWN, tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-31T03:40:18Z on network _ns_name=qdhcp-faa2b805-7898-4fb2-ad51-49251da6e35e, admin_state_up=True, availability_zone_hints=[], availability_zones=['nova'], created_at=2022-03-28T08:39:24Z, description=, id=faa2b805-7898-4fb2-ad51-49251da6e35e, ipv4_address_scope=None, ipv6_address_scope=None, is_default=False, mtu=1500, name=provider1, non_local_subnets=[], port_security_enabled=True, ports=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a16a98>], project_id=a1758405f9c24ae191543248ad65a447, provider:network_type=flat, provider:physical_network=provider, provider:segmentation_id=None, revision_number=2, router:external=True, shared=True, status=ACTIVE, subnets=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a169d8>], tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-28T08:39:29Z, vlan_transparent=None 2022-03-31 11:40:18.516 47489 INFO neutron.agent.dhcp.agent [req-9b1713fa-1082-4ccf-8c8b-e953beaf5e5d - - - - -] DHCP configuration for ports {'20e8d806-f976-4415-85f5-ed2df55978dc'} is completed 2022-03-31 11:40:19.517 47489 INFO neutron.agent.dhcp.agent [-] Trigger reload_allocations for port admin_state_up=True, allowed_address_pairs=[], binding:host_id=4b243894-d651-4700-9a69-28ca3c60446f, binding:profile=local_link_information=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d29aeb28>], binding:vif_details=, binding:vif_type=unbound, binding:vnic_type=baremetal, created_at=2022-03-31T03:40:18Z, description=, device_id=4b243894-d651-4700-9a69-28ca3c60446f, device_owner=baremetal:none, extra_dhcp_opts=[], fixed_ips=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d29aefa8>], id=20e8d806-f976-4415-85f5-ed2df55978dc, mac_address=18:9b:a5:81:46:b7, name=, network_id=faa2b805-7898-4fb2-ad51-49251da6e35e, port_security_enabled=True, project_id=a1758405f9c24ae191543248ad65a447, revision_number=2, security_groups=['f574b5d0-8308-40f4-a8e5-81126b920e8f'], status=DOWN, tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-31T03:40:19Z on network _ns_name=qdhcp-faa2b805-7898-4fb2-ad51-49251da6e35e, admin_state_up=True, availability_zone_hints=[], availability_zones=['nova'], created_at=2022-03-28T08:39:24Z, description=, id=faa2b805-7898-4fb2-ad51-49251da6e35e, ipv4_address_scope=None, ipv6_address_scope=None, is_default=False, mtu=1500, name=provider1, non_local_subnets=[], port_security_enabled=True, ports=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a16a98>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d29aeaf8>], project_id=a1758405f9c24ae191543248ad65a447, provider:network_type=flat, provider:physical_network=provider, provider:segmentation_id=None, revision_number=2, router:external=True, shared=True, status=ACTIVE, subnets=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a169d8>], tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-28T08:39:29Z, vlan_transparent=None 2022-03-31 11:40:19.649 47489 INFO neutron.agent.dhcp.agent [req-7b9253ec-0a60-4309-ac66-8e3ea167cbba - - - - -] DHCP configuration for ports {'20e8d806-f976-4415-85f5-ed2df55978dc'} is completed 2022-03-31 11:40:19.678 47489 INFO neutron.agent.dhcp.agent [-] Trigger reload_allocations for port admin_state_up=True, allowed_address_pairs=[], binding:host_id=4b243894-d651-4700-9a69-28ca3c60446f, binding:profile=local_link_information=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d29c88e8>], binding:vif_details=, binding:vif_type=binding_failed, binding:vnic_type=baremetal, created_at=2022-03-31T03:40:18Z, description=, device_id=4b243894-d651-4700-9a69-28ca3c60446f, device_owner=baremetal:none, extra_dhcp_opts=[], fixed_ips=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d29c8558>], id=20e8d806-f976-4415-85f5-ed2df55978dc, mac_address=18:9b:a5:81:46:b7, name=, network_id=faa2b805-7898-4fb2-ad51-49251da6e35e, port_security_enabled=True, project_id=a1758405f9c24ae191543248ad65a447, revision_number=3, security_groups=['f574b5d0-8308-40f4-a8e5-81126b920e8f'], status=DOWN, tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-31T03:40:19Z on network _ns_name=qdhcp-faa2b805-7898-4fb2-ad51-49251da6e35e, admin_state_up=True, availability_zone_hints=[], availability_zones=['nova'], created_at=2022-03-28T08:39:24Z, description=, id=faa2b805-7898-4fb2-ad51-49251da6e35e, ipv4_address_scope=None, ipv6_address_scope=None, is_default=False, mtu=1500, name=provider1, non_local_subnets=[], port_security_enabled=True, ports=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a16a98>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d28b53d8>], project_id=a1758405f9c24ae191543248ad65a447, provider:network_type=flat, provider:physical_network=provider, provider:segmentation_id=None, revision_number=2, router:external=True, shared=True, status=ACTIVE, subnets=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a169d8>], tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-28T08:39:29Z, vlan_transparent=None 2022-03-31 11:40:19.776 47489 INFO neutron.agent.dhcp.agent [req-99eb793a-230c-490a-b126-ee9b595ed1bf - - - - -] DHCP configuration for ports {'20e8d806-f976-4415-85f5-ed2df55978dc'} is completed 2022-03-31 11:40:21.082 47489 INFO neutron.agent.dhcp.agent [-] Trigger reload_allocations for port admin_state_up=True, allowed_address_pairs=[], binding:host_id=4b243894-d651-4700-9a69-28ca3c60446f, binding:profile=local_link_information=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d288ea68>], binding:vif_details=, binding:vif_type=binding_failed, binding:vnic_type=baremetal, created_at=2022-03-31T03:40:18Z, description=, device_id=4b243894-d651-4700-9a69-28ca3c60446f, device_owner=baremetal:none, extra_dhcp_opts=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d288e9a8>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d288ed38>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d288e4f8>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d288e528>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d288e948>], fixed_ips=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d288e0a8>], id=20e8d806-f976-4415-85f5-ed2df55978dc, mac_address=18:9b:a5:81:46:b7, name=, network_id=faa2b805-7898-4fb2-ad51-49251da6e35e, port_security_enabled=True, project_id=a1758405f9c24ae191543248ad65a447, revision_number=4, security_groups=['f574b5d0-8308-40f4-a8e5-81126b920e8f'], status=DOWN, tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-31T03:40:21Z on network _ns_name=qdhcp-faa2b805-7898-4fb2-ad51-49251da6e35e, admin_state_up=True, availability_zone_hints=[], availability_zones=['nova'], created_at=2022-03-28T08:39:24Z, description=, id=faa2b805-7898-4fb2-ad51-49251da6e35e, ipv4_address_scope=None, ipv6_address_scope=None, is_default=False, mtu=1500, name=provider1, non_local_subnets=[], port_security_enabled=True, ports=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a16a98>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d29c8eb8>], project_id=a1758405f9c24ae191543248ad65a447, provider:network_type=flat, provider:physical_network=provider, provider:segmentation_id=None, revision_number=2, router:external=True, shared=True, status=ACTIVE, subnets=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a169d8>], tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-28T08:39:29Z, vlan_transparent=None 2022-03-31 11:40:21.207 47489 INFO neutron.agent.dhcp.agent [req-d7cb57c1-4cda-4ceb-99ca-18ca650db61b - - - - -] DHCP configuration for ports {'20e8d806-f976-4415-85f5-ed2df55978dc'} is completed I would very appreciate any kind of guidance or help. Thank you, Han Guangyu

2 1