Actions
Bug #18521
closedVM orchestration should provide better error reporting and logging
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Compute resources - VMware
Target version:
-
Description
When compute orchestration on vmWare fails for example due to insufficient permissions for creating hosts (see Required permissions in: https://theforeman.org/manuals/1.14/index.html#5.2.9VMwareNotes) UI reports no errors. API returns message "resource have no errors" which isn't any better.
We must make sure that such errors are logged, reported to users with a meaningful message and ideally with a hint containing some troubleshooting steps.
Updated by Chris Roberts over 5 years ago
- Status changed from New to Duplicate
- Triaged set to No
Dupe of:
24186
Actions