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-common | Assignee: | 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
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/ Hi Eduard, Once it's merged downstream, we can do a build for hotfix. *** Bug 1593616 has been marked as a duplicate of this bug. *** 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 |