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

Need to check VolumeContentSource if creating volume from snapshot #280

Closed
xing-yang opened this issue May 17, 2019 · 1 comment · Fixed by #283
Closed

Need to check VolumeContentSource if creating volume from snapshot #280

xing-yang opened this issue May 17, 2019 · 1 comment · Fixed by #283
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@xing-yang
Copy link
Contributor

In Provision, we should check if VolumeContentSource is populated if creating volume from snapshot is successful and log event to indicate its status.

Note: This needs to be fixed in the CSI hostpath driver first. Otherwise, CI won't pass.
kubernetes-csi/csi-driver-host-path#50

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 15, 2019
kbsonlong pushed a commit to kbsonlong/external-provisioner that referenced this issue Dec 29, 2023
Add server listening log; fix wrong address logged in listening error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants