Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1384294 - What prints to the screen by quick installer is not quiet format
What prints to the screen by quick installer is not quiet format
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.3.1
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Tim Bielawa
liujia
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-10-12 23:14 EDT by liujia
Modified: 2017-03-08 13 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The ansible 'quiet output' config was not set for non-'install' runs of atomic-openshift-installer. Consequence: Users would see full ansible output rather than abbreviated step-by-step output. Fix: The ansible 'quiet output' config is set as the default for all atomic-openshift-installer runs. Result: Users see abbreviated output now and can toggle back to verbose output with -v or --verbose.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-18 07:42:41 EST
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 12:23:26 EST

  None (edit)
Description liujia 2016-10-12 23:14:55 EDT
Description of problem:
When run uninstall with atomic-openshift-installer, the output on the screen is still original format of ansible instead of new format with new callback_plugins.

Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.3.34-1.git.0.5b998bb.el7.noarch
openshift-ansible-callback-plugins-3.3.34-1.git.0.5b998bb.el7.noarch
openshift-ansible-3.3.34-1.git.0.5b998bb.el7.noarch

How reproducible:
always

Steps to Reproduce:
1.run uninstall against OCP3.3 env
#atomic-openshift-installer -c /tmp/installer.cfg.yml uninstall

Actual results:
Uninstall successfully, but the output format is not what we expect.
PLAY [OSEv3:children] **********************************************************

TASK [setup] *******************************************************************
ok: [openshift-118.lab.eng.nay.redhat.com]

TASK [Detecting Operating System] **********************************************
changed: [openshift-118.lab.eng.nay.redhat.com]

TASK [set_fact] ****************************************************************
ok: [openshift-118.lab.eng.nay.redhat.com]

TASK [set_fact] ****************************************************************
ok: [openshift-118.lab.eng.nay.redhat.com]
....

Expected results:
the output info should be brief style like following:
Play 1/30 (localhost)
.
Play 2/30 (localhost)
...

Additional info:
Comment 1 Tim Bielawa 2016-10-27 13:38:08 EDT
More cosmetic than functional error.

Pushing back while we focus on critical bugs for this upcoming release.
Comment 2 Tim Bielawa 2016-11-10 16:22:48 EST
liujia, I updated the quick installer to use the quiet output for the other operations. The changes have been merged into master. Good to test!
Comment 4 liujia 2016-11-14 02:47:18 EST
Version:
atomic-openshift-utils-3.4.23-1.git.0.317b2cd.el7.noarch

Verify following sub-command with quick installer:
1.upgrade ocp3.3 to ocp3.4
# atomic-openshift-installer upgrade
2.scaleup cluster
# atomic-openshift-installer scaleup
3.uninstall
# atomic-openshift-installer uninstall

The output of all sub-commands with quick installer are updates to unitied quiet format.
Comment 6 errata-xmlrpc 2017-01-18 07:42:41 EST
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.