Description of problem: Enable metrics deployment during installation with setting openshift_hosted_metrics_deploy=true in ansible inventory file, installation playbook failed as: TASK [openshift_metrics : Checking generation of {{file_content.kind}} {{file_content.metadata.name}}] *** Monday 27 March 2017 06:44:50 +0000 (0:00:01.841) 0:18:33.813 ********** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ScannerError: {{ item.content | b64decode | from_yaml }}: fatal: [ec2-54-164-204-163.compute-1.amazonaws.com]: FAILED! => { "failed": true } MSG: Unexpected failure during module execution. Version-Release number of selected component (if applicable): openshift-ansible-3.5.45-1.git.0.eb0859b.el7.noarch.rpm How reproducible: Always Steps to Reproduce: 1.Set openshift_hosted_metrics_deploy=true in ansible inventory, start installation playbook. Actual results: Expected results: Additional info:
I'm currently running into other issues when running the BYO playbook trying to recreate this. Can you provide your inventory file you are using please? Can you also provide the '-vvv' output of that failing task? I'm not sure where the 'ScannerError' is coming from.
Gaoyun, Also, how reproducable is this?
I'm able to recreate this now... it seems its having problems with the 'metrics-heapster-rc.yaml' template each time.
https://github.com/openshift/openshift-ansible/pull/3791
Hi, Eric/Scott It's always reproducible when running with openshift-ansible-3.5.45-1, and the metrics related '-vvv' output was attached in Comment 1, sorry for my late reply. And I have tried installation with the proposed PR https://github.com/openshift/openshift-ansible/pull/3791, it works well on metrics deployment, thanks!
Verify this bug with openshift-ansible-3.5.46-1.git.0.f676f1c.el7.noarch.rpm Set openshift_hosted_metrics_deploy=true in ansible inventory, installation playbook run well and metrics pod were deployed.
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