** 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
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
(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
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
@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 to
** 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
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
** 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 notification
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
** 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.
** 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.
https
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
** 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.
https
** 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
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,
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
** 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.
To
** 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.launchpad.net
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
** 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 manage
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
** 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.
https
** 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, which
** 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.
** 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.
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
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
** 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
** 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
** 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
30 matches
Mail list logo
