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

Idempotency Cleanup: [NODES] #3348

Closed
tbielawa opened this issue Feb 13, 2017 · 1 comment
Closed

Idempotency Cleanup: [NODES] #3348

tbielawa opened this issue Feb 13, 2017 · 1 comment

Comments

@tbielawa
Copy link
Contributor

You really should run ara to make your life easier fixing up these items. Sharing the results is difficult due to the size of the generated static reports. Instead below you'll find a copy/paste of tasks and a screenshot.

There are batches of tasks that show up as changed every time the upgrade playbook is ran. These tasks are only from the nodes list of changed tasks. These require review:

Clean package cache	n01.example.com	command	0:00:14	0:00:03	CHANGED	details
Mark node unschedulable	n01.example.com	oadm_manage_node	0:06:21	0:00:00	CHANGED	details
Drain Node for Kubelet upgrade	n01.example.com	command	0:06:22	0:00:01	CHANGED	details
Restart docker	n01.example.com	service	0:06:59	0:00:01	CHANGED	details
Restart rpm node service	n01.example.com	service	0:07:02	0:00:01	CHANGED	details
Set node schedulability	n01.example.com	oadm_manage_node	0:07:04	0:00:00	CHANGED	details

node-changes

@sdodson
Copy link
Member

sdodson commented Feb 14, 2017

I think these are all playbook level idempotency issues. I'm not sure how we can address them, we have to decide if and when it makes sense to completely skip a node. Perhaps if we have verified that its version already matches the desired version?

I think these can all get a pass for now.

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

No branches or pull requests

3 participants