Skip to content

Panic (exit 101) in cloud service delete --force when service is mid-stopping #598

Description

@sdairs

Discovered during v0.4.2 post-merge stress testing.

Repro

chctl cloud service create --name chctl-stress-cp --provider aws --region eu-west-1 --json
# wait until running, then:
chctl cloud service delete --force <id>

Actual

Stdout printed Stopping service … state: stopping, then the process panicked with exit code 101. An immediate retry succeeded (exit 0, service deleted).

Expected

Exit 0, or exit 1 with a clean error message — never a panic. Likely an unwrap() in the stop-then-delete polling path when the service is observed mid-stopping.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingcloudAffects cloud CLI commands

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions