Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1360384 - No cross-linking of OpenShift node to OpenStack instance
No cross-linking of OpenShift node to OpenStack instance
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.6.0
Unspecified Unspecified
high Severity high
: GA
: 5.6.1
Assigned To: Ari Zellner
Jaroslav Henner
container:smartstate
: ZStream
Depends On: 1355911
Blocks:
  Show dependency treegraph
 
Reported: 2016-07-26 10:47 EDT by Chris Pelland
Modified: 2016-08-29 17:32 EDT (History)
10 users (show)

See Also:
Fixed In Version: 5.6.1.2
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1355911
: 1371263 (view as bug list)
Environment:
Last Closed: 2016-08-18 14:00:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1634 normal SHIPPED_LIVE Important: CFME 5.6.1 security, bug fix, and enhancement update 2016-08-18 17:43:52 EDT

  None (edit)
Comment 1 Ari Zellner 2016-07-26 12:27:53 EDT
Darga PR: https://github.com/ManageIQ/manageiq/pull/10061
Comment 4 errata-xmlrpc 2016-08-18 14:00:05 EDT
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://rhn.redhat.com/errata/RHSA-2016-1634.html
Comment 5 Jaroslav Henner 2016-08-24 11:44:03 EDT
It doesn't reproduce with OS 3.2 on OpenStack 9, with none of:

 * cfme 5.6.0.13.20160624114606_13a9153
 * cfme 5.6.1.2.20160810181333_8ba817b

I will test on OS8 tomorrow

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