-
Notifications
You must be signed in to change notification settings - Fork 285
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
[SMAPIv3] xe sr-create
does not report an error when SR.attach
fails
#5532
Comments
ydirson
added a commit
to xcp-ng/xcp-ng-xapi-storage
that referenced
this issue
Mar 26, 2024
SR can then be disposed of using "xe sr-forget" and "zpool destroy". Underlying zpool can be either separately created and given to SR.create, or a set of devices can be specified to create a new zpool on. Notes: - `SR.attach` will be necessary to complete `sr-create`: while from a calling user PoV things appear to have gone fine, SMlog reveals a call to `SR.attach`, which naturally failed as not yet implemented. Any attempt to `xe pbd-plug` naturally also fails. See xapi-project/xen-api#5532. - there is no plugin feature to shield from SR.* calls Originally-by: Matias Ezequiel Vara Larsen <[email protected]> Signed-off-by: Yann Dirson <[email protected]>
Note this also impacts the XFS SR driver in XS8:
|
ydirson
added a commit
to xcp-ng/xcp-ng-xapi-storage
that referenced
this issue
Apr 2, 2024
FIXME: pool passed through `zpool` should get a sanity check before being accepted, and get aligned with what we otherwise create SR can then be disposed of using "xe sr-forget" and "zpool destroy". Underlying zpool can be either separately created and given to SR.create, or a set of devices can be specified to create a new zpool on. Notes: - `SR.attach` will be necessary to complete `sr-create`: while from a calling user PoV things appear to have gone fine, SMlog reveals a call to `SR.attach`, which naturally failed as not yet implemented. Any attempt to `xe pbd-plug` naturally also fails. See xapi-project/xen-api#5532. - there is no plugin feature to shield from SR.* calls Originally-by: Matias Ezequiel Vara Larsen <[email protected]> Signed-off-by: Yann Dirson <[email protected]>
ydirson
added a commit
to xcp-ng/xcp-ng-xapi-storage
that referenced
this issue
Apr 4, 2024
Pool passed through `zpool` should still get a sanity check before being accepted, and get aligned with what we otherwise create, to be completed later. SR can then be disposed of using "xe sr-forget" and "zpool destroy". Underlying zpool can be either separately created and given to SR.create, or a set of devices can be specified to create a new zpool on. Notes: - `SR.attach` will be necessary to complete `sr-create`: while from a calling user PoV things appear to have gone fine, SMlog reveals a call to `SR.attach`, which naturally failed as not yet implemented. Any attempt to `xe pbd-plug` naturally also fails. See xapi-project/xen-api#5532. - there is no plugin feature to shield from SR.* calls Originally-by: Matias Ezequiel Vara Larsen <[email protected]> Signed-off-by: Yann Dirson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
xe sr-create
includes auto-plugging the PBD, and as such afterSR.create
callsSR.attach
. If for any reasonSR.attach
fails, this can only be seen by an error lone inSMlog
- the problem is not reported to the user making the call.The text was updated successfully, but these errors were encountered: