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.

Sign up for GitHub

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

Jump to bottom

Propagate flexvolumes errors #400

Open
LilliJane opened this issue Apr 12, 2018 · 2 comments
Open

Propagate flexvolumes errors #400

LilliJane opened this issue Apr 12, 2018 · 2 comments
Assignees
@advdv @Overv
Labels
Design Required major P0

Comments

@LilliJane
Copy link
Contributor

Expected Behavior

Users should be able to identify a flexvolume related issue easily.

Actual Behavior

At the moment we don't have any easy way to inform our users about what's happening with flexvolumes (from expected behavior to important errors).

One option could be to store the metadata in the dataset (#255).

This issue is opened so we can share ideas and opinions about a new design
@LilliJane
Copy link
Contributor Author

If an output dataset is too big, the flexvolume will try to upload it, which will fail. In this case, we just delete the dataset and unmount the volumes, but users don't have any way to understand why their output dataset is empty.

@LilliJane
Copy link
Contributor Author

It would be interesting to publish events to propagate the errors but also the status of a dataset. And with Kubernetes 1.9, they introduced a way to filter events by objects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@advdv advdv

@Overv Overv

Labels
Design Required major P0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@advdv @Overv @LilliJane