Bug 1562355 - Cloud Volume creation error does not raise VM provision error
Summary: Cloud Volume creation error does not raise VM provision error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.10.0
Assignee: Alexander Demicev
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks: 1578125
TreeView+ depends on / blocked
 
Reported: 2018-03-30 10:26 UTC by Imaan
Modified: 2022-03-13 14:49 UTC (History)
8 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1578125 (view as bug list)
Environment:
Last Closed: 2019-02-11 14:00:28 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Imaan 2018-03-30 10:26:01 UTC
Description of problem:

During VM provision workflow, the error in volume attachment on provider side does not raise the ERROR and VM provisioning state machine continues to work until it reaches the maximum number of retries.

There is do_volume_creation_check [1] method and this method check only "available" status and does not handle "error" status.

There should be error handling for error state on provider side just as it is done for VM provision error [2]

[1] https://github.com/ManageIQ/manageiq-providers-openstack/blob/master/app/models/manageiq/providers/openstack/cloud_manager/provision/volume_attachment.rb#L31

[2] https://github.com/ManageIQ/manageiq-providers-openstack/blob/master/app/models/manageiq/providers/openstack/cloud_manager/provision/cloning.rb#L21

Version: Red Hat CloudForms 4.5

Comment 2 Tina Fitzgerald 2018-04-02 19:15:50 UTC
Hi Marek,

Re-assigning to you since this looks like an Openstack specific issue.

Thanks,
Tina

Comment 5 Jad Haj Yahya 2018-12-02 09:08:14 UTC
Hi Alex,

Could you provide steps to reproduce

Thanks

Comment 6 Ido Ovadia 2018-12-17 09:20:56 UTC
Verified
========
5.10.0.28


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