openshift/openshift-ansible

OpenStack Cinder can report an incorrect device path for volume attachments

salareinavipour opened this issue · 4 comments

salareinavipour commented

OKD version: 3.11

Environment:

  • Cloud provider:
    OpenStack
  • Block storage solution for OKD:
    Cinder

Problem:

OKD uses volume device names based on Cinder API info but PVs created by Cinder have different device names than what OS of hosts shows(e.g., host shows volume is mounted to /dev/vdb, Cinder shows volume is mounted to /dev/vdc on instance).
This can lead to volumes not mounting to pods:

Unable to mount volumes for pod "example_example(6a66157c-2d66-11ea-a01b-fa163ebf7f7d)": timeout expired waiting for volumes to attach or mount for pod "example"/"example"

Possible solution:

As @kiall mentioned in this issue:

Kubernetes(here OKD) should avoid using the known-broken data supplied by Cinder, and detect the device path based on the cinder volume ID, supplied to the instance as the drive serial number.

openshift-bot commented

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

openshift-bot commented

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.