Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1603401

Summary: Uninformative error while trying to deploy overcloud - yaml validation
Product: Red Hat OpenStack Reporter: Udi Shkalim <ushkalim>
Component: rhosp-directorAssignee: Ryan Brady <rbrady>
Status: CLOSED DUPLICATE QA Contact: Gurenko Alex <agurenko>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: dbecker, dpeacock, dprince, laszlo.budai, mburns, morazi, rbrady, sasha, sbaker, therve, ushkalim
Target Milestone: ---Keywords: Triaged, UserExperience, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-27 08:48:44 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:

Description Udi Shkalim 2018-07-19 14:43:33 UTC
Description of problem:

While trying to deploy overcloud I got the following error:
Action tripleo.parameters.update execution failed: Error validating environment for plan overcloud: ERROR: Internal Error


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

How reproducible:
100%

Steps to Reproduce:
1. Have invalid yaml file in the nic-config section
2.
3.

Actual results:
Error message saying Internal Error

Expected results:
Error should be more informative on why and when it failed.

Additional info:

Comment 1 Dan Prince 2018-07-20 18:46:16 UTC
Ryan Brady: This looks related to the parameters update action. Is this something you are still familiar with?

Comment 2 Ryan Brady 2018-08-20 13:12:32 UTC
Yes, I am familiar with the referenced action.  Can someone attach the log file to this BZ so it can be determined how far into the action it got before failure?  
Both this action and it's parent both call into heat, so this might be an issue to improve the error that is being thrown there.

Comment 3 Budai Laszlo 2018-08-24 01:31:28 UTC
I have the same issue. What log files should I provide?

Comment 4 Ryan Brady 2018-09-04 14:39:29 UTC
The undercloud log files.  Most importantly the log files associated with mistral and heat services.

Comment 5 David Peacock 2018-10-30 13:41:16 UTC
I have tried and failed to reproduce this on upstream latest.

@Udi, please would you provide your broken nic-config.yaml as an example for me to test against?

Thank you.
David

Comment 6 Udi Shkalim 2018-10-31 17:39:03 UTC
I do not have the files.
I'll try to reproduce and update.

Comment 7 Thomas Hervé 2018-11-27 08:48:44 UTC

*** This bug has been marked as a duplicate of bug 1601673 ***