-
Notifications
You must be signed in to change notification settings - Fork 108
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
Bug 1902710: UPSTREAM: 89726: Backward support for old KVM driver #473
Conversation
@mandre: This pull request references Bugzilla bug 1902710, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mandre The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
735db15
to
80235d3
Compare
/retest |
1 similar comment
/retest |
@mandre: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/hold this got rotten upstream and closed. Please reopen and get it merged. |
Thanks @sttts, I just noticed @jsafrane had a similar change at kubernetes#96673. |
@mandre: Closed this PR. In response to this:
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. |
@mandre: This pull request references Bugzilla bug 1902710. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state. In response to this:
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. |
With newer versions of OpenStack/libvirt, the path of the attached block storage volume now contains the full volume ID when using virtio-scsi.
The problem is described in the upstream OpenStack cloud provider repository on github [1] and k8s/community [2] and was fixed already for the external cloud provider [3]. However, the fix was never merged for the in-tree cloud provider [4].
Without this change, the Cinder PVC times out attaching the storage to the node when using virtio-scsi and the in-tree cinder provisioned on OSP16.
Kubelet logs show:
Nov 30 12:38:35 mandre-psi-pub-stlh7-worker-0-b4xhh hyperkube[1868]: W1130 12:38:35.640309 1868 openstack_volumes.go:576] Failed to find device for the volumeID: "bcc21b3e-23fa-4464-844c-62506e298744"
Nov 30 12:38:35 mandre-psi-pub-stlh7-worker-0-b4xhh hyperkube[1868]: E1130 12:38:35.640319 1868 attacher.go:249] Error: could not find attached Cinder disk "bcc21b3e-23fa-4464-844c-62506e298744" (path: ""):
[1] kubernetes/cloud-provider-openstack#852
[2] kubernetes/community#4797
[2] kubernetes/cloud-provider-openstack#853
[3] kubernetes#89726