Bug 1625970 - giving volume name shouldn't be mandatory in case of Openstack instance provisioning
Summary: giving volume name shouldn't be mandatory in case of Openstack instance provi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.9.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.10.0
Assignee: Alexander Demicev
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks: 1629124
TreeView+ depends on / blocked
 
Reported: 2018-09-06 10:10 UTC by Niladri Roy
Modified: 2021-12-10 17:22 UTC (History)
9 users (show)

Fixed In Version: 5.10.0.15
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1629124 (view as bug list)
Environment:
Last Closed: 2019-02-12 16:50:53 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Niladri Roy 2018-09-06 10:10:27 UTC
Description of problem:
While lifecycle or service provisioning under the volumes tab, if the volume name is not provided the provisioning errors out with below

[----] E, [2018-09-06T01:48:10.143087 #24651:a87140] ERROR -- : Q-task_id([miq_provision_1040000000000142]) MIQ(ManageIQ::Providers::Openstack::CloudManager::Provision#provision_error) [[ArgumentError]: name is required for this operation] encountered during phase [prepare_volumes]

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

How reproducible:
Always

Steps to Reproduce:
1. Perform a provisioning from Lifecycle button
2. enter all required details
3. in volumes tab, enter only volume size and check "delete volume on instance terminate" [leave the volume name as empty]
4. click submit and provision

Actual results:
[[ArgumentError]: name is required for this operation] encountered during phase [prepare_volumes]

Expected results:
volume name shouldn't be mandatory as Cu doesn't want to enter a new volume name everytime

Additional info:

Comment 6 Niladri Roy 2018-09-10 09:58:15 UTC
Hi Marek,

Cu is provisioning through service catalogs and they already have given a volume size (in the catalog).
They don't want to enter a new volume name everytime and they don't want the same volume name for every instance
random volume name should be good

So Cu requirement is, if the volume name field is blank, a volume with random volume name should get created

I have asked Cu that if they are OK with UUID (a random number) being the volume name for the newly created volume. I guess that would make things simpler

Comment 10 Ido Ovadia 2018-11-15 12:57:55 UTC
Verified
========
5.10.0.23


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