Bug #18521

VM orchestration should provide better error reporting and logging

Added by Tomáš Strachota over 1 year ago. Updated over 1 year ago.

Assigned To:-
Category:Compute resources - VMware
Target version:Team Marek backlog
Difficulty: Bugzilla link:1396974
Found in release: Pull request:
Story points-
Velocity based estimate-


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.


#1 Updated by Tomáš Strachota over 1 year ago

  • Bugzilla link set to 1396974

Also available in: Atom PDF