https://github.com/ManageIQ/manageiq/pull/6592
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/eeedeed1830d225d40eafbc3960ccb4f86727e32 commit eeedeed1830d225d40eafbc3960ccb4f86727e32 Author: Ladislav Smola <lsmola> AuthorDate: Wed Feb 10 16:37:07 2016 +0100 Commit: Ladislav Smola <lsmola> CommitDate: Wed Feb 10 18:17:29 2016 +0100 OpenStack ignore missing volume mountpoint Seems like after some operations, the mountpoit of volume can get missing. Let's ignore that fact and log warn. Fixes BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1304740 .../manageiq/providers/openstack/cloud_manager/refresh_parser.rb | 6 ++++++ 1 file changed, 6 insertions(+)
https://github.com/ManageIQ/manageiq/pull/6577
Detected commit referencing this ticket while ticket status is MODIFIED.
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=37a97bbb80020d7aa09b32cbc50542fe53b2dffd commit 37a97bbb80020d7aa09b32cbc50542fe53b2dffd Author: Ladislav Smola <lsmola> AuthorDate: Wed Feb 10 16:37:07 2016 +0100 Commit: Ladislav Smola <lsmola> CommitDate: Mon Mar 7 14:01:12 2016 +0100 OpenStack ignore missing volume mountpoint Seems like after some operations, the mountpoit of volume can get missing. Let's ignore that fact and log warn. Fixes BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1304740 .../manageiq/providers/openstack/cloud_manager/refresh_parser.rb | 6 ++++++ 1 file changed, 6 insertions(+)
Please add verification steps.
same verification as in this https://bugzilla.redhat.com/show_bug.cgi?id=1306362
Whether am I missing any step, please let me know...?
CloudForms inventory is not failing when an openstack cinder volume contains no 'device' directive in the attachments property. Also, link is broken when mount point is null. Verified Version :-5.6.0.5-beta2.4.20160503153816_1fb554f
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/RHBA-2016:1348