Description of problem: In case the configure conversion host ansible playbook is not run, the playbook log file download should be disabled. Version-Release number of selected component (if applicable): CFME-5.11.5.1 RHV-4.3 How reproducible: an example for a case were this ansible playbook is not run is in this Bug 1810135 - "[v2v] Add a check that conversion host VM has least one IP address in the inventory". The conversion host VM did not have IP address, and thus the conversion host playbook was not ran.
When the playbook has not run, the 'context_data' attribute of the task doesn't have a field named 'conversion_host_enable' (or 'conversion_host_check', or 'conversion_host_disable').
https://github.com/ManageIQ/manageiq-v2v/pull/1131
New commit detected on ManageIQ/manageiq-v2v/ivanchuk: https://github.com/ManageIQ/manageiq-v2v/commit/6ae2d20d2425a03de491e22ce078791a2bd86d54 commit 6ae2d20d2425a03de491e22ce078791a2bd86d54 Author: Milan Zázrivec <mzazrivec> AuthorDate: Mon May 11 11:57:29 2020 +0000 Commit: Milan Zázrivec <mzazrivec> CommitDate: Mon May 11 11:57:29 2020 +0000 Merge pull request #1131 from mturley/bz1827127-disable-playook-log-while-running [BZ#1827127] Disable conversion host log download when playbook has not run (cherry picked from commit d1d4ab8f2886428aba462cbd7d23cb90296f36d7) https://bugzilla.redhat.com/show_bug.cgi?id=1827127 app/javascript/react/screens/App/Settings/screens/ConversionHostsSettings/components/ConversionHostsListItem.js | 12 +- app/javascript/react/screens/App/Settings/screens/ConversionHostsSettings/components/__tests__/ConversionHostsListItem.test.js | 41 +- app/javascript/react/screens/App/Settings/screens/ConversionHostsSettings/components/__tests__/__snapshots__/ConversionHostsListItem.test.js.snap | 9 + 3 files changed, 59 insertions(+), 3 deletions(-)
New commit detected on ManageIQ/manageiq-v2v/jansa: https://github.com/ManageIQ/manageiq-v2v/commit/fcc6d3f48d2bd010bb15a878621ece7bcee95c6f commit fcc6d3f48d2bd010bb15a878621ece7bcee95c6f Author: Milan Zázrivec <mzazrivec> AuthorDate: Mon May 11 11:57:29 2020 +0000 Commit: Milan Zázrivec <mzazrivec> CommitDate: Mon May 11 11:57:29 2020 +0000 Merge pull request #1131 from mturley/bz1827127-disable-playook-log-while-running [BZ#1827127] Disable conversion host log download when playbook has not run (cherry picked from commit d1d4ab8f2886428aba462cbd7d23cb90296f36d7) https://bugzilla.redhat.com/show_bug.cgi?id=1827127 app/javascript/react/screens/App/Settings/screens/ConversionHostsSettings/components/ConversionHostsListItem.js | 12 +- app/javascript/react/screens/App/Settings/screens/ConversionHostsSettings/components/__tests__/ConversionHostsListItem.test.js | 41 +- app/javascript/react/screens/App/Settings/screens/ConversionHostsSettings/components/__tests__/__snapshots__/ConversionHostsListItem.test.js.snap | 9 + 3 files changed, 59 insertions(+), 3 deletions(-)
@Md Nadeem, Looking at the appliance, I don't see an item for auto-conv-osp-instance3 in the conversion host settings page, you must have removed it. Can you run the configuration again? This message appears in the log file, not in the UI, correct? I think this is expected behavior. If the playbook fails, we want the log to be available so the user can see in detail why it failed. As I understand it, the log download should only be disabled if the playbook failed to start at all (i.e. there is no log to download, so it would just fail to download). Fabien, can you verify this?
@Mike Turley Thank you for the response. Yes, the message appear in log file and I am agree with you on the point it should allow to download the log if playbook run. To reproduce the issue, I have tried to configure a conversion host(having no ip associated), However the detail of the conversion not appeared on conversion host page once the configuration widget gets closed. This behavior block me to verify this BZ. I have logged a new BZ for this unexpected behavior. >> https://bugzilla.redhat.com/show_bug.cgi?id=1842806
It sounds like what you observed initially is the expected behavior. Thanks for opening the separate BZ for the new issue.
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/RHSA-2020:2480