Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1878723

Summary: trouble with infrastructure-playbooks/purge-iscsi-gateways.yml on containerized install
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Patrick C. F. Ernzer <pcfe>
Component: DocumentationAssignee: Ranjini M N <rmandyam>
Documentation sub component: Block Device Guide QA Contact: Preethi <pnataraj>
Status: CLOSED CURRENTRELEASE Docs Contact: Mary Frances Hull <mhull>
Severity: high    
Priority: high CC: aschoen, ceph-eng-bugs, csharpe, gabrioux, gmeno, gsitlani, hyelloji, kdreyer, kelwhite, mamccoma, mhackett, mhull, nthomas, pcuzner, rcarrier, rmandyam, sbaldwin, vereddy, ykaul
Version: 4.1   
Target Milestone: rc   
Target Release: 4.3   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-05 18:50:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1811582, 1966534    

Description Patrick C. F. Ernzer 2020-09-14 11:58:25 UTC
Description of problem:
I seem unable to use infrastructure-playbooks/purge-iscsi-gateways.yml on a containerised RHCS 4.1 install.

Version-Release number of selected component (if applicable):
ceph-ansible-4.0.25.2-1.el8cp.noarch

How reproducible:
always

Steps to Reproduce:
1. have a working Ceph cluster
2. add two [iscsigws]
3. deploy
4. decide against iSCSI
5. attempt to purge iSCSI gateways as per documentation

Actual results:
TASK [igw_purge | purging the gateway configuration] *****************************************************************************************************************************************************************************************
Monday 14 September 2020  10:42:10 +0200 (0:00:00.123)       0:00:10.707 ****** 
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ModuleNotFoundError: No module named 'rados'
fatal: [f5-422-02.storage.pcfe.net]: FAILED! => changed=false 
  module_stderr: |-
    Traceback (most recent call last):
      File "<stdin>", line 114, in <module>
      File "<stdin>", line 106, in _ansiballz_main
      File "<stdin>", line 49, in invoke_module
      File "/usr/lib64/python3.6/imp.py", line 235, in load_module
        return load_source(name, filename, file)
      File "/usr/lib64/python3.6/imp.py", line 170, in load_source
        module = _exec(spec, sys.modules[name])
      File "<frozen importlib._bootstrap>", line 618, in _exec
      File "<frozen importlib._bootstrap_external>", line 678, in exec_module
      File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
      File "/tmp/ansible_igw_purge_payload_sazj4vxu/__main__.py", line 40, in <module>
    ModuleNotFoundError: No module named 'rados'
  module_stdout: ''
  msg: |-
    MODULE FAILURE
    See stdout/stderr for the exact error
  rc: 1

Expected results:
If ceph-ansible handles my install and I use a containerized install type, I do expect all needed python modules present.

Additional info:

Comment 10 Paul Cuzner 2021-07-12 02:21:41 UTC
No - building a rhel7/container/rhcs4 environment now to confirm the steps

Comment 22 Preethi 2021-10-21 10:07:51 UTC
@Ranjini, Content looks good to me and above mentioned comments are implemented. Moving to Verified state.