Check cluster settings before and after the deploy
Bug #1564363 reported by
Dennis Dmitriev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Mikhail Samoylov | ||
Mitaka |
Fix Released
|
High
|
Mikhail Samoylov | ||
Newton |
Fix Committed
|
High
|
Mikhail Samoylov |
Bug Description
In https:/
Looks like it is not affecting the cluster itself, because OSTF passed succesfully.
But we don't know if the cluster was deployed with the settings that system tests requested, not with the some random or missed settings that produce working cluster but with not expected configuration.
We would add a check that will store a cluster settings before each deploy and compare it with the cluster settings at the end of the deploy, to catch the issues with missing objects.
Changed in fuel: | |
assignee: | Fuel QA Team (fuel-qa) → Alexander Kurenyshev (akurenyshev) |
Changed in fuel: | |
importance: | Wishlist → High |
Changed in fuel: | |
assignee: | Alexander Kurenyshev (akurenyshev) → Mikhail Samoylov (msamoylov) |
To post a comment you must log in.
Dennis +100 for such check. It also may be useful in tests for unlock settings tab