** Changed in: juju-core
Status: New => 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/1727355
Title:
Juju attempts to bootstrap bionic by default
To manage notifications about
using juju 1.25.13 (from ppa:juju/stable) in an updated trusty system
this problem is still there, to solve it default-series can be set.
root@juju1:~# apt-cache policy distro-info-data
distro-info-data:
Installed: 0.18ubuntu0.8
Candidate: 0.18ubuntu0.8
Version table:
*** 0.18ubuntu0.8 0
This bug was fixed in the package distro-info-data - 0.28ubuntu0.7
---
distro-info-data (0.28ubuntu0.7) xenial; urgency=medium
* Declare our breaks: against the correct juju-2.0 binary package, not
against juju-core which is juju-1 in xenial and not affected.
LP: #1727355.
I think we can release it to updates, but shouldn't release it to
security.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to bootstrap bionic by default
To manage
So what is the final verdict? Should this distro-info-data be bin-copied
to -security as well? I guess I'll leave it in your hands Robie as you
seem to have more context.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FTR, I had this juju-core installed:
1.25.6-0ubuntu1.16.04.2 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64
Packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On a xenial server, with distro-info-data 0.28ubuntu0.6 from current
xenial-updates, juju-core is removed:
0.28ubuntu0.6 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
root@atlas:~# apt install distro-info-data
Reading package lists... Done
Building
On a xenial server, with distro-info-data 0.28ubuntu0.6 from current
xenial-updates, juju-core is removed:
0.28ubuntu0.6 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
root@atlas:~# apt install distro-info-data
Reading package lists... Done
Building
FTR, I had this juju-core installed:
1.25.6-0ubuntu1.16.04.2 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64
Packages
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Actually the discussion was about about 1800 UTC yesterday. I was
getting a timeout trying to post the previous comment yesterday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju
There's some more discussion in #ubuntu-devel right now explaining why a
pocket copy of distro-info-data containing the Breaks to security would
be bad and will break things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
17:58 rbasak: if you're sruing it, just get someone to
pocket-copy it to -security after
17:58 mdeslaur: ah, OK. I was under the impression that a
pocket copy in that direction wasn't always safe.
17:58 (though seems unlikely to be an issue for distro-info-
data)
17:58 it isn't, but this
7:47 slangasek: looks good, but do you know any reason for
distro-info-data 0.28ubuntu0.3 to be in the security pocket?
17:48 rbasak: not offhand
17:49 Seems like some distro-info-data updates were
deliberately being put in there.
17:49 So now I don't know whether it's correct for this fix
** Changed in: distro-info-data (Ubuntu Xenial)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to bootstrap bionic
Sorry, 'juju-2.0'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to bootstrap bionic by default
To manage notifications about this bug go to:
Robie Basak and Andreas Hasenack have observed that the Breaks: from
distro-info-data are against the wrong package: juju-core is built from
juju-1 source and there is no newer version of this binary package in
xenial which is not affected by the Breaks:, resulting in distro-info-
data being held
This bug was fixed in the package juju-core - 2.3.1-0ubuntu0.17.04.1
---
juju-core (2.3.1-0ubuntu0.17.04.1) zesty; urgency=medium
* New upstream release. (LP: #1718213)
juju-core (2.2.6-0ubuntu0.17.04.3) zesty; urgency=medium
* Only juju 2.3+ supports cidr expansion for no
This bug was fixed in the package juju-core - 2.3.1-0ubuntu0.16.04.1
---
juju-core (2.3.1-0ubuntu0.16.04.1) xenial; urgency=medium
* New upstream release. (LP: #1718213)
juju-core (2.2.6-0ubuntu0.16.04.3) xenial; urgency=medium
* Only juju 2.3+ supports cidr expansion for no
This bug was fixed in the package distro-info-data - 0.28ubuntu0.6
---
distro-info-data (0.28ubuntu0.6) xenial; urgency=medium
* Restore the 'LTS' label for 18.04, and declare a Breaks: on the older
versions of juju-core that don't handle this correctly. LP: #1727355.
--
This bug was fixed in the package distro-info-data - 0.33ubuntu0.4
---
distro-info-data (0.33ubuntu0.4) zesty; urgency=medium
* Restore the 'LTS' label for 18.04, and declare a Breaks: on the older
versions of juju-core that don't handle this correctly. LP: #1727355.
--
Confirming 2.3.1 proposed package works for xenial and zesty.
1. Bootstrap completes successfully
2. Agent is used from stream
3. default-series in metadata is xenial
4. distro-info-data contains bionic
** Tags removed: verification-needed verification-needed-xenial
verification-needed-zesty
Frode, the procps restart is necessary to apply the sysctl parameters we
set for LXD containers to provide a better experience for the juju use
case. If we don't do this, it would require a system restart for the
parameters to apply.
--
You received this bug notification because you are a member
It seems systemd has always acted this way, but apparently there's a fix
in 232+.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to bootstrap bionic by default
To
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
# grep -a container /proc/1/environ
container=lxc
Because of the juju deb post-inst script running 'invoke-rc.d procps
restart' you will get an
Hello Jason, or anyone else affected,
Accepted juju-core into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/2.2.6-0ubuntu0.17.04.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
For SRU verification, we want to ensure juju bootstrap still selects
xenial, even after distro-info-data shows bionic as an LTS.
I confirmed using the restored distro-info-data packages in zesty and
xenial proposed that juju is selecting xenial as the proper default
series. In addition, I
Hello Jason, or anyone else affected,
Accepted distro-info-data into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/distro-
info-data/0.28ubuntu0.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
This bug shouldn't be marked as Fix Released against Juju based on
Dean's comment, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to bootstrap bionic by default
Hello Jason, or anyone else affected,
Accepted juju-core into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/2.2.6-0ubuntu0.17.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Changed in: juju-core (Ubuntu Trusty)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to bootstrap bionic by default
To manage
** Changed in: juju-core (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: juju-core (Ubuntu Zesty)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New => Invalid
** Changed in: juju-core (Ubuntu Artful)
Status: New => Invalid
** Changed in: juju-core (Ubuntu Xenial)
Status: New => Triaged
**
>We could change Juju code to hard code the preferred LTS as one we know
works but this means we need to change Juju each time we want to update
the preferred LTS.
I strongly prefer an approach where what version of Ubuntu deployed
doesn't change on release dates. (similar breakage happened to
Yes, you are 100% correct. We can determine from distro info if the
labelled LTS release is ready or not. Juju 2.2.6 does do this check now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
> Although the effect of Juju using the series flagged by distro data as
latest LTS means that it will attempt to use bionic before it is ready.
distro-info-data clearly flags bionic as not released yet. For example,
"distro-info --devel" works as expected. So please have Juju use that
I filed bug 1727693 to track CI in Juju for distro-info-data changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to bootstrap bionic by default
To manage
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to bootstrap bionic by default
To manage notifications about this bug go to:
Although the effect of Juju using the series flagged by distro data as
latest LTS means that it will attempt to use bionic before it is ready.
We could change Juju code to hard code the preferred LTS as one we know
works but this means we need to change Juju each time we want to update
the
This issue is not that Juju breaks when a new series is released. The
problem is that Juju defaults to using the latest LTS as the series for
which to bring up machines if none is specified by the user. If bionic
becomes the latest LTS, Juju will try and find agent binaries to match.
And if we are
Reusing this same bug for the SRU to revert this.
** Changed in: distro-info-data (Ubuntu Zesty)
Status: Fix Released => In Progress
** Changed in: distro-info-data (Ubuntu Xenial)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member
This bug was fixed in the package distro-info-data - 0.33ubuntu0.3
---
distro-info-data (0.33ubuntu0.3) zesty; urgency=medium
* Drop the 'LTS' label from 18.04 as a temporary workaround for a juju
bug. This will be added back as soon as the juju fix is published
to
This bug was fixed in the package distro-info-data - 0.28ubuntu0.5
---
distro-info-data (0.28ubuntu0.5) xenial; urgency=medium
* Drop the 'LTS' label from 18.04 as a temporary workaround for a juju
bug. This will be added back as soon as the juju fix is published
to
distro-info-data seems to be working fine, although wrong with the
deliberate removal of LTS.
(zesty-amd64)root@impulse:/home/bdmurray/source-trees/apport/lp-retracer-config#
distro-info --lts
xenial
(zesty-amd64)root@impulse:/home/bdmurray/source-trees/apport/lp-retracer-config#
distro-info
** Changed in: juju
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/1727355
Title:
Juju attempts to bootstrap bionic by default
To manage notifications
Tested working on zesty:
# juju bootstrap lxd --debug
18:41:15 INFO juju.cmd supercommand.go:63 running juju [2.0.2 gc go1.7.4]
...
18:41:15 DEBUG juju.cmd.juju.commands bootstrap.go:834 provider attrs: map[]
18:41:16 INFO cmd cmd.go:141 Adding contents of
Tested working on xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to
$ juju bootstrap lxd --debug
..
18:25:50 DEBUG juju.cmd.juju.commands bootstrap.go:988 preparing controller
with config: map[https-proxy: no-proxy:127.0.0.1,localhost,::1
provisioner-harvest-mode:destroyed test-mode:false image-stream:released
apt-http-proxy: default-series:xenial ...
...
Hello Jason, or anyone else affected,
Accepted distro-info-data into zesty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/distro-
info-data/0.33ubuntu0.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
48 matches
Mail list logo
