Bug 1297330 - [RFE][UX] provide a user-friendly error message when the nic names aren't found on the nodes
Summary: [RFE][UX] provide a user-friendly error message when the nic names aren't fou...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-validations
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Upstream M2
: ---
Assignee: Florian Fuchs
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 1442136
TreeView+ depends on / blocked
 
Reported: 2016-01-11 08:55 UTC by Udi Kalifon
Modified: 2023-09-14 03:20 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-14 11:56:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-28581 0 None None None 2023-09-14 03:16:43 UTC

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

Comment 20 Red Hat Bugzilla 2023-09-14 03:15:55 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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