Open neo-liang-sap opened 2 years ago
@neo-liang-sap No more than 5 labels permitted, but 21 labels were given.
@neo-liang-sap
Shoot: sretestneo/sre-g-test v1.21.9
created at 2021-04-14 01:04
by Neo Liang (BTP Core FP TS SRE (CHN))
on aws
in eu-west-1
with purpose development
at 3
nodes and 28
pods and 32
API server requests/second (max of last 24h each)
Seed: garden/aws
@neo-liang-sap You opened a priority issue on the weekend. Please read https://wiki.wdf.sap.corp/wiki/display/Kubernetes/Gardener+Support and https://wiki.wdf.sap.corp/wiki/display/Kubernetes/DevOps+24x7 carefully for more information on how Gardener is operated on a weekend.
@gardener-robot You have mentioned internal references in the public. Please check.
@gardener-robot You have mentioned internal references in the public. Please check.
@neo-liang-sap âšī¸ Please take note of this issue.
/author-action
@neo-liang-sap The issue was assigned to you under author-action
. Please unassign yourself when you are done. Thank you.
/author-action
@neo-liang-sap The issue was assigned to you under author-action
. Please unassign yourself when you are done. Thank you.
/author-action
@neo-liang-sap The issue was assigned to you under author-action
. Please unassign yourself when you are done. Thank you.
@neo-liang-sap No more than 5 labels permitted, but 21 labels were given.
@ishan16696 has acknowledged the VictorOps alert and looking into this issue
/author-action
@neo-liang-sap The issue was assigned to you under author-action
. Please unassign yourself when you are done. Thank you.
/author-action
@neo-liang-sap The issue was assigned to you under author-action
. Please unassign yourself when you are done. Thank you.
This issue has no status label. Please correct the situation.
/status in-progress
@neo-liang-sap, @etiennnr This ticket has not been touched since 3 days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap, @etiennnr This ticket has not been touched since 3 days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap, @etiennnr This issue has not been touched since 64 days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap, @etiennnr [in-progress] This issue has not been touched since 68 days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap, @etiennnr This issue has not been touched since 70 days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap, @etiennnr This issue has not been touched since 59 work days. Please add a follow up comment and/or change the status/
label.
/handover
@neo-liang-sap Command "/handover" failed with "AssertionError(['neo-liang-sap'])".
/handover @neo-liang-sap
@neo-liang-sap neo-liang-sap handover this issue to you, please take care.
/handover
@neo-liang-sap Command "/handover" failed with "AssertionError(['neo-liang-sap'])".
/handover
@neo-liang-sap Command "/handover" failed with "AssertionError((['neo-liang-sap'],))".
/handover @neo-liang-sap
@neo-liang-sap neo-liang-sap handover this issue to you, please take care.
/handover
@neo-liang-sap neo-liang-sap handover this ticket to you, please take care.
/handover @neo-liang-sap
@neo-liang-sap neo-liang-sap handover this issue to you, please take care.
/handover
@neo-liang-sap neo-liang-sap handover this ticket to you, please take care.
@neo-liang-sap This issue has not been touched since 10 work days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap This issue has not been touched since 21 work days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap This issue has not been touched since 24 work days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap This issue has not been touched since 24 work days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap This issue has not been touched since 28 work days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap This issue has not been touched since 92 work days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap This issue has not been touched since 97 work days. Please add a follow up comment and/or change the status/
label.
@neo-liang-sap This issue has not been touched since 174 work days. Please add a follow up comment and/or change the status/
label.
Which cluster is affected?
Cluster Details Dashboard Link
: https://dashboard.garden.dev.k8s.ondemand.com/namespace/garden-sretestneo/shoots/sre-g-test/What happened?
What you expected to happen?
When did it happen or started to happen?
Absolute
:Relative
:How would we reproduce it (concisely and precisely)?
Anything else we need to know?
Help us categorise this issue for faster resolution:
/area audit-logging auto-scaling backup certification control-plane cost delivery disaster-recovery documentation high-availability logging metering monitoring networking os performance quality security storage usability user-management /component gardener dashboard documentation /kind bug regression post-mortem /os garden-linux suse-chost /platform alicloud aws azure gcp converged-cloud
/priority critical