Bug 1472296 - Fail to deploy with OVN (environments/neutron-ml2-ovn-ha.yaml)
Summary: Fail to deploy with OVN (environments/neutron-ml2-ovn-ha.yaml)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: beta
: 12.0 (Pike)
Assignee: Numan Siddique
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On: 1472729
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-18 11:55 UTC by Arie Bregman
Modified: 2018-02-05 19:10 UTC (History)
7 users (show)

Fixed In Version: openstack-tripleo-heat-templates-7.0.3-0.20171024200823.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 21:42:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Arie Bregman 2017-07-18 11:55:55 UTC
Description of problem:

We added a new job in CI to deploy Director OSP 12 with OVN by providing environments/neutron-ml2-ovn-ha.yaml and it fails

Version-Release number of selected component (if applicable): OSP 12


How reproducible: 100%


Steps to Reproduce:
1. Deploy Director HA OSP 12 and pass this environment file to 'overcloud deploy': environments/neutron-ml2-ovn-ha.yaml

OR 

1. Go to OVN Jenkins Job (like will be provided in next comment) and press on build

Actual results: 

1:47:12 overcloud.AllNodesDeploySteps.ControllerDeployment_Step3.0:
11:47:12   resource_type: OS::Heat::StructuredDeployment
11:47:12   physical_resource_id: 04f67261-7442-48ac-9761-a7bf98155fe0
11:47:12   status: CREATE_FAILED
11:47:12   status_reason: |
11:47:12     Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 6
11:47:12   deploy_stdout: |


Expected results: Overcloud deployed successfully

Comment 2 Numan Siddique 2017-07-19 12:35:34 UTC
This failure is most likely because of this - https://bugzilla.redhat.com/show_bug.cgi?id=1472729.

Is it possible to run the below command in one of the controllers and see if the file ovndb-servers is present in the below location.

$ls -l /usr/lib/ocf/resource.d/ovn/ovndb-servers

If this file is not present, then that's the reason why it is failing. The openvswitch-ovn-common package is expected to create this file and looks like it is not.

Comment 3 Numan Siddique 2017-07-19 13:29:02 UTC
For successful OVN HA deployment, OVS 2.7.1+ is required and the BZ [1] -  addressed.

From the logs I see that OVS version used is 2.7.0 and I see the below error messages in /var/log/puppet/heat-debug.log

*********************8
2017-07-18 11:41:51 +0000 Puppet (debug): try 1/10: /usr/sbin/pcs -f /var/lib/pacemaker/cib/puppet-cib-backup20170718-35672-157szde resource create ovndb_servers ocf:ovn:ovndb-servers master_ip=172.17.1.16 nb_master_port=6641 sb_master_port=6642 manage_northd=yes meta notify=true op start timeout=200s stop timeout=200s --master --disabled
2017-07-18 11:41:51 +0000 Puppet (debug): Error: Error: Agent 'ocf:ovn:ovndb-servers' is not installed or does not provide valid metadata: Metadata query for ocf:ovn:ovndb-servers failed: -5, use --force to override
Warning: flag '--master' is deprecated, use keyword 'master' instead (see the usage)
**************************

Please see the BZ [1] for more details.


[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1472729

Comment 4 Numan Siddique 2017-08-01 12:45:18 UTC
Assigned it back to Assaf. The OVS 2.7.2 packages should come from the ovs team.

Comment 15 errata-xmlrpc 2017-12-13 21:42:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462


Note You need to log in before you can comment on or make changes to this bug.