[FSunstone] Overall improvements to the error reporting

[vichansson]

Description In a lot of cases, the error messages reported by oned are shadowed by a generic one in FireEdge. This leads to a lot of uncertainty and reduces debuggability.

Use case Receive all core error messages directly in FireEdge & using a generic one as the last resort.

Interface Changes No interface changes necessary, visually the reporting mechanism is sufficient.

Examples In FireEdge if you try logging in with the wrong user, you will get no feedback when the log in fails. This is the error message reported in oned.log and should be forwarded to FireEdge so that the user will be made aware of the failed log in attempt: [Z0][ReM][E]: Req:8512 UID:- one.user.info result FAILURE [one.user.info] User couldn't be authenticated, aborting call.

Task list

• Update field names to be more descriptive as these names are part of the error message displayed to the user

Additional Context

Related to:

• https://github.com/OpenNebula/one/issues/6529
• https://github.com/OpenNebula/one/issues/6553

Progress Status

• [ ] Code committed
• [ ] Testing - QA
• [ ] Documentation (Release notes - resolved issues, compatibility, known issues)