[Bug 1545913] Re: [FFe] juju-core 2.0

** Changed in: juju-core (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1545913 Title: [FFe] juju-core 2.0 To manage notifications about

[Bug 1409639] Re: juju needs to support systemd for >= vivid

(I should have added: but will support Ubuntu, with a couple of minor adjustments) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1409639 Title: juju needs to support systemd for

[Bug 1409639] Re: juju needs to support systemd for >= vivid

Systemd support is currently under development, primarily to support CentOS: http://reviews.vapour.ws/r/671/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1409639 Title: juju nee

[Bug 1316579] Re: --upload-tools doesn't work with bootstrap on armhf machine managed by maas

I'm pretty sure this is fixed in 1.21-alpha1. Can someone with an ARM machine please test it? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1316579 Title: --upload-tools doesn't

[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider

@danieru: what network interfaces show up? is the primary network interface called something other than "eth0"? If so, you'd need to set the "network-bridge" attribute in environments.yaml. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed t

[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider

** No longer affects: juju-core/1.20 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notificati

[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider

** Also affects: juju-core/1.20 Importance: Undecided Status: New ** Changed in: juju-core/1.20 Milestone: None => 1.20.2 ** Changed in: juju-core/1.20 Importance: Undecided => High ** Changed in: juju-core/1.20 Status: New => Triaged -- You received this bug notificati

[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider

Sorry, I was thinking that lp:1337091 was released already. We will look at getting it into 1.20.2. If you set the kernel parameter via MAAS [0] prior to first boot, then I would concur that it's probably not going to help. If, however, you modified GRUB after it came up and rebooted, I think that

[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider

Rick, Sorry for the frustration. It is certainly not unreasonable to expect 14.04 to be working. br0 is only brought up on first boot, so rebooting would not have triggered that part of cloud-config again. I believe we are looking at back-porting Juju 1.20.2 (the next stable release) into 14.04.

[Bug 1250007] Re: Bootstrapping azure causes memory to fill

** Changed in: juju-core Status: In Progress => Fix Committed ** Changed in: juju-core Milestone: next-stable => 1.19.4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/125

[Bug 1250007] Re: Bootstrapping azure causes memory to fill

** Changed in: juju-core Status: Triaged => In Progress ** Changed in: juju-core Assignee: (unassigned) => Andrew Wilkins (axwalk) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu.

[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider

> So, my nodes don't have eth0, but p1p1, if that makes any difference. This is most likely the key; the MAAS provider code assumes it's dealing with eth0. Thanks for the information. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juj

[Bug 1316272] Re: juju destroy-environment >=256 nodes fails

Sadly I do not have a 256+ node MAAS to test with. I'm going to mark this as Fix Committed; please let me know if you still have issues. ** Changed in: juju-core Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, whic

[Bug 1316272] Re: juju destroy-environment >=256 nodes fails

** Branch linked: lp:~axwalk/juju-core/lp1260171-stopinstances-ids -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1316272 Title: juju destroy-environment >=256 nodes fails To man

[Bug 1316272] Re: juju destroy-environment >=256 nodes fails

** Changed in: juju-core Assignee: (unassigned) => Andrew Wilkins (axwalk) ** Changed in: juju-core Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu.

[Bug 1316272] Re: juju destroy-environment >=256 nodes fails

We already do POST when stopping instances. The problem is likely that we first have to map instance IDs to instances so we can stop them (this is dumb and needs to change; see lp:1260171). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed t

[Bug 1313785] Re: Can't SSH with "juju ssh" command to EC2 instance.

** Changed in: juju-core Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1313785 Title: Can't SSH with "juju ssh" command to EC2 instance. T

[Bug 1313785] Re: Can't SSH with "juju ssh" command to EC2 instance.

** Branch linked: lp:~axwalk/juju-core/lp1313785-ssh-useproxy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1313785 Title: Can't SSH with "juju ssh" command to EC2 instance. To manag

[Bug 1313785] Re: Can't SSH with "juju ssh" command to EC2 instance.

Thanks, I hadn't noticed the version difference. I can also reproduce the issue with a 1.18.2 server. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1313785 Title: Can't SSH with "juju

[Bug 1313785] Re: Can't SSH with "juju ssh" command to EC2 instance.

** Changed in: juju-core Status: Triaged => In Progress ** Changed in: juju-core Assignee: (unassigned) => Andrew Wilkins (axwalk) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchp

[Bug 1313785] Re: Can't SSH with "juju ssh" command to EC2 instance.

I am not able to reproduce this. juju ssh will now ssh to machine 0's public address directly, and then proxy through that to machine 0's internal address. This is to support environments where machines do not have unique public addresses (i.e. with load balancing). Can you please ssh to the mach

[Bug 1248283] Re: juju userdata should not restart networking

** Branch linked: lp:~axwalk/juju-core/lp1271144-maas-bridge-utils ** Changed in: juju-core Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bug

[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider

** Branch linked: lp:~axwalk/juju-core/lp1271144-maas-bridge-utils ** Changed in: juju-core Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bug

[Bug 1248283] Re: juju userdata should not restart networking

** Changed in: juju-core Status: Triaged => In Progress ** Changed in: juju-core Assignee: (unassigned) => Andrew Wilkins (axwalk) ** Changed in: juju-core Milestone: 1.18.0 => 1.17.6 -- You received this bug notification because you are a member of Ubuntu Server Team,

[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider

** Changed in: juju-core Assignee: Roger Peppe (rogpeppe) => Andrew Wilkins (axwalk) ** Changed in: juju-core Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu.

[Bug 1284127] Re: juju deploy fails against juju-core 1.17.3 environment with 1.17.2 client

This only affects 1.17.2 and 1.17.3 interaction, so we can just close it. There was a change introduced in 1.17.2 to add an "image-stream" config attribute, which was previously specific to the Azure provider. The config default (omit) was invalid, though, causing the bug lp:1277636. We fixed this

[Bug 1240260] Re: juju bootstrap does not honor https_proxy in environment when fetching tools

You should be able to just set http_proxy, and have that work. Go will honour http_proxy, and do the usual CONNECT method. But, depends on whether you specifically don't want to proxy HTTP traffic. We'll need to make changes to our code to support both http_proxy and https_proxy, or wait for Go t

[Bug 1182898] Re: Please support `juju --version`

** Changed in: juju-core Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1182898 Title: Please support `juju --version` To manage notificat

[Bug 1182898] Re: Please support `juju --version`

** Branch linked: lp:~axwalk/juju-core/lp1182898-add-version-flag -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1182898 Title: Please support `juju --version` To manage notifica

[Bug 1182898] Re: Please support `juju --version`

** Changed in: juju-core Assignee: (unassigned) => Andrew Wilkins (axwalk) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1182898 Title: Please support `juju --version`