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

creating a DiskPool with incorrect path cannot be corrected due to: Failed to create a BDEV #1521

Closed
aep opened this issue Oct 12, 2023 · 1 comment
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one

Comments

@aep
Copy link

aep commented Oct 12, 2023

  1. i created a disk pool with a typo in the path
  2023-10-12T14:54:46.608479Z ERROR operator_diskpool: The block device(s): dev/disk/by-id/nvme-SAMSUNG_MZQL23T8HCLS-00A07_S64HNN0W100247 can not be found
  1. so i corrected the mistake by adding the missing /
    after kubectl apply, mayastor-operator-diskpool is stuck with
 2023-10-12T14:58:13.517578Z ERROR operator_diskpool: Unable to create or import pool error in response: status code '409 Conflict', content: 'RestJsonError { details: "", message: "SvcError :: Deleting: Pool Resource pending deletion - please retry", kind: Deleting }'
    at k8s/operators/src/pool/main.rs:304
    in operator_diskpool::create_or_import with name: "pool-uca2k", status: Some(DiskPoolStatus { cr_state: Creating, pool_status: None, capacity: 0, used: 0, available: 0 })
    in operator_diskpool::reconcile with name: uca2k, status: Some(DiskPoolStatus { cr_state: Creating, pool_status: None, capacity: 0, used: 0, available: 0 })
    in kube_runtime::controller::reconciling object with object.ref: DiskPool.v1beta1.openebs.io/pool-uca2k.mayastor, object.reason: error policy requested retr
  1. so i tried deleting the object, but that's not possible:


  2023-10-12T15:13:21.566660Z ERROR openapi::clients::tower::configuration: failed to issue request, status: 500 Internal Server Error
    at openapi/src/clients/tower/configuration.rs:238
    in openapi::clients::tower::configuration::HTTP with http.method: DELETE, http.url: http://mayastor-api-rest:8081/v0/nodes/uca2k/pools/pool-uca2k, otel.name: DELETE http://mayastor-api-rest:8081/v0/nodes/uca2k/pools/pool-uca2k, otel.kind: "client", http.status_code: 500, otel.status_code: "ERROR", otel.status_code: "ERROR", http.status_code: 500
    in operator_diskpool::delete_pool with name: "pool-uca2k", status: Some(DiskPoolStatus { cr_state: Terminating, pool_status: Some(Unknown), capacity: 0, used: 0, available: 0 })
    in operator_diskpool::delete_finalizer with attempt_delete: true, name: "pool-uca2k"
    in operator_diskpool::reconcile with name: uca2k, status: Some(DiskPoolStatus { cr_state: Terminating, pool_status: Some(Unknown), capacity: 0, used: 0, available: 0 })
    in kube_runtime::controller::reconciling object with object.ref: DiskPool.v1beta1.openebs.io/pool-uca2k.mayastor, object.reason: reconciler requested retry

  2023-10-12T15:13:21.566794Z ERROR operator_diskpool: e: CleanupFailed(Response { source: Expected(ResponseContent { status: 500, body: RestJsonError { details: "import_pool::status: Internal, message: \"Failed to create a BDEV '/disk/by-id/nvme-SAMSUNG_MZQL23T8HCLS-00A07_S64HNN0W100247'\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"date\": \"Thu, 12 Oct 2023 15:13:21 GMT\", \"content-length\": \"0\"} }", message: "SvcError::GrpcRequestError", kind: Internal } }) })
    at k8s/operators/src/pool/main.rs:596
    in operator_diskpool::reconcile with name: uca2k, status: Some(DiskPoolStatus { cr_state: Terminating, pool_status: Some(Unknown), capacity: 0, used: 0, available: 0 })
    in kube_runtime::controller::reconciling object with object.ref: DiskPool.v1beta1.openebs.io/pool-uca2k.mayastor, object.reason: reconciler requested retry





note that the path is still wrong. i said dev/disk , correcting it to /dev/disk. i never specifed /disk

@aep aep added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one label Oct 12, 2023
@tiagolobocastro
Copy link
Contributor

This has been fixed by #1552 and should be released as part of 2.5 soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one
Projects
None yet
Development

No branches or pull requests

3 participants