flyteplugins.union.errors

Volume-specific runtime errors.

These subclass the :mod:flyte.errors taxonomy, so they keep flyte’s system/user recoverability classification (and their str() is the message), while giving callers a stable flyteplugins.union.errors surface to catch — e.g. except VolumeMountError or, more broadly, except VolumeError (system) / except VolumeUsageError (caller misuse).

Each concrete type carries a fixed error code (surfaced on the flyte error envelope) via the _code class attribute; subclasses just override it.

Directory

Errors

Exception	Description
`VolumeCommandError`	A backend CLI invocation (e.
`VolumeError`	Base for Volume system failures — infra/runtime problems the caller.
`VolumeMigrateNoop`	Metadata-store migration was requested to the store type already in use.
`VolumeMountError`	The volume could not be mounted — the client exited prematurely, the.
`VolumeMountTimeout`	The mount did not become a FUSE mountpoint within the timeout.
`VolumeNoIndex`	An operation needs a published index, but the Volume has none.
`VolumeNotForkable`	Fork was requested on a Volume that is neither mounted nor has an index.
`VolumeNotMounted`	An operation that needs a live mount was called on an unmounted Volume.
`VolumeStoreTypeNotSet`	The Volume’s `metadata_store_type` is unset and couldn’t be resolved.
`VolumeUnmountError`	The volume could not be unmounted (`fusermount` kept returning EBUSY).
`VolumeUsageError`	Base for Volume user errors — caller misuse the caller can fix.