Bug 1368003 - add node/reinstall against ose-3.3 fail when quick install with an config file which has new node and installed node
Summary: add node/reinstall against ose-3.3 fail when quick install with an config fil...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Samuel Munilla
QA Contact: liujia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-18 06:08 UTC by liujia
Modified: 2017-03-22 20:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-01-18 12:52:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 17:23:26 UTC

Comment 2 liujia 2016-08-18 07:57:04 UTC
the same problem:
when run "atomic-openshift-installer -u install", it will directly abort auto with msg but not output the choice items which should be given as a hint.

Comment 5 liujia 2016-10-28 10:17:43 UTC
Version:
atomic-openshift-utils-3.4.13-1.git.0.ff1d588.el7.noarch

Steps:
1.trigger an install with quick installer in an installed env
# atomic-openshift-installer install

2.trigger an scaleup with quick installer in an installed env
# atomic-openshift-installer scaleup

Result:
1.it will hint user for an mixed env and warn user to continue for reinstall:
input(n), it will exit.
input(y), it will go to reinstall workflow and run install playbook again for the cluster.

2.it will install new node for scaleup the cluster successfully.

Now add new node and re-install have been splitted and it can go to corresponding workflow successfully, but for specified installer.cfg.yml, it still has another issue which has been tracked in another bug-Bug 1389667. As for this bug, i think it is fixed.

Comment 7 errata-xmlrpc 2017-01-18 12:52:28 UTC
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-2017:0066


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