Actions
Bug #9251
closed
User story #8844: Redesign Rudder web interface
Infamous "Server cannot be contacted at this time" when trying to access node details of a deleted node
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
If we delete a node, and reload the page, we get the awful "Server cannot be contacted at this time", because code raises an exception.
See excerpt of logs:
[2016-10-06 15:25:38] ERROR com.normation.rudder.web.components.ShowNodeDetailsFromNode - Could not get Node 'd48a5baa-3c30-4ad3-a5f3-34510cdcde7c' details because it does not exist [2016-10-06 15:25:38] ERROR net.liftweb.http.LiftRules - Exception being returned to browser when processing /ajax_request/F1114631579519LKBYPG-00/ java.lang.Exception: Could not get Node 'd48a5baa-3c30-4ad3-a5f3-34510cdcde7c' details because it does not exist [2016-10-06 15:25:39] ERROR com.normation.rudder.web.components.ShowNodeDetailsFromNode - Could not get Node 'd48a5baa-3c30-4ad3-a5f3-34510cdcde7c' details because it does not exist [2016-10-06 15:25:39] ERROR net.liftweb.http.LiftRules - Exception being returned to browser when processing /ajax_request/F1114631579519LKBYPG-00/ java.lang.Exception: Could not get Node 'd48a5baa-3c30-4ad3-a5f3-34510cdcde7c' details because it does not exist
Updated by 
Updated by 
Updated by 
Updated by
Actions