Activity log for bug #1416928

Date Who What changed Old value New value Message
2015-02-02 02:07:21 Fabricio Costi bug added bug
2015-02-02 02:16:58 Fabricio Costi description node 0: bootstrap, lxc/0-2 node 1: lxc/0-6 node 2: metal only - on node 0, physical and lxc machines and all unit agents have the ip from node 0 lxcbr0 bridge assigned to apiaddress in agent.conf. they report correctly their state. - on node 1, physical and lxc machine and all unit agents have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. they can't reach it. - on node 2, physical machine agent have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. can't reach it. manually changing apiaddress on all agents to juju-br0 ip of node 0, stopping and starting all the agents solved the issue. after reboot, same problem happens as agent.conf is overwritten by juju on all lxc and units. juju-core 1.21.1 node 0: bootstrap, lxc/0-2 node 1: lxc/0-6 node 2: metal only - on node 0, physical and lxc machines and all unit agents have the ip from node 0 lxcbr0 bridge assigned to apiaddress in agent.conf. they report correctly their state. - on node 1, physical and lxc machine and all unit agents have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. they can't reach it. - on node 2, physical machine agent have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. can't reach it. manually changing apiaddress on all agents to juju-br0 ip of node 0, stopping and starting all the agents solved the issue. after reboot, same problem happens as agent.conf is overwritten by juju on all lxc and units.
2015-02-02 02:20:06 Fabricio Costi summary juju agent using lxcbr0 address as apiaddress instead of juju-br0 after reboot juju agent using lxcbr0 address as apiaddress instead of juju-br0 breaks agents
2015-02-02 04:40:44 Fabricio Costi description juju-core 1.21.1 node 0: bootstrap, lxc/0-2 node 1: lxc/0-6 node 2: metal only - on node 0, physical and lxc machines and all unit agents have the ip from node 0 lxcbr0 bridge assigned to apiaddress in agent.conf. they report correctly their state. - on node 1, physical and lxc machine and all unit agents have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. they can't reach it. - on node 2, physical machine agent have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. can't reach it. manually changing apiaddress on all agents to juju-br0 ip of node 0, stopping and starting all the agents solved the issue. after reboot, same problem happens as agent.conf is overwritten by juju on all lxc and units. juju-core 1.21.1 node 0: bootstrap, lxc/0-2 - juju-br0 10.10.18.51 (eth0) - lxcbr0 10.0.3.1 - eth1 in promisc mode node 1: lxc/0-6 - juju-br0 10.10.18.52 (eth0) - lxcbr0 10.0.3.1 - virbr0 192.168.122.1 - eth1 in promisc mode node 2: metal only - juju-br0 10.10.18.53 (eth0) - virbr0 192.168.122.1 - eth1 in promisc mode - on node 0, physical and lxc machines and all unit agents have the ip from node 0 lxcbr0 bridge assigned to apiaddress in agent.conf. They report correctly their state. - on node 1, physical and lxc machine and all unit agents have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. They can't reach WSS. - on node 2, physical machine agent have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. Can't reach WSS. I am assuming all agents are getting the lxcbr0 ip from node 0 as node 2 do not have an lxcbr0 and yet it has the 10.0.3.1 ip assigned to its apiaddress in agent.conf. Manually changing apiaddress on all agents to juju-br0 ip of node 0, stopping and starting all the agents temporarily solved the issue. After reboot, same problem happens as agent.conf is overwritten by juju on all machines, lxc and units.
2015-02-02 14:15:30 Curtis Hovey tags lxc network
2015-02-02 14:15:47 Curtis Hovey tags lxc network api lxc network
2015-02-03 02:25:23 Paul Gear attachment added machine-6.log https://bugs.launchpad.net/juju-core/+bug/1416928/+attachment/4310918/+files/machine-6.log
2015-02-03 14:01:34 Curtis Hovey juju-core: status New Triaged
2015-02-03 14:01:37 Curtis Hovey juju-core: importance Undecided High
2015-02-03 14:01:38 Curtis Hovey juju-core: milestone 1.23
2015-02-03 14:01:48 Curtis Hovey nominated for series juju-core/1.21
2015-02-03 14:01:48 Curtis Hovey bug task added juju-core/1.21
2015-02-03 14:01:48 Curtis Hovey nominated for series juju-core/1.22
2015-02-03 14:01:48 Curtis Hovey bug task added juju-core/1.22
2015-02-03 14:01:55 Curtis Hovey juju-core/1.21: status New Triaged
2015-02-03 14:02:04 Curtis Hovey juju-core/1.22: status New Triaged
2015-02-03 14:02:06 Curtis Hovey juju-core/1.21: importance Undecided High
2015-02-03 14:02:08 Curtis Hovey juju-core/1.22: importance Undecided High
2015-02-03 14:02:11 Curtis Hovey juju-core/1.21: milestone 1.23
2015-02-03 14:02:17 Curtis Hovey juju-core/1.21: milestone 1.23 1.21.2
2015-02-03 14:02:26 Curtis Hovey juju-core/1.22: milestone 1.22-beta3
2015-02-09 11:43:13 Dimiter Naydenov juju-core/1.21: status Triaged Incomplete
2015-02-09 13:58:28 Curtis Hovey juju-core/1.21: status Incomplete Triaged
2015-02-09 16:33:21 Dimiter Naydenov juju-core/1.21: milestone 1.21.2
2015-02-09 18:05:43 Curtis Hovey juju-core/1.21: milestone 1.21.3
2015-02-10 21:37:46 Curtis Hovey juju-core/1.22: milestone 1.22-beta3 1.22-beta4
2015-02-11 15:40:07 Curtis Hovey description juju-core 1.21.1 node 0: bootstrap, lxc/0-2 - juju-br0 10.10.18.51 (eth0) - lxcbr0 10.0.3.1 - eth1 in promisc mode node 1: lxc/0-6 - juju-br0 10.10.18.52 (eth0) - lxcbr0 10.0.3.1 - virbr0 192.168.122.1 - eth1 in promisc mode node 2: metal only - juju-br0 10.10.18.53 (eth0) - virbr0 192.168.122.1 - eth1 in promisc mode - on node 0, physical and lxc machines and all unit agents have the ip from node 0 lxcbr0 bridge assigned to apiaddress in agent.conf. They report correctly their state. - on node 1, physical and lxc machine and all unit agents have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. They can't reach WSS. - on node 2, physical machine agent have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. Can't reach WSS. I am assuming all agents are getting the lxcbr0 ip from node 0 as node 2 do not have an lxcbr0 and yet it has the 10.0.3.1 ip assigned to its apiaddress in agent.conf. Manually changing apiaddress on all agents to juju-br0 ip of node 0, stopping and starting all the agents temporarily solved the issue. After reboot, same problem happens as agent.conf is overwritten by juju on all machines, lxc and units. juju-core 1.21.1 node 0: bootstrap, lxc/0-2     - juju-br0 10.10.18.51 (eth0)     - lxcbr0 10.0.3.1     - eth1 in promisc mode node 1: lxc/0-6     - juju-br0 10.10.18.52 (eth0)     - lxcbr0 10.0.3.1     - virbr0 192.168.122.1     - eth1 in promisc mode node 2: metal only     - juju-br0 10.10.18.53 (eth0)     - virbr0 192.168.122.1     - eth1 in promisc mode - on node 0, physical and lxc machines and all unit agents have the ip from node 0 lxcbr0 bridge assigned to apiaddress in agent.conf. They report correctly their state. - on node 1, physical and lxc machine and all unit agents have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. They can't reach WSS. - on node 2, physical machine agent have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. Can't reach WSS. I am assuming all agents are getting the lxcbr0 ip from node 0 as node 2 do not have an lxcbr0 and yet it has the 10.0.3.1 ip assigned to its apiaddress in agent.conf. Manually changing apiaddress on all agents to juju-br0 ip of node 0, stopping and starting all the agents temporarily solved the issue. After reboot, same problem happens as agent.conf is overwritten by juju on all machines, lxc and units. To reproduce: juju bootstrap juju ssh 0 "sudo grep -A 1 apiaddresses /var/lib/juju/agents/machine-0/agent.conf" apiaddresses: - REAL_ETH0_ADDRESS:17070 juju ssh 0 "sudo apt-get install -y lxc" juju ssh 0 "sudo reboot -n" juju ssh 0 "sudo grep -A 1 apiaddresses /var/lib/juju/agents/machine-0/agent.conf" apiaddresses: - 10.0.3.1:17070
2015-02-11 15:58:41 Curtis Hovey description juju-core 1.21.1 node 0: bootstrap, lxc/0-2     - juju-br0 10.10.18.51 (eth0)     - lxcbr0 10.0.3.1     - eth1 in promisc mode node 1: lxc/0-6     - juju-br0 10.10.18.52 (eth0)     - lxcbr0 10.0.3.1     - virbr0 192.168.122.1     - eth1 in promisc mode node 2: metal only     - juju-br0 10.10.18.53 (eth0)     - virbr0 192.168.122.1     - eth1 in promisc mode - on node 0, physical and lxc machines and all unit agents have the ip from node 0 lxcbr0 bridge assigned to apiaddress in agent.conf. They report correctly their state. - on node 1, physical and lxc machine and all unit agents have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. They can't reach WSS. - on node 2, physical machine agent have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. Can't reach WSS. I am assuming all agents are getting the lxcbr0 ip from node 0 as node 2 do not have an lxcbr0 and yet it has the 10.0.3.1 ip assigned to its apiaddress in agent.conf. Manually changing apiaddress on all agents to juju-br0 ip of node 0, stopping and starting all the agents temporarily solved the issue. After reboot, same problem happens as agent.conf is overwritten by juju on all machines, lxc and units. To reproduce: juju bootstrap juju ssh 0 "sudo grep -A 1 apiaddresses /var/lib/juju/agents/machine-0/agent.conf" apiaddresses: - REAL_ETH0_ADDRESS:17070 juju ssh 0 "sudo apt-get install -y lxc" juju ssh 0 "sudo reboot -n" juju ssh 0 "sudo grep -A 1 apiaddresses /var/lib/juju/agents/machine-0/agent.conf" apiaddresses: - 10.0.3.1:17070 juju-core 1.21.1 node 0: bootstrap, lxc/0-2     - juju-br0 10.10.18.51 (eth0)     - lxcbr0 10.0.3.1     - eth1 in promisc mode node 1: lxc/0-6     - juju-br0 10.10.18.52 (eth0)     - lxcbr0 10.0.3.1     - virbr0 192.168.122.1     - eth1 in promisc mode node 2: metal only     - juju-br0 10.10.18.53 (eth0)     - virbr0 192.168.122.1     - eth1 in promisc mode - on node 0, physical and lxc machines and all unit agents have the ip from node 0 lxcbr0 bridge assigned to apiaddress in agent.conf. They report correctly their state. - on node 1, physical and lxc machine and all unit agents have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. They can't reach WSS. - on node 2, physical machine agent have the node 0 lxcbr0 ip assigned to apiaddress in agent.conf. Can't reach WSS. I am assuming all agents are getting the lxcbr0 ip from node 0 as node 2 do not have an lxcbr0 and yet it has the 10.0.3.1 ip assigned to its apiaddress in agent.conf. Manually changing apiaddress on all agents to juju-br0 ip of node 0, stopping and starting all the agents temporarily solved the issue. After reboot, same problem happens as agent.conf is overwritten by juju on all machines, lxc and units. To reproduce with 1.21 in a cloud: juju bootstrap juju ssh 0 "sudo grep -A 1 apiaddresses /var/lib/juju/agents/machine-0/agent.conf"   apiaddresses:   - REAL_ETH0_ADDRESS:17070 juju ssh 0 "sudo apt-get install -y lxc" juju ssh 0 "sudo reboot -n" juju ssh 0 "sudo grep -A 1 apiaddresses /var/lib/juju/agents/machine-0/agent.conf"   apiaddresses:   - 10.0.3.1:17070 Or with manual-provider with lxc installed on the target state-server: juju bootstrap juju ssh 0 "sudo grep -A 1 apiaddresses /var/lib/juju/agents/machine-0/agent.conf"   apiaddresses:   - 10.0.3.1:17070
2015-02-11 17:48:42 Curtis Hovey juju-core: importance High Critical
2015-02-11 22:42:14 Curtis Hovey juju-core/1.22: importance High Critical
2015-02-11 22:42:16 Curtis Hovey juju-core/1.21: importance High Critical
2015-02-11 22:42:19 Curtis Hovey juju-core: importance Critical High
2015-02-11 22:43:41 Curtis Hovey juju-core: assignee Dimiter Naydenov (dimitern)
2015-02-11 22:43:57 Curtis Hovey juju-core/1.21: assignee Dimiter Naydenov (dimitern)
2015-02-11 22:44:10 Curtis Hovey juju-core/1.22: assignee Dimiter Naydenov (dimitern)
2015-02-11 22:48:17 Curtis Hovey juju-core: importance High Critical
2015-02-11 22:48:39 Curtis Hovey juju-core: importance Critical High
2015-02-16 15:46:20 Dimiter Naydenov juju-core: status Triaged In Progress
2015-02-17 07:57:29 Dimiter Naydenov juju-core/1.21: status Triaged In Progress
2015-02-17 07:57:33 Dimiter Naydenov juju-core/1.22: status Triaged In Progress
2015-02-17 19:52:59 Dimiter Naydenov juju-core/1.21: status In Progress Fix Committed
2015-02-17 19:53:17 Dimiter Naydenov juju-core: status In Progress Triaged
2015-02-17 19:53:20 Dimiter Naydenov juju-core/1.22: status In Progress Triaged
2015-02-17 19:53:37 Dimiter Naydenov juju-core/1.22: assignee Dimiter Naydenov (dimitern) James Tunnicliffe (dooferlad)
2015-02-17 19:53:48 Dimiter Naydenov juju-core: assignee Dimiter Naydenov (dimitern) James Tunnicliffe (dooferlad)
2015-02-17 21:37:21 Curtis Hovey juju-core/1.21: status Fix Committed In Progress
2015-02-17 23:12:08 Curtis Hovey juju-core/1.21: status In Progress Fix Committed
2015-02-17 23:55:10 Curtis Hovey juju-core/1.21: status Fix Committed Fix Released
2015-02-18 18:35:08 James Tunnicliffe juju-core: status Triaged In Progress
2015-02-18 18:35:14 James Tunnicliffe juju-core/1.22: status Triaged In Progress
2015-02-18 22:39:39 Curtis Hovey juju-core/1.22: status In Progress Fix Released
2015-02-19 15:50:54 James Tunnicliffe juju-core: status In Progress Fix Committed
2015-02-19 15:50:59 James Tunnicliffe juju-core: status Fix Committed In Progress
2015-02-19 16:37:07 James Tunnicliffe juju-core: status In Progress Fix Committed
2015-03-09 17:50:25 Curtis Hovey juju-core: status Fix Committed Fix Released
2015-03-09 19:09:56 Curtis Hovey juju-core: milestone 1.23 1.23-beta1
2015-04-10 00:36:39 Joshua Randall bug added subscriber Joshua Randall