February 2023 - openstack-discuss

[manila] Manila Bugsquash (Feb 27th to Mar 3rd)
by Carlos Silva 24 Feb '23

24 Feb '23

Hello Zorillas! We have been planning our bugsquash for a couple of weeks now, and time has come! We have seen a trend on the number of bugs increasing this cycle, and we have identified that we have many bugs that already have a fix proposed but we didn't get those changes merged. Merging such issues would help us to fix those bugs and continue reducing our bug backlog. So for this bugsquash we will be focusing on getting closure for such changes! Vida (vhari) kindly groomed the bugs list [1]. We will be meeting on Monday to have a kick-off call at 16 UTC [2], so we can assign reviewers to the changes or discuss the progress of the changes if that is the case. [1] https://ethercalc.net/8ru5hurhelyl [2] https://bluejeans.com/371190441 Looking forward to see you there! Thank you, carloss

1 0

[all][elections][ptl][tc] Combined PTL/TC 2023.2 cycle Election Nominations End
by Tony Breeds 24 Feb '23

24 Feb '23

The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 9 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Monasca, OpenStack_Charms, Rally, Sahara, Senlin, Swift, Tripleo, Vitrage, Winstackers There are 0 projects that will have elections. -- TC Election Details -- There are 5 candidates for 5 seats. Given that there are no polls that need to be held, this concludes the election process. Congratulations to our new and returning leaders. Thank you, Tony, on behalf of the election officials. [0] https://governance.openstack.org/election/#bobcar-ptl-candidates [1] https://governance.openstack.org/election/#bobcat-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

3 5

[release] Release countdown for week R-3, Feb 27 Mar 03
by Herve Beraud 24 Feb '23

24 Feb '23

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, March 02. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2023.1 branch will be cut. This branch will track the 2023.1 Antelope release. Once stable/2023.1 has been created, the master branch will be ready to switch to 2023.2 Bobcat development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2023.1 Antelope plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2023.1 branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/2023.1 branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be 2023.2 Bobcat) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any 2023.1 Antelope release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 02 (R-3 week) Final RC deadline: March 17 (R-1 week) Final 2023.1 Antelope release: March 22 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[kolla-ansible] [yoga] [magnum] [k8s] cannot attach persistent volume to pod
by Stuart Whitman 24 Feb '23

24 Feb '23

Hello, When I try to attach a persistent cinder volume to a pod, I get FailedMount and FailedAttachVolume timeout events. I also get these errors in the log of the csi-cinder-controllerplugin-0 pod: E1020 13:38:41.747511 1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.VolumeAttachment: the server could not find the requested resource E1020 13:38:41.748187 1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.CSINode: the server could not find the requested resource I fixed a CrashLoopBackoff error with the csi-snapshotter container in the csi-cinder-controllerplugin-0 pod by providing the label "csi_snapshotter_tag=v4.0.0" when I created the cluster template. I found that suggestion in an issue on the GitHub cloud-provider-openstack project. I'm not finding any help with this error on Google. Thanks, -Stu _____________________________________ The information contained in this e-mail and any attachments from Group W may contain confidential and/or proprietary information and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, be aware that any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of that fact by return e-mail and permanently delete the e-mail and any attachments to it.

3 5

[neutron] Neutron drivers meeting
by Rodolfo Alonso Hernandez 24 Feb '23

24 Feb '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[magnum] Registry other than dockerhub
by Vivian Rook 23 Feb '23

23 Feb '23

We ran into a problem while deploying magnum when another project exhausted the dockerhub limit on anonymous pulls from a few of the kube-system pods that are deployed. Namely: daemonset.apps/k8s-keystone-auth daemonset.apps/openstack-cloud-controller-manager deployment.apps/kubernetes-dashboard deployment.apps/dashboard-metrics-scraper This would fail with an error noting that dockerhub was blocking the request as too many pulls had happened. We could get around this by adding in a secret with a docker login, and editing those deployments and daemonsets to use that credential. It would appear the container_infra_prefix label can be modified to point to a different registry. Though this would mean we would have to clone all of the images, including images that are from registries other than dockerhub. Leading me to wonder if there isn't an existing registry that one can use using magnum, on quay.io or some host that isn't limiting pulls? Alternatively, is it possible that the dockerhub images that do not pull (some do, coredns for instance does, I suspect it is due to it having "Sponsored OSS" status on dockerhub) without limits could be hosted elsewhere? Or perhaps already are and the default that magnum sets to pull could be updated to those? Alternatively, alternatively, I haven't found an option for giving a dockerhub user/pass to magnum in the documentation, and looking at the code it doesn't appear that there is a variable for one, so I suspect it is not there. Could such an option be added? Thank you -- *Vivian Rook (They/Them)* Site Reliability Engineer Wikimedia Foundation <https://wikimediafoundation.org/>

4 3

[barbican][blazar][ec2-api][freezer][kuryr][monasca][murano][neutron][sahara][solum][winstackers] broken gate on master branch
by Elõd Illés 23 Feb '23

23 Feb '23

Hi $teams_in_subject, Similarly like one week ago, I've generated dummy patches to see gate health of projects' deliverables (but for cycle-with-rc deliverables this time), that have not merged patches recently [1]. These patches show that you have broken gate jobs. Could teams please check what those failures are, and fix them as soon as possible? Thanks in advance! (Note: similarly as I've mentioned in my previous mail, these failures are also mostly tox v4 related issues, that should be easy to fix) [1] https://review.opendev.org/q/topic:release-health-check-cwr-antelope+is:open Thanks, Előd Illés irc: elodilles @ #openstack-release

2 1

[all] Any good alternatives to uwsgi?
by Thomas Goirand 23 Feb '23

23 Feb '23

Hi there! It's been a few Debian release that all OpenStack APIs are served using uwsgi. Unfortunately: https://github.com/unbit/uwsgi/commit/5838086dd4490b8a55ff58fc0bf0f108caa4e… The question is then: - Is continuing to use uwsgi sustainable? - Is there good alternatives? I do not like at all using Apache mod_wsgi, because restarting Apache would mean restarting all services. So I prefer something standalone. I have no clue if gunicorn is well suited for the job, and if: - it performs well - it implements the multi-interpreter API (which IMO is mandatory to avoid global interpreter locks...) Any opinion? Cheers, Thomas Goirand (zigo)

12 19

(Openstack-Neutron)ResourceInError: resources.activelogic: Went to status ERROR due to \"Message: Build of instance 6072c3e9-e530-4173-93b0-4338d6651ade aborted: Failed to allocate the network(s), not rescheduling., Code: 500\"\n2023-02-20 16:32:07Z [activelogic]: CREATE_FAILED ResourceInError: resources.activelogic: Went to status ERROR due to \"Message: Build of instance 356868a0-7341-43e4-8711-58d633fd745b aborted: Failed to allocate the network(s), not rescheduling
by Adivya Singh 23 Feb '23

23 Feb '23

Hi Team, I get these error not often , but some times Went to status ERROR due to \"Message: Build of instance 6072c3e9-e530-4173-93b0-4338d6651ade aborted: Failed to allocate the network(s), not rescheduling., Code: 500\"\n2023-02-20 16:32:07Z [activelogic]: CREATE_FAILED ResourceInError: resources.activelogic: Went to status ERROR due to \"Message: Build of instance 356868a0-7341-43e4-8711-58d633fd745b aborted: Failed to allocate the network(s), not rescheduling My initial thought was these errors related to OVS switch as it goes in some kind of a loop while creating a instance, Any thought on this

3 2

keypair missing from users in Open Stack(Xena Version)
by Adivya Singh 23 Feb '23

23 Feb '23

Hi Team, I am facing an issue where key pairs are missing from users project id all of a sudden. Any thoughts on this. Regards Adivya Singh

3 4