Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Domain priority changes on miqimport. #145

Open
stana opened this issue Jul 23, 2019 · 2 comments
Open

Domain priority changes on miqimport. #145

stana opened this issue Jul 23, 2019 · 2 comments

Comments

@stana
Copy link

stana commented Jul 23, 2019

After cloudforms upgrade to 5.10.6.1 doing miqimport (with --overwrite) of domain that does not have highest priority, imports the domain as the highest priority?

For example if have domains -
DomainB (priority 3)
DomainA (priority 2)
RedHat (priority 1)
ManageIQ (priority 0)

miqexport-ing of DomainA, and then doing - miqimport with --overwrite, will change priority of DomainA and import it as highest priority (above DomainB).

@branic
Copy link
Contributor

branic commented Jul 23, 2019

@stana That is expected behavior.

When --overwrite is enabled the domain is deleted prior to imported (https://github.com/rhtconsulting/cfme-rhconsulting-scripts/blob/master/rhconsulting_miq_ae_datastore.rake#L13-L15)

@stana
Copy link
Author

stana commented Jul 23, 2019

@branic Thanks for quick response.
Our deployment process hasn't changed. Prior to CloudForms 4.7 priority specified in __domain__.yaml was preserved on miqimport. i.e. we could import a domain (even after deletion) to priority that is not the highest. Seems as of CloudForms 4.7 new automation domain can only be imported to top priority and we have to manually change priority through UI.
(edited formatting)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants