February 2023 - openstack-discuss

[cinder] Bug Report - 02-08-2023
by Sofia Enriquez 08 Feb '23

08 Feb '23

This is a bug report from 02-01-2023 to 02-08-2023. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/2004565 "non-exploitable resource exhaustion with malicious vmdk." Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/2004484 "list dependencies with tox4." Unassigned. - https://bugs.launchpad.net/cinder/+bug/2004537 "[storwize] Invalid Exception raised due to Invalid port set value." Assigned to Kumar Kanishka. Low - https://bugs.launchpad.net/cinder/+bug/2004630 "Dell PowerFlex: Unnecessary login happens." Assigned to Jean Pierre Roquesalane. - [outreachy possible first contribution] https://bugs.launchpad.net/cinder-tempest-plugin/+bug/2006594 "Inaccurate docstring test_boot_cloned_encrypted_volume." Unassigned. Cheers,

1 1

[ALL] Why we dont have an official forum?
by Nguyễn Hữu Khôi 08 Feb '23

08 Feb '23

Hello guys. Openstack is a very interesting project, many questions from users will make it grow more and more but I see that people, including me, still ask the same question. It is hard to sort or find knowledge by this way. If we hope this project spreads for people, we need a new way to share knowledge and skills, we are in the modern world but the way to access and exchange information in this project is too obsolete. This is a wall to slow down this project. Nguyen Huu Khoi

13 19

[largescale-sig] Next meeting: Feb 8, 9utc (!)
by Thierry Carrez 08 Feb '23

08 Feb '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC. This is a new hour, as we decided to rotate meetings between an APAC+EU time and a EU+US time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230208T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

slow server list
by Parsa Aminian 08 Feb '23

08 Feb '23

3 2

[ironic]Could I use x86 ironic to deploy arm bare metal node?
by 韩光宇 08 Feb '23

08 Feb '23

Hi, I deploy ironic in x86 env, could I use it to deploy arm bare metal node? My concern is mainly whether the files transferred in the tftp phase of PXE cannot be cross-architecture. Do I need to deploy a dedicated arm-architecture ironic-conductor node for arm-architecture bare metal nodes? Thanks

3 3

[TripleO] what option to enable restart compute node if it becomes unavailable/not pingable
by Ruslanas Gžibovskis 08 Feb '23

08 Feb '23

Hi all, Since TripleO is Openstack Over Openstack, and overcloud is able to recover instances if they become unavailable, how to enable/force undercloud to launch reset over redfish/idrac? Any suggestions? If that is relevant, I use ussuri, but I think this should not be relevant to the question for the option since I would like to have same enabled in latest release also. -- Ruslanas Gžibovskis +370 6030 7030

2 1

[QA] openstack-tox-py27 failures PSA
by Dariusz Smigiel 08 Feb '23

08 Feb '23

Hi Team, Recent change [1] to remove python27 from images caused issues across jobs still using python 2.7 There are a lot of projects failing due to that. [2] The solution is to update bindep.txt [3] The fix was discussed with the #opendev team and can be summarized as follows. [4] ``` 15:37 <clarkb> I think we have ~3 options: A) revert/or readd python2-dev installs B) ask projects to fix their broken bindep.txts (something we've asked for for years at this point) or C) update -py27 jobs to explicitly install python2 for you ``` I hope it helps. Best regards, Dariusz [1]: https://review.opendev.org/c/openstack/project-config/+/872476/ [2]: https://zuul.opendev.org/t/openstack/builds?job_name=openstack-tox-py27&ski… [3]: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/872983 [4]: https://meetings.opendev.org/irclogs/%23opendev/%23opendev.2023-02-07.log.h…

4 4

Updating copyConditions for Gerrit 3.7
by Ian Wienand 08 Feb '23

08 Feb '23

Hello, Change [1] modifies our Gerrit ACL files to move from the deprecated copy conditionals flags. In simpler terms, these are the flags that set rules for labels about "+2/-2 votes aren't removed when new changesets are updated" or "keep votes when a trivial rebase is made". Projects that have made custom labels (things like "Review-Priority", "Backport-Candidate", etc.) will have specified these as part of the label configuration. There should be no change to the rules applied to labels from this transition; the old rules have been translated into the new format. However, a double check is always welcome; if you project uses custom labels you might like to quickly look at [1]. We plan to merge this change in a few days. In going through all projects, I did notice that projects have perhaps copy-pasted the label/rules and possibly they are not always working as intended. If you use custom labels, it might be an idea to just again double-check the rules are what you want for your project. The new format is quite simple; described at [2] -- basically if the query matches on the new changeset, using standard Gerrit searching rules, then the votes will be copied forward to the new changeset. We are aware that Gerrit 3.6 changed the UI for showing custom labels, and the custom labels are less visible by default. We have raised some of the issues upstream [3]. So far there hasn't been a lot of community engagement with this, but we will keep the discussion going. It is good to remember that Gerrit does have a quite powerful ability to make customised dashboards, and we have gerrit-dash-creator (see samples at [4]) to help as well. Thanks, -i [1] https://review.opendev.org/c/openstack/project-config/+/867931 [2] https://gerrit-review.googlesource.com/Documentation/config-labels.html#lab… [3] https://groups.google.com/g/repo-discuss/c/gYVD-iBR9Ow [4] https://gerrit-dash-creator.readthedocs.io/en/latest/dashboards/index.html

1 0

[all][tc] Technical Committee next weekly meeting on 2023 Feb 8 at 1600 UTC
by Ghanshyam Mann 08 Feb '23

08 Feb '23

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

1 1

Hi, I am watcher ptl chenker. Could you help analyze watcher py38 error？thanks!
by 陈克 08 Feb '23

08 Feb '23

On the surface, the py38 unit test error. But after further analysis, I found that the use cases of failure are all because stevedore cannot be loaded. Here's what I do: 1、Analyzed the version of stevedore 4.1.1 looks like there is no problem. 2、Searched the merged code in watcher history, and found no suspicious points The gerrit link: 871531 Looking forward to your reply. Thanks!

1 1