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:
More cosmetic than functional error. Pushing back while we focus on critical bugs for this upcoming release.
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!
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.
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