Red Hat Bugzilla – Bug 1290788
undefined method `id' for nil:NilClass when trying to display all containers
Last modified: 2016-04-22 01:00:14 EDT
Created attachment 1104649 [details]
Description of problem:
Unknown failure when trying to display all containers.
Logs and screenshot in attachment.
Steps to Reproduce:
1. Unknown, but it's possible that is related to displaying containers during refreshes (containers removed)
A fatal error happens when trying to display all containers.
It should be possible to list all containers.
From the log it seems that a provider refresh was issued:
[----] I, [2015-12-05T15:22:31.310196 #14031:45798c] INFO -- : Started POST "/ems_container/button/1?pressed=ems_container_refresh" for 127.0.0.1 at 2015-12-05 15:22:31 -0500
and right after that navigating to the container explorer (GET "/container/explorer"):
[----] I, [2015-12-05T15:22:36.109044 #14031:45798c] INFO -- : Started GET "/container/explorer" for 127.0.0.1 at 2015-12-05 15:22:36 -0500
[----] I, [2015-12-05T15:22:36.110139 #14031:45798c] INFO -- : Processing by ContainerController#explorer as HTML
[----] I, [2015-12-05T15:22:36.165944 #14031:45798c] INFO -- : Rendered layouts/_flash_msg.html.haml (0.0ms)
[----] I, [2015-12-05T15:22:36.169932 #14031:45798c] INFO -- : Rendered layouts/_perf_options.html.haml (3.8ms)
[----] I, [2015-12-05T15:22:36.170026 #14031:45798c] INFO -- : Rendered layouts/_performance.html.haml (4.2ms)
[----] I, [2015-12-05T15:22:36.170078 #14031:45798c] INFO -- : Rendered container/explorer.html.haml within layouts/application (4.4ms)
[----] F, [2015-12-05T15:22:36.170314 #14031:45798c] FATAL -- : Error caught: [NoMethodError] undefined method `id' for nil:NilClass
(more logs in attachment)
triggered calling _perf_options.html.haml probably because of bug 1286247, fixed with:
I think that such fix can alleviate this bug but we should make sure that if the @record is nil (current container, or any other entity, is deleted all the possible views are not crashing)
Created attachment 1104650 [details]
I can't reproduce the failure.
Might caused by the container controller refactor or different change related to containers Timelines/Utilization, if that's the case it should be OK.
Federico, Is there something you want me to do with this bug?
(In reply to Daniel Korn from comment #3)
> Federico, Is there something you want me to do with this bug?
Let's wait and see if it reproduces (as we don't have clear steps to trigger this and check if it's fixed or not).
Closing this until we see it again... if so, please reopen