Bug 1409097 – OSPD10 + SR-IOV deployment fails while using nic IDs in the compute yaml.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1409097 - OSPD10 + SR-IOV deployment fails while using nic IDs in the compute yaml.

Summary:	OSPD10 + SR-IOV deployment fails while using nic IDs in the compute yaml.

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	os-net-config (Show other bugs)
Sub Component:
Version:	10.0 (Newton)
Hardware:	All Linux

Priority	unspecified Severity high
Target Milestone:	Upstream M3
Target Release:	11.0 (Ocata)
Assigned To:	Saravanan KR
QA Contact:	Yariv
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:	1235009 1416070
	Show dependency tree / graph

Reported:	2016-12-29 07:59 EST by Ziv
Modified:	2017-05-17 15:53 EDT (History)
CC List:	17 users (show)

See Also:
Fixed In Version:	os-net-config-6.0.0-3.el7ost
Doc Type:	Known Issue
Doc Text:	Currently, the Red Hat OpenStack Platform director 10 with SRIOV overcloud deployment fails when using the NIC IDs (for example, nic1, nic2, nic3 and so on) in the compute.yaml file. As a workaround, you need to use NIC names (for example, ens1f0, ens1f1, ens2f0, and so on) instead of the NIC IDs to ensure the overcloud deployment completes successfully.
Story Points:	---
Clone Of:
Clones:	1416070 (view as bug list)
Environment:
Last Closed:	2017-05-17 15:53:41 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
/var/log/messages (1.75 MB, text/plain) 2016-12-29 07:59 EST, Ziv	no flags	Details
image (40.46 KB, image/png) 2016-12-29 08:01 EST, Ziv	no flags	Details
yaml files (4.54 KB, application/x-gzip) 2016-12-29 08:04 EST, Ziv	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Launchpad	1653097	None	None	None	2016-12-30 00:00 EST
OpenStack gerrit	415682	None	None	None	2017-01-24 09:04 EST
Red Hat Product Errata	RHEA-2017:1245	normal	SHIPPED_LIVE	Red Hat OpenStack Platform 11.0 Bug Fix and Enhancement Advisory	2017-05-17 19:01:50 EDT

Groups: None (edit)

Description Ziv 2016-12-29 07:59:37 EST

Created attachment 1235874 [details]
/var/log/messages

Description of problem:

As a part of OSPD10 SR-IOV deploymnet, I have configured the compute yaml file (please find it attached) to use nic id's (nic1, nic2, nic3, etc).

The deployment got stuck on step 5 and eventually it fails due to a timeout.
I have established a connection to one of the computes, and found out in "/var/log/messages" that the nics order isn't correct as it should, it have been changed after the creation of the VF's. nic4 should be mapped to ens2f0 and nic5 should be mapped to ens2f1 (see attached image).

I have tried to use nic names (ens1f0, ens1f1, ens2f0, etc) instead of nic id's, and in this case the overcloud deployment finished successfully.  



Version-Release number of selected component (if applicable):
OSPD10 - 1 controller, two computes with SR-IOV enabled.


How reproducible:
Always

Steps to Reproduce:
1. deploy ospd with attached yamls.


Actual results:
deployment fails due to timeout

Expected results:
overcloud deploy should finish successfully


Additional info:
Compute hardware, HPE ProLiant DL380 Gen9 server, HPE Ethernet 10Gb 2-port 560SFP sr-iov nic.

Comment 1 Ziv 2016-12-29 08:01 EST

Created attachment 1235875 [details]
image

Comment 2 Ziv 2016-12-29 08:04 EST

Created attachment 1235876 [details]
yaml files

Comment 3 Saravanan KR 2017-01-18 02:25:06 EST

Review - https://review.openstack.org/#/c/415682/

Comment 7 Ziv 2017-05-17 05:48:13 EDT

Hi,

It was verified.

Thanks,
Ziv

Comment 8 errata-xmlrpc 2017-05-17 15:53:41 EDT

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:1245

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