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

Bug 1726195

Summary: Neutron command throws errors "503 Service Unavailable" with contrail+TLS everywhere
Product: Red Hat OpenStack Reporter: Shailesh Chhabdiya <schhabdi>
Component: openstack-neutronAssignee: Assaf Muller <amuller>
Status: CLOSED DUPLICATE QA Contact: Roee Agiman <ragiman>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: amuller, bdobreli, chrisw, ipetrova, scohen
Target Milestone: ---Keywords: ZStream
Target Release: ---   
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: 2019-07-03 10:45: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 Shailesh Chhabdiya 2019-07-02 10:19:05 UTC 
Description of problem:

Cannot run any neutron cli and glance cli with contrail and  TLS everywhere enabled.

Whenever we hit the command we get following error.

~~~
(overcloud) [stack@director-ctl ~]$ openstack image create --file /home/stack/images/overcloud-full.qcow2 --disk-format qcow2 dummy_image
503 Service Unavailable: No server is available to handle this request. (HTTP 503)
(overcloud) [stack@director-ctl ~]$ neutron agent-list
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
<html><body><h1>503 Service Unavailable</h1>
No server is available to handle this request.
</body></html>

~~~


Version-Release number of selected component (if applicable):
Red Hat OpenStack Platform 13


Actual results:
CLi is not working

Expected results:
CLI should work.

Additional info:
Without Contrail it works fine.
Also other than neutron and glance cli other cli works fine
Comment 11 Irina Petrova 2019-07-03 10:45:39 UTC 

*** This bug has been marked as a duplicate of bug 1703460 ***