Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1372609 - The node should be set back to schedulable after the node service have been restarted
The node should be set back to schedulable after the node service have been r...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
3.3.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.3.1
Assigned To: Devan Goodwin
Anping Li
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-09-02 04:14 EDT by Anping Li
Modified: 2016-10-27 12:13 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Handlers in upgrade playbooks which restart the node service could trigger only after the node was marked schedulable again. Consequence: Nodes could be upgraded, marked schedulable again, then immediately restarted. Fix: Handlers are now explictly run before we mark the node schedulable again. Result: Node will restart before being set schedulable again.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-10-27 12:13:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2122 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix update 2016-10-27 16:11:30 EDT

  None (edit)
Description Anping Li 2016-09-02 04:14:24 EDT
Description of problem:
The node should be set back to schedulable after the node service have been restarted.



Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.3.20

How reproducible:
always

Steps to Reproduce:
1. Check the upgrade logs.

TASK [Set node schedulability] *************************************************
  <---snip--->
RUNNING HANDLER [restart openvswitch] ******************************************
  <---snip--->
RUNNING HANDLER [restart node] *************************************************
  <---snip--->


Actual results:


Expected results:


Additional info:
Comment 2 Devan Goodwin 2016-09-02 16:00:12 EDT
Anping am I correct this was a containerized environment?
Comment 5 Anping Li 2016-10-07 21:57:21 EDT
Can't install openshift-ansible-playbooks-3.3.30

[root@qe-upgrade-working host1]# dnf install atomic-openshift-utils
Last metadata expiration check performed 0:02:03 ago on Sat Oct  8 01:49:35 2016.
Error: nothing provides openshift-ansible-callback-plugins = 3.3.30 needed by openshift-ansible-playbooks-3.3.30-1.git.0.b260e04.el7.noarch
(try to add '--allowerasing' to command line to replace conflicting packages)
Comment 7 Anping Li 2016-10-12 21:37:40 EDT
Blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1383189
Comment 8 Anping Li 2016-10-14 05:08:51 EDT
Verified and pass
Comment 10 errata-xmlrpc 2016-10-27 12:13:22 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:2122

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