Bug 1855124 - [RHV 4.4] Failures caused due to changes in ansible-2.9.10
Summary: [RHV 4.4] Failures caused due to changes in ansible-2.9.10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: RHHI-V 1.8
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1855164 1855352 1855531
Blocks: RHHI-V-1.8-Engineering-Inflight-BZs
TreeView+ depends on / blocked
 
Reported: 2020-07-09 02:48 UTC by SATHEESARAN
Modified: 2020-08-04 14:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1855164 (view as bug list)
Environment:
Last Closed: 2020-08-04 14:52:36 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:3314 0 None None None 2020-08-04 14:52:50 UTC

Description SATHEESARAN 2020-07-09 02:48:29 UTC
Description of problem:
-----------------------
While performing RHHI-V deployment, only the HE host is added to the 'Default' cluster. But the other 2 hosts are not added to the cluster. 

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHVH 4.4 (RHVH-4.4-20200707.0-RHVH-x86_64-dvd1.iso	)
ansible-2.9.10

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Complete the RHHI-V deployment with 3 nodes

Actual results:
----------------
RHV Manager 4.4 shows only one host in the cluster

Expected results:
-----------------
All the hosts used for deployment should be added to the cluster

Additional info:
----------------
1. This flow worked till last RHVH 4.4 ISO and the latest RHVH 4.4 ISO included ansible-2.9.10 and this causing this regression
2. The issue is also seen with RHHI-V 1.7 deployment based on RHV 4.3.11

Comment 1 SATHEESARAN 2020-07-09 02:49:09 UTC
Deployment was attempted with ansible-2.9.9 and the deployment worked good.

Comment 3 SATHEESARAN 2020-07-09 12:45:08 UTC
The issue is root caused, it is mainly because of change in ansible-2.9.10-1.el8ae

The task that add the hosts to the cluster uses 'delegate_to', with the latest
change in ansible, when using 'delegate_to' to the remote host, then the connection
parameter needs to be explicitly provided, else the value is inherited from 'ansible_connection' 
which most of the times is 'local'. So the changes happen only on the localhost, instead of
remote host.

To fix this problem, the task is expected to have 'connection: ssh' where
delegate_to: <remote-host> is used.

Comment 5 SATHEESARAN 2020-07-18 07:26:17 UTC
All the dependent bugs are moved ON_QA, moving this bug also to ON_QA for verification

Comment 6 SATHEESARAN 2020-07-18 07:28:03 UTC
Verified with RHVH-4.4.1 - RHVH-4.4-20200716.0-RHVH-x86_64-dvd1.iso	

Deployment automatically added the required hosts while attempting for deployment
from web console (cockpit). The deployment also succeeded when attempted using
ansible playbooks from CLI

Comment 8 errata-xmlrpc 2020-08-04 14:52:36 UTC
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 (RHHI for Virtualization 1.8 bug fix and enhancement update), 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/RHEA-2020:3314


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