2013-10-30 14:20:10 |
Chris Glass |
bug |
|
|
added bug |
2013-10-31 14:47:35 |
Curtis Hovey |
tags |
|
landscape |
|
2013-10-31 14:48:41 |
Curtis Hovey |
summary |
Juju manual provider does not destroy the .jenv file when running destroy-environment |
destroy-environment no longer removes .jenv |
|
2013-10-31 14:48:46 |
Curtis Hovey |
juju-core: status |
New |
Triaged |
|
2013-10-31 14:48:49 |
Curtis Hovey |
juju-core: importance |
Undecided |
High |
|
2013-10-31 14:48:52 |
Curtis Hovey |
juju-core: milestone |
|
1.17.0 |
|
2013-10-31 14:49:11 |
Curtis Hovey |
tags |
landscape |
destroy-environment landscape |
|
2013-10-31 14:49:50 |
Curtis Hovey |
tags |
destroy-environment landscape |
charmers destroy-environment landscape |
|
2013-10-31 14:51:50 |
Curtis Hovey |
description |
Running "juju destroy-enviornment" when using the null provider does not delete the ~/.juju/environments/null.jenv file. This results in user confusion when for example a failure was due to an incorrect configuration.
Steps to reproduce:
1. Install a fresh ubuntu server inside a KVM to use as a bootstrap node.
2. run "juju init; juju switch null"
3. edit ~/.juju/environments.yaml, add the KVM's IP address in the null provider's "bootstrap-host" entry. Make a typo.
4. run "juju bootstrap". Since step 3 introduced a typo, the environment fails to bootstrap.
5. correct the typo.
6. Run "juju destroy-environment"
7. Run "juju bootstrap" again.
What happens:
The first Ip address entered is used in all subsequent bootstraps. Juju destroy-environment 's behavior is not consistent with other providers implementations.
What was expected:
The juju destroy-environment command should remove the ~/.juju/environments/null.jenv file. This would make a subsequent environment creation regenerate that file, therefore allowing for a successful deployement. Similarly, a call to "destroy-environment" for other providers allows to correct provider configuration mistake.
Subjective comment:
It is reasonable to assume that "juju destroy-environment" resets juju's knowledge of the environment. |
Running "juju destroy-enviornment" when using the null provider and other providers does not delete the ~/.juju/environments/null.jenv file. This results in user confusion when for example a failure was due to an incorrect configuration.
Steps to reproduce:
1. Install a fresh ubuntu server inside a KVM to use as a bootstrap node.
2. run "juju init; juju switch null"
3. edit ~/.juju/environments.yaml, add the KVM's IP address in the null provider's "bootstrap-host" entry. Make a typo.
4. run "juju bootstrap". Since step 3 introduced a typo, the environment fails to bootstrap.
5. correct the typo.
6. Run "juju destroy-environment"
7. Run "juju bootstrap" again.
What happens:
The first Ip address entered is used in all subsequent bootstraps. Juju destroy-environment 's behavior is not consistent with other providers implementations.
What was expected:
The juju destroy-environment command should remove the ~/.juju/environments/null.jenv file. This would make a subsequent environment creation regenerate that file, therefore allowing for a successful deployement. Similarly, a call to "destroy-environment" for other providers allows to correct provider configuration mistake.
Subjective comment:
It is reasonable to assume that "juju destroy-environment" resets juju's knowledge of the environment.
ADDENDUM
This affects several providers |
|
2013-11-01 11:17:03 |
William Reade |
juju-core: assignee |
|
Andrew Wilkins (axwalk) |
|
2013-11-01 11:17:07 |
William Reade |
juju-core: milestone |
1.17.0 |
2.0 |
|
2013-11-13 04:58:04 |
Andrew Wilkins |
juju-core: status |
Triaged |
In Progress |
|
2013-11-13 04:59:46 |
Andrew Wilkins |
branch linked |
|
lp:~axwalk/juju-core/lp1246983-cli-api-removeagents |
|
2013-11-13 17:10:27 |
Chris Glass |
bug |
|
|
added subscriber Landscape Bugs |
2014-01-15 02:20:10 |
Andrew Wilkins |
juju-core: status |
In Progress |
Won't Fix |
|
2014-01-15 02:20:12 |
Andrew Wilkins |
juju-core: status |
Won't Fix |
Fix Committed |
|
2014-01-15 02:20:31 |
Andrew Wilkins |
juju-core: milestone |
2.0 |
1.17.1 |
|
2014-01-28 15:48:35 |
Curtis Hovey |
juju-core: status |
Fix Committed |
Fix Released |
|
2014-01-28 19:09:22 |
Adam Collard |
tags |
charmers destroy-environment landscape |
charmers destroy-environment landscape micro-cluster |
|