Bug 1273680
| Summary: | HA overcloud with network isolation deployment fails | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] RDO | Reporter: | Alexander Chuzhoy <sasha> | ||||||||||
| Component: | rdo-manager | Assignee: | John Trowbridge <jtrowbri> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Shai Revivo <srevivo> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | Liberty | CC: | apevec, chris.brown, ihrachys, jtrowbri, mburns, mcornea, sasha | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | Liberty | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2017-06-18 06:24:14 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: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Alexander Chuzhoy
2015-10-21 01:35:16 UTC
It can be eg. neutron-server failing to reply, or AMQP broker failing to start, or anything in between. Without proper logs provided, it's hard to say. /var/log/messages snippets are NOT enough to make clear call. Created attachment 1085060 [details]
neutron server log
Attaching the neutron server.log on the first controller on Sasha's environment.
Neutron related packages:
python-neutron-lbaas-7.0.0-1.el7.noarch
openstack-neutron-openvswitch-7.0.0-2.el7.noarch
python-neutron-7.0.0-2.el7.noarch
openstack-neutron-7.0.0-2.el7.noarch
python-neutronclient-3.1.0-1.el7.noarch
openstack-neutron-common-7.0.0-2.el7.noarch
openstack-neutron-lbaas-7.0.0-1.el7.noarch
openstack-neutron-ml2-7.0.0-2.el7.noarch
openstack-neutron-metering-agent-7.0.0-2.el7.noarch
OK, logs suggest configuration issue for server. Please show what's core_plugin. Also, please attach all logs, not a single snippet. I don't see debug logs that could show which configuration the server sees. Overall, let's try to avoid the churn and provide logs and configs in advance without waiting for devs to request them. Was cisco networking plugin installed? Last time we saw ValueError: Empty module name when neutron is loading plugins was when cisco plugin from Kilo was installed (it has duplicate ml2 entry point confusing stevedore) Cisco plugin is NOT Liberty compatible yet and most not be installed. Created attachment 1085078 [details]
Neutron configuration files
Attaching the neutron configuration files in /etc/neutron.
What Ihar said, also rpm -qa or even full sosreport (which might too big for BZ attachment, so upload somewhere e.g. personal fedorapeople.org page) Created attachment 1085079 [details]
Neutron log files
Attaching the Neutron log files in /var/log/neutron
[root@overcloud-controller-0 ~]# rpm -qa | grep cisco python-networking-cisco-2015.1.0-1.el7.noarch fence-agents-cisco-ucs-4.0.11-13.el7_1.2.x86_64 fence-agents-cisco-mds-4.0.11-13.el7_1.2.x86_64 OK, I see cisco config files in the config tarball. I believe that's the issue Alan mentioned. Created attachment 1085084 [details]
sosreport
Attaching the sosreport.
overcloud controller has kilo repo enabled which should not be the case! I'm also not sure where is centos-cloud-rdo coming from, that repo is not defined in either cloud sig or rdo-release RPM: base/7/x86_64 CentOS-7 - Base centos-cloud-rdo CentOS Cloud RDO extras/7/x86_64 CentOS-7 - Extras openstack-kilo OpenStack Kilo Repository updates/7/x86_64 CentOS-7 - Updates Please rebuild images using only steps from https://etherpad.openstack.org/p/RDO-Manager_liberty: yum install -y http://rdoproject.org/repos/openstack-liberty/rdo-release-liberty.rpm export NODE_DIST=centos7 export RDO_RELEASE='liberty' openstack overcloud image build --all This is at least related, I would probably say duplicate actually of https://bugzilla.redhat.com/show_bug.cgi?id=1271200 My last comment from the above BZ for completeness: This is fixed in the liberty-testing repo http://buildlogs.centos.org/centos/7/cloud/x86_64/openstack-liberty/ with python-tripleoclient-0.0.11-3 However, I am going to leave it assigned until the fix is also in delorean. In order to use the release repo when building images it is now needed to: `export RDO_RELEASE=<release>` so for liberty: `export RDO_RELEASE='liberty'` by default it will use kilo. This was fixed a while back so can be closed. |