Skip to content
Janitor

Janitor #217

Sign in to view logs

Janitor

Janitor #217

Triggered via schedule October 17, 2024 03:19
@cpinjanicpinjani
⁠ b6458b2
main
Status Success
Total duration 1h 25m 41s
Artifacts –

janitor.yaml

on: schedule
azure-janitor
29m 27s
azure-janitor
aws-janitor
1h 25m
aws-janitor
gcp-janitor
31s
gcp-janitor
Fit to window
Zoom out
Zoom in

Annotations

6 errors
aws-janitor
failed to delete security group sg-0bb8492492ac188a4: failed to delete security group sg-0bb8492492ac188a4: DependencyViolation: resource sg-0bb8492492ac188a4 has a dependent object
aws-janitor
failed to delete security group sg-03fadb311127dc16a: failed to delete security group sg-03fadb311127dc16a: DependencyViolation: resource sg-03fadb311127dc16a has a dependent object
aws-janitor
failed to mark cloudformation stack auto-eks-hp-ci-uiyuc-eks-vpc for future deletion: failed to update cloudformation stack auto-eks-hp-ci-uiyuc-eks-vpc: ValidationError: Stack:arn:aws:cloudformation:***:312662503588:stack/auto-eks-hp-ci-uiyuc-eks-vpc/685f9bd0-87a3-11ef-8d2a-02a5e128c529 is in UPDATE_ROLLBACK_FAILED state and can not be updated.
aws-janitor
failed to mark cloudformation stack auto-eks-hp-ci-ebtkk-eks-vpc for future deletion: failed to update cloudformation stack auto-eks-hp-ci-ebtkk-eks-vpc: ValidationError: Stack:arn:aws:cloudformation:***:312662503588:stack/auto-eks-hp-ci-ebtkk-eks-vpc/6856c230-87a3-11ef-bac3-0609fd31f9bd is in UPDATE_ROLLBACK_FAILED state and can not be updated.
aws-janitor
failed to delete cloudformation stack eksctl-auto-eks-hp-ci-eftiz-cluster: failed to wait for cloudformation stack eksctl-auto-eks-hp-ci-eftiz-cluster to delete: ResourceNotReady: failed waiting for successful resource state
aws-janitor
failed to delete cloudformation stack eksctl-auto-eks-hp-ci-ewpyg-cluster: failed to wait for cloudformation stack eksctl-auto-eks-hp-ci-ewpyg-cluster to delete: ResourceNotReady: failed waiting for successful resource state