Bug 1518630 - When adding or updating an OpenStack Volume Name, Provider or target refresh is not executed
Summary: When adding or updating an OpenStack Volume Name, Provider or target refresh ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.10.0
Assignee: Marek Aufart
QA Contact: Omri Hochman
URL:
Whiteboard: testathon
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-29 11:18 UTC by Loic Avenel
Modified: 2019-02-07 23:00 UTC (History)
8 users (show)

Fixed In Version: 5.10.0.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 23:00:39 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:0212 0 None None None 2019-02-07 23:00:46 UTC

Description Loic Avenel 2017-11-29 11:18:53 UTC 
Description of problem: When adding or updating an OpenStack Volume Name, Provider or target refresh is not executed


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


How reproducible: Always


Steps to Reproduce:
1. Go to Network>OpenStack Cinder
2. select a volume, update it
3. Information are not refreshed

Actual results:


Expected results:


Additional info:
Comment 3 Sam Lucidi 2018-08-13 20:10:48 UTC 
https://github.com/ManageIQ/manageiq-content/pull/401
Comment 4 Danylo Kholodov 2018-09-10 10:15:59 UTC 
Verified at the CFME 5.10.0.14
Comment 5 errata-xmlrpc 2019-02-07 23:00:39 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/RHSA-2019:0212
Note You need to log in before you can comment on or make changes to this bug.