Bug 1299325 - Checking master service status failed during restart on the none HA Master env
Summary: Checking master service status failed during restart on the none HA Master env
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Andrew Butcher
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-18 06:38 UTC by Anping Li
Modified: 2016-01-29 20:58 UTC (History)
5 users (show)

Fixed In Version: openshift-ansible-3.0.34-1.git.0.b0511f9.el7aos
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-29 20:58:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Anping Li 2016-01-18 06:38:34 UTC
Description of problem:
Rolling restart failed at the task 'Check master service status' on the  none Master HA Environment

Version-Release number of selected component (if applicable):
openshift-ansible-3.0.33-1

How reproducible:
Always

Steps to Reproduce:
1. Set OSE Environment  1 Master + 1 Hosts
2. ansible-playbook -i /root/config/oserhel /root/openshift-ansible/playbooks/byo/openshift-master/restart.yml

Actual results:
TASK: [pause ] **************************************************************** 
skipping: [10.14.6.120]

TASK: [set_fact ] ************************************************************* 
skipping: [10.14.6.120]

PLAY [Determine which masters are currently active] *************************** 

GATHERING FACTS *************************************************************** 
ok: [10.14.6.120]

TASK: [Check master service status] ******************************************* 
fatal: [10.14.6.120] => error while evaluating conditional: openshift.master.cluster_method == 'pacemaker'

FATAL: all hosts have already failed -- aborting

PLAY RECAP ******************************************************************** 
           to retry, use: --limit @/root/restart.retry

10.14.6.120                : ok=12   changed=0    unreachable=1    failed=0   
localhost                  : ok=7    changed=0    unreachable=0    failed=0   

Expected results:
The rolling restart succeed


Additional info:

Comment 1 Brenton Leanhardt 2016-01-18 16:08:50 UTC
Andrew has a fix for this and I've verified it.  We'll deliver it to QE in today's build.

Comment 3 Anping Li 2016-01-19 02:55:53 UTC
The fix works well, so move bug to Verified


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