Bug 1781459 - RHHI-V deployment fails with latest gluster-ansible packages
Summary: RHHI-V deployment fails with latest gluster-ansible packages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.7
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: RHHI-V 1.7
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1781462
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-10 04:19 UTC by SATHEESARAN
Modified: 2020-02-13 15:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Cause: In gluster-ansible-feature build some untested commit regarding geo-rep included which was causing issue Fix: Excluded geo-rep commits which was not necessary in build Result: Deployment works as expected.
Clone Of:
: 1781462 (view as bug list)
Environment:
Last Closed: 2020-02-13 15:57:23 UTC
Embargoed:


Attachments (Terms of Use)
inventory yml (4.37 KB, application/octet-stream)
2019-12-10 04:36 UTC, SATHEESARAN
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0508 0 None None None 2020-02-13 15:57:37 UTC

Description SATHEESARAN 2019-12-10 04:19:19 UTC
Description of problem:
-----------------------
With the latest gluster-ansible-features and gluster-ansible-roles packages, RHHI-V deployment is failing.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gluster-ansible-features-1.0.5-4.el7rhgs
gluster-ansible-roles-1.0.5-6.el7rhgs

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

Steps to Reproduce:
-------------------
1. Deploy RHVH 4.3.7 and update RHVH

Actual results:
---------------
Deployment fails

Expected results:
-----------------
Deployment should succeed

Comment 1 SATHEESARAN 2019-12-10 04:29:00 UTC
When enabling ansible debug messages

<snip>
2019-12-10 09:34:32,745 p=root u=24395 | ansible-playbook 2.9.1
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /root/../usr/bin/ansible-playbook
  python version = 2.7.5 (default, Jun 11 2019, 14:33:56) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]
2019-12-10 09:34:32,745 p=root u=24395 | Using /etc/ansible/ansible.cfg as config file
2019-12-10 09:34:33,284 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vdo_create.yml
2019-12-10 09:34:33,289 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vg_create.yml
2019-12-10 09:34:33,295 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/thick_lv_create.yml
2019-12-10 09:34:33,299 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/thin_pool_create.yml
2019-12-10 09:34:33,304 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/thin_volume_create.yml
2019-12-10 09:34:33,310 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/cache_setup.yml
2019-12-10 09:34:33,319 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/fscreate.yml
2019-12-10 09:34:33,328 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/mount.yml
2019-12-10 09:34:33,394 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/nfs_ganesha/tasks/prerequisites.yml
2019-12-10 09:34:33,406 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/nfs_ganesha/tasks/distribute_keys.yml
2019-12-10 09:34:33,471 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/nfs_ganesha/tasks/master_tasks.yml
2019-12-10 09:34:33,486 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/nfs_ganesha/tasks/enable_ganesha.yml
2019-12-10 09:34:33,499 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/nfs_ganesha/tasks/add_new_nodes.yml
2019-12-10 09:34:33,538 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/gluster_hci/tasks/prerequisites.yml
2019-12-10 09:34:33,621 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/gluster_hci/tasks/glusterd_ipv6.yml
2019-12-10 09:34:33,627 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/gluster_hci/tasks/hci_volumes.yml
2019-12-10 09:34:33,650 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/gluster_hci/tasks/ssl-setup.yml
2019-12-10 09:34:33,680 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/ctdb/tasks/setup_ctdb.yml
2019-12-10 09:34:33,705 p=root u=24395 | statically imported: /etc/ansible/roles/gluster.features/roles/geo_replication/tasks/georep_session_create.yml
2019-12-10 09:34:33,808 p=root u=24395 | ERROR! couldn't resolve module/action 'geo_rep'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/etc/ansible/roles/gluster.features/roles/geo_replication/tasks/georep_session_create.yml': line 80, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

# Enable geo-replication
- name: Create the geo-rep session
  ^ here

</snip>

Comment 2 SATHEESARAN 2019-12-10 04:36:47 UTC
Created attachment 1643483 [details]
inventory yml

Comment 3 SATHEESARAN 2019-12-16 02:46:22 UTC
Tested with gluster-ansible-features-1.0.5-5.el7rhgs.

RHHI-V deployment was successful with RHVH 4.3.8 & RHGS 3.5.1 ( glusterfs-6.0-24.el7rhgs )

Comment 6 errata-xmlrpc 2020-02-13 15:57:23 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, 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-2020:0508


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