Bug 1785736 - Purging storage clusters fail " registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.1 msg: '[Errno 2] No such file or directory'"
Summary: Purging storage clusters fail " registry.redhat.io/openshift4/ose-prometheus-...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 4.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 4.1
Assignee: Dimitri Savineau
QA Contact: Ameena Suhani S H
Karen Norteman
URL:
Whiteboard:
: 1786594 (view as bug list)
Depends On:
Blocks: 1816167
TreeView+ depends on / blocked
 
Reported: 2019-12-20 19:39 UTC by Harish Munjulur
Modified: 2020-07-09 09:57 UTC (History)
17 users (show)

Fixed In Version: ceph-ansible-4.0.15-1.el8, ceph-ansible-4.0.15-1.el7
Doc Type: Bug Fix
Doc Text:
.Running the Ansible `purge-cluster.yml` playbook no longer fails when the dashboard feature is disabled Previously, using the `purge-cluster-yml` playbook to purge clusters failed when the dashboard feature was disabled with the following error message: ---- registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.1 msg: '[Errno 2] No such file or directory' ---- This occurred because the `dashboard_enabled` variable was ignored. With this update, the `dashboard_enabled` variable is correctly handled, and `purge-cluster.yml` runs successfully.
Clone Of:
Environment:
Last Closed: 2020-05-19 17:31:40 UTC
Embargoed:
hyelloji: needinfo-


Attachments (Terms of Use)
purge error logs (20.03 KB, application/vnd.oasis.opendocument.text)
2019-12-20 19:39 UTC, Harish Munjulur
no flags Details
complete purge error logs (16.02 KB, application/vnd.oasis.opendocument.text)
2019-12-20 20:03 UTC, Harish Munjulur
no flags Details
Providing proper complete logs for the bz (704.97 KB, text/plain)
2019-12-23 07:39 UTC, Ameena Suhani S H
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 4882 0 None closed purge: fix purge cluster failed when container images does not exist 2021-01-22 05:33:10 UTC
Github ceph ceph-ansible pull 5024 0 None closed purge: fix purge cluster failed when container images does not exist (bp #4882) 2021-01-22 05:32:29 UTC
Red Hat Product Errata RHSA-2020:2231 0 None None None 2020-05-19 17:31:54 UTC

Description Harish Munjulur 2019-12-20 19:39:59 UTC
Created attachment 1646894 [details]
purge error logs

Description of problem: purge-cluster.yml fail with the below error
Purging of cluster fails with error " registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.1
  msg: '[Errno 2] No such file or directory'"


Version-Release number of selected component (if applicable):
ansible version = 2.8.7
ceph version = 14.2.4-26.el7cp (e2de9960d580ef8c3047880ad0e545c06092c5a0) nautilus (stable)

How reproducible: 2/2


Steps to Reproduce:
1. Run ansible-playbook purge-cluster.yml

2.Fails with the error no file or directory


Actual results: Purging of cluster should be successful


Expected results:Purging of existing cluster should be successful 


Additional info:Attached document has the fail reports

work around used: removing lines from line number 119 to 158 from purge-cluster.yml and then run the playbook purge-cluster.yml works fine.

Comment 1 Harish Munjulur 2019-12-20 20:03:02 UTC
Created attachment 1646901 [details]
complete purge error logs

Comment 2 Ameena Suhani S H 2019-12-23 07:39:10 UTC
Created attachment 1647290 [details]
Providing proper complete logs for the bz

Comment 3 Sunil Angadi 2019-12-26 11:42:19 UTC
*** Bug 1786594 has been marked as a duplicate of this bug. ***

Comment 16 errata-xmlrpc 2020-05-19 17:31:40 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/RHSA-2020:2231


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