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.

Sign up for GitHub

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

Jump to bottom

Set user_data_update_policy: ignore or stack becomes unrecoverable on update #360

Closed
ioggstream opened this issue Jun 15, 2017 · 0 comments
Closed

Set user_data_update_policy: ignore or stack becomes unrecoverable on update #360

ioggstream opened this issue Jun 15, 2017 · 0 comments

Comments

@ioggstream
Copy link
Contributor

ioggstream commented Jun 15, 2017 •
edited
Loading

when

I change ca-certificate.yaml or some other cloud-init file

I expect

  • the hosts not to be recreated if I change eg. ca_cert
  • changes to be possibile in post-deploy

instead

  • the hosts will be recreated
  • usually heat ends with multiple bastions / hosts and the whole stack get messy

a solution

could be adding to the nodes

user_data_update_policy: IGNORE
ioggstream added a commit to ioggstream/openshift-on-openstack that referenced this issue Jun 26, 2017
@ioggstream
Fix redhat-openstack#360: don't recreate hosts when user_data changes…
4a10816 
… as heat gets stuck and the stack become unrecoverable.
@ioggstream ioggstream changed the title Set user_data_update_policy: ignore on bastion Set user_data_update_policy: ignore or stack becomes unrecoverable on update Jun 26, 2017
@ioggstream ioggstream mentioned this issue Aug 16, 2017
Merged
tomassedovic added a commit that referenced this issue Oct 3, 2017
@tomassedovic
Merge pull request #365 from ioggstream/360-avoid-host-replacement
54dd01b 
Fix #360: don't recreate hosts when user_data changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ioggstream