Bug 1677230

Summary: Error validating plan with custom service ERROR: The Resource Type (OS::TripleO::Services::Dummy) could not be found.
Product: Red Hat OpenStack Reporter: Eduard Barrera <ebarrera>
Component: openstack-tripleo-commonAssignee: Rabi Mishra <ramishra>
Status: CLOSED ERRATA QA Contact: Arik Chernetsky <achernet>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: amcleod, bartosz.kupidura, dbecker, ebarrera, jappleii, jmelvin, jslagle, madgupta, mburns, morazi, pmannidi, pmorey, ramishra, slinaber
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-common-8.6.6-18.el7ost python-tripleoclient-9.2.6-9.el7ost Doc Type: Bug Fix
Doc Text:
Previously, adding new services to roles data with user environment resource mappings failed when creating or updating plans. With this update, the stack and template validation is bypassed when creating and updating plans, and adding new services no longer fails.
Story Points: ---
Clone Of:
: 1721282 (view as bug list) Environment:
Last Closed: 2019-04-30 17:27:36 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:
Bug Depends On:    
Bug Blocks: 1721282    

Description Eduard Barrera 2019-02-14 10:19:45 UTC
Description of problem:

We are finding problems when createing a custom service, this is working perfectly with OSP12. I'm testing OSP13 and I'm facing this issue.

$ openstack overcloud deploy --templates -r roles_data_with_dummy.yaml -e dummy.yaml 

Started Mistral Workflow tripleo.validations.v1.check_pre_deployment_validations. Execution ID: bd47c9b7-a7f2-4cb3-bd42-eb391b44a192
Waiting for messages on queue 'tripleo' with no timeout.
Creating Swift container to store the plan
Creating plan from template files in: /tmp/tripleoclient-APWnHt/tripleo-heat-templates
Started Mistral Workflow tripleo.plan_management.v1.create_deployment_plan. Execution ID: 60a55b80-9f06-420c-a26a-002699271c78
Error validating environment for plan overcloud: ERROR: The Resource Type (OS::TripleO::Services::Dummy) could not be found.
Exception creating plan: Error validating environment for plan overcloud: ERROR: The Resource Type (OS::TripleO::Services::Dummy) could not be found.


Similar to:

 https://bugzilla.redhat.com/show_bug.cgi?id=1577536


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


How reproducible:


Steps to Reproduce:

 -> install OSP13 director
 -> import baremetal servers
 -> create template_test directory 
 -> add dummy service to custom role
 -> deploy # openstack overcloud deploy --templates -r roles_data_with_dummy.yaml -e dummy.yaml 


Actual results:

Started Mistral Workflow tripleo.validations.v1.check_pre_deployment_validations. Execution ID: bd47c9b7-a7f2-4cb3-bd42-eb391b44a192
Waiting for messages on queue 'tripleo' with no timeout.
Creating Swift container to store the plan
Creating plan from template files in: /tmp/tripleoclient-APWnHt/tripleo-heat-templates
Started Mistral Workflow tripleo.plan_management.v1.create_deployment_plan. Execution ID: 60a55b80-9f06-420c-a26a-002699271c78
Error validating environment for plan overcloud: ERROR: The Resource Type (OS::TripleO::Services::Dummy) could not be found.
Exception creating plan: Error validating environment for plan overcloud: ERROR: The Resource Type (OS::TripleO::Services::Dummy) could not be found.

Expected results:
no errors

Additional info:

The same procedure works correctly on OSP12
Similar to [1] but our code is already patched

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

Comment 3 Cédric Jeanneret 2019-02-18 14:30:07 UTC
Hello Eduard,

Care to provide the version for, at least, python-tripleoclient ?
apparently it should have a patch[1] - at least it's what seem to solve the issue you linked.

Cheers,

C.

[1] https://review.openstack.org/#/c/564692/

Comment 13 Rabi Mishra 2019-03-11 05:14:41 UTC
Hi Eduard,

Once it's merged downstream, we can do a build for hotfix.

Comment 15 Alex Schultz 2019-03-12 19:21:40 UTC
*** Bug 1593616 has been marked as a duplicate of this bug. ***

Comment 36 errata-xmlrpc 2019-04-30 17:27:36 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/RHBA-2019:0939