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.

Sign up for GitHub

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

Jump to bottom

Kubelet.exe on Windows Server Core 1809 - Errors with Failed create pod sandbox.. rpc error: code - Unknown desc ... hnsCall Failed in Win32: The object already exits #72696

Closed
pcdavies opened this issue Jan 8, 2019 · 8 comments
Closed

Kubelet.exe on Windows Server Core 1809 - Errors with Failed create pod sandbox.. rpc error: code - Unknown desc ... hnsCall Failed in Win32: The object already exits #72696

pcdavies opened this issue Jan 8, 2019 · 8 comments
Labels
area/provider/vmware Issues or PRs related to vmware provider kind/bug Categorizes issue or PR as related to a bug. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/windows Categorizes an issue or PR as relevant to SIG Windows.

Comments

@pcdavies
Copy link

pcdavies commented Jan 8, 2019 •
edited
Loading

What happened:

Using VMWare Fusion on a MAC, I have successfully deployed a CentOS Master and CentOS Node cluster. With the examples I'll provide, it is just using a simple NAT network, but I get the same result if a create a second Network with a static IP address. The Kube Cluster works perfectly. I am also able to Successfully join a Windows 1809 Core Server to the cluster following the documentation found on "https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/joining-linux-workers". I am using a Flannel network. The Windows Node shows in a ready State.

However, A failure occurs when a deployment is made to the Windows node. When I "apply" a deployment to the cluster with the nodeSelector set to beta.kubernetes.io/os: windows, the pod successfully "begins" deployment on the Windows node. (note: I'm pre-tested downloading and running the Image on the windows node with a docker command and it works, so the correct image is being downloaded).

I have deployed the example found on the previously referenced microsoft documentation, with the same result, but in the simple example shown below I used this deployment:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: iis
spec:
  replicas: 1
  selector:
    matchLabels:
      app: iis
  template:
    metadata:
      labels:
        app: iis
    spec:
      containers:
      - name: iis
        image: microsoft/iis
        resources:
          limits:
            memory: "128Mi"
            cpu: 2
        ports:
        - containerPort: 80
      nodeSelector:
        beta.kubernetes.io/os: windows

Here are the 3 nodes - knnode3w is the Windows Server Core 1809, the other nodes are CentOS 7

[kubeuser@knmaster ~]$ kubectl get nodes
NAME       STATUS   ROLES    AGE    VERSION
knmaster   Ready    master   168m   v1.13.1
knnode1    Ready    <none>   162m   v1.13.1
knnode3w   Ready    <none>   46m    v1.12.4

List of all the pods:

[kubeuser@knmaster ~]$ kubectl get pods -o wide --all-namespaces
NAMESPACE     NAME                                   READY   STATUS             RESTARTS   AGE    IP                NODE       NOMINATED NODE   READINESS GATES
default       iis-6c559f5868-vscxm                   0/1     CrashLoopBackOff   21         44m    <none>            knnode3w   <none>           <none>
kube-system   coredns-86c58d9df4-gwr57               1/1     Running            2          170m   10.244.0.6        knmaster   <none>           <none>
kube-system   coredns-86c58d9df4-qzqt6               1/1     Running            2          170m   10.244.0.7        knmaster   <none>           <none>
kube-system   etcd-knmaster                          1/1     Running            2          169m   192.168.168.141   knmaster   <none>           <none>
kube-system   kube-apiserver-knmaster                1/1     Running            2          169m   192.168.168.141   knmaster   <none>           <none>
kube-system   kube-controller-manager-knmaster       1/1     Running            2          169m   192.168.168.141   knmaster   <none>           <none>
kube-system   kube-flannel-ds-amd64-6stbk            1/1     Running            3          168m   192.168.168.141   knmaster   <none>           <none>
kube-system   kube-flannel-ds-amd64-vh7lt            1/1     Running            4          164m   192.168.168.167   knnode1    <none>           <none>
kube-system   kube-proxy-kpbvz                       1/1     Running            1          164m   192.168.168.167   knnode1    <none>           <none>
kube-system   kube-proxy-pkr65                       1/1     Running            2          168m   192.168.168.141   knmaster   <none>           <none>
kube-system   kube-scheduler-knmaster                1/1     Running            2          169m   192.168.168.141   knmaster   <none>           <none>
kube-system   kubernetes-dashboard-57df4db6b-sjqg5   1/1     Running            1          158m   10.244.1.3        knnode1    <none>           <none>

Failed POD Description

[kubeuser@knmaster ~]$ kubectl describe pod iis-6c559f5868-vscxm
Name:               iis-6c559f5868-vscxm
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               knnode3w/10.244.2.2
Start Time:         Tue, 08 Jan 2019 15:10:33 -0500
Labels:             app=iis
                    pod-template-hash=6c559f5868
Annotations:        <none>
Status:             Running
IP:                 
Controlled By:      ReplicaSet/iis-6c559f5868
Containers:
  iis:
    Container ID:   docker://f9ebe56d1a94a2c58d9318c42f7e5f213ebdb466f728c48695fc798d1207173a
    Image:          microsoft/iis
    Image ID:       docker-pullable://microsoft/iis@sha256:d87a0d0e81126544d4dca9e5b4f6b51805a3ca6f03615f5caf8e0a96d741eb97
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    -1073741510
      Started:      Tue, 08 Jan 2019 15:53:00 -0500
      Finished:     Tue, 08 Jan 2019 15:53:00 -0500
    Ready:          False
    Restart Count:  21
    Limits:
      cpu:     2
      memory:  128Mi
    Requests:
      cpu:        2
      memory:     128Mi
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-m267c (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-m267c:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-m267c
    Optional:    false
QoS Class:       Guaranteed
Node-Selectors:  beta.kubernetes.io/os=windows
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason                  Age                   From               Message
  ----     ------                  ----                  ----               -------
  Normal   Scheduled               45m                   default-scheduler  Successfully assigned default/iis-6c559f5868-vscxm to knnode3w
  Warning  FailedCreatePodSandBox  45m                   kubelet, knnode3w  Failed create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e" network for pod "iis-6c559f5868-vscxm": NetworkPlugin cni failed to set up pod "iis-6c559f5868-vscxm_default" network: error while ProvisionEndpoint(8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0,01FA9118-E56D-4D85-AE5A-86517EFDAA18,8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e): failed to create the new HNSEndpoint: hnsCall failed in Win32: The object already exists. (0x1392), failed to clean up sandbox container "8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e" network for pod "iis-6c559f5868-vscxm": NetworkPlugin cni failed to teardown pod "iis-6c559f5868-vscxm_default" network: failed to find HNSEndpoint 8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0: Endpoint 8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0 not found]
  Normal   Pulling                 44m (x3 over 45m)     kubelet, knnode3w  pulling image "microsoft/iis"
  Normal   Pulled                  44m (x3 over 44m)     kubelet, knnode3w  Successfully pulled image "microsoft/iis"
  Normal   Created                 44m (x3 over 44m)     kubelet, knnode3w  Created container
  Normal   Started                 44m (x3 over 44m)     kubelet, knnode3w  Started container
  Normal   Killing                 44m (x3 over 44m)     kubelet, knnode3w  Killing container with id docker://iis:Need to kill Pod
  Normal   SandboxChanged          25m (x473 over 45m)   kubelet, knnode3w  Pod sandbox changed, it will be killed and re-created.
  Warning  BackOff                 19s (x1055 over 44m)  kubelet, knnode3w  Back-off restarting failed container

Here is the Log (kubelet.exe.knnode3w.KNNODE3W_Administrator.log.ERROR.20190108-120851.540) from the Windows Node:

Log file created at: 2019/01/08 12:08:51
Running on machine: knnode3w
Binary: Built with gc go1.10.4 for windows/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0108 12:08:51.760198     540 server.go:731] Kubelet needs to run as uid `0`. It is being run as -1
E0108 12:10:34.923890     540 docker_sandbox.go:688] ResolvConfPath is empty.
E0108 12:10:35.561080     540 cni.go:310] Error adding network: error while ProvisionEndpoint(8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0,01FA9118-E56D-4D85-AE5A-86517EFDAA18,8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e): failed to create the new HNSEndpoint: hnsCall failed in Win32: The object already exists. (0x1392)
E0108 12:10:35.561080     540 cni.go:278] Error while adding to cni network: error while ProvisionEndpoint(8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0,01FA9118-E56D-4D85-AE5A-86517EFDAA18,8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e): failed to create the new HNSEndpoint: hnsCall failed in Win32: The object already exists. (0x1392)
E0108 12:10:35.631138     540 cni.go:330] Error deleting network: failed to find HNSEndpoint 8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0: Endpoint 8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0 not found
E0108 12:10:35.918901     540 remote_runtime.go:96] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = [failed to set up sandbox container "8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e" network for pod "iis-6c559f5868-vscxm": NetworkPlugin cni failed to set up pod "iis-6c559f5868-vscxm_default" network: error while ProvisionEndpoint(8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0,01FA9118-E56D-4D85-AE5A-86517EFDAA18,8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e): failed to create the new HNSEndpoint: hnsCall failed in Win32: The object already exists. (0x1392), failed to clean up sandbox container "8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e" network for pod "iis-6c559f5868-vscxm": NetworkPlugin cni failed to teardown pod "iis-6c559f5868-vscxm_default" network: failed to find HNSEndpoint 8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0: Endpoint 8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0 not found]
E0108 12:10:35.921900     540 kuberuntime_sandbox.go:65] CreatePodSandbox for pod "iis-6c559f5868-vscxm_default(74849a59-1381-11e9-b92d-000c293748f0)" failed: rpc error: code = Unknown desc = [failed to set up sandbox container "8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e" network for pod "iis-6c559f5868-vscxm": NetworkPlugin cni failed to set up pod "iis-6c559f5868-vscxm_default" network: error while ProvisionEndpoint(8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0,01FA9118-E56D-4D85-AE5A-86517EFDAA18,8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e): failed to create the new HNSEndpoint: hnsCall failed in Win32: The object already exists. (0x1392), failed to clean up sandbox container "8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e" network for pod "iis-6c559f5868-vscxm": NetworkPlugin cni failed to teardown pod "iis-6c559f5868-vscxm_default" network: failed to find HNSEndpoint 8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0: Endpoint 8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0 not found]
E0108 12:10:35.924902     540 kuberuntime_manager.go:657] createPodSandbox for pod "iis-6c559f5868-vscxm_default(74849a59-1381-11e9-b92d-000c293748f0)" failed: rpc error: code = Unknown desc = [failed to set up sandbox container "8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e" network for pod "iis-6c559f5868-vscxm": NetworkPlugin cni failed to set up pod "iis-6c559f5868-vscxm_default" network: error while ProvisionEndpoint(8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0,01FA9118-E56D-4D85-AE5A-86517EFDAA18,8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e): failed to create the new HNSEndpoint: hnsCall failed in Win32: The object already exists. (0x1392), failed to clean up sandbox container "8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e" network for pod "iis-6c559f5868-vscxm": NetworkPlugin cni failed to teardown pod "iis-6c559f5868-vscxm_default" network: failed to find HNSEndpoint 8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0: Endpoint 8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0 not found]
E0108 12:10:35.926903     540 pod_workers.go:186] Error syncing pod 74849a59-1381-11e9-b92d-000c293748f0 ("iis-6c559f5868-vscxm_default(74849a59-1381-11e9-b92d-000c293748f0)"), skipping: failed to "CreatePodSandbox" for "iis-6c559f5868-vscxm_default(74849a59-1381-11e9-b92d-000c293748f0)" with CreatePodSandboxError: "CreatePodSandbox for pod \"iis-6c559f5868-vscxm_default(74849a59-1381-11e9-b92d-000c293748f0)\" failed: rpc error: code = Unknown desc = [failed to set up sandbox container \"8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e\" network for pod \"iis-6c559f5868-vscxm\": NetworkPlugin cni failed to set up pod \"iis-6c559f5868-vscxm_default\" network: error while ProvisionEndpoint(8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e_cbr0,01FA9118-E56D-4D85-AE5A-86517EFDAA18,8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e): failed to create the new HNSEndpoint: hnsCall failed in Win32: The object already exists. (0x1392), failed to clean up sandbox container \"8ef4df26e9eda04371317603867f4074a0dd6146da7d390562dbf858abf3969e\" network for pod \"iis-6c559f5868-vscxm\": NetworkPlugin cni failed to teardown pod \"iis-6c559f5868-vscxm_default\" network: failed to find HNSEndpoint 8-- More  --

I ran the following commands to join the Windows Node to the Cluster:

start.ps1 -ManagementIP 192.168.168.168 -ClusterCIDR 10.244.0.0./16 -ServiceCIDR 10.96.0.0/12 -KubeDnsServiceIP 10.96.0.10

AddRoutes.ps1 192.168.168.141

What you expected to happen:

That a simple sample pod would deploy to the Windows Node.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):

On Linux:

[kubeuser@knmaster ~]$ kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:39:04Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:31:33Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}

On Windows

Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.4", GitCommit:"f49fa022dbe63faafd0da106ef7e05a29721d3f1", GitTreeState:"clean", BuildDate:"2018-12-14T07:10:00Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:31:33Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}

  • Cloud provider or hardware configuration: On Premises... running on Mac with vmware fusion Version Professional Version 10.1.5

  • OS (e.g. from /etc/os-release):

Master and Node1

NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

Windows Server

Microsoft Windows [Version 10.0.17763.107]
@pcdavies pcdavies added the kind/bug Categorizes issue or PR as related to a bug. label Jan 8, 2019
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 8, 2019
@pcdavies
Copy link
Author

pcdavies commented Jan 8, 2019

Adding sig labels:

/sig Networking
/sig Windows
/sig VMWare

@k8s-ci-robot k8s-ci-robot added sig/windows Categorizes an issue or PR as relevant to SIG Windows. area/provider/vmware Issues or PRs related to vmware provider and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 8, 2019
@pcdavies
Copy link
Author

pcdavies commented Jan 8, 2019

/sig Network

@k8s-ci-robot k8s-ci-robot added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Jan 8, 2019
@guhuajun
Copy link

guhuajun commented Jan 9, 2019

Greetings,

I have tested K8S on Windows with Flannel Overlay last week, it also fails.
Since it is a Windows issue, we can get some help from Microsoft side.
https://github.com/microsoft/sdn/issues

Literally, following error usually means the port is occupied by another container. You may run docker ps -a on the Windows box to verify.

failed to create the new HNSEndpoint: hnsCall failed in Win32: The object already exists. (0x1392)

@pcdavies
Copy link
Author

pcdavies commented Jan 9, 2019

Hi @guhuajun,

What is the best way to get microsoft's help? Should I repost in https://github.com/microsoft/sdn/issues and point to this issues, or just repost and duplicate the content?

There does not seem to be a conflict with the ports. Here is a docker ps command after the windows node has joined, but prior to deploying a kubernetes pod:

PS C:\k> docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
PS C:\k> docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

After running the kubectl apply -f iis-win.yml command, the results from the docker ps commands return:

PS C:\k> docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
PS C:\k> docker ps -a
CONTAINER ID        IMAGE               COMMAND                   CREATED              STATUS                                   PORTS               NAMES
616a159e72ec        kubeletwin/pause    "cmd /S /C 'cmd /c p…"    2 seconds ago        Up 1 second                                                  k8s_POD_iis-5596fb9cf6-bchkw_default_7e6fa386-142b-11e9-a852-000c293748f0_74
ed53fd241d2c        kubeletwin/pause    "cmd /S /C 'cmd /c p…"    4 seconds ago        Exited (3221225786) 1 second ago                             k8s_POD_iis-5596fb9cf6-bchkw_default_7e6fa386-142b-11e9-a852-000c293748f0_73
85bffe790c91        kubeletwin/pause    "cmd /S /C 'cmd /c p…"    8 seconds ago        Exited (3221225786) 4 seconds ago                            k8s_POD_iis-5596fb9cf6-bchkw_default_7e6fa386-142b-11e9-a852-000c293748f0_72
b77b88776b9d        kubeletwin/pause    "cmd /S /C 'cmd /c p…"    11 seconds ago       Exited (3221225786) 8 seconds ago                            k8s_POD_iis-5596fb9cf6-bchkw_default_7e6fa386-142b-11e9-a852-000c293748f0_71
7c1562fffde7        kubeletwin/pause    "cmd /S /C 'cmd /c p…"    13 seconds ago       Exited (3221225786) 10 seconds ago                           k8s_POD_iis-5596fb9cf6-bchkw_default_7e6fa386-142b-11e9-a852-000c293748f0_70
bc83ae8f0f6b        microsoft/iis       "C:\\ServiceMonitor.e…"   16 seconds ago       Exited (3221225786) 14 seconds ago                           k8s_iis_iis-5596fb9cf6-bchkw_default_7e6fa386-142b-11e9-a852-000c293748f0_6
e7718150148e        kubeletwin/pause    "cmd /S /C 'cmd /c p…"    18 seconds ago       Exited (3221225786) 12 seconds ago                           k8s_POD_iis-5596fb9cf6-bchkw_default_7e6fa386-142b-11e9-a852-000c293748f0_69
0256278d7c08        kubeletwin/pause    "cmd /S /C 'cmd /c p…"    21 seconds ago       Exited (3221225786) 18 seconds ago                           k8s_POD_iis-5596fb9cf6-bchkw_default_7e6fa386-142b-11e9-a852-000c293748f0_68

If I do a docker logs 22f4baec68d0 on the microsoft/iis exited container, there is nothing in the log file

@pcdavies pcdavies mentioned this issue Jan 9, 2019
Closed
@guhuajun
Copy link

Thanks for updating. Flannel on Windows are still under developing. Hope we will have a workaround for this issue.

@song-jiang
Copy link

I am hitting the same The object already exits issue on AWS windows server 1809 with container.

@pcdavies
Copy link
Author

See resolution in issue #298 referenced above.

@GOVYANSONG
Copy link

GOVYANSONG commented Mar 18, 2019 •
edited
Loading

diagnosis.zip

I am hitting the same The object already exits issue on Azure VM windows server 1809 with container.

@GOVYANSONG GOVYANSONG mentioned this issue Mar 19, 2019
Closed
@Grovespaz Grovespaz mentioned this issue May 13, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/provider/vmware Issues or PRs related to vmware provider kind/bug Categorizes issue or PR as related to a bug. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/windows Categorizes an issue or PR as relevant to SIG Windows.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@pcdavies @guhuajun @k8s-ci-robot @song-jiang @GOVYANSONG