May 2022 - openstack-discuss - lists.openstack.org

Fwd: unable to connect instance to external network
by Vinesh N 15 May '22

15 May '22

hi, openstack - tripleo installed and was able to launch the instances. Machine has two interfaces, eth2 for external(WAN 192.168.35.0/24) and eth3 for internal(LAN 10.0.20.0/24). issue: unable to reach route interface by following command. (in this case, my route ipaddres 10.0.1.73) * openstack network create public * openstack subnet create --network public public --subnet-range 10.0.1.0/24 --allocation-pool start=10.0.1.40,end=10.0.1.80 --dns-nameserver 8.8.8.8 --gateway 10.0.1.1 --no-dhcp * openstack network create public --provider-physical-network datacentre --provider-network-type vlan --provider-segment 1 --external --share here is my ml2_conf.ini ******************************************************** [ml2] type_drivers=geneve,vlan,flat tenant_network_types=geneve mechanism_drivers=ovn path_mtu=0 extension_drivers=qos,port_security,dns [ml2_type_geneve] max_header_size=38 vni_ranges=1:65536 [ml2_type_vlan] network_vlan_ranges=datacentre:1:1000 [ml2_type_flat] flat_networks=datacentre #[linux_bridge] #physical_interface_mappings = datacentre:br-ex #physical_interface_mappings = datacentre:ens20f2 [ovn] ovn_nb_connection=tcp:10.0.1.158:6641 ovn_sb_connection=tcp:10.0.1.158:6642 ovsdb_connection_timeout=180 neutron_sync_mode=log ovn_l3_mode=True vif_type=ovs ovn_metadata_enabled=True enable_distributed_floating_ip=True dns_servers= ovn_emit_need_to_frag=False **************************************************************** here is my controller network: (ens2042 external and ens2043 internal interfaces) [root@overcloud-controller-0 ~]# ip a |more 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens20f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000 link/ether 00:25:90:fe:0f:dc brd ff:ff:ff:ff:ff:ff inet6 fe80::225:90ff:fefe:fdc/64 scope link valid_lft forever preferred_lft forever 3: ens20f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 00:25:90:fe:0f:dd brd ff:ff:ff:ff:ff:ff 4: ens20f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:25:90:fe:0f:de brd ff:ff:ff:ff:ff:ff inet 192.168.35.86/24 brd 192.168.35.255 scope global dynamic noprefixroute ens20f2 valid_lft 39528sec preferred_lft 39528sec inet6 fe80::f2d5:4cdf:ab4f:4f14/64 scope link noprefixroute valid_lft forever preferred_lft forever 5: ens20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:25:90:fe:0f:df brd ff:ff:ff:ff:ff:ff inet6 fe80::225:90ff:fefe:fdf/64 scope link valid_lft forever preferred_lft forever 6: ib0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 4092 qdisc fq_codel state DOWN group default qlen 256 link/infiniband 80:00:02:08:fe:80:00:00:00:00:00:00:e4:1d:2d:03:00:21:eb:51 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff 7: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether fa:8f:18:e9:44:e6 brd ff:ff:ff:ff:ff:ff 8: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 00:25:90:fe:0f:dc brd ff:ff:ff:ff:ff:ff inet 10.0.1.179/24 brd 10.0.1.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fefe:fdc/64 scope link valid_lft forever preferred_lft forever 9: vlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 42:f0:35:f5:cf:5f brd ff:ff:ff:ff:ff:ff inet 10.0.1.179/24 brd 10.0.1.255 scope global vlan1 valid_lft forever preferred_lft forever inet 10.0.1.141/32 brd 10.0.1.255 scope global vlan1 valid_lft forever preferred_lft forever inet 10.0.1.158/32 brd 10.0.1.255 scope global vlan1 valid_lft forever preferred_lft forever inet6 fe80::40f0:35ff:fef5:cf5f/64 scope link valid_lft forever preferred_lft forever 10: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 76:36:79:8f:4f:b7 brd ff:ff:ff:ff:ff:ff 11: genev_sys_6081: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc noqueue master ovs-system state UNKNOWN group default qlen 1000 link/ether 0e:59:d6:99:85:78 brd ff:ff:ff:ff:ff:ff inet6 fe80::c59:d6ff:fe99:8578/64 scope link valid_lft forever preferred_lft forever Note: I tried with 192.168.35.0/24/200.168.35.0/24 for the external network topology as well. Thanks, Vinesh ---------------

1 0

ImportError: cannot import name 'ceph_spec'" | Openstack Wallaby | Tripleo
by Swogat Pradhan 15 May '22

15 May '22

Hi Team, I am deploying openstack wallaby using the deployed ceph method. I am currently facing this issue while deploying overcloud. Can someone please check ? "2022-05-13 14:17:51.022353 | 48d539a1-1679-730f-272a-0000000000cb | TASK | Create the RGW Daemon spec definition", "An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ImportError: cannot import name 'ceph_spec'", "2022-05-13 14:17:51.669288 | 48d539a1-1679-730f-272a-0000000000cb | FATAL | Create the RGW Daemon spec definition | overcloud-controller-0 | error={\"changed\": false, \"module_stderr\": \"Traceback (most recent call last):\\n File \\\"<stdin>\\\", line 102, in <module>\\n File \\\"<stdin>\\\", line 94, in _ansiballz_main\\n File \\\"<stdin>\\\", line 40, in invoke_module\\n File \\\"/usr/lib64/python3.6/runpy.py\\\", line 205, in run_module\\n return _run_module_code(code, init_globals, run_name, mod_spec)\\n File \\\"/usr/lib64/python3.6/runpy.py\\\", line 96, in _run_module_code\\n mod_name, mod_spec, pkg_name, script_name)\\n File \\\"/usr/lib64/python3.6/runpy.py\\\", line 85, in _run_code\\n exec(code, run_globals)\\n File \\\"/tmp/ansible_ceph_mkspec_payload_iwqyfs7g/ansible_ceph_mkspec_payload.zip/ansible/modules/ceph_mkspec.py\\\", line 24, in <module>\\nImportError: cannot import name 'ceph_spec'\\n\", \"module_stdout\": \"\", \"msg\": \"MODULE FAILURE\\nSee stdout/stderr for the exact error\", \"rc\": 1}", With regards, Swogat Pradhan

2 6

[all][tc] What's happening in Technical Committee: summary May 13, 2022: Reading: 5 min
by Ghanshyam Mann 14 May '22

14 May '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on May 12. Most of the meeting discussions are summarized in this email. Meeting summary logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-05-12-15.00.log.html * Next TC weekly meeting will be on May 19 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by May 18. 2. What we completed this week: ========================= * FIPS goal is selected community-wide goal now[2]. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], we have started the many items. Open Reviews ----------------- * Nine open reviews for ongoing activities[4]. Change OpenStack release naming policy proposal ----------------------------------------------------------- In today's TC meeting [5], we discussed this topic with Foundation staff and we all agreed to give the release name process handling to Foundation. TC will not be involved in the process. The release name will be mainly used for marketing purposes and we will use the release number as the primary identifier in our release scheduling, automated processes, directory structure etc. The agreed proposal is up for review[6] New release cadence open items --------------------------------------- 1. release notes strategy: Brian presented the different possible ways to reflect the tick-tock ( hoping this is the last time I am using these names as we agree to change them, see below ) release notes combination[7] and we agreed with the 'simple' approach[8]. 2. release cadence terminology With the outcome of the legal check, it is not clear to us that tick-tock words are ok to use for the new release cadence terminology and in what form/combination. In TC, we decided to use a different name and 'SLURP' (Skip Level Upgrade Release Process) is the choice of the majority. I have pushed the patch to reflect the same in the TC resolution[9]. Improve project governance --------------------------------- Slawek has the proposal the framework up and it is under review[10]. New ELK service dashboard: e-r service ----------------------------------------------- Tripleo team joined the TC meeting and we agreed to merge the master and rdo branches in the elastic-recheck repo. It is completely fine to keep both devstack-based and tripleo focus things and maintain them collaboratively. The hosting part will be investigated by the dpawlik Consistent and Secure Default RBAC ------------------------------------------- We had our weekly call on Tuesday 10 May and we agreed on the 'service' role part. I will update the spec for this. The heat open item is still in discussion and Takashi sent an email asking the feedback about the 'split stack' approach, please respond with your thought[11] While we are discussing the heat/scope things, we agreed to work on the 'new defaults' at least (separate from scope which will see later). Please find the summary/plan in etherpad L97[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. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's the situation again on ML and hope Braden will be ready with their company side permission[14]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15]. Project updates ------------------- * None 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[16]. [2] https://governance.openstack.org/tc/goals/selected/fips.html 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://meetings.opendev.org/meetings/tc/2022/tc.2022-05-12-15.00.log.html#… [6] https://review.opendev.org/c/openstack/governance/+/841800 [7] https://review.opendev.org/c/openstack/cinder/+/840996 [8] https://review.opendev.org/c/openstack/cinder/+/840996/1/releasenotes/sourc… [9] https://review.opendev.org/c/openstack/governance/+/840354 [10] https://review.opendev.org/c/openstack/governance/+/839880 [11] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028490.html [12] https://etherpad.opendev.org/p/rbac-zed-ptg#L97 [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[manila] Manila Zed hack-a-thon
by Carlos Silva 14 May '22

14 May '22

Hi Zorillas and fellow stackers, Over the past cycles we had a good effort to add OSC support to Manila. We are quite close to parity now (thanks to all the Zorillas involved). In those changes, we didn't focus on automated functional testing. Over PTG we came up with the idea to host a hack-a-thon, so we could enhance our functional test coverage, helping to ensure the quality of our OSC. We will be doing that from *May 16th to May 23rd.* The work on OSC is currently being tracked here: https://tree.taiga.io/project/gouthampacha-openstack-manila-osc-integration… What are the plans for the hack-a-thon: - There are few examples of recent additions [1][2] that could serve as inspiration. You're free to create, claim and edit Taiga cards for the implementation you're chasing. Please reach out to me (carloss) or Goutham (gouthamr) if you have to be added to the taiga board. Also, Add yourself as a "watcher" to two other Taiga cards that someone else is implementing, this will mean that you will be a code reviewer on these implementations! - You can work in teams - min size: 1, max size: 2 - You can submit code between May 16th 1500 UTC and May 23rd 1500 UTC to count towards this hack-a-thon - During the hack-a-thon, we'll use #openstack-manila on OFTC to chat, and hop onto a meeting room [3] - We'll have a one hour kick-off session on May 16th at 1500 UTC - On this session we will also cover the environment setup - We'll use the manila community meeting hour as a mid-point status check (May 19th, 1500 UTC) - We'll have a half-hour close out meeting to discuss reviews, AIs and futures (May 23rd, 1500 UTC) All sessions will take place on the [3] bridge. Please feel free to reach out here or on OFTC's #openstack-manila if you have any questions! Huge thank you to Maari for helping us out with the backlog. I hope to see you there and that we accomplish good things with this Hackathon! [1] https://review.opendev.org/c/openstack/python-manilaclient/+/707577 [2] https://review.opendev.org/c/openstack/python-manilaclient/+/836834 [3] https://bluejeans.com/371190441 Regards, carloss

1 0

[release] Release countdown for week R-20, May 16 - 20
by Előd Illés 14 May '22

14 May '22

Development Focus ----------------- The Zed-1 milestone is next week, on May 19th, 2022! Project team plans for the Zed cycle should now be solidified. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library which had changes but has not been otherwise released since the Yoga release. PTL's or release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well, by posting a -1. If we do not hear anything at all by the end of the week, we will assume things are OK to proceed. NB: If one of your libraries is still releasing 0.x versions, start thinking about when it will be appropriate to do a 1.0 version. The version number does signal the state, real or perceived, of the library, so we strongly encourage going to a full major version once things are in a good and usable state. Upcoming Deadlines & Dates -------------------------- Zed-1 milestone: May 19th, 2022 OpenInfra Summit: June 7-9, 2022 (Berlin) Előd Illés irc: elodilles

1 0

[puppet] Gate blocker: Installation of the systemtap package fails
by Takashi Kajinami 13 May '22

13 May '22

Hello, We are currently facing consistent failure in centos stream 9 integration jobs. which is caused by the new dyninst package. I've already reported the issue in bz[1] and we are currently waiting for the updated systemtap package. Please avoid rechecking until the package is released [1] https://bugzilla.redhat.com/show_bug.cgi?id=2079892 If the fix is not released for additional days then we can merge the temporal workaround to unblock our jobs. https://review.opendev.org/c/openstack/puppet-openstack-integration/+/840188 Last week we also saw centos stream 8 jobs consistently failing but it seems these jobs were already fixed by the new python3-qt5 package. [2] https://bugzilla.redhat.com/show_bug.cgi?id=2079895 Thank you, Takashi

2 3

[TripleO] Gate blocker on Wallaby/Victoria/Train - Content-provider job failing
by Sandeep Yadav 13 May '22

13 May '22

Hello All, Currently, we have a check/gate blocker on Tripleo Content-provider job for wallaby and earlier branches. The content-provider job cannot pull Ceph related containers because quay.ceph.io is not accessible. The details have been added to the launchpad bug[1]. Please hold rechecks while we are investigating the issue. In the meantime, We are trying to switch the registry to pull ceph related containers and waiting for the triple ceph team squad reviews on the patch[2]. [1] https://bugs.launchpad.net/tripleo/+bug/1973115 [2] https://review.opendev.org/c/openstack/tripleo-common/+/841512 Sandeep (on behalf of TripleO CI team)

1 1

Meet the OpenStack community in Berlin, June 7-9
by Helena Spease 13 May '22

13 May '22

Hi everyone, OpenInfra Summit Berlin is around the corner, and in less than a month, hundreds of OpenStack community members will be in Berlin, Germany to present and share the latest upstream development, use cases and news in the OpenStack community. Here I have compiled all the OpenStack sessions that you can look forward to at the Summit. https://superuser.openstack.org/articles/what-can-you-expect-to-learn-about… <https://superuser.openstack.org/articles/what-can-you-expect-to-learn-about…> Don’t forget to register before the Summit prices increase on May 16 at 11:59 PM PT to save on your ticket purchase and learn all about the OpenStack project at the OpenInfra Summit Berlin, June 7-9. You can register for your ticket here: https://openinfrasummitberlin.eventbrite.com <https://openinfrasummitberlin.eventbrite.com/> Cheers, Helena

1 0

[neutron] Drivers meeting agenda - 13.05.2022.
by Lajos Katona 13 May '22

13 May '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. [RFE][fwaas][OVN]support l3 firewall for ovn driver (#link https://bugs.launchpad.net/neutron/+bug/1971958) * On Demand agenda: (ralonsoh): https://bugs.launchpad.net/neutron/+bug/1973049: with the SQLAlchemy 2.0 compatibility patch in place (n-lib 2.21.0), there are some issues when an API call (e.g.: user command) updates the same resource as another RPC call (agent call). This is very frequent with port status and FIP status. Sometimes (I still need to investigate the reason), the retry command detects that there is another SQL transaction in progress ( https://paste.opendev.org/show/beHzMCKjVLmE5nX0ZXZX/) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[Neutron][neutron-vpnaas] proposing Mohammed Naser for neutron-vpnaas core reviewer
by Lajos Katona 13 May '22

13 May '22

Hi, I would like to propose Mohammed Naser (mnaser) as a core reviewer to neutron-vpnaas. He and his company uses neutron-vpnaas in production and volunteered to help in the maintenance of it. You can vote/feedback in this email thread. If there is no objection by 6th of May, we will add Mohammed to the core list. Thanks Lajos

6 6