Fix overcloud deploy to allow force keystone init
Bug #1592926 reported by
Pradeep Kilambi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Pradeep Kilambi |
Bug Description
Currently overcloud deploy will only run post deploy config (keystone init) on create only. This breaks upgrades and reruns as the endpoints for newer services wont be created.
Allow a new force override option so users can manually run --force-postconfig to get missing endpoints back into keystone.
Changed in tripleo: | |
assignee: | nobody → Pradeep Kilambi (pkilambi) |
Changed in tripleo: | |
status: | New → In Progress |
Changed in tripleo: | |
importance: | Undecided → High |
milestone: | none → newton-2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/330096 /git.openstack. org/cgit/ openstack/ python- tripleoclient/ commit/ ?id=430565216a5 277b09580bdfca4 f906c34815f8ff
Committed: https:/
Submitter: Jenkins
Branch: master
commit 430565216a5277b 09580bdfca4f906 c34815f8ff
Author: Pradeep Kilambi <email address hidden>
Date: Wed Jun 15 12:25:46 2016 -0400
Run post deploy config on force
keystone init currently only runs on create. This causes issues
and ends up with broken deploys on re-runs or upgrades. This
change ensures we expose a new force option so user can manually
run post config deploy and get back missing endpoints. Also modify
keystone init to check all services instead of just nova before
triggering keystone endpoint create.
I understand this is moving to puppet, but so long as this is here
lets make sure it works for upgrades and reruns.
Closes-bug: #1592926
Change-Id: I2337acaf68bd2d c1245de752a434e 138f8a0ccd1