jiebi/CodeConvo huggingface dataset:
Code change:
The based container images for are shipped with the wrong architecture within the manifest if not amd64: Refers to We updated the images a few minutes ago to buster-v1.3.0, which are now ready to be used as base for the multi-architecture images. If the images contain the right architectures, then it may magically happen that the kube-proxy images are fixed, too. This is because we already use the build syntax for it: /cc
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig release

Related discussion:
text: configs[CheckMetadataConcealment] = Config{e2eRegistry, "metadata-concealment", "1.2"} configs[CudaVectorAdd] = Config{e2eRegistry, "cuda-vector-add", "1.0"} configs[CudaVectorAdd2] = Config{e2eRegistry, "cuda-vector-add", "2.0"} <del> configs[DebianIptables] = Config{buildImageRegistry, "debian-iptables", "buster-v1.4.0"} </del> <ins> configs[DebianIptables] = Config{buildImageRegistry, "debian-iptables", "buster-v1.5.0"} </ins> configs[EchoServer] = Config{e2eRegistry, "echoserver", "2.2"} configs[Etcd] = Config{gcRegistry, "etcd", "3.4.13-0"} configs[GlusterDynamicProvisioner] = Config{dockerGluster, "glusterdynamic-provisioner", "v1.0"}
Code change:
What happened: The current in-tree PV topology is still using beta version label "failure-". This was intentionally not upgrade because of CSI migration. However, since the CSI migration timeline is likely to slip, and with the fix of , it should be safe to update the in-tree PVC to GA version () So that we can unblock removing the beta label from node. What you expected to happen: Replace all beta topology label to GA version once merged. /sig storage /cc
/assign
GitHub didn't allow me to assign the following users: kassarl. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
gce-pd topology update already merged:
aws-ebs topology update is here:
/triage accepted
cinder topology fix is here: Waiting for topology label update.
OpenStack Cinder:
/reopen Has vsphere made the fix?
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Not yet. is going to make the fix.

Related discussion:
text: for k, v := range labels { pv.Labels[k] = v var values []string <del> if k == v1.LabelFailureDomainBetaZone { </del> <ins> if k == v1.LabelTopologyZone || k == v1.LabelFailureDomainBetaZone { </ins> values, err = volumehelpers.LabelZonesToList(v) if err != nil { return nil, fmt.Errorf("failed to convert label string for Zone: %s to a List: %v", v, err)
Code change:
What happened: The current in-tree PV topology is still using beta version label "failure-". This was intentionally not upgrade because of CSI migration. However, since the CSI migration timeline is likely to slip, and with the fix of , it should be safe to update the in-tree PVC to GA version () So that we can unblock removing the beta label from node. What you expected to happen: Replace all beta topology label to GA version once merged. /sig storage /cc
/assign
GitHub didn't allow me to assign the following users: kassarl. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
gce-pd topology update already merged:
aws-ebs topology update is here:
/triage accepted
cinder topology fix is here: Waiting for topology label update.
OpenStack Cinder:
/reopen Has vsphere made the fix?
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Not yet. is going to make the fix.

Related discussion:
text: translator := NewvSphereCSITranslator() topologySelectorTerm := v1.TopologySelectorTerm{[]v1.TopologySelectorLabelRequirement{ { <ins> Key:    v1.LabelTopologyZone, Values: []string{"zone-a"}, }, { Key:    v1.LabelTopologyRegion, Values: []string{"region-a"}, }, }} topologySelectorTermWithBetaLabels := v1.TopologySelectorTerm{[]v1.TopologySelectorLabelRequirement{ { </ins> Key:    v1.LabelFailureDomainBetaZone, Values: []string{"zone-a"}, },
Code change:
What happened: The current in-tree PV topology is still using beta version label "failure-". This was intentionally not upgrade because of CSI migration. However, since the CSI migration timeline is likely to slip, and with the fix of , it should be safe to update the in-tree PVC to GA version () So that we can unblock removing the beta label from node. What you expected to happen: Replace all beta topology label to GA version once merged. /sig storage /cc
/assign
GitHub didn't allow me to assign the following users: kassarl. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
gce-pd topology update already merged:
aws-ebs topology update is here:
/triage accepted
cinder topology fix is here: Waiting for topology label update.
OpenStack Cinder:
/reopen Has vsphere made the fix?
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Not yet. is going to make the fix.

Related discussion:
text: expSc: NewStorageClass(map[string]string{"storagepolicyname": "test-policy-name", paramcsiMigration: "true"}, []v1.TopologySelectorTerm{topologySelectorTerm}), }, { <ins> name:  "translate with storagepolicyname and allowedTopology beta labels", sc:    NewStorageClass(map[string]string{"storagepolicyname": "test-policy-name"}, []v1.TopologySelectorTerm{topologySelectorTermWithBetaLabels}), expSc: NewStorageClass(map[string]string{"storagepolicyname": "test-policy-name", paramcsiMigration: "true"}, []v1.TopologySelectorTerm{topologySelectorTermWithBetaLabels}), }, { </ins> name:  "translate with raw vSAN policy parameters, datastore and diskformat", sc:    NewStorageClass(map[string]string{"hostfailurestotolerate": "2", "datastore": "vsanDatastore", "diskformat": "thin"}, []v1.TopologySelectorTerm{topologySelectorTerm}), expSc: NewStorageClass(map[string]string{"hostfailurestotolerate-migrationparam": "2", "datastore-migrationparam": "vsanDatastore", "diskformat-migrationparam": "thin", paramcsiMigration: "true"}, []v1.TopologySelectorTerm{topologySelectorTerm}),
Code change:
What happened: The current in-tree PV topology is still using beta version label "failure-". This was intentionally not upgrade because of CSI migration. However, since the CSI migration timeline is likely to slip, and with the fix of , it should be safe to update the in-tree PVC to GA version () So that we can unblock removing the beta label from node. What you expected to happen: Replace all beta topology label to GA version once merged. /sig storage /cc
/assign
GitHub didn't allow me to assign the following users: kassarl. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
gce-pd topology update already merged:
aws-ebs topology update is here:
/triage accepted
cinder topology fix is here: Waiting for topology label update.
OpenStack Cinder:
/reopen Has vsphere made the fix?
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Not yet. is going to make the fix.

Related discussion:
text: } } // Get the node zone information <del> nodeFd := node.ObjectMeta.Labels[v1.LabelFailureDomainBetaZone] nodeRegion := node.ObjectMeta.Labels[v1.LabelFailureDomainBetaRegion] </del> <ins> nodeFd := node.ObjectMeta.Labels[v1.LabelTopologyZone] nodeRegion := node.ObjectMeta.Labels[v1.LabelTopologyRegion] </ins> nodeZone := &cloudprovider.Zone{FailureDomain: nodeFd, Region: nodeRegion} nodeInfo := &NodeInfo{dataCenter: res.datacenter, vm: vm, vcServer: res.vc, vmUUID: nodeUUID, zone: nodeZone} nm.addNodeInfo(node.ObjectMeta.Name, nodeInfo)
Code change:
What happened: The current in-tree PV topology is still using beta version label "failure-". This was intentionally not upgrade because of CSI migration. However, since the CSI migration timeline is likely to slip, and with the fix of , it should be safe to update the in-tree PVC to GA version () So that we can unblock removing the beta label from node. What you expected to happen: Replace all beta topology label to GA version once merged. /sig storage /cc
/assign
GitHub didn't allow me to assign the following users: kassarl. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
gce-pd topology update already merged:
aws-ebs topology update is here:
/triage accepted
cinder topology fix is here: Waiting for topology label update.
OpenStack Cinder:
/reopen Has vsphere made the fix?
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Not yet. is going to make the fix.

Related discussion:
text: // FIXME: For now, pick the first zone of datastore as the zone of volume labels := make(map[string]string) if len(dsZones) > 0 { <del> labels[v1.LabelFailureDomainBetaRegion] = dsZones[0].Region labels[v1.LabelFailureDomainBetaZone] = dsZones[0].FailureDomain </del> <ins> labels[v1.LabelTopologyRegion] = dsZones[0].Region labels[v1.LabelTopologyZone] = dsZones[0].FailureDomain </ins> } return labels, nil }
Code change:
What happened: The current in-tree PV topology is still using beta version label "failure-". This was intentionally not upgrade because of CSI migration. However, since the CSI migration timeline is likely to slip, and with the fix of , it should be safe to update the in-tree PVC to GA version () So that we can unblock removing the beta label from node. What you expected to happen: Replace all beta topology label to GA version once merged. /sig storage /cc
/assign
GitHub didn't allow me to assign the following users: kassarl. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
gce-pd topology update already merged:
aws-ebs topology update is here:
/triage accepted
cinder topology fix is here: Waiting for topology label update.
OpenStack Cinder:
/reopen Has vsphere made the fix?
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Not yet. is going to make the fix.

Related discussion:
text: term := v1.TopologySelectorTerm{ MatchLabelExpressions: []v1.TopologySelectorLabelRequirement{ { <del> Key:    v1.LabelFailureDomainBetaZone, </del> <ins> Key:    v1.LabelTopologyZone, </ins> Values: zones, }, },
Code change:
What happened: The current in-tree PV topology is still using beta version label "failure-". This was intentionally not upgrade because of CSI migration. However, since the CSI migration timeline is likely to slip, and with the fix of , it should be safe to update the in-tree PVC to GA version () So that we can unblock removing the beta label from node. What you expected to happen: Replace all beta topology label to GA version once merged. /sig storage /cc
/assign
GitHub didn't allow me to assign the following users: kassarl. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
gce-pd topology update already merged:
aws-ebs topology update is here:
/triage accepted
cinder topology fix is here: Waiting for topology label update.
OpenStack Cinder:
/reopen Has vsphere made the fix?
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Not yet. is going to make the fix.

Related discussion:
text: zones = append(zones, zoneA) nodeSelectorMap := map[string]string{ // nodeSelector set as zoneB <del> v1.LabelFailureDomainBetaZone: zoneB, </del> <ins> v1.LabelTopologyZone: zoneB, </ins> } verifyPodSchedulingFails(client, namespace, nodeSelectorMap, scParameters, zones, storagev1.VolumeBindingWaitForFirstConsumer) })
Code change:
What happened: The current in-tree PV topology is still using beta version label "failure-". This was intentionally not upgrade because of CSI migration. However, since the CSI migration timeline is likely to slip, and with the fix of , it should be safe to update the in-tree PVC to GA version () So that we can unblock removing the beta label from node. What you expected to happen: Replace all beta topology label to GA version once merged. /sig storage /cc
/assign
GitHub didn't allow me to assign the following users: kassarl. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
gce-pd topology update already merged:
aws-ebs topology update is here:
/triage accepted
cinder topology fix is here: Waiting for topology label update.
OpenStack Cinder:
/reopen Has vsphere made the fix?
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Not yet. is going to make the fix.

Related discussion:
text: ginkgo.By("Verify zone information is present in the volume labels") for _, pv := range persistentvolumes { // Multiple zones are separated with "__" <del> pvZoneLabels := strings.Split(pv.ObjectMeta.Labels["failure-domain.beta.kubernetes.io/zone"], "__") </del> <ins> pvZoneLabels := strings.Split(pv.ObjectMeta.Labels[v1.LabelTopologyZone], "__") </ins> for _, zone := range zones { gomega.Expect(pvZoneLabels).Should(gomega.ContainElement(zone), "Incorrect or missing zone labels in pv.") }
Code change:
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When reviewing Windows kubelet logs noticed errors like: What you expected to happen: The stats should be returned How to reproduce it (as minimally and precisely as possible): This occurs when the pods has just started or during termination. To simulate the issue: Then deploy pod: Anything else we need to know?: The container is in a state but is has not started running so the call to get the stats fails: This is handled in other places like moby: and Environment: Kubernetes version (use ): 1.18+ Cloud provider or hardware configuration: aks-engine OS (e.g: ): Windows Kernel (e.g. ): 2019 Install tools: Network plugin and version (if this is a network-related bug): Others: Dockershim /sig windows /priority critical-urgent /assign
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
cc:

Related discussion:
text: case err := <-injectedError: return nil, err } <del> // Never get here. return nil, nil </del> }
Code change:
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When reviewing Windows kubelet logs noticed errors like: What you expected to happen: The stats should be returned How to reproduce it (as minimally and precisely as possible): This occurs when the pods has just started or during termination. To simulate the issue: Then deploy pod: Anything else we need to know?: The container is in a state but is has not started running so the call to get the stats fails: This is handled in other places like moby: and Environment: Kubernetes version (use ): 1.18+ Cloud provider or hardware configuration: aks-engine OS (e.g: ): Windows Kernel (e.g. ): 2019 Install tools: Network plugin and version (if this is a network-related bug): Others: Dockershim /sig windows /priority critical-urgent /assign
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
cc:

Related discussion:
text: import ( "context" <ins> "strings" </ins> "time" "github.com/Microsoft/hcsshim"
Code change:
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: When reviewing Windows kubelet logs noticed errors like: What you expected to happen: The stats should be returned How to reproduce it (as minimally and precisely as possible): This occurs when the pods has just started or during termination. To simulate the issue: Then deploy pod: Anything else we need to know?: The container is in a state but is has not started running so the call to get the stats fails: This is handled in other places like moby: and Environment: Kubernetes version (use ): 1.18+ Cloud provider or hardware configuration: aks-engine OS (e.g: ): Windows Kernel (e.g. ): 2019 Install tools: Network plugin and version (if this is a network-related bug): Others: Dockershim /sig windows /priority critical-urgent /assign
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
cc:

Related discussion:
text: // That will typically happen with init-containers in Exited state. Docker still knows about them but the HCS does not. // As we don't want to block stats retrieval for other containers, we only log errors. if !hcsshim.IsNotExist(err) && !hcsshim.IsAlreadyStopped(err) { <del> klog.Errorf("Error opening container (stats will be missing) '%s': %v", containerID, err) </del> <ins> klog.V(4).Infof("Error opening container (stats will be missing) '%s': %v", containerID, err) </ins> } return nil, nil }