Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 2259076

Summary:	python3-tap-as-a-service: taas_plugin.ini is ignored by neutron-server
Product:	[Community] RDO	Reporter:	kajinamit
Component:	distribution	Assignee:	Alfredo Moralejo <amoralej>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	trunk
Target Milestone:	---
Target Release:	trunk
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-01-24 16:56:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description kajinamit 2024-01-19 03:42:08 UTC

Description of problem:

The python3-tap-as-a-service package installs the taas_plugin.ini file in /etc/neutron and create a symbolic link to the file in /usr/share/neutron/server .
However the link is named `taas_plugin.ini` and neutron-server ignores the file because it only loads "*.conf".

We should rename the link so that it's picked up by neutron-server.


Version-Release number of selected component (if applicable):
openstack-neutron-23.1.0-0.20240111194413.a89b5e5.el9.noarch
python3-tap-as-a-service-12.1.0-0.20231121221337.0d5d106.el9.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install python3-tap-as-a-service
2. Enable the TaaS plugin
3. Start neutron-server

Actual results:
neutron-server fails to start because it does not load service_provide option in taas_plugin.ini

Expected results:
neutron-server loads taas_plugin.ini and starts without errors

Additional info:
This was initially found in the attempt to enable taas in [1]

[1] https://review.opendev.org/c/openstack/puppet-openstack-integration/+/906018

Comment 1 kajinamit 2024-01-24 16:53:42 UTC

I confirmed that the issue was fixed in  python3-tap-as-a-service-12.1.0-0.20240119074325.7c3912b.el9.noarch . I may later attempt backports but I'm ok to close this now.

Comment 2 Alfredo Moralejo 2024-01-24 16:56:39 UTC

Thanks for reporting and fix it!