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

Administrator operations error reporting #296

Open
pferrel opened this issue Apr 9, 2021 · 2 comments
Open

Administrator operations error reporting #296

pferrel opened this issue Apr 9, 2021 · 2 comments
Assignees
Milestone

Comments

@pferrel
Copy link
Collaborator

pferrel commented Apr 9, 2021

can we store error status for engine add, update, delete so that future status will report errors that are only in the logs. We are only reporting these possible errors in logs with the etcd async engine ops.

@pferrel
Copy link
Collaborator Author

pferrel commented Apr 9, 2021

The engine ops are now async with the REST calls. This is somewhat like how we handle hctl import ... and hctl train ... as "jobs". However engine ops are tied to the Administrator, not a specific engine so they may have a different lifecycle and status info. If we stored some info with other jobs, then errors that had only gone to the server logs can be stored in a form where they can be retrieved in an hctl status engines ... call.

@pferrel pferrel self-assigned this Apr 9, 2021
@pferrel pferrel added this to the future milestone Apr 9, 2021
@pferrel
Copy link
Collaborator Author

pferrel commented Apr 9, 2021

only applies to Harness 1.0+

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant