Bug 1328356 - atomic-openshift are out of service for a while after running pre.yml
Summary: atomic-openshift are out of service for a while after running pre.yml
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Devan Goodwin
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-19 08:08 UTC by Anping Li
Modified: 2017-03-08 18:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-22 22:22:52 UTC
Target Upstream Version:


Attachments (Terms of Use)
the ansilbe logs for pre.yaml (39.83 KB, text/plain)
2016-04-19 09:15 UTC, Anping Li
no flags Details

Comment 1 Anping Li 2016-04-19 09:15:29 UTC
Created attachment 1148443 [details]
the ansilbe logs for pre.yaml

Comment 4 Devan Goodwin 2016-09-08 19:26:58 UTC
Situation here should be improved quite a bit today, afaik there is nothing in pre.yml that should take down any services so these should not affect running systems.

Once we proceed to upgrade itself we upgrade each master 1 at a time, then for every node (which includes masters) we set it unschedulable, then upgrade docker if required, then upgrade the node/openvswitch and restart services. I believe service downtime is about as minimal as possible at this point, I can't see any extraneous tasks in the plays between taking the service down or node offline, and when they come back.

Sending back to you Anping, let me know if you think there is anything else that can be done. If not lets close this.

Comment 5 Anping Li 2016-09-09 14:19:22 UTC
I works fine now. So move to verified

Comment 6 Devan Goodwin 2016-09-14 18:05:06 UTC
Moving this to private as I don't think there's any relevant doctext to be written here.


Note You need to log in before you can comment on or make changes to this bug.