Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1516996 - Exporting a mistral environment and trying to update it afterward fails
Summary: Exporting a mistral environment and trying to update it afterward fails
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-mistralclient
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 11.0 (Ocata)
Assignee: Toure Dunnon
QA Contact: nlevinki
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-23 19:50 UTC by David Hill
Modified: 2018-06-22 12:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-06-22 12:29:54 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Launchpad 1769491 None None None 2018-05-19 20:28:34 UTC
OpenStack gerrit 569411 None None None 2018-05-19 20:59:19 UTC

Description David Hill 2017-11-23 19:50:42 UTC
Description of problem:
Exporting a mistral environment with "mistral environment-get -f yaml (or json) overcloud > overcloud.yaml " and trying to update the overcloud environment with "mistral environment-update overcloud.yaml" fails on the name key being missing.   Exporting the values seems to export the keys with the first letter of the key capitalized such as "Name" for instance and when trying to import it back, it fails because it's not called "name" ...  

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

How reproducible:

Steps to Reproduce:
1. mistral environment-get -f yaml overcloud > overcloud.yaml
2. mistral environment-update overcloud.yaml

Actual results:
Fails finding "name"

Expected results:
Should find it...  If I fix "Name" to "name", it then fails to update the environment because the key "Created at" and "Updated at" are not allowed keys.   Perhaps we should simply overlook those 2 keys.

Additional info:

Comment 8 Scott Lewis 2018-06-22 12:29:54 UTC
OSP11 is now retired, see details at

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