Bug 1391794 - pre_upgrade checks didn't report stoped master/node service
Summary: pre_upgrade checks didn't report stoped master/node service
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: liujia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-04 05:05 UTC by liujia
Modified: 2017-08-25 15:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-25 15:51:28 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description liujia 2016-11-04 05:05:15 UTC 
Description of problem:
When master or node service was stoped, ran pre_upgrade playbook before upgrade, it did not report this abnormal serives status.

Version-Release number of selected component (if applicable):
ansible-2.2.0.0-0.100.el7.noarch
openshift-ansible-playbooks-3.4.16-1.git.0.c846018.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Stoped master/node service in OCP3.4 cluster
2. Run pre_upgrade playbook
# ansible-playbook -i hosts /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_4/upgrade.yml -e openshift_upgrade_nodes_serial=4 --tags pre_upgrade

Actual results:
The playbook complete successfully without any errors or results about stoped services.

Expected results:
It should report the error.
Note You need to log in before you can comment on or make changes to this bug.