Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1442765 - UI: Unable to create cloud volume
UI: Unable to create cloud volume
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.8.0
Unspecified Unspecified
high Severity high
: GA
: 5.9.0
Assigned To: Alexander Demicev
Ola Pavlenko
ui:storage:volume
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-17 08:58 EDT by Satyajit Bulage
Modified: 2018-03-01 08:11 EST (History)
9 users (show)

See Also:
Fixed In Version: 5.9.0.5
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-01 08:11:36 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack


Attachments (Terms of Use)
Screenshot showing actual results (63.63 KB, image/png)
2017-04-17 08:58 EDT, Satyajit Bulage
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0380 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 13:37:12 EST

  None (edit)
Description Satyajit Bulage 2017-04-17 08:58:10 EDT
Created attachment 1272061 [details]
Screenshot showing actual results

Description of problem: Add cloud volume is not working, showing two entries for the same volume. One entry having status Creating and anther having an error. See attached screenshot.


Version-Release number of selected component (if applicable): 5.8.0.10-beta1.20170411212748_e47d319 


How reproducible:100%


Steps to Reproduce:
1. Navigate to Storage --> Block Storage --> Volumes
2. Add Volume and wait for some time
3. 

Actual results: After some time on Volumes page displaying 2 entries for the same Volume.


Expected results: Cloud Volume should be added without any error.


Additional info:
Comment 10 errata-xmlrpc 2018-03-01 08:11:36 EST
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-2018:0380

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