Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FSunstone] Forward oneflow errors properly #6529

Closed
2 of 3 tasks
vichansson opened this issue Mar 8, 2024 · 0 comments · Fixed by OpenNebula/docs#2888
Closed
2 of 3 tasks

[FSunstone] Forward oneflow errors properly #6529

vichansson opened this issue Mar 8, 2024 · 0 comments · Fixed by OpenNebula/docs#2888

Comments

@vichansson
Copy link
Contributor

vichansson commented Mar 8, 2024

Description
FireEdge should properly forward any errors coming from oneflow. Currently the generic Request failed with status code 500 is being used as the error message parsing fails in FireEdge.

To Reproduce
Produce any type of error, for example, attempt adding a new role to a service that's not been deployed properly.

Expected behavior
FireEdge should properly forward the error message from oneflow, in this case:
Cannot modify roles in state: FAILED_DEPLOYING

Details

  • Affected Component: [FireEdge]
  • Version: [development, 6.8]

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
@vichansson vichansson self-assigned this Mar 8, 2024
@tinova tinova added this to the Release 7.0 milestone Mar 11, 2024
vichansson added a commit to OpenNebula/docs that referenced this issue Apr 11, 2024
Signed-off-by: Victor Hansson <vhansson@opennebula.io>
@vichansson vichansson linked a pull request Apr 11, 2024 that will close this issue
2 tasks
tinova pushed a commit to OpenNebula/docs that referenced this issue Apr 11, 2024
Signed-off-by: Victor Hansson <vhansson@opennebula.io>
@tinova tinova modified the milestones: Release 7.0, Release 6.10.0 Apr 17, 2024
@tinova tinova closed this as completed Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants