Bootstrap without specifying arch and image doesn't fail cleanly
Bug #1999753 reported by
Simon Richardson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
When using --bootstrap--image without --bootstrap-
```
juju bootstrap localhost test --build-agent --bootstrap-
ERROR --bootstrap-image must be used with --bootstrap-
```
then
```
juju bootstrap localhost test --build-agent --bootstrap-
ERROR controller "test" already exists
```
Didn't catch on the bootstrap-image and bootstrap-base.
Changed in juju: | |
milestone: | 3.1-beta1 → 3.1-rc1 |
Changed in juju: | |
milestone: | 3.1-rc1 → 3.1-rc2 |
Changed in juju: | |
milestone: | 3.1-rc2 → 3.1-rc3 |
To post a comment you must log in.
So this is "error while creating doesn't properly cleanup the registry"? or
is this "we shouldn't be erroring under this circumstance"?
John
=:->
On Thu, Dec 15, 2022 at 5:00 AM Simon Richardson <email address hidden>
wrote:
> Public bug reported: constraints doesn't image=five base=ubuntu@ 22.04 constraints, image=five base=ubuntu@ 22.04 --bootstrap- constraints "arch=arm64" /bugs.launchpad .net/bugs/ 1999753 /bugs.launchpad .net/juju/ +bug/1999753/ +subscriptions
>
> When using --bootstrap--image without --bootstrap-
> correctly remove the controller from the controllers.yaml.
>
>
> ```
> juju bootstrap localhost test --build-agent --bootstrap-
> --bootstrap-
> ERROR --bootstrap-image must be used with --bootstrap-
> specifying architecture
> ```
> then
> ```
> juju bootstrap localhost test --build-agent --bootstrap-
> --bootstrap-
> ERROR controller "test" already exists
> ```
> Didn't catch on the bootstrap-image and bootstrap-base.
>
> ** Affects: juju
> Importance: Low
> Status: Triaged
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> Bootstrap without specifying arch and image doesn't fail cleanly
>
> To manage notifications about this bug go to:
> https:/
>
>