Bug 1432868 – Excluders should be installed on new node/master when scaleup cluster

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1432868 - Excluders should be installed on new node/master when scaleup cluster

Summary:	Excluders should be installed on new node/master when scaleup cluster

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	3.5.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jan Chaloupka
QA Contact:	liujia
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-16 05:39 EDT by liujia
Modified:	2017-07-24 10 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	Cause: excluders are not acknowledged during node/master scale up Consequence: excluders are not installed on new nodes/masters Fix: install excluders on new nodes/masters as well Result: excluders are installed on new nodes/masters when scaling up
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-04-11 17:15:54 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:0903	normal	SHIPPED_LIVE	OpenShift Container Platform atomic-openshift-utils bug fix and enhancement	2017-04-12 18:45:42 EDT

Groups: None (edit)

Description liujia 2017-03-16 05:39:47 EDT

Description of problem:
Run scaleup.yml playbook to add new node to existed cluster, excluders is not installed on the new node. Since excluders are necessary component for ocp installation by default, then it should keep the same rule when scaleup a cluster. Especially docker-excluder is needed to ensure right version docker to be installed. 

Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.5.35-1.git.0.7aa4728.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Install ocp3.5 on fresh hosts
2. Scaleup above cluster to add new node
# ansible-playbook -i hosts2 /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-node/scaleup.yml
3.

Actual results:
No excluders installed on the new node after scaleup.

Expected results:
Excluders should be installed on the new node and take effect during scaleup.

Additional info:
The same issue when scaleup master on ha env.

Comment 1 Jan Chaloupka 2017-03-16 11:27:39 EDT

Upstream PR: https://github.com/openshift/openshift-ansible/pull/3681

Comment 2 Jan Chaloupka 2017-03-17 08:18:01 EDT

Merged upstream.

Comment 4 Anping Li 2017-03-20 04:18:59 EDT

The scaleup should call disable_excluder.yml before docker is installed(prior Task Configure docker hosts ).  Otherwise, an unexpected docker may be installed.

Comment 6 Anping Li 2017-03-21 03:40:14 EDT

Verified and pass with atomic-openshift-utils-3.5.39-1.git.0.cb12cdb.el7.noarch

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