Trusty is no longer a supported Juju series.
** Changed in: juju
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599886
Title:
apt-mirror does not override
@John I fully agree. All this information is already available to juju,
so IMHO juju should just use it. Instead of picking up information from
MAAS, juju should just take a peak into host's cloud-config data and use
it to generate LXD and KVM cloud-config. Obviously, it should override
some
Note that any time you actively need to use custom userdata is probably a
time where Juju is failing to model something important. So while it is an
outlet to getting something that works, it should still be a bug that we
don't support the underlying use case correctly.
John
=:->
On Sun, Dec
cloud-init user-data customization seems to be an easy solution for
this:
https://github.com/juju/juju/pull/8177 (merged)
https://github.com/juju/juju/pull/8177/files
https://github.com/juju/juju/pull/8188 (pending)
https://github.com/juju/juju/pull/8188/files
It adds several useful mechanisms:
** Tags removed: cpec
** Tags added: cpe-onsite
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599886
Title:
apt-mirror does not override security.ubuntu.com for containers on
trusty
To manage
Any milestone for this?
This is quite crucial when deploying on private clouds and limiting
outgoing traffic on instances to only trusted or validated sources. And
we don't want to use security.ubuntu.com as repository but our own
private repositories inside the OpenStack
--
You received this
So Juju itself could accept apt_security_mirror as the configuration key
and map that to whatever is necessary for the series we are deploying.
John
=:->
On Mar 8, 2017 20:19, "Seyeong Kim" wrote:
> I agree with jameinel,
>
> supporting kind of apt_security_mirror is
I agree with jameinel,
supporting kind of apt_security_mirror is better rather than failsafe.
but still there is one issue if juju can support sort of
'apt_security_mirror' from now.
because of differences between cloud-init versions on trusty and xenial.
I'm not sure it's possible to make
It feels like overriding security.ubuntu.com should be a separate setting,
since it is security sensitive, vs having the normal 'apt_mirror' override
both settings always. Otherwise why would cloud-init itself have 2
different settings.
maybe 'apt_security_mirror' ? I'm not sure on the specific
@Anastasia (anastasia-macmood)
tested 2.0.3, 2.1 and 2.2-alpha1.1 but have same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599886
Title:
apt-mirror does not override security.ubuntu.com
tested 2.0.3 but have same issue
and FYI
I talked smoser who maintains cloud-init.
he also think this is not cloud-init bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599886
Title:
As I wrote in the bug description, security.ubuntu.com can be overwritten on
trusty by:
#cloud-config
system_info:
package_mirrors:
- arches: [i386, amd64]
failsafe:
primary: http://localmirror.example.com/ubuntu
security: http://localmirror.example.com/ubuntu
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug
** Changed in: cloud-init (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Fix Released
--
You received this bug notification because you are a member of
@Seyeong Kim (xtrusia),
You have previously tested against 2.0.2 and 2.1 beta (I am guessing
both on xenial).
Have you had a chance to test your fix with Juju on trusty? Latest equivalent
versions are 2.0.3 and 2.1-rc1.
** Changed in: juju
Status: Triaged => Incomplete
--
You
cloud-init on trusty has no functionality for security repository.
(0.7.5-0ubuntu1.21)
below commit on upstream is related but there are a lot of dependencies.
so i'm not sure it's fixable.
commit d861415ff9ab816b1183b8c58ec35348be4fd458
Author: Christian Ehrhardt
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
17 matches
Mail list logo