Wrong type for direct_mandatory_flag opt

Bug #1909036 reported by Ben Nemec on 2020-12-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.messaging
High
Ben Nemec

Bug Description

As reported in https://bugs.launchpad.net/oslo.messaging/+bug/1905965:

"""
When i am trying to add following value in /etc/senlin/senlin.conf

[DEFAULT]
transport_url = rabbit://senlin:94d7aecb853145779db8f1dcb@10.65.6.176:5671//senlin?ssl=1

[oslo_messaging_rabbit]
ssl = True
direct_mandatory_flag = False

I am getting error in logs

Dec 22 14:43:26 os-lab-infra-1-senlin-container-16f24bbe senlin-conductor[8591]: 2020-12-22 14:43:25.999 8591 ERROR oslo_service.service [-] Error starting t
hread.: oslo_config.cfg.ConfigFileValueError: Value for option direct_mandatory_flag from LocationInfo(location=<Locations.user: (4, True)>, detail='/etc/senlin/senlin.conf') is not
 valid: invalid literal for int() with base 10: 'False'
"""

For some reason direct_mandatory_flag is an IntOpt with a default of True. Looking at where it is used, I believe the boolean type is correct.

This issue was fixed in the openstack/oslo.messaging 12.6.1 release.

Satish Patel (satish-txt) wrote :

>> This issue was fixed in the openstack/oslo.messaging 12.6.1 release.

What was the fix?

Satish Patel (satish-txt) wrote :

Reason i am asking because i am still seeing error like following in logs

 Feb 19 23:11:56 ostack-phx-api-1-1-senlin-container-314663f9 senlin-wsgi-api[81]: 2021-02-19 23:11:56.587 81 ERROR oslo.messaging._drivers.impl_rabbit [-] [2f14560c-4a21-4cea-b779-731d7aea2cce] AMQP server on 10.65.7.69:5671 is unreachable: <RecoverableConnectionError: unknown error>. Trying again in 1 seconds.: amqp.exceptions.RecoverableConnectionError: <RecoverableConnectionError: unknown error>

$ openstack cluster list
HttpException: 500: Server Error for url: http://10.65.0.16:8778/v1/clusters?global_project=False, Timed out waiting for a reply to message ID 696d17d4615543389e6ada47030e3304

This issue was fixed in the openstack/oslo.messaging 10.2.3 release.

This issue was fixed in the openstack/oslo.messaging 12.1.6 release.

This issue was fixed in the openstack/oslo.messaging 12.5.2 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers