juju 1.17.x cannot destroy a 1.16.5 azure environment
Bug #1277636 reported by
Curtis Hovey
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Andrew Wilkins |
Bug Description
CI has observed that juju 1.17.x cannot call destroy-environment
$ juju destroy-environment --force test-cloud-azure
ERROR empty image-stream in environment configuration
But doing this with 1.16.5 does succeed
$ juju destroy-environment -e test-cloud-azure
WARNING: this command will destroy the "test-cloud-azure" environment (type: azure)
This includes all machines, services, data and other resources.
Continue [y/N]? y
This may relate to the change that made image-stream available to all providers instead of just azure
Related branches
lp:~axwalk/juju-core/lp1277636-image-stream-default
- Juju Engineering: Pending requested
-
Diff: 61 lines (+15/-3)3 files modifiedenvirons/config/config.go (+4/-3)
environs/config/config_test.go (+1/-0)
provider/azure/config_test.go (+10/-0)
tags: | added: ci |
Changed in juju-core: | |
milestone: | none → 1.17.3 |
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.