xander-sh

Hi, no, VM is correct. VM id - 5007a902-7820-61fb-2611-ec354b516999

> Hi @xander-sh, thank your for the detailed report! I looked at the logs and I see the following: "Found 12 ports for segment 090d3269-9acc-4eb1-8f4b-f1a04fbd0f6a" > > After this printout...

> Looks like the attachment on provided port has a different id? > > ``` > "attachment" : { > "id" : "e071c0d7-7366-41e9-a75d-3f125fa2e37f", > "traffic_tag" : 0, > "hyperbus_mode" :...

> Some background: Based on description of the issue, I suspected pagination might not be working properly on NSX on `vifs` API, similar to problem described here https://github.com/vmware/terraform-provider-nsxt/blob/master/nsxt/resource_nsxt_policy_vm_tags.go#L67 > >...

We have the same problem on k8s 1.17.4 and vmware csi driver v1.1.0 After update vmware csi driver to v2.0.1 metric are present on kubelet. I think you should find...

As it was said in issue https://kb.vmware.com/s/article/89437, problem solved after upgrade nsx-t to 3.2.2.1.