Description of problem: When running robo.conf using latest gdeploy i see that the following false error messages gets logged on stdout. TASK [Attach to Red Hat subscription pool] ************************************* fatal: [hostedengineSM1.lab.eng.blr.redhat.com]: FAILED! => {"changed": true, "cmd": ["subscription-manager", "attach", "--pool=8a85f9823e3d5e43013e3ddd4e9509c4"], "delta": "0:00:28.362165", "end": "2016-10-04 04:53:16.321333", "failed": true, "failed_when_result": true, "rc": 0, "start": "2016-10-04 04:52:47.959168", "stderr": "", "stdout": "Successfully attached a subscription for: Employee SKU", "stdout_lines": ["Successfully attached a subscription for: Employee SKU"], "warnings": []} ...ignoring I see some deprecation warnings while running engine and robo.conf files. Any updates required in files as suggested in these warnings? TASK [Create/Enabling yum repos] *********************************************** [DEPRECATION WARNING]: Skipping task due to undefined Error, in the future this will be a fatal error.: 'repolist' is undefined. This feature will be removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. Version-Release number of selected component (if applicable): gdeploy-2.0.1-2.el7rhgs.noarch.rpm ansible-2.2.0-0.50.prerelease.el7.noarch.rpm How reproducible: Always Steps to Reproduce: 1. Install gdeploy and ansible. 2. Run the command 'gdeploy -c engine-robo.conf' 3. Actual results: False Errors and warnings given in the description are seen. Expected results: False Errors and warnings should not be seen. Additional info:
Fix: https://github.com/gluster/gdeploy/commit/2322d352 resolves the issue.
Commit: https://github.com/gluster/gdeploy/commit/2322d35290b0f50 fixes the issue.
Verified and works fine with build gdeploy-2.0.1-8.el7rhgs.noarch. I am not seeing any deprecation warnings and false errors during subscription-manager invocation.
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://rhn.redhat.com/errata/RHSA-2017-0260.html