Skip to content

Use powershell command Get-item. target to get target symlink issue #93759

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

Closed
jingxu97 opened this issue Aug 6, 2020 · 4 comments
Closed

Use powershell command Get-item. target to get target symlink issue #93759

jingxu97 opened this issue Aug 6, 2020 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/windows Categorizes an issue or PR as relevant to SIG Windows.

Comments

@jingxu97
Copy link
Contributor

jingxu97 commented Aug 6, 2020

As a workaround solution for issue, golang/go#39786, I used powershell command "(Get-Item -Path %s ).Target" to get the target symlink. However, it does not work under following situation.

  1. PD disk attached to Windows node, partitioned and formatted
  2. create a symlink /var/lib/kubelet/plugins/... to the volume
  3. create a symlink for pod volume to the above link /var/lib/kubelet/pod/xx/volume/xxx
  4. create a subdir under the path in step 3 /var/lib/.../volume/xxx/subpath

When using powershell command to get the target link, it works for path 3, but not path 4.
Run command (Get-item -Path /var/lib/kubelet/pod/xx/volume/xxx).Target, it will get path /var/lib/kubelet/plugins/... correctly,
but (Get-item -Path /var/lib/kubelet/pod/xx/volume/xxx/subpath).Target, it will return C:/subpath which does not exist.

@jingxu97 jingxu97 added the kind/bug Categorizes issue or PR as related to a bug. label Aug 6, 2020
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 6, 2020
@jingxu97 jingxu97 added the sig/windows Categorizes an issue or PR as relevant to SIG Windows. label Aug 6, 2020
@k8s-ci-robot k8s-ci-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 6, 2020
@jingxu97 jingxu97 added the sig/storage Categorizes an issue or PR as relevant to SIG Storage. label Aug 6, 2020
jingxu97 added a commit to jingxu97/kubernetes that referenced this issue Aug 15, 2020
sharadg pushed a commit to sharadg/kubernetes that referenced this issue Oct 23, 2020
@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 Nov 4, 2020
jingxu97 added a commit to jingxu97/kubernetes that referenced this issue Nov 20, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 4, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/windows Categorizes an issue or PR as relevant to SIG Windows.
Projects
None yet
Development

No branches or pull requests

3 participants