jiebi/CodeConvo huggingface dataset:
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 --The value of err in was always nil, and it will lead to incorrect behavior in some case. Assign to in Use functions in any place. (In all environments) /assign /sig scheduling /sig testing
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

Discussion:
func DoCleanupNode(client clientset.Interface, nodeName string, strategy PrepareNodeStrategy) error { var err error for attempt := 0; attempt < retries; attempt++ { <del> node, err := client.CoreV1().Nodes().Get(context.TODO(), nodeName, metav1.GetOptions{}) </del> <ins> var node *v1.Node node, err = client.CoreV1().Nodes().Get(context.TODO(), nodeName, metav1.GetOptions{}) </ins> if err != nil { return fmt.Errorf("Skipping cleanup of Node: failed to get Node %v: %v", nodeName, err) }
Change:
/kind failing-test /kind flake /sig cloud-provider /area provider/vmware Flaked on Is this the same issue as ?
/assign There seems to be a data-race here.
There's a finalizer that trips up the test case. TestSecretUpdated set flag and read from so when the logout read and the test is write the ,they lead to I came up with a mutex where the klog library reads Or a lock on the kubernetes vsphere logout function. Any better suggestions? /cc
the use of a runtime finalizer is suspect... that's the only use in our codebase and makes unit testing really hard. also, the use of the global logger in TestSecretUpdated is suspect... the code under test should be structured to allow testing the results without plumbing through the global logger
/cc
/assign
/triage accepted
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
Since the test is still failed, pick up at /cc

Discussion:
return configFromSim() } <ins> func init() { klog.InitFlags(nil) } </ins> func TestSecretUpdated(t *testing.T) { datacenter := "0.0.0.0" secretName := "vccreds"

if err != nil { t.Fatalf("Should succeed when a valid config is provided: %s", err) } <del> klog.Flush() klog.InitFlags(nil) </del> flag.Set("logtostderr", "false") flag.Set("alsologtostderr", "false") flag.Set("v", "9")
Change:
once the we hit a beta release, we can reset the default value for strict handling to false to prep for 1.23. /assign /kind bug /priority important-soon /milestone v1.22
/triage accepted
Hi Bug Triage from SIG Release here .. Checking to see if this issue is going to make it to v1.22 milestone bearing in mind code freeze is 07/08/2021. Feel free to reach out if there are any questions/concerns.
Hi, Bug Triage here, removing this issue from 1.22, as there hasn't been activity on that issue for 16 days. /milestone clear
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:

Discussion:
} func NewResourceExpirationEvaluator(currentVersion apimachineryversion.Info) (ResourceExpirationEvaluator, error) { <del> ret := &resourceExpirationEvaluator{ // TODO https://github.com/kubernetes/kubernetes/issues/101951 set this back to false after beta is tagged. strictRemovedHandlingInAlpha: true, } </del> <ins> ret := &resourceExpirationEvaluator{} </ins> if len(currentVersion.Major) > 0 { currentMajor64, err := strconv.ParseInt(currentVersion.Major, 10, 32) if err != nil {
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 --When I run some e2e storage testcases locally, below testcases as an example, I consistently saw the below error message, ceph should be deployed successfully and testcase should pass. Run the testcases mentioned above. e.g. Kubernetes version (use ): ALL Cloud provider or hardware configuration: ARM64 OS (e.g: ): ubuntu18 Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:
/sig testing /sig storage
/assign
is this happening in CI? please provide links to occurences?
Hey, Ben, I update the issue description a little bit, this won't be an issue on X86 which is currently the default arch CI is running, but tons of testcases will fail on ARM64 due to this issue. Eventually, we hope the k8s will have a ARM CI along with the more adoption of arch beside the X86, and thus, those e2e testcases should workable on ARM64 firstly. I will explain why it failed on ARM64 in the PR desc, pls help to review, thanks!
/triage accepted

Discussion:
<del> linux/amd64=fedora:26 linux/arm64=arm64v8/fedora:26 linux/ppc64le=ppc64le/fedora:26 </del> <ins> linux/amd64=fedora:33 linux/arm64=arm64v8/fedora:33 linux/ppc64le=ppc64le/fedora:33 </ins>

CROSS_BUILD_COPY qemu-QEMUARCH-static /usr/bin/ # Base Packages <del> RUN yum install -y wget strace psmisc procps-ng ceph ceph-fuse && yum clean all </del> <ins> RUN yum install -y wget strace psmisc procps-ng ceph ceph-fuse hostname && yum clean all </ins> # Get ports exposed EXPOSE 6789

# Prepare a RBD volume "foo" (only with layering feature, the others may # require newer clients). # NOTE: we need Ceph kernel modules on the host that runs the client! <ins> # As the default pool `rbd` might not be created on arm64 platform for ceph deployment, # should create it if it does not exist. arch=$(uname -m) if [[ ${arch} = 'aarch64' || ${arch} = 'arm64' ]]; then if [[ $(ceph osd lspools) = "" ]]; then ceph osd pool create rbd 8 rbd pool init rbd fi fi </ins> rbd import --image-feature layering block foo # Prepare a cephfs volume
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 --On Windows 20H2 we are observing crashloops with fluent-bit due to a malformed Windows Event Log entry in the Security log. Fluent-bit to not crash loop. Bring up a GCE Windows cluster on Windows 20H2. You may see a loss of logs. Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /sig windows /triage accepted

Discussion:
# TODO(pjh): move the logging agent code below into a separate # module; it was put here temporarily to avoid disrupting the file layout in # the K8s release machinery. <del> $LOGGINGAGENT_VERSION = '1.7.3' </del> <ins> $LOGGINGAGENT_VERSION = '1.7.5' </ins> $LOGGINGAGENT_ROOT = 'C:fluent-bit' $LOGGINGAGENT_SERVICE = 'fluent-bit' $LOGGINGAGENT_CMDLINE = '*fluent-bit.exe*'

Interval_Sec 2 # Channels Setup,Windows PowerShell Channels     application,system,security <del> Tag          winevent.raw </del> <ins> Tag          winevt.raw </ins> DB           /var/run/google-fluentbit/pos-files/winlog.db # Json Log Example:

Hard_rename log message [FILTER] <ins> Name        modify Match       winevt.raw Hard_rename Message message [FILTER] </ins> Name         parser Match        kube_* Key_Name     message
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 --command fails because of I think the link is from k/k's Am I right?? kubetest command succeeds With installed, OR Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:
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 /sig testing
/assign
Need cherry-picks for 1.21, 1.20 to address this. is updated but downloaded downloads and executes its /reopen
Reopened this issue. <detailsIn response to : Need cherry-picks for 1.21, 1.20 to address this. 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
cc
this was cherry picked AFAICT, thank you!

Discussion:
mkdir -p "${download_path}" if [[ $(which gsutil) ]] && [[ "$url" =~ ^https://storage.googleapis.com/.* ]]; then <del> gsutil cp "${url//'https://storage.googleapis.com/'/'gs://'}" "${download_path}/${file}" </del> <ins> gsutil cp "${url//'https://storage.googleapis.com/'/gs://}" "${download_path}/${file}" </ins> elif [[ $(which curl) ]]; then # if the url belongs to GCS API we should use oauth2_token in the headers curl_headers=""

if "${need_download}"; then if [[ $(which gsutil) ]] && [[ "$kubernetes_tar_url" =~ ^https://storage.googleapis.com/.* ]]; then <del> gsutil cp "${kubernetes_tar_url//'https://storage.googleapis.com/'/'gs://'}" "${file}" </del> <ins> gsutil cp "${kubernetes_tar_url//'https://storage.googleapis.com/'/gs://}" "${file}" </ins> elif [[ $(which curl) ]]; then # if the url belongs to GCS API we should use oauth2_token in the headers curl_headers=""
Change:
for the windows test Im seeing in some e2es im running on 1.22... We wouldnt have in our e2e tests hardcoded / Run with
/sig windows
/assign
/assign
/triage accepted

Discussion:
var ( windowsBusyBoximage = imageutils.GetE2EImage(imageutils.Agnhost) <del> linuxBusyBoxImage   = "docker.io/library/nginx:1.15-alpine" </del> <ins> linuxBusyBoxImage   = imageutils.GetE2EImage(imageutils.Nginx) </ins> ) var _ = SIGDescribe("Hybrid cluster network", func() {
Change:
<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -- ci-kubernetes-generate-make-test-count10 pr:pull-kubernetes-unit ci-kubernetes-unit ci-kubernetes-generate-make-test-count10 TestAttacherMountDeviceWithInline links to appreciated links to specific failures in spyglass appreciated <!-- Please see the deflaking doc () for more guidance! --
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
/assign
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig sig-storage </details
/sig storage

Discussion:
// AddWatchReactor appends a reactor to the end of the chain. func (c *Fake) AddWatchReactor(resource string, reaction WatchReactionFunc) { <ins> c.Lock() defer c.Unlock() </ins> c.WatchReactionChain = append(c.WatchReactionChain, &SimpleWatchReactor{resource, reaction}) } // PrependWatchReactor adds a reactor to the beginning of the chain. func (c *Fake) PrependWatchReactor(resource string, reaction WatchReactionFunc) { <ins> c.Lock() defer c.Unlock() </ins> c.WatchReactionChain = append([]WatchReactor{&SimpleWatchReactor{resource, reaction}}, c.WatchReactionChain...) }
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 --Consider the following log line: I expected the podUID to be printed rather than an address/pointer. Run a static pod on a non-standalone kubelet, watch logs for mirrorclient entries. Fix is this line: We probably want to check if the UID is nil, and if so, print what it points to. /sig node /area logging /help Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : <!-- 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! --#### What happened: /area logging /help Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: </details
/assign
/triage accepted

Discussion:
DeleteMirrorPod(podFullName string, uid *types.UID) (bool, error) } <del> // nodeGetter is a subset a NodeLister, simplified for testing. </del> <ins> // nodeGetter is a subset of NodeLister, simplified for testing. </ins> type nodeGetter interface { // Get retrieves the Node for a given name. Get(name string) (*v1.Node, error)

klog.ErrorS(err, "Failed to parse a pod full name", "podFullName", podFullName) return false, err } <del> klog.V(2).InfoS("Deleting a mirror pod", "pod", klog.KRef(namespace, name), "podUID", uid) </del> <ins> var uidValue types.UID if uid != nil { uidValue = *uid } klog.V(2).InfoS("Deleting a mirror pod", "pod", klog.KRef(namespace, name), "podUID", uidValue) </ins> var GracePeriodSeconds int64 if err := mc.apiserverClient.CoreV1().Pods(namespace).Delete(context.TODO(), name, metav1.DeleteOptions{GracePeriodSeconds: &GracePeriodSeconds, Preconditions: &metav1.Preconditions{UID: uid}}); err != nil { // Unfortunately, there's no generic error for failing a precondition
Change:
[X] Test PR: kuberenetes/kubernetes 17 June 2021 [x] Two weeks soak end date: 1 Jul 2021 [X] Test promotion PR: kubernetes/kubernetes According to this APIsnoop query, there are still some remaining StatefulSet endpoints which are untested. Create a watch to track stateful set events Create a stateful set with a static label. Confirm that the pods are running. Get the stateful set status. Parse the response and confirm that the stateful set status conditions can be listed. Update the stateful set status. Confirm via the watch that the status has been updated. Patch the stateful set status. Confirm via the watch that the status has been patched. Using an existing as a template for a new for stateful set lifecycle test. This query shows the endpoints hit within a short period of running the e2e test If a test with these calls gets merged, test coverage will go up by 3 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance
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
/reopen
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

Discussion:
StorageClass or a dynamic provisioner. release: v1.9 file: test/e2e/apps/statefulset.go <ins> - testname: StatefulSet, status sub-resource codename: '[sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should validate Statefulset Status endpoints [Conformance]' description: When a StatefulSet is created it MUST succeed. Attempt to read, update and patch its status sub-resource; all mutating sub-resource operations MUST be visible to subsequent reads. release: v1.22 file: test/e2e/apps/statefulset.go </ins> - testname: CertificateSigningRequest API codename: '[sig-auth] Certificates API [Privileged:ClusterAdmin] should support CSR API operations [Conformance]'

framework.ExpectEqual(len(ssList.Items), 0, "filtered list should have no Statefulsets") }) <del> ginkgo.It("should validate Statefulset Status endpoints", func() { </del> <ins> /* Release: v1.22 Testname: StatefulSet, status sub-resource Description: When a StatefulSet is created it MUST succeed. Attempt to read, update and patch its status sub-resource; all mutating sub-resource operations MUST be visible to subsequent reads. */ framework.ConformanceIt("should validate Statefulset Status endpoints", func() { </ins> ssClient := c.AppsV1().StatefulSets(ns) labelSelector := "e2e=testing"
Change:
We should fine grained debug statements to ExecWithOptions in the framework class , so that in tests where theres alot of execs where hangs can happen i.e. on windows, we can see where tests are getting clogged up. Mostly i want this for , but i suppose its a generic improvement
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 testing /good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /sig testing /good-first-issue 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
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale

Discussion:
const tty = false <ins> Logf("ExecWithOptions: Clientset creation") </ins> req := f.ClientSet.CoreV1().RESTClient().Post(). Resource("pods"). Name(options.PodName).

}, scheme.ParameterCodec) var stdout, stderr bytes.Buffer <ins> Logf("ExecWithOptions: execute(POST %s %s)", req.URL()) </ins> err = execute("POST", req.URL(), config, options.Stdin, &stdout, &stderr, tty) if options.PreserveWhitespace { return stdout.String(), stderr.String(), err }
Change:
<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --- gce-os-master-alpha-features kubernetes.Up 05.2021 log- & in this test are deprecated starting with this the tests are failing therefore I'm also pinging
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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
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
Kubelet log:
It seems to be related with . /cc I read the context: fixed pull-kubernetes-e2e-gce-alpha-features job failure for PR . gce-os-master-alpha-features need a similar change.
I tried to fix it in
the PR seems to solved it, thank you!

Discussion:
volumeMounts: - name: influxdb-persistent-storage mountPath: /data <del> - image: gcr.io/google_containers/heapster_grafana:v2.1.1 </del> <ins> - image: gcr.io/google_containers/heapster_grafana:v2.6.0-2 </ins> name: grafana env: resources:
Change:
The latest release of CNI plugins is , but we still have . I'll attempt to create a PR for this based on the .
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 network
- assigning to you :)

Discussion:
# CNI plugins - name: "cni" <del> version: 0.8.7 </del> <ins> version: 0.9.1 </ins> refPaths: - path: cluster/gce/gci/configure.sh match: DEFAULT_CNI_VERSION=

# CNI storage path for Windows nodes export WINDOWS_CNI_STORAGE_PATH="https://storage.googleapis.com/k8s-artifacts-cni/release" # CNI version for Windows nodes <del> export WINDOWS_CNI_VERSION="v0.8.7" </del> <ins> export WINDOWS_CNI_VERSION="v0.9.1" </ins> # Pod manifests directory for Windows nodes on Windows nodes. export WINDOWS_MANIFESTS_DIR="${WINDOWS_K8S_DIR}manifests" # Directory where cert/key files will be stores on Windows nodes.

set -o pipefail ### Hardcoded constants <del> DEFAULT_CNI_VERSION='v0.8.7' DEFAULT_CNI_HASH='8f2cbee3b5f94d59f919054dccfe99a8e3db5473b553d91da8af4763e811138533e05df4dbeab16b3f774852b4184a7994968f5e036a3f531ad1ac4620d10ede' </del> <ins> DEFAULT_CNI_VERSION='v0.9.1' DEFAULT_CNI_HASH='b5a59660053a5f1a33b5dd5624d9ed61864482d9dc8e5b79c9b3afc3d6f62c9830e1c30f9ccba6ee76f5fb1ff0504e58984420cc0680b26cb643f1cb07afbd1c' </ins> DEFAULT_NPD_VERSION='v0.8.7' DEFAULT_NPD_HASH='853576423077bf72e7bd8e96cd782cf272f7391379f8121650c1448531c0d3a0991dfbd0784a1157423976026806ceb14ca8fb35bac1249127dbf00af45b7eea' DEFAULT_CRICTL_VERSION='v1.21.0'

// utils.go contains functions used across test suites. const ( <del> cniVersion       = "v0.8.7" </del> <ins> cniVersion       = "v0.9.1" </ins> cniArch          = "amd64" cniDirectory     = "cni/bin" // The CNI tarball places binaries under directory under "cni/bin". cniConfDirectory = "cni/net.d"