Description of problem: Try to deploy Metrics 3.5 using Ansible, the job failed at TASK [openshift_metrics : Stop Heapster] *************************************** task path: /home/penli/work/src/github.com/penli1/tmp/openshift-ansible/roles/openshift_metrics/tasks/stop_metrics.yaml:13 fatal: [MASTER]: FAILED! => { "failed": true, "msg": "'dict object' has no attribute 'stdout_lines'" } This might caused by: 1. the output of {{metrics_heapster_rc.stdout_lines}} have multiple vars when task running. 2. the pods are not running yet Version-Release number of selected component (if applicable): openshift v3.5.0.7+390ef18 Metrics 3.5.0 How reproducible: always Steps to Reproduce: 1. prepare the inventory file [oo_first_master] $MASTER ansible_user=root ansible_ssh_user=root ansible_ssh_private_key_file="/home/penli/.ssh/libra.pem" openshift_public_hostname=$MASTER [oo_first_master:vars] deployment_type=openshift-enterprise openshift_release=v3.5.0 openshift_metrics_install_metrics=true openshift_metrics_hawkular_hostname=hawkular-metrics.$SUBDOMAIN openshift_metrics_project=openshift-infra openshift_metrics_image_prefix=registry.ops.openshift.com/openshift3/ openshift_metrics_image_version=3.5.0 2. git clone https://github.com/openshift/openshift-ansible.git (In this test, I'm using dev's branch bz_1414477_missing_import_jks_deuce) ) 3. ansible-playbook -vvv -i ~/inventory playbooks/common/openshift-cluster/openshift_metrics.yml 4. task fail and abort. 5. login the master machine and check the pod status # oc get pod -n openshift-infra NAME READY STATUS RESTARTS AGE hawkular-cassandra-1-br736 0/1 Running 0 1m hawkular-metrics-hp7pj 0/1 Running 0 1m heapster-g3rqr 0/1 Running 0 2m 6. wait for several minutes, pods are healthy and running. # oc get pod -n openshift-infra NAME READY STATUS RESTARTS AGE hawkular-cassandra-1-br736 1/1 Running 0 16m hawkular-metrics-hp7pj 1/1 Running 0 17m heapster-g3rqr 1/1 Running 0 17m Expected results: install successfully. Additional info: Ansible execution log and Events attached.
@pengli I am unable to determine how you actually got ino this state because the uninstall task should only be executed when 'openshift_metrics_install_metrics' equals 'False'. Made a slight change to conditionally include the start/stop task based on the var evaluation in PR https://github.com/openshift/openshift-ansible/pull/3150
(In reply to Jeff Cantrill from comment #3) > @pengli I am unable to determine how you actually got ino this state because > the uninstall task should only be executed when > 'openshift_metrics_install_metrics' equals 'False'. Made a slight change to > conditionally include the start/stop task based on the var evaluation in PR > https://github.com/openshift/openshift-ansible/pull/3150 thanks for the update, it do happen every time in my fresh install test, I'll veriry&close it once it's merged to master branch.
This has been merged into ocp and is in OCP v3.5.0.12 or newer.
As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1418910#c3, this is also blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1418911
verified with master branch, issue is not reproduced.
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