Open Vyom-Yadav opened 8 months ago
This issue is currently awaiting triage.
If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
As the Alpha 3 release cut is approaching (2nd Nov) /priority critical-urgent /kind failing-test
I will check the AMI used for this test. There is a known issue with a newer cloud-init version that is affecting recently built Ubuntu 20.04 AMIs.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Which jobs are flaking?
master-informing:
Which tests are flaking?
capa-e2e-conformance.[It] [unmanaged] [conformance] tests conformance
Testgrid link
https://testgrid.k8s.io/sig-release-master-informing#periodic-conformance-main-k8s-main
Reason for failure (if possible)
Relevant SIG(s)
/sig cluster-lifecycle