| 2013-11-25 03:24:37 |
Tim Penhey |
bug |
|
|
added bug |
| 2013-11-25 09:38:31 |
Kent Lin |
bug |
|
|
added subscriber Kent Lin |
| 2013-11-25 14:14:02 |
Martin Packman |
juju-core: assignee |
|
Martin Packman (gz) |
|
| 2013-11-28 01:15:13 |
Martin Packman |
nominated for series |
|
juju-core/1.16 |
|
| 2013-11-28 01:15:13 |
Martin Packman |
bug task added |
|
juju-core/1.16 |
|
| 2013-11-28 01:15:28 |
Martin Packman |
juju-core/1.16: importance |
Undecided |
High |
|
| 2013-11-28 01:15:28 |
Martin Packman |
juju-core/1.16: status |
New |
Fix Committed |
|
| 2013-11-28 01:15:28 |
Martin Packman |
juju-core/1.16: milestone |
|
1.16.4 |
|
| 2013-11-28 01:15:28 |
Martin Packman |
juju-core/1.16: assignee |
|
Martin Packman (gz) |
|
| 2013-11-28 01:15:36 |
Martin Packman |
juju-core: status |
Triaged |
In Progress |
|
| 2013-11-28 09:15:18 |
Martin Packman |
branch linked |
|
lp:~gz/juju-core/juju-update-bootstrap |
|
| 2013-12-02 17:56:26 |
Curtis Hovey |
juju-core/1.16: status |
Fix Committed |
Fix Released |
|
| 2013-12-05 14:21:54 |
Martin Packman |
juju-core: status |
In Progress |
Fix Committed |
|
| 2013-12-05 14:21:54 |
Martin Packman |
juju-core: milestone |
|
1.17.0 |
|
| 2013-12-20 17:43:32 |
Curtis Hovey |
juju-core: status |
Fix Committed |
Fix Released |
|
| 2014-02-07 13:53:54 |
James Page |
bug task added |
|
juju-core (Ubuntu) |
|
| 2014-02-07 13:54:16 |
James Page |
nominated for series |
|
Ubuntu Saucy |
|
| 2014-02-07 13:54:16 |
James Page |
bug task added |
|
juju-core (Ubuntu Saucy) |
|
| 2014-02-07 13:54:28 |
James Page |
juju-core (Ubuntu): status |
New |
Fix Released |
|
| 2014-02-07 14:03:26 |
Launchpad Janitor |
branch linked |
|
lp:~james-page/ubuntu/saucy/juju-core/1.16.5 |
|
| 2014-04-10 10:57:20 |
James Page |
description |
The purpose of this plugin is to update a bootstrap address on all other running juju machines given that the bootstrap node has failed completely, and another bootstrap node has been brought up using the plugins described in bug 1254574 and bug 1254577.
Fundamentally this should be reasonably simple:
run 'juju status' and parse the results to get a list of machines to ssh into (excluding machine 0).
for each machine:
ssh to that machine
stop the machine agent and each unit agent
edit the udp address in the /etc/rsyslog configuration for each juju agent
restart rsyslog
edit the api addresses and state addresses stored for the machine and each unit agent
start the machine agent and each unit agent |
[Impact]
Users of juju environments with failed bootstrap nodes are unable to restore the environment (backup/recovery)
[Test Case]
In a failed environment which has had a new bootstrap node provisioned and the original state restored from backup as described in bug #1254729
juju update-bootstrap
Existing machines will be updated to report into the new juju bootstrap node.
[Regression Potential]
Minimal; this new plugin is separate to the existing codebase.
[Original Bug Report]
The purpose of this plugin is to update a bootstrap address on all other running juju machines given that the bootstrap node has failed completely, and another bootstrap node has been brought up using the plugins described in bug 1254574 and bug 1254577.
Fundamentally this should be reasonably simple:
run 'juju status' and parse the results to get a list of machines to ssh into (excluding machine 0).
for each machine:
ssh to that machine
stop the machine agent and each unit agent
edit the udp address in the /etc/rsyslog configuration for each juju agent
restart rsyslog
edit the api addresses and state addresses stored for the machine and each unit agent
start the machine agent and each unit agent |
|
| 2014-12-05 07:03:17 |
Rolf Leggewie |
juju-core (Ubuntu Saucy): status |
New |
Won't Fix |
|
