I can't re-assign it seems. Poke @thumper.
** Changed in: golang-juju-loggo (Ubuntu)
Assignee: Nicholas Skaggs (nskaggs) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: juju-core (Ubuntu)
Status: New => Fix Committed
** Changed in: juju-core (Ubuntu)
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/17664
** Description changed:
This syncs juju with the upstream release bringing the latest bugfixes
and enhancements.
[SRU Information]
juju-core has a stable release exception, including for major version
updates, https://wiki.ubuntu.com/JujuUpdates.
[Impact]
A full list of targeted
I tested juju 2.3.7 and found no issues. Tested:
Bootstrap xenial and bionic controllers
Deploy various workloads, including percona
Installed and bootstrapped 2.3.2 controller and model, upgraded package, and
tested juju-upgrade 2.3.2 -> 2.3.7
Checked bash-completion
Deployed offline (xenial and
The source package can be found in https://git.launchpad.net/~juju-
qa/ubuntu/+source/juju-core, master branch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766415
Title:
[SRU] Juju 2.3.7
To mana
** Changed in: juju-core (Ubuntu)
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/1765257
Title:
[SRU] Juju 2.3.6
To manage notifications about this bug go to:
https://b
As an update to note, the juju team has done further manual testing on
the build in ppa:racb/experimental to ensure it meets our needs. This
included running real workloads and performing controller operations
like migration and HA. We're happy with the package.
--
You received this bug notificat
Public bug reported:
I am requesting we bump mongodb to the latest 3.6 version.
Rationale:
The default version of openssl in bionic is 1.1. Mongo3.4 doesn't support this
version, while mongo3.6 does.
Mongo upstream support generally averages 3 to 3.5 years, see
https://www.mongodb.com/support-
Thanks. You are correct. This is just playing with packaging; the source
is unchanged. I was thinking the same about not needing an FFe, but I
filed one anyway. If nothing else, it can provide clarity for anyone who
may have wondered why the split occurred.
--
You received this bug notification b
Public bug reported:
I am requesting a mongodb-server-core package that provides only
mongodb-server-binaries, with no user or services management. The
package should remain in universe, and be supported accordingly.
Rationale:
Juju is migrating to mongodb 3.4 for bionic, and would like to phase
** Changed in: juju-core (Ubuntu)
Status: In Progress => 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/1744968
Title:
[SRU] Juju 2.3.2
To manage notifications about this bug go
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done 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/1744968
Title:
[SRU] Juju 2.3.
I tested juju 2.3.2 and found it working, able to bootstrap, deploy,
bash completion all work. I deployed a bionic controller and workload as
well without any apparent issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Changed in: juju-core (Ubuntu Xenial)
Status: New => In Progress
** Changed in: juju-core (Ubuntu Artful)
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/1744968
adt test coverage for all supported archs,
http://autopkgtest.ubuntu.com/packages/j/juju-core/.
Finally, manual verification and testing of the package has been done
per https://wiki.ubuntu.com/JujuUpdates
** Affects: juju-core (Ubuntu)
Importance: Undecided
Assignee: Nicholas Skaggs
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
/usr/sbin/fanctl: arithmetic expression: expecting primary |
unconfigured interfaces cause ifup failur
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
**
Both zesty and xenial are verified. Bootstrap and deploy, update-clouds
and tab completion all working.
** Tags removed: verification-needed verification-needed-xenial
verification-needed-zesty
** Tags added: verification-done verification-done-xenial
verification-done-zesty
--
You received th
** Changed in: juju
Status: Triaged => Invalid
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
/usr/sbin/fanctl: arithmetic expression: expe
** Summary changed:
- [SRU] Juju 2.2.6
+ [SRU] Juju 2.3.1
** Description changed:
This syncs juju with the upstream release bringing the latest bugfixes
and enhancements.
[SRU Information]
juju-core has a stable release exception, including for major version
updates, https://wiki.ubu
We will seek to ship juju-mongo3.6 in leiu of this package. We need
mongo3.6 for juju 2.4, which will ship with bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730706
Title:
RM FTBFS with new
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 manage
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 confirme
Both zesty and xenial are verified and working successfully. I was able
to bootstrap and deploy on multiple providers, update-clouds and tab
completion worked, binaries and version are all as expected.
** Tags removed: verification-needed verification-needed-xenial
verification-needed-zesty
** Ta
** 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 notificati
Due to bug 1727355 which has a critical fix required for juju to operate
properly on xenial, we're aiming to land juju 2.2.6 now.
** Description changed:
This syncs juju with the upstream release bringing the latest bugfixes
and enhancements.
[SRU Information]
juju-core has a stable re
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
"/root/.local/share/juju/ssh/juju_id_r
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 bootstrap
$ 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 ...
...
18:25:
For SRU purposes, you can verify this changed against juju via the
following:
juju bootstrap --debug lxd (or any provider you wish)
Confirm the following from the output:
1. Bootstrap completes successfully
2. Agent is used from stream
Look for something similar to:
juju.environs.bootstrap boots
** Changed in: juju
Status: Triaged => In Progress
** Changed in: juju
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/1727355
Title:
no matching ag
The package works successfully, however, dh_install is missing a file
required for bash completion. We should ensure this file is also copied
to ensure bash completion continues to work for new installs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
We've been using and testing against this newer version in our CI for
more than a month without seeing any issues. All normal juju operations
work, and I can connect to the juju database as expected. I tested this
on xenial and zesty.
--
You received this bug notification because you are a member
** Tags removed: verification-needed verification-needed-xenial
verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
This syncs juju with the upstream release bringing the latest bugfixes
and enhancements.
[SRU Information]
juju-core has a stable release exception, including for major version updates,
https://wiki.ubuntu.com/JujuUpdates.
[Impact]
A full list of targeted bugs can be seen a
** Changed in: juju-core (Ubuntu)
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/1614969
Title:
Juju packaging allows builds for unsupported architectures
Michael, these failed to build on some arches; so looks like they didn't
move into proposed (we are always running proposed). Nevertheless, I've
installed them now onto our xenial and zesty CI slaves so they will run
through the slew of testing now. We'll monitor for regressions.
--
You received
** Summary changed:
- Remove juju-core from zesty
+ Remove juju-core from artful
** Description changed:
Juju is now releasing as a snap as the primary means of consumption. For
those still needing a debian package the juju ppas will be maintained.
However from a distro perspective, folks
** Changed in: juju-core-1 (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: conjure-up (Ubuntu Xenial)
Status: New => 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
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624914
Title:
juju fails to build on all 32bit architectures
To manage notificat
** Changed in: juju-core-1 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: juju-core (Ubuntu)
Status: In Progress => Fix Released
** Changed in: juju-core-1 (Ubuntu)
Status: Fix Released => Invalid
** Changed in: juju-core (Ubuntu)
Status: Fix Released =>
Public bug reported:
Instaling subiquity package and running it results in this runtime
error.
2017-07-24 15:00:05,407 subiquity:77 Starting SUbiquity v0.0.5
2017-07-24 15:00:05,407 subiquity:78 Arguments passed: ['/usr/bin/subiquity']
2017-07-24 15:00:05,407 subiquitycore.utils:31 Checking envir
Public bug reported:
Juju is now releasing as a snap as the primary means of consumption. For
those still needing a debian package the juju ppas will be maintained.
However from a distro perspective, folks wanting juju should snap
install juju rather than apt install juju. With that in mind, we wo
The packages for X and Y need to retain this behavior. However, the
zesty archive won't have juju-core or juju-1.25.
** Project changed: juju-reports => juju-release-tools
** Changed in: juju-release-tools
Importance: High => Medium
--
You received this bug notification because you are a mem
** Also affects: juju-reports
Importance: Undecided
Status: New
** Changed in: juju-reports
Status: New => Triaged
** Changed in: juju-reports
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This issue should be corrected now as of 2.1-beta5. There is a juju-2
symlink you can depend on that will point to the latest juju-2 binary on
your system.
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Invalid
** Changed in: juju
Status: Triaged => Invalid
** Changed in: j
I can confirm this works on xenial after installing squashfuse.
root@clean-lark:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename: xenial
root@clean-lark:~# uname -a
Linux clean-lark 4.4.0-63-generic #84-U
Yakkety still has 1.0.43.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630789
Title:
normal users can't run snaps inside of LXD containers
To manage notifications about this bug go to:
https://bu
I have verified both xenial and yakkety functionality. In particular,
I've been using this version on xenial for some time without realizing
it hadn't yet been verified (I'm always running -proposed).
I'll note the bash completion functionality is the same as the previous
package, and doesn't cont
** Also affects: juju
Importance: Undecided
Status: New
** Changed in: juju
Milestone: None => 2.1-rc1
** Changed in: juju
Status: New => Triaged
** Changed in: juju
Importance: Undecided => Critical
** Changed in: juju
Assignee: (unassigned) => Menno Smits (menno.s
** Changed in: phablet-tools
Assignee: Nicholas Skaggs (nskaggs) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269163
Title:
phablet-click-test-setup should support launch
** Description changed:
- Juju 1.25.8 is a stable update containing critical bug fixes, for backup
- restore, charm metrics, and mac os sierra for the 1.25 series.
+ Juju 1.25.8 is a stable update containing critical bug fixes including
+ backup restore, charm metrics, openstack security group rem
** Branch linked: lp:~juju-qa/ubuntu/xenial/juju/2.0.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648894
Title:
[SRU] Juju 2.0.2
To manage notifications about this bug go to:
https://bugs.launc
Public bug reported:
This syncs juju with the upstream releases bringing the latest bugfixes.
[SRU Information]
juju-core has a stable release exception, including for major version updates,
https://wiki.ubuntu.com/JujuUpdates.
[Impact]
A full list of targeted bugs can be seen against the miles
** Branch linked: lp:~juju-qa/ubuntu/trusty/juju/juju-1.25.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646913
Title:
[SRU] Juju 1.25.8
To manage notifications about this bug go to:
https://bug
** 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/1646913
Title:
[SRU] Juju 1.25.8
To manage notifications about this bug
Public bug reported:
Juju 1.25.8 is a stable update containing critical bug fixes, for backup
restore, charm metrics, and mac os sierra for the 1.25 series.
[SRU Information]
juju-core has a stable release exception, including for major version
updates, https://wiki.ubuntu.com/JujuUpdates.
[Imp
** Changed in: juju-release-tools
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/1631038
Title:
Need /etc/sysctl.d/10-juju.conf
To manage notifications a
Just adding a comment to note that indeed on 32-bit arches both the
install and upgrade show the DEBCONF message and remove all associated
binaries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/161496
** Tags removed: verification-needed
** Tags added: v-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617440
Title:
[SRU] Juju 2 GA
To manage notifications about this bug go to:
https:/
Works properly for yakkety. juju.conf installed and values set properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631038
Title:
Need /etc/sysctl.d/10-juju.conf
To manage notifications about t
@Nicolas, /usr/lib/sysctl.d/ does override /etc/sysctl.conf. Note, these
settings are already an increase from the default. These are lower
values than in the wiki, but are deemed safe enough to deploy to all
users. You should absolutely bump these values should you wish to run a
more production en
** Tags removed: verification-needed
** Tags added: v-done-xenial v-failed-yakkety
** Tags removed: v-failed-yakkety
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Tags removed: verification-done
** Tags added: v-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/1617440
Title:
[SRU] Juju 2 GA
To manage notifications about this bug go to:
https://bu
Installing xenial build, I am no longer prompted on supported
architectures.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614969
Xenial package installed and working as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617440
Title:
[SRU] Juju 2 GA
** Changed in: juju-core (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: juju-core (Ubuntu)
Status: New => 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/1614969
** Description changed:
The current juju packaging specifies all for architecture, but juju
itself only officially supports 64-bit architectures. We should update
- juju, conjure-up, charm, and charm-tools to specify to build on only
- supported architectures for all ppa and archive versions.
Updating to say this works properly in xenial, but not in yakkety.
Yakkety is missing the sysctl file; it's not installed. This needs to be
corrected in the debian/rules.
** Tags removed: verification-needed
** Tags added: verification-done verification-failed
--
You received this bug notificati
I am now able to bootstrap using LXD 2.0.5.
juju bootstrap lxd lxd
Creating Juju controller "lxd" on lxd/localhost
Looking for packaged Juju agent version 2.0.0 for amd64
To configure your system to better support LXD containers, please see:
https://github.com/lxc/lxd/blob/master/doc/production-s
As per http://autopkgtest.ubuntu.com/packages/j/juju-core, the test was
skipped and the autopkgtest suite succeeded.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Diff shows LXD is added, and we can see from yakkety and zesty the tests
are running on new LXD uploads.
https://launchpadlibrarian.net/290947340/juju-
core_2.0~beta15-0ubuntu2.16.04.1_2.0.0-0ubuntu0.16.04.1.diff.gz
** Tags removed: verification-needed
** Tags added: verification-done
--
You re
** Description changed:
Juju errors with: invalid config: lxd version 2.1, juju needs at least
2.0.0
As seen here:
http://reports.vapour.ws/releases/issue/57b5c506749a567eabd11a4a
Full log not given here because it contains certs. See above link for
full logs.
+
+ [SRU Informat
** Description changed:
Juju's autopkgtests don't execute when a new version of LXD is uploaded.
This means a breaking change uploaded into LXD isn't caught before LXD
lands.
This is because juju 2.0 doesn't depend on LXD directly, but instead
lists it as a recommends. The juju-1 pack
** Description changed:
In order to increase the number of containers that can be used with the
lxd provider we need an /etc/sysctl.d/10-juju.conf file setting:
- fs.inotify.max_user_watches = 524288
- fs.inotify.max_user_instances = 256
+ fs.inotify.max_user_watches = 524288
+
** Description changed:
Since --upload-tools is now no longer needed, juju needs to fallback to
using bundled jujud in the case where no matching agents are found in
streams. For example,
6:38:07 INFO juju.environs.manual init.go:120 series: zakkety,
characteristics: arch=amd64 cpu-co
** Changed in: juju-core (Ubuntu Yakkety)
Status: In Progress => Fix Released
** Changed in: juju-core (Ubuntu Yakkety)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu Xenial)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: juju-core (Ubuntu Xenial)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
--
You received
** Changed in: juju-core (Ubuntu Zesty)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu Yakkety)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu Xenial)
Assignee: (unassigned) => Nicholas Skaggs
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New => In Progress
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
--
You received this bug notification because you
** Summary changed:
- [SRU] Juju 2-rc3 for Xenial
+ [SRU] Juju 2 GA
** Description changed:
- Juju 2.0 is not quite final, as per the risks and timeline outlined in
- the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
- post-xenial release. This updates juju to an upgradeable R
** Description changed:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
- post-xenial release. This updates juju to the lastest 2.0 milestone
- version.
+ post-xenial release. This updates juju to an up
** Summary changed:
- [SRU] Juju 2 beta 17 for Xenial
+ [SRU] Juju 2-rc3 for Xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617440
Title:
[SRU] Juju 2-rc3 for Xenial
To manage notifications
1.0.41 was backported which has the fix. This should be released.
** Changed in: snap-confine (Ubuntu Xenial)
Status: In Progress => 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/1
** Changed in: juju-release-tools
Status: In Progress => Fix Released
** Changed in: juju-core (Ubuntu)
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
Public bug reported:
The current ubuntu (xenial / yakkety) packages are missing needed
updates. Specifically, juju needs golang.org/x/crypto/acme/autocert.
I can note that sid contains these updated packages, but yakkety is
still missing them. See https://packages.debian.org/sid/all/golang-
golan
** Description changed:
The juju team is requesting an FFE for juju. Juju-2 represents API
changes and new features and bugfixes for juju. This FFE is intended to
cover the acceptance of the updated juju package.
Timeline
- We have released 16 betas of juju-2 so far over the
Given juju2 is now RC and has promises of being upgradeable, I think
this is safe to move forward on. For folks who have to have it, it will
be in the stable juju ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Changed in: juju-core (Ubuntu)
Status: Triaged => 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/1578550
Title:
ftbfs on yakkety
To manage notifications about this bug go to:
@mwhudson, I utilized the tool locally and everything seemed fine. For
now, bug 1564500 prevents a full CI run until it lands in xenial proper.
I think we should discuss a set of autopkgtests to help bridge the gap
in the interim.
That said, given 3.2.9 is in yakkety we've not seen any issues in t
Looks good.
/usr/lib/juju/mongo3.2/bin/mongo
MongoDB shell version: 3.2.9
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605976
** Changed in: juju-core (Ubuntu)
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/1484132
Title:
[FFe] juju-core 1.25
To manage notifications about this bug go to:
https
** No longer affects: charm-tools (Ubuntu)
** No longer affects: charm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614969
Title:
Juju packaging allows builds for unsupported architectur
Martin, the edge channel in the snap store has replaced the daily ppa.
This ppa is where we release betas:
https://launchpad.net/~juju/+archive/ubuntu/devel
Now as to landing this fix, we've pushed packages to proposed as you've
seen, but encountered various failures with beta16 and now beta17. T
** Summary changed:
- [SRU] Juju 2 beta 16 for Xenial
+ [SRU] Juju 2 beta 17 for Xenial
** Description changed:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates juju
Public bug reported:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates juju to the lastest 2.0 milestone
version.
[SRU Information]
juju-core has a stable release exception
** Changed in: juju-release-tools
Status: Triaged => In Progress
** Changed in: juju-core (Ubuntu)
Status: New => In Progress
** Changed in: juju-release-tools
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu)
Assignee: (u
Public bug reported:
The juju team is requesting an FFE for juju. Juju-2 represents API
changes and new features and bugfixes for juju. This FFE is intended to
cover the acceptance of the updated juju package.
Timeline
We have released 16 betas of juju-2 so far over the xenial and now ya
@mwhudson, once mongo3.2.8 is in the proposed queue for xenial, we can
ensure a CI test run or two before landing. Let us know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605976
Title:
[2.0] bum
1 - 100 of 736 matches
Mail list logo
