This bug was fixed in the package juju-core - 1.17.6-0ubuntu1
---
juju-core (1.17.6-0ubuntu1) trusty; urgency=medium
* New upstream point release, including fixes for:
- br0 not bought up by cloud-init with MAAS provider (LP: #1271144).
- ppc64el enablement for juju/lxc (LP:
** Changed in: juju-core
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129720
Title:
juju instances not including the "default" security group
To manag
** Changed in: juju-core
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129720
Title:
juju instances not including the "default" security group
To manage
Since some deployments will want the global default group added to Juju
machines and others not, we've decided to make it configurable - the
default is false so existing behaviour is preserved. But deployments
that want to use the default group can do so but changing the config
option to true.
--
I'm not sure adding the default group is the right fix for wanting ad-
hoc per environment rules. I'd prefer if juju started tolerating
external tampering with the environment-specific juju group it adds to
all machines it creates. We could potentially report via status any
addition ports opened.
** Branch linked: lp:~wallyworld/juju-core/instance-default-secgroup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129720
Title:
juju instances not including the "default" security group
To manage
** Changed in: juju-core
Milestone: None => 1.17.1
** Changed in: juju-core
Assignee: (unassigned) => Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged => In Progress
** Changed in: juju
Status: Triaged => Won't Fix
--
You received this bug notification bec
** Changed in: juju-core (Ubuntu)
Importance: Undecided => High
** Changed in: juju-core (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129720
Title:
juju
** Tags removed: openstack
** Tags added: openstack-provider
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129720
Title:
juju instances not including the "default" security group
To manage notific
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
** Tags added: canonical-webops openstack security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
not quite the same, but juju environments also have a default group that
this these rules can be applied to once per env.
On Tue, Nov 19, 2013 at 10:43 PM, Haw Loeung <1129...@bugs.launchpad.net>wrote:
> ** Also affects: juju-core
>Importance: Undecided
>Status: New
>
> ** Also affec
** Also affects: juju-core
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
12 matches
Mail list logo