Bug 1824680 - Host upgrade failed on ovirt-host-deploy-vnc-certificates : Create cert dir using python2 instead of python3
Summary: Host upgrade failed on ovirt-host-deploy-vnc-certificates : Create cert dir u...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: ovirt-host-deploy-ansible
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.4.1
: ---
Assignee: Dana
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On: 1819248
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-16 11:54 UTC by Petr Matyáš
Modified: 2020-04-17 05:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-17 05:55:49 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)

Description Petr Matyáš 2020-04-16 11:54:22 UTC
Description of problem:
When upgrading a host the action fails on creating of certificate dirs.
    "stdout" : "fatal: [host]: FAILED! => {\"changed\": false, \"module_stderr\": \"Shared connection to host closed.\\r\\n\", \"module_stdout\": \"/bin/sh: /usr/bin/python2: No such file or directory\\r\\n\", \"msg\": \"The module failed to execute correctly, you probably need to set the interpreter.\\nSee stdout/stderr for the exact error\", \"rc\": 127}",


Version-Release number of selected component (if applicable):
ovirt-engine-4.4.0-0.32.master.el8ev.noarch

How reproducible:
actually not sure, another host succeed without problems

Steps to Reproduce:
1. have a host with upgrades available
2. upgrade the host
3.

Actual results:
fails on cert dir creation

Expected results:
upgrade successful

Additional info:

Comment 2 Martin Perina 2020-04-16 12:02:42 UTC
(In reply to Petr Matyáš from comment #0)
> Description of problem:
> When upgrading a host the action fails on creating of certificate dirs.
>     "stdout" : "fatal: [host]: FAILED! => {\"changed\": false,
> \"module_stderr\": \"Shared connection to host closed.\\r\\n\",
> \"module_stdout\": \"/bin/sh: /usr/bin/python2: No such file or
> directory\\r\\n\", \"msg\": \"The module failed to execute correctly, you
> probably need to set the interpreter.\\nSee stdout/stderr for the exact
> error\", \"rc\": 127}",
> 
> 
> Version-Release number of selected component (if applicable):
> ovirt-engine-4.4.0-0.32.master.el8ev.noarch
> 
> How reproducible:
> actually not sure, another host succeed without problems

Were boths hosts EL8 or one of them was EL7?

Comment 3 Petr Matyáš 2020-04-16 12:04:33 UTC
All hosts are regular RHEL 8, same HW even. The one that failed was the original host in this HE setup.

Comment 4 Dana 2020-04-16 20:57:52 UTC
Was this vm installed different somehow?
Its parameters look strange-
"distribution": "OtherLinux",
"distribution_major_version": "NA",
"distribution_release": "NA",
"distribution_version": "NA",

And the even more interesting thing is, that 'OtherLinux' doesn't even exist in the OS_FAMILY_MAP:
https://github.com/ansible/ansible/blob/f58780fb28341fb07cd8fe188c983097574fb436/lib/ansible/module_utils/facts/system/distribution.py#L413

Comment 5 Michal Skrivanek 2020-04-17 05:55:49 UTC
/etc/redhat-release is empty. Dunno what happened to it, but it's not a valid change, system is failing to recognize OS. It's like that since at least:
2020-04-02T15:23:04Z CRITICAL Detection of Platform Module failed: No valid Platform ID detected

We don't support unknown OSes


Note You need to log in before you can comment on or make changes to this bug.