July 2022 - openstack-discuss - lists.openstack.org

Zun connector for persistent shared files system Manila
by Vaibhav 13 Nov '22

13 Nov '22

Hi, I am using zun for running containers and managing them. I deployed cinder also persistent storage. and it is working fine. I want to mount my Manila shares to be mounted on containers managed by Zun. I can see a Fuxi project and driver for this but it is discontinued now. With Cinder only one container can use the storage volume at a time. If I want to have a shared file system to be mounted on multiple containers simultaneously, it is not possible with cinder. Is there any alternative to Fuxi. is there any other mechanism to use docker Volume support for NFS as shown in the link below? https://docs.docker.com/storage/volumes/ Please advise and give a suggestion. Regards, Vaibhav

2 4

[all] Deprecated Zuul queue syntax
by Clark Boylan 16 Sep '22

16 Sep '22

Hello, Zuul deprecated declaring shared queues at a pipeline level with release 4.1.0 [0]. Zuul's current plan is to stop accepting this form of configuration with a future 7.0.0 release. More details on what needs to change can be found in Zuul's reminder notice on the Zuul mailing list [1]. I expect we have about a month before the v7 release which should give us plenty of time to fix this. If we don't fix this before the v7 release the expected fallout will be that these project branches will not have any pipelines defined, which means no Zuul jobs will run against that project branch until the configs are updated. I've marked this for everyone because 98 repositories are affected, and I'm not sure listing them all in the subject would be productive. Here is the list of affected repos: openstack/adjutant openstack/ansible-collection-kolla openstack/ansible-role-collect-logs openstack/ansible-role-tripleo-modify-image openstack/barbican openstack/barbican-tempest-plugin openstack/barbican-ui openstack/blazar openstack/blazar-tempest-plugin openstack/ceilometer openstack/cinderlib openstack/cloudkitty openstack/cloudkitty-tempest-plugin openstack/cyborg-tempest-plugin openstack/designate openstack/designate-dashboard openstack/designate-tempest-plugin openstack/devstack-gate openstack/ec2-api openstack/ec2api-tempest-plugin openstack/freezer openstack/freezer-tempest-plugin openstack/heat openstack/heat-dashboard openstack/heat-tempest-plugin openstack/horizon openstack/ironic openstack/ironic-inspector openstack/ironic-lib openstack/ironic-prometheus-exporter openstack/ironic-python-agent openstack/ironic-tempest-plugin openstack/kayobe openstack/kayobe-config openstack/kayobe-config-dev openstack/kolla openstack/kolla-ansible openstack/kuryr openstack/magnum openstack/magnum-tempest-plugin openstack/manila openstack/manila-tempest-plugin openstack/masakari openstack/masakari-monitors openstack/mistral openstack/mistral-tempest-plugin openstack/monasca-api openstack/monasca-common openstack/monasca-events-api openstack/monasca-log-api openstack/monasca-tempest-plugin openstack/murano openstack/murano-tempest-plugin openstack/networking-generic-switch openstack/octavia openstack/octavia-tempest-plugin openstack/openstack-chef openstack/os-net-config openstack/os-win openstack/oswin-tempest-plugin openstack/paunch openstack/project-config openstack/puppet-pacemaker openstack/puppet-tripleo openstack/python-designateclient openstack/python-ironicclient openstack/python-saharaclient openstack/python-tripleoclient openstack/python-troveclient openstack/sahara openstack/sahara-tests openstack/senlin openstack/senlin-tempest-plugin openstack/solum openstack/solum-tempest-plugin openstack/telemetry-tempest-plugin openstack/tenks openstack/tripleo-ci openstack/tripleo-ci-health-queries openstack/tripleo-common openstack/tripleo-heat-templates openstack/tripleo-quickstart openstack/tripleo-quickstart-extras openstack/tripleo-upgrade openstack/trove openstack/trove-tempest-plugin openstack/vitrage openstack/vitrage-tempest-plugin openstack/watcher openstack/watcher-tempest-plugin openstack/zaqar openstack/zaqar-tempest-plugin openstack/zun openstack/zun-tempest-plugin windmill/windmill windmill/windmill-backup x/neutron-classifier x/vmware-nsx I'll go ahead and push changes to windmill/* and x/* as those are leftovers from splitting things up into tenants and haven't ended up in their own tenants yet. But it would be great if OpenStack can work on cleaning up this deprecated syntax in the OpenStack repos. I've attached a file with a listing that includes more details for each repo (branches and specific config files) to make it easier for people to find where the old syntax is located so that it can be replaced with the new syntax. [0] https://zuul-ci.org/docs/zuul/latest/releasenotes.html#relnotes-4-1-0-depre… [1] https://lists.zuul-ci.org/pipermail/zuul-discuss/2022-May/001801.html

2 2

[ironic][xena] problems updating redfish_password for existing node
by Wade Albright 23 Aug '22

23 Aug '22

Hi, I'm hitting a problem when trying to update the redfish_password for an existing node. I'm curious to know if anyone else has encountered this problem. I'm not sure if I'm just doing something wrong or if there is a bug. Or if the problem is unique to my setup. I have a node already added into ironic with all the driver details set, and things are working fine. I am able to run deployments. Now I need to change the redfish password on the host. So I update the password for redfish access on the host, then use an 'openstack baremetal node set <node> --driver-info redfish_password=<newpass>' command to set the new redfish_password. Once this has been done, deployment no longer works. I see redfish authentication errors in the logs and the operation fails. I waited a bit to see if there might just be a delay in updating the password, but after awhile it still didn't work. I restarted the conductor, and after that things work fine again. So it seems like the password is cached or something. Is there a way to force the password to update? I even tried removing the redfish credentials and re-adding them, but that didn't work either. Only a conductor restart seems to make the new password work. We are running Xena, using rpm installation on Oracle Linux 8.5. Thanks in advance for any help with this issue.

3 21

[all] Proposed Antelope cycle schedule
by Előd Illés 20 Aug '22

20 Aug '22

Hi, As we are beyond Zed milestone 2 for more than 2 weeks now, it's time to start planning the next, Antelope cycle and its release schedule: Antelope schedule: https://review.opendev.org/c/openstack/releases/+/850753 (or see its generated page [1]) Feel free to review it and comment on the patch if there is something that should be considered for the schedule. [1] https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Thanks, Előd Illés irc: elodilles

3 3

[Neutron][Octavia][ovn-octavia-provider] proposing Fernando Royo for ovn-octavia-provider core reviewer
by Lajos Katona 17 Aug '22

17 Aug '22

Hi I would like to propose Fernando Royo (froyo) as a core reviewer to the ovn-octavia-provider project. Fernando is very active in the project (see [1] and [2]). As ovn-octavia-provider is a link between Neutron and Octavia I ask both Neutron and Octavia cores to vote by answering to this thread, to have a final decision. Thanks for your consideration. [1]: https://review.opendev.org/q/owner:froyo%2540redhat.com [2]: https://www.stackalytics.io/report/contribution?module=neutron-group&projec… Cheers Lajos

6 6

[horizon][plugins] Horizon angular based plugins are broken after migrating to angularjs 1.8.2.2
by vishal manchanda 16 Aug '22

16 Aug '22

Hello everyone, Horizon team recently migrated XStatic-Angular 1.5.8.0->1.8.2.2 [1] and after that many horizon angular based plugins start failing [2]. We already fixed these issues in horizon [3]. So I guess we need to fix the similar thing in horizon plugins. Why did we migrated Angular 1.5.8.0->1.8.2.2? The angularjs version is updated 1.5.8.0->1.8.2.2 to include the CVE fixed in the latest version. Also, there is a security bug reported for the same [4]. I have also created an etherpad to track the progress for failed horizon plugins [5]. Action items for the horizon plugins team either fixed their plugins or review/merge the patch pushed by horizon team members on priority basis to fix the gate. The npm jobs are failing in below horizon plugins : • ironic-ui • octavia-dashboard • senlin-dashboard • designate-dashboard • vitrage-dashboard • murano-dashboard • zaqar-ui • zun-ui • magnum-ui In case of any queries, please feel free to reach out to Horizon channel #openstack-horizon. Thanks & Regards, Vishal Manchanda(irc: vishalmanchanda) [1] https://review.opendev.org/c/openstack/requirements/+/844099 [2] https://review.opendev.org/c/openstack/horizon/+/845733 [3] https://review.opendev.org/c/openstack/horizon/+/843346 [4] https://bugs.launchpad.net/horizon/+bug/1955556 [5] https://etherpad.opendev.org/p/Fix_Horizon_Plugins_With_Angularjs_v1.8.2.2

2 2

[tc] August 2022 OpenInfra Board Sync
by Jeremy Stanley 11 Aug '22

11 Aug '22

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2022-08-board-openstack-sync I've also created a Framadate poll has in order to identify a few preferred dates and times. Responses must be submitted by Friday, 2022-07-15, in order to provide the board members with time to pick from the available options. The poll can be found here: https://framadate.org/atdFRM8YeUtauSgC Feel free to reply here on the mailing list, or you can reach out to me directly by E-mail or as fungi in the #openstack-tc IRC channel, with any questions you may have. -- Jeremy Stanley

1 3

Need help on rabbitmq
by AJ_ sunny 10 Aug '22

10 Aug '22

Hi team I am using kolla-ansible based openstack infra and getting below error in logs seems frequent rabbitmq disconnections <0.5023.16> closing AMQP connection <0.5023.16> (10.80.0.13:40356 -> 10.80.0.13:5672 - mod_wsgi:19:d3196668-57e5-46dc-8b69-78d73b5873a0): missed heartbeats from client, timeout: 60s AMQP server on 10.80.0.13:5672 is unreachable: [Errno 104] Connection reset by peer. Trying again in 1 seconds.: ConnectionResetError: [Errno 104] Connection reset by peer Is this bug or any resolution for fixing this issue? Thanks Arihant Jain

4 4

Correct way to add firewall rules in tripleo | Wallaby
by Swogat Pradhan 09 Aug '22

09 Aug '22

Hi, I am trying to add a rule for zabbix in my tripleo wallaby setup on top of centos 8 stream. i followed https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… but got the error message: [ERROR]: Failed, module return: {'msg': 'value of action must be one of: append, insert, got: accept', 'failed': True, 'invocation': {'module_args': {'state': 'present', 'action': 'accept', 'jump': 'ACCEPT', 'chain': 'INPUT', 'protocol': 'tcp', 'source': '172.25.161.50', 'ctstate': ['NEW'], 'ip_version': 'ipv4', 'comment': '301 allow zabbix ipv4', 'destination_port': '10050', 'table': 'filter', 'match': [], 'syn': 'ignore', 'flush': False}}, 'warnings': ["The value 10050 (type int) in a string field was converted to '10050' (type string). If this does not look like what you expect, quote the entire value to ensure it does not change."], '_ansible_parsed': True} [ERROR]: Failed, return data: {'stdout': None, 'stderr': None, 'msg': 'value of action must be one of: append, insert, got: accept', 'cmd': None, 'rc': 0, 'failed': True} 2022-07-21 01:27:33.335477 | 48d539a1-1679-1e80-25fd-000000005aa1 | TASK | Manage firewall rules 2022-07-21 01:27:33.351515 | 48d539a1-1679-1e80-25fd-000000005542 | FATAL | Manage firewall rules | overcloud-controller-0 | error={"changed": false, "cmd": null, "msg": "value of action must be one of: append, insert, got: accept", "rc": 0, "stderr": null, "stdout": null} When i tried the following link: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15… <https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15…> my script is running fine but rules are not updated in iptables for zabbix. Can you please suggest a correct approach to open port 10050 in tripleo? With regards, Swogat Pradhan

2 1

[nova] Review guide for PCI tracking for Placement patches
by Balazs Gibizer 09 Aug '22

09 Aug '22

Hi Nova, The first batch of patches are up for review for the PCI tracking for Placement feature. These mostly covers two aspects of the spec[1]: 1) renaming [pci]passthrough_whitelist to [pci]device_spec 2) pci inventory reporting to placement, excluding existing PCI allocation healing in placement This covers the first 4 sub chapters of Proposed Change chapter of the spec[1] up until "PCI alias configuration". I noted intentional deviations from the spec in the spec review [2] and I will push a follow up to the spec at some point fixing those. I tried to do it in small steps hence the long list of commits[3]: #2) pci inventory reporting to placement, excluding existing PCI allocation healing in placement 5827d56310 Stop if tracking is disable after it was enabled before a4b5788858 Support [pci]device_spec reconfiguration 10642c787a Reject devname based device_spec config b0ad05fb69 Ignore PCI devs with physical_network tag f5a34ee441 Reject mixed VF rc and trait config c60b26014f Reject PCI dependent device config 5cf7325221 Extend device_spec with resource_class and traits eff0df6a98 Basics for PCI Placement reporting #1) renaming [pci]passthrough_whitelist to [pci]device_spec adfe34080a Rename whitelist in tests ea955a0c15 Rename exception.PciConfigInvalidWhitelist to PciConfigInvalidSpec 55770e4c14 Rename [pci]passthrough_whitelist to device_spec There is a side track branching out from "adfe34080a Rename whitelist in tests" to clean up the device spec handling[4]: 514500b5a4 Move __str__ to the PciAddressSpec base class 3a6198c8fb Fix type annotation of pci.Whitelist class f70adbb613 Remove unused PF checking from get_function_by_ifname b7eef53b1d Clean up mapping input to address spec types 93bbd67101 Poison /sys access via various calls in test 467ef91a86 Remove dead code from PhysicalPciAddress 233212d30f Fix PciAddressSpec descendants to call super.__init__ ad5bd46f46 Unparent PciDeviceSpec from PciAddressSpec cef0d2de4c Extra tests for remote managed dev spec 2fa2825afb Add more test coverage for devname base dev spec adfe34080a Rename whitelist in tests This is not a mandatory part of the feature but I think they improve the code in hand and even fixing some small bugs. I will continue with adding allocation healing for existing PCI allocations. Any feedback is highly appreciated. Cheers, gibi [1] https://specs.openstack.org/openstack/nova-specs/specs/zed/approved/pci-dev… [2] https://review.opendev.org/c/openstack/nova-specs/+/791047 [3] https://review.opendev.org/q/topic:bp/pci-device-tracking-in-placement [4] https://review.opendev.org/q/topic:bp/pci-device-spec-cleanup

1 2