Project

General

Profile

Bug #27972

Can't edit hosts if compute resource is inaccessible

Added by Adam Winberg 12 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

We use vmware as compute resource, and if our vCenter server is down for some reason we can't edit hosts at all in Foreman. We only get the error message:

 Oops, we're sorry but something went wrong Got HTTP 503: Service unavailable

It would make more sense in these instances if just the vm configuration tab was inaccessible. As it is now, we cant edit any puppet parameters even though they are completely independent of any compute resource capabilities.

Also available in: Atom PDF