September 2022 - openstack-discuss

Microstack - VM networking & installation probs
by Tim Kahlke 06 Sep '22

06 Sep '22

Hi, I tried to install microstack 245 via Canonical and am running into the “old” VM-can’t-connect-external-network problem. OS: Ubuntu 20.04 Microstack v245 Install seems to have worked ok using sudo snap install microstack --beta. However, journalctl -xe shows ovsdb-server[83528]: ovs|26322|socket_util|ERR|6642:0.0.0.0: bind: Address already in use But not sure if that’s related or not. Network setup is the default, i.e., external 10.20.20.0/24 and internal 192.168.1.0/24. From the host machine I can ping the VMs and vice versa, but I can’t get past the host from the VM. I tried to apply some of the solutions I found on the web, so far without success. This one seems to work for people but my microstack doesn’t seem to have the ovs-vsctl command anywhere. Any suggestions would be much appreciated. Tim

2 1

[manila] LVM shares are unmounted on reboot
by Vaibhav 06 Sep '22

06 Sep '22

Dear All, One of the host running Manila-share service has rebooted. After the reboot the LVMs are not mounted on the Manila mount points. I use LVM Driver with DHSS=False. default_share_type = default_share_type share_name_template = manila-%s rootwrap_config = /etc/manila/rootwrap.conf api_paste_config = /etc/manila/api-paste.ini auth_strategy = keystone my_ip=192.168.82.2 enabled_share_backends = lvm enabled_share_protocols = NFS state_path=/var/lib/manila [lvm] share_backend_name = LVM share_driver = manila.share.drivers.lvm.LVMShareDriver driver_handles_share_servers = False lvm_share_volume_group = VGZunManila lvm_share_export_ips = 192.168.82.2 lvm_share_export_root = $state_path/mnt After the reboot LVMs are there but they are mounted on their respective share location. Any way to solve this and this to be done automatically? Regards, Vaibhav

2 2

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations Last Days - FINAL REMINDER
by Amy Marrich 06 Sep '22

06 Sep '22

This is your last reminder for the election, I know the US , CA, and a few other countries are on holiday today. Please also read Jeremy's early email about the TC seats and governance. Thank, Amy\ ----------------------------------------------- A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Sep 07, 2022 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2022-08-24 23:45:00 UTC Nominations end @ 2022-09-07 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 2 days, 4:16:33 Nominations progress : 84.44% --------------------------------------------------- Projects[1] : 52 Projects with candidates : 35 ( 67.31%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 17 (Adjutant Barbican Keystone Masakari Mistral OpenStackSDK OpenStack_Charms Openstack_Chef Oslo Release_Management Requirements Sahara Senlin Skyline Swift Venus Zun) =================================================== Stats gathered @ 2022-09-05 19:28:27 UTC This means that with approximately 2 days left, 17 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[neutron] Team meeting on Sept. 6 cancelled
by Lajos Katona 06 Sep '22

06 Sep '22

Hi, Sorry for late mail, but tomorrow I can't drive the team meeting, so I have to cancel it. I will be otherwise available tomorrow (except around the meeting time), so you can reach me on neutron channel for example. Lajos Katona (lajoskatona)

1 0

Error During installation devstack ModuleNotFoundError: No module named 'neutron'
by mahdi n 06 Sep '22

06 Sep '22

I was installing DevStack on Ubuntu 20.04 when I encountered this error It says that the Neutron module was not found while neutron is installed ++lib/neutron_plugins/ovn_agent:filter_network_api_extensions:439 > /usr/local/bin/python3.8 -c 'from neutron.common.ovn import extensions ;\ > > print(",".join(extensions.ML2_SUPPORTED_API_EXTENSIONS)) > ' > Traceback (most recent call last): > > File "<string>", line 1, in <module> > > ModuleNotFoundError: No module named 'neutron' > > +lib/neutron_plugins/ovn_agent:filter_network_api_extensions:439 > >

3 2

[all][election][tc] TC election at risk of single-employer majority
by Jeremy Stanley 05 Sep '22

05 Sep '22

The extended nomination period for the upcoming TC election closes in just over two days. We need to elect people to fill 4 of the 9 seats on the TC during this round. We currently have just enough candidates to fill the open seats, but in so doing we would end up with a majority of the TC members employed by the same company. Appendix 4 of the bylaws of the Open Infrastructure Foundation, the Technical Committee Member Policy[*], states: > In the event of a Technical Committee election that would result > in half or more of the members of the Technical Committee being > Affiliated, the Board of Directors may defer the effective date of > office of the newly elected Technical Committee members who are > Affiliated for a period not to exceed thirty (30) days after a > resolution by the Board of Directors approving such deferral. The > Board of Directors must pass such resolution within thirty (30) > days of the notice of election results from the Technical > Committee. During such period of deferral, the Technical Committee > and the Board of Directors shall work to resolve the issue by > agreement among themselves, such as by a resignation of one or > more Technical Committee members or having the Individual Member > with the next highest number of votes become a member of the > Technical Committee. If the Technical Committee and the Board of > Directors are not able to agree on a resolution within such thirty > (30) day period, the Board of Directors may require another > election for such positions. In order to avoid this outcome, we need additional nominees with a variety of affiliations immediately. If you've considered running for a seat on the OpenStack TC before, now is definitely the time. Please see earlier announcements[**] from the election officials for details on how to submit your nomination. Thanks! [*] https://openinfra.dev/legal/openstack-technical-committee-member-policy [**] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030094.… https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030241.… -- Jeremy Stanley

1 0

Secret getPayload() openstack4j
by Srinivasan T 05 Sep '22

05 Sep '22

Hi, I'm unable to get the secret's payload from openstack4j, it always returns null. Secret secret = os.barbican().secrets().get("19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60"); secret.getPayload(); //Always returns null The same works when using the OpenStack CLI, openstack secret get --payload_content_type 'application/octet-stream' --file secret-payload http://x.x.x.x:9311/v1/secrets/19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60 I'm using the below OpenStack4j version, Bundle-Name: OpenStack4j Core Bundle-Version: 3.6.0 OpenStack is in Queens version. Let me know if someone can help on this. Regards, Srini

2 1

[adjutant][magnum][mistral][sahara][watcher][zaqar][tc] broken gate for deliverables
by Előd Illés 05 Sep '22

05 Sep '22

Hi, Now that we have passed Zed-3 milestone, Release team starts to check the health of deliverables via their gate healthiness. The 1st round of checks showed that the following deliverables seem to have blocked gates: python-adjutantclient [1] python-magnumclient [2] python-mistralclient [3] python-saharaclient [4] python-watcherclient [5] python-zaqarclient [6] We are asking the teams to fix their gates and propose a release after it is fixed as soon as possible, otherwise these deliverables might not be part of the official Zed release. [1] https://review.opendev.org/c/openstack/python-adjutantclient/+/855763 [2] https://review.opendev.org/c/openstack/python-magnumclient/+/855778 [3] https://review.opendev.org/c/openstack/python-mistralclient/+/855781 [4] https://review.opendev.org/c/openstack/python-zaqarclient/+/855796 [5] https://review.opendev.org/c/openstack/python-watcherclient/+/855795 [6] https://review.opendev.org/c/openstack/python-saharaclient/+/855787 Thanks, Előd Illés irc: elodilles

2 1

http proxy support
by Oliver Weinmann 02 Sep '22

02 Sep '22

Hi, I was wondering if there is a way to set a http proxy in kolla-ansible during deployment / update etc. Today I wanted to pull new containers and this saturates our internet connection. What we usually do is have machine that massively download stuff from the internet use a squid proxy that throttles their bandwidth. I found the following feature request: https://bugs.launchpad.net/kolla-ansible/+bug/1829586 And it seems some work had been done, but I can't seem to find any info if the change really made it into production: https://review.opendev.org/c/openstack/kolla-ansible/+/692006/ Any help or hints are highly appreciated. Cheers, Oliver

2 4

[all][tc] What's happening in Technical Committee: summary 2022 Sept 2: Reading: 5 min
by Ghanshyam Mann 02 Sep '22

02 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 01. Most of the meeting discussions are summarized in this email. Meeting full recording is available @ https://www.youtube.com/watch?v=WDfOx1m-wog and summary logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-01-15.01.log.html * Next TC weekly meeting will be on Sept 08 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 07. 2. What we completed this week: ========================= * Appointed Dale Smith as Adjutant PTL for Zed cycle[2] * Switched requirements to distributed leadership [3] * Added Exception for the combined 2023.1(Antelope) elections [4] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[5], four are completed and others items are in-progress. Open Reviews ----------------- * Four open reviews for ongoing activities[6]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- By considering the holiday weeks, we decided to extend the nomination by a week[7]. The new deadline for nomination is Sept 7 [8]. We request you not to delay your nomination for PTL or TC. Define 2023.1 cycle testing runtime ------------------------------------------- Testing runtime for the 2023.1 cycle is up for review [9]. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * "TC + Leader interaction" sessions is scheduled for Oct 17 Monday 15-17 UTC[10], * I have created the TC PTG etherpad to collect the topic[11]. * I sent email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[12] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[14]15]. Project updates ------------------- * Switch release management to distributed leadership[16] 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[17]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [18] 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/+/849606 [3] https://review.opendev.org/c/openstack/governance/+/854685 [4] https://review.opendev.org/c/openstack/governance/+/854624 [5] https://etherpad.opendev.org/p/tc-zed-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030241.… [8] https://governance.openstack.org/election/ [9] https://review.opendev.org/c/openstack/governance/+/854375 [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [11] https://etherpad.opendev.org/p/tc-2023-1-ptg [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] https://etherpad.opendev.org/p/zuul-config-error-openstack [15] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [16] https://review.opendev.org/c/openstack/governance/+/855276 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0