Bug 1761610

Summary:	installing ansible-runner-service setup script does not create an iso directory
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Paul Cuzner <pcuzner>
Component:	Ceph-Installer	Assignee:	Paul Cuzner <pcuzner>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	aschoen, ceph-eng-bugs, ceph-qe-bugs, mmurthy, nthomas, tserlin, ykaul
Target Milestone:	rc
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-ceph-installer-0.9-2.el8cp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-31 12:47:36 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:

Description Paul Cuzner 2019-10-14 21:19:16 UTC

Description of problem:
After installing cockpit-ceph-installer, you run the ansible-runner-service script to standup the ansible api service. this script creates the directories used by the container, but is missing an ISO directory required for the ceph-ansible ISO installation method.

Version-Release number of selected component (if applicable):
cockpit-ceph-installer-0.9-1

How reproducible:
100%

Steps to Reproduce:
1. install cockpit-ceph-installer
2. run ansible-runner-service.sh
3. look at the directory under /usr/share/ansible-runner-service - iso is missing

Actual results:
missing iso directory

Expected results:
iso should be there by default

Additional info:

Comment 1 RHEL Program Management 2019-10-14 21:19:24 UTC

Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 2 Paul Cuzner 2019-10-15 22:50:06 UTC

fixed in upstream commit 4b4a52b99bb396e532dc06cf6561128e89925891

Comment 6 errata-xmlrpc 2020-01-31 12:47: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, 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:0312