Bug 1279435 - undefined method `block_storage_disk_usage' for nil:NilClass [ems_cluster/show]
Summary: undefined method `block_storage_disk_usage' for nil:NilClass [ems_cluster/show]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.5.0
Assignee: Richard Su
QA Contact: Marius Cornea
URL:
Whiteboard: openstack
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-09 13:04 UTC by Marius Cornea
Modified: 2015-12-08 13:45 UTC (History)
9 users (show)

Fixed In Version: 5.5.0.11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-08 13:45:36 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2551 0 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 17:58:09 UTC

Description Marius Cornea 2015-11-09 13:04:19 UTC
Description of problem:
When going to the BlockStorage deployment role the following error shows up:
undefined method `block_storage_disk_usage' for nil:NilClass [ems_cluster/show]

Version-Release number of selected component (if applicable):
5.5.0.9-beta2.20151102161742_5530c9a

How reproducible:
100%

Steps to Reproduce:
1. Add Openstack Plaftorm Director provider with at least 1 block storage node
2. Go to Infrastructure - Deployment Roles
3. Click on the large icons listing
4. Click on the Block storage role (e.g. overcloud-BlockStorage-vosex3dykmos)

Actual results:
undefined method `block_storage_disk_usage' for nil:NilClass [ems_cluster/show]

Expected results:
The Block storage deployment role details show up.

Comment 2 Richard Su 2015-11-16 15:41:39 UTC
Merged, https://github.com/ManageIQ/manageiq/pull/5394

Comment 5 errata-xmlrpc 2015-12-08 13:45:36 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-2015:2551


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