Bug 1819052 - [ceph-ansible] infrastructure-playbooks/purge-cluster.yml fails for rgw host
Summary: [ceph-ansible] infrastructure-playbooks/purge-cluster.yml fails for rgw host
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 4.1
Assignee: Guillaume Abrioux
QA Contact: Vasishta
URL:
Whiteboard:
: 1821135 1866519 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-31 05:03 UTC by Ameena Suhani S H
Modified: 2020-08-17 15:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-03 02:40:00 UTC
Embargoed:


Attachments (Terms of Use)
group_vars, inventory and ansible purge logs (533.00 KB, text/plain)
2020-03-31 05:03 UTC, Ameena Suhani S H
no flags Details

Description Ameena Suhani S H 2020-03-31 05:03:06 UTC
Created attachment 1674950 [details]
group_vars, inventory and ansible purge logs

Description of problem:
infrastructure-playbooks/purge-cluster.yml fails for rgw with error as [1].

[1]fatal: [magna126]: FAILED! => 
  msg: |-
    The task includes an option with an undefined variable. The error was: 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'instance_name'
  
    The error appears to be in '/usr/share/ceph-ansible/infrastructure-playbooks/purge-cluster.yml': line 306, column 7, but may
    be elsewhere in the file depending on the exact syntax problem.
  
    The offending line appears to be:
  
  
        - name: stop ceph rgws with systemd
          ^ here


Version-Release number of selected component (if applicable):

ceph-ansible-4.0.17-1.el8.noarch
ansible-2.9.6-1.el8ae.noarch
ceph version 14.2.8-27.el8cp 

How reproducible:
2/2

Steps to Reproduce:
1. Deploy a cluster with rgw host
2. Run "ansible-playbook infrastructure-playbooks/purge-cluster.yml -vvvv"


Actual results:
The purge failed with [1].

Expected results:
The purge should be successful.


Additional info:

Comment 3 Guillaume Abrioux 2020-04-06 13:30:37 UTC
*** Bug 1821135 has been marked as a duplicate of this bug. ***

Comment 5 Guillaume Abrioux 2020-08-17 15:13:16 UTC
*** Bug 1866519 has been marked as a duplicate of this bug. ***


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