Bug 1297330

Summary: [RFE][UX] provide a user-friendly error message when the nic names aren't found on the nodes
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: openstack-tripleo-validationsAssignee: Florian Fuchs <flfuchs>
Status: CLOSED WONTFIX QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: achernet, apannu, beth.white, flfuchs, jbuchta, jjoyce, jrist, jschluet, mburns, mcornea, morazi, rhel-osp-director-maint, sclewis, slinaber, tvignaud, ukalifon
Target Milestone: Upstream M2Keywords: FutureFeature
Target Release: ---Flags: jbuchta: needinfo? (flfuchs)
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-14 11:56:45 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:
Bug Depends On:    
Bug Blocks: 1442136    

Description Udi Kalifon 2016-01-11 08:55:12 UTC 
Description of problem:
I tried to deploy with network isolation using the same templates I used for 7.1, and the deployment hung for 4 hours and then timed out. There were no clues in any of the logs as to the simple explanation for the problem, and I wasn't able to guess it myself: I used nic names like ethX and it's now enpXXX...


How reproducible:
100%


Steps to Reproduce:
1. Deploy with templates that don't match the nic namings used by your OS


Actual results:
Deployment fails, no clues provided to the user as to where to look for the problem.


Expected results:
A clear error message which says exactly what the problem is, that any user can understand
Comment 3 Mike Burns 2016-04-07 21:03:37 UTC 
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Comment 5 Jason E. Rist 2016-09-29 11:18:11 UTC 
This needs more info: how was this error done? CLI? UI?  what tool was used to deploy?
Comment 6 Udi Kalifon 2016-09-29 11:30:07 UTC 
This error occurs when you configure the networking in your plans, and you use the wrong naming method for the NICs. For example you call them ethX instead of enoX or enp...
Comment 7 Ola Pavlenko 2016-10-05 16:59:27 UTC 
Blueprint is here : https://blueprints.launchpad.net/tripleo/+spec/nic-names-validations
Comment 8 Ola Pavlenko 2016-12-12 14:36:25 UTC 
Possible candidate for M-3