December 2020 - openstack-discuss

ssh authentication error with Gerrit
by Pete Zaitcev 26 Dec '20

26 Dec '20

Hello: Does anyone here happen to know how to deal with something like this: ........... debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ssh-rsa SHA256:RXNl/GKyDaKiIQ93BoDvrNSKUPFvA1PNeAO9QiirYZU debug1: Host '[review.opendev.org]:29418' is known and matches the RSA host key. debug1: Found key in /q/zaitcev/.ssh/known_hosts:133 debug1: rekey out after 4294967296 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 4294967296 blocks debug1: Will attempt key: /q/zaitcev/.ssh/id_rsa_ostk2014 RSA SHA256:nz5*** explicit agent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: /q/zaitcev/.ssh/id_rsa_ostk2014 RSA SHA256:nz5*** explicit agent debug1: send_pubkey_test: no mutual signature algorithm debug1: No more authentication methods to try. zaitcev(a)review.opendev.org: Permission denied (publickey). [zaitcev@suzdal swift-dark]$ I guess that ssh client in Fedora 33 has a cipher suite that has no intersection with the ssh server at review.opendev.org. But I do not understand what the server is offering, so I do not know what I need to enable. Thanks in advance, -- Pete

2 2

[qa][tempest-plugins][release][stable] Releasing stein-em tag for Tempest plugins
by Ghanshyam Mann 26 Dec '20

26 Dec '20

Hello Everyone, As the stable/stein branch is in Extended Maintenance now[1], Tempest has dropped the support of stable/stein[2]. Tempest and its plugins are branchless which means the master version of Tempest and its plugins are used to test the supported stable branches. Once the stable branch is moved to EM state then, Tempest and its plugins compatible tag needs to be released so that we can keep testing the EM stable branches with this tag once the master Tempest and its plugins are not compatible[3]. This tag can be used as the latest compatible version of Tempest and its plugins for testing the stable/stein in upstream as well as production cloud testing. I have proposed all release patches: - https://review.opendev.org/q/topic:%22tempest-plugin-stein-em%22+(status:op… [1] https://releases.openstack.org/stein/index.html [2] https://review.opendev.org/c/openstack/tempest/+/766770 [3] https://docs.openstack.org/tempest/latest/stable_branch_support_policy.html -gmann

1 0

grouping resources on specific set of nodes
by Volodymyr Litovka 26 Dec '20

26 Dec '20

Hi colleagues, I can't realize how to do the simple-looking thing: there are few locations with small amount of compute/storage/network resources (like small branches with 3 physical servers for both compute, storage and network roles) and I want to see all these locations as single cloud and manage them centrally using single "controller cluster", while localizing resource usage to the specific location. _Kind of_ assign specific project to location "A" and, thus, all resources (VMs, networks, storage resources, ...) in this project will be allocated from nodes, physically located in location "A". Are there any ways to implement this kind of behavior in Openstack? Thank you. -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison

1 0

New nova compute nodes not correctly adding into service
by Grant Morley 25 Dec '20

25 Dec '20

Hi All, I was wondering if anyone could point me in the right direction with an issue we are having adding in new compute nodes to our platform. We have been trying to add a few new compute nodes to increase our capacity and upon configuring them with OSA and them appearing to be in service we have noticed that no new instances are provisioning onto them. We did a test by disabling all compute nodes except for the new ones and an instance launch failed with "No valid compute hosts were found" We have enabled debug mode on Nova and also looked at the nova-api containers ( scheduler, compute etc ) and it appears there is not even an attempt to try and launch an instance on the new hosts from what we can see. The only thing we have noticed on the newly added hosts is that the "privsep-helper" doesn't appear to be started whereas on a working node it is running. We have not changed the software versions of OpenStack or OSA, we are running Queens. The newly added compute node is reporting itself back fine from what we can see: Total usable vcpus: 72, total allocated vcpus: 0 _report_final_resource_view /openstack/venvs/nova-17.1.2/lib/python2.7/site-packages/nova/compute/resource_tracker.py:827 2020-12-24 16:26:32.895 6491 INFO nova.compute.resource_tracker [req-6c58a97e-b7cb-4987-a219-da5b1ce156f8 - - - - -] Final resource view: name=compute-27.openstack.local phys_ram=257826MB used_ram=2048MB phys_disk=30166GB used_disk=0GB total_vcpus=72 used_vcpus=0 pci_stats=[] 2020-12-24 16:26:33.022 6491 DEBUG nova.compute.resource_tracker [req-6c58a97e-b7cb-4987-a219-da5b1ce156f8 - - - - -] Compute_service record updated for compute-27:compute-27.openstack.local _update_available_resource /openstack/venvs/nova-17.1.2/lib/python2.7/site-packages/nova/compute/resource_tracker.py:767 2020-12-24 16:26:33.023 6491 DEBUG oslo_concurrency.lockutils [req-6c58a97e-b7cb-4987-a219-da5b1ce156f8 - - - - -] Lock "compute_resources" released by "nova.compute.resource_tracker._update_available_resource" :: held 0.334s inner /openstack/venvs/nova-17.1.2/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:285 2020-12-24 16:26:35.001 6491 DEBUG oslo_service.periodic_task [req-6c58a97e-b7cb-4987-a219-da5b1ce156f8 - - - - -] Running periodic task ComputeManager._poll_rebooting_instances run_periodic_tasks /openstack/venvs/nova-17.1.2/lib/python2.7/site-packages/oslo_service/periodic_task.py:215 Does anyone know of any other logs we can check / enable that might lead us in the right direction to figure out why the new hosts are not adding in? Any help would be greatly appreciated as we are a bit stumped at the moment. Many thanks, -- Grant Morley Site Reliability Engineer, Civo Ltd Unit H-K, Gateway 1000, Whittle Way Stevenage, Herts, SG1 2FP, UK Visit us at www.civo.com <https://www.civo.com/> Signup for an account now > <https://www.civo.com/signup>

3 2

[cinder] patches for lower-constraints
by Brian Rosmaita 23 Dec '20

23 Dec '20

As discussed at today's cinder meeting, there are patches available that address the lower constraints problems arising from the upgraded pip dependency resolver for most cinder deliverables. Except for master, I've tried to keep the changes minimal. One possibly controversial change has been to add indirect dependencies to test-requirements.txt in a few cases where the version range was so wide that the resolver was taking a very long time to figure out a satisfactory resolution. An example of this is the cinder stable/train patch: https://review.opendev.org/c/openstack/cinder/+/767954 I'm not sure when these patches will be merged, but you can always add the appropriate one as a dependency in gerrit to get the check jobs to pass on your patch. You can find them by using the gerrit hashtag 'fix-l-c': https://review.opendev.org/q/hashtag:fix-l-c Apparently only the owner of a review can add a hashtag, so os-brick/master (merged, owned by lpetrut) and the patches for the non-releaseable stable branches that e0ne is working on aren't in the list yet.

1 0

[cinder] limited review bandwidth until 4 January 2021
by Brian Rosmaita 23 Dec '20

23 Dec '20

Just a reminder that most cinder cores will not be active from tomorrow (24 December) through 4 January 2021. Happy holidays! brian

1 0

[cinder] meeting time change poll
by Brian Rosmaita 23 Dec '20

23 Dec '20

At today's meeting, Lucio proposed moving the cinder weekly meeting time. Please respond to this poll to assess some options before Tuesday 22 December at 1200 UTC. https://rosmaita.wufoo.com/forms/wallaby-cinder-meeting-time-poll/ There's a free-form field on the form so you can propose other alternatives. We aren't considering changing the day of the meeting (Wednesday) at this time, but that's a possibility if it would encourage more attendance. NOTE: next week's meeting, Wednesday 23 December, will be held at the usual time of 1400 UTC. cheers, brian

1 1

[tc] weekly meeting summary
by Mohammed Naser 23 Dec '20

23 Dec '20

Hi everyone, Here's a summary of what happened in our TC weekly meeting last Thursday, Dec 17th. # ATTENDEES (LINES SAID) 1. mnaser (82) 2. gmann (46) 3. diablo_rojo (25) 4. jungleboyj (18) 5. fungi (10) 6. belmoreira (6) 7. ricolin (4) # MEETING SUMMARY 1. Rollcall 2. Skipping the next meetings. Due to the upcoming holidays, we are skipping the next two meetings on Dec 24 and Dec 31st. Mnaser to send an email with details. 3. Follow up on past action items - mnaser send email to ML to find volunteers to help drive goal selection: email sent, and no one strongly opposed. mnaser will write a proposed goal for X about stabilization/cooldown. - gmann complete retirement of searchlight & qinling: DONE - diablo_rojo complete retirement of karbor: In progress, getting there. 4. Audit SIG list and chairs (diablo_rojo) - This list is out of date and a lot of chairs are not active anymore. If any SIG has completed their purpose then we move them to an advisory state, otherwise close. diablo_rojo reach out to SIGs/ML and start auditing states of SIGs 5. Annual report suggestions (diablo_rojo) - mnaser and diablo_rojo are working on the annual report for OpenStack, ideas are welcome. Once it's mostly written a draft will be sent out before submitting it. 6. X cycle goal selection start This item has to go with the action item above regarding the stabilization goal proposal. We'll remove this item from the agenda. 7. Audit and clean-up tags (gmann) - http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019505… gmann started ML on API tag and will see how many projects start and will continue on other tag audits in parallel. We'll remove sub-items in there in the meantime. gmann continue to audit tags + outreach to the community to apply for them 8. X cycle release name vote recording (gmann) - Votes are recorded in ML, mnaser will remove X cycle release name vote recording from the agenda. 9. CentOS 8 releases are discontinued / switch to CentOS 8 Stream (gmann/yoctozepto) - We have an action item to get the community to get together and the QA team is doing the right thing. We'll remove centos 8 topic from the upcoming agenda. 10. Open reviews - https://review.opendev.org/q/projects:openstack/governance+is:open - https://review.opendev.org/c/openstack/governance/+/759904 - https://review.opendev.org/c/openstack/governance/+/759904/7/resolutions/20… # ACTION ITEMS - mnaser send out email about skipping both upcoming meetings - mnaser write a proposed goal for X about stabilization/cooldown - diablo_rojo complete retirement of karbor - diablo_rojo reach out to SIGs/ML and start auditing states of SIGs - mnaser drop X cycle goal selection start from agenda - gmann continue to audit tags + outreach to the community to apply for them - mnaser drop X cycle release name vote recording - mnaser remove centos 8 topic from upcoming agenda To read the full logs of the meeting, please refer to http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-12-17-15.00.log.html -- Mohammed Naser VEXXHOST, Inc.

1 0

[tc] weekly meeting skip
by Mohammed Naser 23 Dec '20

23 Dec '20

Hi there, Due to the upcoming holidays, we are skipping the next TC meetings on Dec 24th and Dec 31st. We will resume with our regular schedule on Thursday, January 7th. Thank you & happy holidays! Regards Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

oslo message direct_mandatory_flag question
by Satish Patel 22 Dec '20

22 Dec '20

Folks, I am getting a very strange error from time to time on senlin logs and when it hits this error i can't do anything in senlin until i restart service. After googling i found this bug https://bugs.launchpad.net/oslo.messaging/+bug/1905965 It's pretty much related to my issue because I am running the latest victoria. Dec 22 13:56:44 os-lab-infra-1-senlin-container-16f24bbe senlin-wsgi-api[8188]: 2020-12-22 13:56:44.212 8188 ERROR oslo.messaging._drivers.impl_rabbit [-] [df314561-6415-4103-a1fd-14ab95182cfb] AMQP server on 10.65.6.176:5671 is unreachable: <RecoverableConnectionError: unknown error>. Trying again in 1 seconds.: amqp.exceptions.RecoverableConnectionError: <RecoverableConnectionError: unknown error> Dec 22 13:56:44 os-lab-infra-1-senlin-container-16f24bbe senlin-wsgi-api[8188]: 2020-12-22 13:56:44.220 8188 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: Server unexpectedly closed connection Dec 22 13:56:44 os-lab-infra-1-senlin-container-16f24bbe senlin-conductor[8250]: 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server [req-3c89475b-89fc-404b-8537-df7a587261d9 462618bed32745d2a9166bcc33fc117e f1502c79c70f4651be8ffc7b844b584f - - -] MessageUndeliverable error, source exception: Basic.return: (312) NO_ROUTE, routing_key: reply_54d93c43fe894ed18ce8092f4497306b, exchange: : : oslo_messaging.exceptions.MessageUndeliverable 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/oslo_messaging/rpc/server.py", line 184, in _process_incoming 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server message.reply(res) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 149, in reply 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server self._send_reply(conn, reply, failure) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 125, in _send_reply 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server conn.direct_send(self.reply_q, rpc_common.serialize_msg(msg)) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1320, in direct_send 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server self._ensure_publishing(self._publish_and_raises_on_missing_exchange, 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1202, in _ensure_publishing 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server self.ensure(method, retry=retry, error_callback=_error_callback) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/oslo_messaging/_drivers/impl_rabbit.py", line 826, in ensure 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server ret, channel = autoretry_method() 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/kombu/connection.py", line 525, in _ensured 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server return fun(*args, **kwargs) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/kombu/connection.py", line 601, in __call__ 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server return fun(*args, channel=channels[0], **kwargs), channels[0] 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/oslo_messaging/_drivers/impl_rabbit.py", line 815, in execute_method 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server method() 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1294, in _publish_and_raises_on_missing_exchange 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server self._publish(exchange, msg, routing_key=routing_key, 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1238, in _publish 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server self._producer.publish( 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/kombu/messaging.py", line 175, in publish 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server return _publish( 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/kombu/messaging.py", line 197, in _publish 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server return channel.basic_publish( 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/amqp/channel.py", line 1782, in basic_publish_confirm 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server self.wait([spec.Basic.Ack, spec.Basic.Nack], callback=confirm_handler) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/amqp/abstract_channel.py", line 86, in wait 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server self.connection.drain_events(timeout=timeout) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/amqp/connection.py", line 514, in drain_events 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server while not self.blocking_read(timeout): 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/amqp/connection.py", line 520, in blocking_read 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server return self.on_inbound_frame(frame) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/amqp/method_framing.py", line 77, in on_frame 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server callback(channel, msg.frame_method, msg.frame_args, msg) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/amqp/connection.py", line 526, in on_inbound_method 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server return self.channels[channel_id].dispatch_method( 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/amqp/abstract_channel.py", line 143, in dispatch_method 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server listener(*args) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/amqp/channel.py", line 2006, in _on_basic_return 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server callback(exc, exchange, routing_key, message) 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server File "/openstack/venvs/senlin-22.0.0.0b2.dev56/lib/python3.8/site-packages/oslo_messaging/_drivers/impl_rabbit.py", line 852, in on_return 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server raise exceptions.MessageUndeliverable(exception, exchange, routing_key, 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server oslo_messaging.exceptions.MessageUndeliverable 2020-12-22 13:56:44.461 8250 ERROR oslo_messaging.rpc.server Dec 22 13:56:45 os-lab-infra-1-senlin-container-16f24bbe senlin-wsgi-api[8188]: 2020-12-22 13:56:45.248 8188 INFO oslo.messaging._drivers.impl_rabbit [-] [df314561-6415-4103-a1fd-14ab95182cfb] Reconnected to AMQP server on 10.65.6.176:5671 via [amqp] client with port 44246. Dec 22 13:56:53 os-lab-infra-1-senlin-container-16f24bbe senlin-health-manager[8218]: 2020-12-22 13:56:53.954 8218 INFO senlin.engine.health_manager [req-c0118d24-9f32-47c8-926e-eb4b60f922cd 462618bed32745d2a9166bcc33fc117e f1502c79c70f4651be8ffc7b844b584f - - -] Health check passed for all nodes in cluster f51b3154-fb8e-43f2-b68b-03b091c1e0bf. Dec 22 13:57:23 os-lab-infra-1-senlin-container-16f24bbe senlin-health-manager[8218]: 2020-12-22 13:57:23.962 8218 INFO senlin.engine.health_manager [req-472f4403-fd66-422a-8a84-a0b0f51d94cc 462618bed32745d2a9166bcc33fc117e f1502c79c70f4651be8ffc7b844b584f - - -] Health check passed for all nodes in cluster f51b3154-fb8e-43f2-b68b-03b091c1e0bf. Dec 22 13:57:23 os-lab-infra-1-senlin-container-16f24bbe senlin-health-manager[8218]: 2020-12-22 13:57:23.963 8218 INFO senlin.engine.health_manager [req-a5ff1fe3-35e8-443b-b91a-aa1d78656569 462618bed32745d2a9166bcc33fc117e f1502c79c70f4651be8ffc7b844b584f - - -] Health check passed for all nodes in cluster f51b3154-fb8e-43f2-b68b-03b091c1e0bf. Dec 22 13:57:44 os-lab-infra-1-senlin-container-16f24bbe uwsgi[8188]: Tue Dec 22 13:57:44 2020 - uwsgi_response_writev_headers_and_body_do(): Connection reset by peer [core/writer.c line 306] during GET /v1/clusters?global_project=False (10.65.6.17) Dec 22 13:57:44 os-lab-infra-1-senlin-container-16f24bbe senlin-wsgi-api[8188]: 2020-12-22 13:57:44.448 8188 CRITICAL senlin-api [req-3c89475b-89fc-404b-8537-df7a587261d9 462618bed32745d2a9166bcc33fc117e f1502c79c70f4651be8ffc7b844b584f - - -] Unhandled error: OSError: write error 2020-12-22 13:57:44.448 8188 ERROR senlin-api OSError: write error 2020-12-22 13:57:44.448 8188 ERROR senlin-api Dec 22 13:57:53 os-lab-infra-1-senlin-container-16f24bbe senlin-health-manager[8218]: 2020-12-22 13:57:53.955 8218 INFO senlin.engine.health_manager [req-8a578e8e-438d-45c1-b81d-c6f3aed5fc81 462618bed32745d2a9166bcc33fc117e f1502c79c70f4651be8ffc7b844b584f - - -] Health check passed for all nodes in cluster f51b3154-fb8e-43f2-b68b-03b091c1e0bf. As per advice i have tired to add following snippet to fix this issue [DEFAULT] transport_url = rabbit://senlin:94d7aecb853145779db8f1dcb@10.65.6.176:5671//senlin?ssl=1 [oslo_messaging_rabbit] ssl = True direct_mandatory_flag = False But i got error when trying to set direct_mandatory_flag option 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' Any idea what is going on here?

2 2