Skip to content

Scheduler API request error messages need to have detailed errors #181

@Sindica

Description

@Sindica

Currently, scheduler failures due to API service call does not have clear error message in log. For example, registration returned with not enough capacity only shows JSON error in scheduler log. List failure with message being trunked is shows as JSON error with '{".

This is confusing and can delay development/testing.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions