February 2022 - openstack-discuss

[election][Neutron]PTL candidacy for Z
by Lajos Katona 09 Feb '22

09 Feb '22

Hello Openstack Community, I write to submit my candidacy for the Neutron PTL position during the Z cycle. I have been PTL for the Yoga cycle, and I would like to serve the community for another cycle. During the last few cycles the team faced a lot of challenges, like: * Lack of review capacity, which on the other hand means that we have a lot to review, and that is good. * Channel in developers from new companies. * Keep Neutron stable while at the same time keep the speed of feature development. * CI instabilities. * Keep coverage and decrease the load Neutron jobs cause in the infra. The team tried to address these, so we have biweekly video meeting for CI issues (on the other week we kept the IRC for CI meeting), we increased the size of the drivers team, we included back some retired stadium project with new developers who would like to maintain them, or worked actively to decrease the amount of jobs we execute for each commit. As a summary I would like to continue with a focus on these items to keep Networking in Openstack stable and inclusive. Thank you for your time and consideration. Lajos Katona (lajoskatona)

1 0

[kolla] [horizon] Custom logos (WAS: [Openstack-operators] Horizon Custom Logos (Queens, 13.0.1))
by Gregory Orange 09 Feb '22

09 Feb '22

We have been using Ubuntu VMs for the control plane until now, so it was a simple matter of inserting our logo-splash.svg and logo.svg into /var/lib/openstack-dashboard/static/dashboard/img/ and then restarting services. Now we're switching to Kolla, and the relevant path isn't mounted as is the case with the likes of /etc/kolla/horizon and /var/log/kolla. We don't (yet?) build our own container images, so I'm wondering what next. Did anyone get any further with this? On 21/8/18 9:28 pm, Nick Jones wrote: > Hi Erich. > > Yeah, I battled against this myself quite recently. Here's what I did > to add a logo to the Horizon splash page and to the header of each page > itself. > > Create a file called _splash.html, containing: > > <div class="text-center"> > <img class="splash-logo" src={% themable_asset "img/logo.png" %}> > </div> > > And a file called _brand.html, containing: > > {% load branding %} > {% load themes %} > > <a class="navbar-brand" href="{% site_branding_link %}" target="_self"> > <img class="openstack-logo" src="{% themable_asset 'img/logo.png' %}" > alt="{% site_branding %}"> > </a> > > I then created a folder > called /usr/share/openstack-dashboard/openstack_dashboard/themes/default/templates/auth/ > and copied _splash.html into there, copied _brand.html > into /usr/share/openstack-dashboard/openstack_dashboard/templates/header/, > and finally my 'logo.png' was copied > into /usr/lib/python2.7/site-packages/openstack_dashboard/static/dashboard/img/ > > Note that this approach might differ slightly from your setup, as in my > case it's a Kolla-based deployment so these changes are applied to the > image I'm using to deploy a Horizon container. But it's the same > release (Queens) and a CentOS base image, so in principle the steps > should work for you. > > Hope that helps. > > -- > > -Nick > > On 20 August 2018 at 17:40, Erich Weiler <weiler(a)soe.ucsc.edu > <mailto:weiler@soe.ucsc.edu>> wrote: > > Hi Y'all, > > I've been banging my head against a wall for days on this item and > can't find anything via google on how to get around it - I am trying > to install a custom logo onto my Horizon Dashboard front page (the > splash page). I have my logo ready to go, logo-splash.png. I have > tried following the instructions here on how to install a custom logo: > > https://docs.openstack.org/horizon/queens/admin/customize-configure.html > <https://docs.openstack.org/horizon/queens/admin/customize-configure.html> > > But it simply doesn't work. It seems this stanza... > > #splash .login { > background: #355796 url(../img/my_cloud_logo_medium.png) no-repeat > center 35px; > } > > ...doesn't actually replace the logo (which is logo-splash.svg), it > only seems to put my file, logo-splash.png as the *background* to > the .svg logo. And since the option there is "no-repeat center", it > appears *behind* the svg logo and I can't see it. I played around > with those options, removing "no-repeat" for example, and it > dutifully shows my logo repeating in the background. But I need the > default logo-splash.svg file to actually be gone and my logo to > exist in it's place. Maybe I'm missing something simple? > > I'm restarting apache and memchached after every change I make when > I was testing. > > And because the images directory is rebuilt every time I restart > apache, I can't even copy in a custom logo-splash.svg file. Which > wouldn't help anyway, as I want my .png file in there instead. I > don't have the means to create a .svg file at this time. ;) > > Help! > > As a side note, I'm using the Queens distribution via RedHat. > > Many thanks in advance, > erich > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators(a)lists.openstack.org > <mailto:OpenStack-operators@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators> > > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- Gregory Orange Cloud System Administrator Scientific Platforms Team building representative Pawsey Supercomputing Centre, CSIRO

3 3

Recently Upgraded to XENA and getting this error
by Adivya Singh 09 Feb '22

09 Feb '22

Hello, We have recently upgraded to XENA release of Openstack, and getting this error while trying to Resize instance using GUI, it is telling "Danger , Please try Later" Same is working properly from CLI without any issue Any thoughts on this Regards Adivya Singh

9 11

[kolla-ansible] custom configuration override issue.
by Satish Patel 09 Feb '22

09 Feb '22

Folks, I have a working kolla-ansible environment and now I want to push out some nova custom changes to specific compute nodes and I am trying the following override but somehow it doesn't work for me. Ansible inventory file multinode [control] 192.168.75.141 ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key 192.168.75.142 ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key 192.168.75.143 ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key [compute] 192.168.75.[144:175] ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key I want to change some option on 192.168.75.199 compute server, I don't have compute name in inventory so i am using IP address for override but somehow that doesn't work /etc/kolla/config/nova/192.168.75.199/nova.conf I have tried the following to use hypervisor hostname but that doesn't work. What am I doing wrong here? /etc/kolla/config/nova/COMP01.local/nova.conf Following works for me but they are for global not for specific nodes. How do i override specific node file? /etc/kolla/config/nova/nova-compute.conf

2 4

Error: Not authorized for image
by Michael STFC 09 Feb '22

09 Feb '22

Hi All, I have a problem with vm. Its in error state and rebooting won’t fixed it and still no luck. Error: Failed to perform requested operation on instance “xxx-production-db”, the instance has an error status: Please try again later [Error: Not authorized for image 3457dd8a-037a-4360-b77a-059d2782cbbf.].

1 0

[neutron] Bug deputy report for week of January 31
by Lajos Katona 08 Feb '22

08 Feb '22

Hi Neutron Team I was bug deputy in neutron last week. Summary ======= Needs attention ============ * Neutron-dynamic-routing does not work with OVN ( https://bugs.launchpad.net/neutron/+bug/1959666) * [stein][neutron] Static rules losed ( https://bugs.launchpad.net/neutron/+bug/1959884) * VM gets wrong ipv6 address from neutron-dhcp-agent after ipv6 address on port was changed (https://bugs.launchpad.net/neutron/+bug/1959697) Bugs with assignees ================ * Random Tempest test failures(SSH failure) in openvswitch jobs ( https://bugs.launchpad.net/neutron/+bug/1959564) ** https://review.opendev.org/c/openstack/neutron/+/827315 * QoS Ingress bandwidth limit with OVS backend may not work as expected ( https://bugs.launchpad.net/neutron/+bug/1959567) ** WIP: https://review.opendev.org/c/openstack/neutron/+/827112 * test_local_ip_connectivity test failing in stable/xena jobs ( https://bugs.launchpad.net/neutron/+bug/1959573) ** MERGED: https://review.opendev.org/c/openstack/neutron/+/827057 * pip 22 breaks python3.6 jobs (Victoria and older CI jobs) ( https://bugs.launchpad.net/neutron/+bug/1959600) ** MERGED: https://review.opendev.org/q/Iab2c391d5388461fe9e9037cee81884ce8032e72 * minimum_packet_rate qos rule type is not visible in the GET /v2.0/qos/rule-types response ( https://bugs.launchpad.net/neutron/+bug/1959749) ** https://review.opendev.org/q/topic:bug%252F1959749 * "get_rule_type" should not check the context admin status ( https://bugs.launchpad.net/neutron/+bug/1959778) ** https://review.opendev.org/c/openstack/neutron-lib/+/827533 * ovn-octavia loadbalancer not working when VIP is on a dual-stack provider network (https://bugs.launchpad.net/neutron/+bug/1959903 ) ** https://review.opendev.org/c/openstack/ovn-octavia-provider/+/827670 * [ovn] Stale ports in the OVN database at churn ( https://bugs.launchpad.net/neutron/+bug/1960006) ** https://review.opendev.org/c/openstack/neutron/+/827834 * neutron-tempest-with-uwsgi job failing tempest tests with: Floating ip <fip> failed to associate with server <server id> in time ( https://bugs.launchpad.net/neutron/+bug/1960022 ) ** MERGED: https://review.opendev.org/c/openstack/tempest/+/814085 * NullQuota driver returns None that breaks client API ( https://bugs.launchpad.net/neutron/+bug/1960032) ** https://review.opendev.org/c/openstack/neutron/+/827875 Low hanging fruit ============= * potential performance issue when scheduling network segments ( https://bugs.launchpad.net/neutron/+bug/1959750) Need more information ================== * Disallow users to allocate gateway ip of external subnets as floating ip ( https://bugs.launchpad.net/neutron/+bug/1959699 ) Regards Lajos Katona (lajoskatona)

2 1

OpenInfra Summit Berlin- CFP Deadline in 24 Hours!
by Erin Disney 08 Feb '22

08 Feb '22

The deadline for the upcoming OpenInfra Summit’s Call for Presentations is in 24 hours! CFP for the Berlin Summit (June 7-9th) is still open until February 9th at 22:59 UTC (4:59 PM CT). Reminder that Summit attendance fees are waived for all accepted speakers. Submit your talk for the OpenInfra Summit here: https://cfp.openinfra.dev/app/berlin-2022 2022 Summit Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops NEW: Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security More Summit resources: Registration is live at Early Bird pricing: https://openinfrasummitberlin.eventbrite.com/ Sponsorships are available: https://openinfra.dev/summit-sponsor Apply for the Travel Support Program: https://openinfrafoundation.formstack.com/forms/TSP_Berlin2022 Questions or issues with your submission? Email speakersupport(a)openinfra.dev and we will be happy to help you sort it out. Thanks, Erin Erin Disney Event Marketing Open Infrastructure Foundation Erin Disney Event Marketing Open Infrastructure Foundation

1 0

[all][Neutron][Octavia][Nova][Kuryr] Bump pyroute2 version to 0.6.5 in stable/wallaby
by Lucas Alvares Gomes 08 Feb '22

08 Feb '22

Hi, I currently have a patch up for openstack/requirements [0] bumping the version of the pyroute2 library from 0.5.14 to 0.6.5 as the older version have a memory leak issue [1] in the NDB module which can cause the service using the library to be killed by the OOM killer because of an out-of-memory condition. This email was a suggestion by a core reviewer to raise awareness from the broader community to this change/issue. Please if you have any concerning about this version bump let us know here on in the patch itself [0] [0] https://review.opendev.org/c/openstack/requirements/+/828091 [1] https://github.com/svinota/pyroute2/issues/789 Cheers, Lucas

2 2

[ironic]Anaconda deploy interface config
by Carol Bouchard 08 Feb '22

08 Feb '22

Ironic folks: I'm trying to spawn a RHEL7 image using a kickstart file and having issues with stage2 file. First I used bifrost to initially setup a couple of VMs. (There is no openstack/glance). I'm now using one of those VMs to boot up with RHEL7. I changed the VM config with the following: *| deploy_interface | anaconda* * | instance_info | {'kernel': 'http://myip:8080/RHEL7/vmlinuz <http://myip:8080/RHEL7/vmlinuz>', 'ramdisk': 'http://myip:8080/RHEL7/initrd.img <http://myip:8080/RHEL7/initrd.img>', 'image_source': 'http://myip:8080/RHEL7/initrd.img <http://myip:8080/RHEL7/initrd.img>', 'stage2': 'http://myip:8080/RHEL7/squashfs.img <http://myip:8080/RHEL7/squashfs.img>', 'ks_cfg': 'http://myip:8080/RHEL7/ks.cfg.template <http://myip:8080/RHEL7/ks.cfg.template>', 'ks_template': 'http://myip:8080/RHEL7/ks.cfg.template <http://myip:8080/RHEL7/ks.cfg.template>'}* ironic.conf changes I made are as follows: *enabled_deploy_interfaces = direct,ramdisk,anaconda* *[anaconda]default_ks_template = file:///etc/ironic/ks.cfg.template* The error I'm getting is as follows: *$ baremetal node show testvm1 --field last_error* *| last_error | Deploy step deploy.deploy failed with IsADirectoryError: [Errno 21] Is a directory: '/httpboot/4e41df61-84b1-5856-bfb6-6b5f2cd3dd11/LiveOS/squashfs.img'.* Tail end of traceback is as follows: * ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/common/pxe_utils.py", line 1245, in cache_ramdisk_kernel ironic-conductor[]: ERROR ironic.conductor.utils deploy_utils.fetch_images(ctx, TFTPImageCache(), list(t_pxe_info.values()), ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/deploy_utils.py", line 240, in fetch_images ironic-conductor[]: ERROR ironic.conductor.utils cache.fetch_image(href, path, ctx=ctx, force_raw=force_raw) ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/image_cache.py", line 120, in fetch_image ironic-conductor[]: ERROR ironic.conductor.utils dest_up_to_date = _delete_dest_path_if_stale(master_path, ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/image_cache.py", line 460, in _delete_dest_path_if_stale ironic-conductor[]: ERROR ironic.conductor.utils os.unlink(dest_path) ironic-conductor[]: ERROR ironic.conductor.utils IsADirectoryError: [Errno 21] Is a directory: '/httpboot/4e41df61-84b1-5856-bfb6-6b5f2cd3dd11/LiveOS/squashfs.img'* Please advise. Carol

3 5

[election][cinder] PTL Candidacy for Z
by Rajat Dhasmana 08 Feb '22

08 Feb '22

Hi All, I would like to announce my candidacy for PTL of the Cinder project for the Z cycle. Since this is the first time I'm proposing my candidacy, I would like to briefly introduce myself. I started contributing to OpenStack back in the Queens release (although not very actively) and started focusing on the Cinder project in the Rocky release. I became a core reviewer in Cinder in the mid of the Stein release and since then I've been actively contributing to the Cinder project in terms of features, bug fixes, reviews etc. I'm also a part of Cinder's core security group and a stable core and currently serving as release liaison for Cinder for the past 3 releases. Coming to the focus for the Z release, Cinder receives an abundance of commits every cycle in terms of new drivers, driver features, core cinder features, bug fixes, improvements etc and we've always faced a shortage in reviews. It is not due to fewer people working actively but more of a priority issue in their respective roles. I would like to encourage contributors to discuss with their managers about the importance of code review in opensource and how it is helpful for the community and the individuals as well. Apart from that, I would like to revisit the security issues backlog since that hasn't been looked upon in quite some time and if we encounter something that needs attention, we can also hold core security meetings from time to time to address the issues. We are also getting active driver contributions every cycle which is a good thing, but sadly the driver implementation patches seem to have a lot of mistakes which are well documented in the driver contribution docs and something I would like to highlight in the Z PTG (as most of the vendors join it and propose their driver ideas). Again, the documentation is not perfect as we discussed in Yoga PTG. Following up upon this and improving it is another focus I support for Cinder. Lastly, I would like to put more emphasis upon the 3rd Party CI compliance check which we haven't done in a while and it would be good to know how many vendors are actually maintaining their CI consistently. There are some new ideas started by Brian in the past releases which I would like to continue. Some examples include the last cinder meeting being a video+IRC meeting and every third Friday of the month, we have a festival of XS reviews which significantly reduced the backlog of open patches. In the end, I would like to say, I want to continue the good trends set in the Cinder community and improve on certain areas where there is not much attention being given. I will do my best to address the above mentioned items during my time as PTL. Thanks for considering me. Rajat Dhasmana (whoami-rajat)

1 0