Bug 1508451

Summary:	[ceph-iscsi-cli]: pools and images with hyphens ('-') are rejected by the API
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Jason Dillaman <jdillama>
Component:	iSCSI	Assignee:	Jason Dillaman <jdillama>
Status:	CLOSED ERRATA	QA Contact:	Manohar Murthy <mmurthy>
Severity:	medium	Docs Contact:	Bara Ancincova <bancinco>
Priority:	medium
Version:	3.0	CC:	ceph-eng-bugs, ceph-qe-bugs, jbrier, jdillama, tchandra
Target Milestone:	rc
Target Release:	3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-iscsi-cli-2.7-1.el7cp	Doc Type:	Bug Fix
Doc Text:	.Pools and images with hyphens ('-') are no longer rejected by the API Previously, the iSCSI `gwcli` utility did not support hyphens in pool or image names. As such it was not possible to create a disk using a pool or image name that included hyphens ("-") by using the iSCSI `gwcli` utility. With this update to {product}, the iSCSI `gwcli` utility correctly handles hyphens. As such creating a disk using a pool or image name with hyphens is now supported.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-26 18:16:43 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:	1494421, 1584264

Description Jason Dillaman 2017-11-01 13:05:18 UTC

Description of problem:
Pools or images with hyphens in their name are rejected by the API and cannot be used. This restriction should not exist and should be relaxed.

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

How reproducible:
100%

Steps to Reproduce:
1. use gwcli
2. attempt to create a disk using a pool or image name that includes a hyphen

Actual results:
The disk creation is rejected by the API

Expected results:
The disk creation should succeed.

Comment 12 errata-xmlrpc 2018-09-26 18:16:43 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-2018:2819