Bug 1390135
| Summary: | [quick install]scaleup with quick install in unattended mode should not ask user to input host info | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | liujia <jiajliu> |
| Component: | Installer | Assignee: | Tim Bielawa <tbielawa> |
| Status: | CLOSED ERRATA | QA Contact: | Wenkai Shi <weshi> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.4.0 | CC: | aos-bugs, jokerman, mmccomas, tbielawa |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The command line option that flags unattended mode was not being checked when the scaleup routine was ran.
Consequence: Users would be prompted to enter host information.
Fix: The unattended mode flag is checked during the scaleup routine.
Result: Users are kicked out and given instructions on how to continue if the unattended mode flag is set during a scaleup run.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-12 18:48:10 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
liujia
2016-10-31 09:39:31 UTC
Not critical. Pushing off for now. A fix for this has been submitted in this pr: https://github.com/openshift/openshift-ansible/pull/3061 Verified with version atomic-openshift-utils-3.5.23-1.git.0.1cd0089. # atomic-openshift-installer -u scaleup Welcome to the OpenShift Enterprise 3 Scaleup utility. --- The 'scaleup' operation does not support unattended functionality. Re-run the installer without the '-u' or '--unattended' option to continue. I will have to take a look at this 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:0903 |