I am the original bug reporter for 560804 -- a workaround I found while
being affected by the bug is below -- perhaps it will be useful to you
as well:
Mouse pointer can be made to "reappear" by switching to a TTY session
and then back. For example, pressing Ctrl+Alt+F1, then Ctrl+Alt+F7 to
switch
** 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
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
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
** 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
** 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
** 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
** 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
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
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
**
** 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
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-
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
** 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
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
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
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-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
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
@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
** 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:
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
** 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/
** 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
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
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
** 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.
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
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
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
** 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
Ohh are you connect via ptp or ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210891
Title:
Doesn't recognize music files in portable device
To manage notifications about this bug go to:
https://
John, are the id3 tags set correctly on the device? Will any of the
music play?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210891
Title:
Doesn't recognize music files in portable device
To mana
I've created a vUDS session here, and I would encourage conversations
surrounding reporting bugs in ubuntu to it:
https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-
reporting-bugs
I began looking at editing the wiki page before realizing this is a
bigger discussion point than e
** Changed in: unity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308317
Title:
applications in full-screen do not align properly after minimization
To ma
For reference music app sees the same error.
usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene: unrecognized option '--file='
/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene: invalid option -- 'I'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Any update on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124071
Title:
[tabs] Cannot add Tabs programmatically
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
With the new header, what is the status on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124071
Title:
[tabs] Cannot add Tabs programmatically
To manage notifications about this bug go to:
h
** Changed in: phablet-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321463
Title:
Cannot run individual AP tests using phablet-test-run
To manage no
Specifically, this import fails when using a qualified name:
# First let's try python3, without python2 path
defaultpy="/usr/bin/python3"
import_error=$(adb shell "cd /home/phablet/autopilot; $defaultpy -c 'import
$TESTSUITE'")
if [ -n "$import_error" ]; then
echo 'running
** Branch linked: lp:~nskaggs/ubuntu-calendar-app/fix-ap-flo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321775
Title:
High CPU usage observed across EDS and indicator-datetime causing
clock ap
** 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
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
** 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
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
** Also affects: trusty-backports
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/1583740
Title:
mongo client is missing
To manage notifications about this
Public bug reported:
Juju 1.25.6 is a stable update containing critical bug fixes, including
MAAS compatibility, for the 1.25 series.
[SRU Information]
juju-core has a stable release exception, including for major version
updates, https://wiki.ubuntu.com/JujuUpdates.
[Impact]
This update brings
** Branch linked: lp:~juju-qa/ubuntu/yakkety/juju/juju-1.25.6
** Branch linked: lp:~juju-qa/ubuntu/trusty/juju/juju-1.25.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611855
Title:
[SRU] Juju 1.
** Summary changed:
- [SRU] Juju 1.25.6
+ [SRU] Juju 1.25.6 for trusty
** Branch unlinked: lp:~juju-qa/ubuntu/yakkety/juju/juju-1.25.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611855
Title:
*** This bug is a duplicate of bug 1611855 ***
https://bugs.launchpad.net/bugs/1611855
Public bug reported:
Juju 1.25.6 is a stable update containing critical bug fixes, including
MAAS compatibility, for the 1.25 series.
[SRU Information]
juju-core has a stable release exception, including
** Branch linked: lp:~juju-qa/ubuntu/yakkety/juju/juju-1.25.6
** Description changed:
Juju 1.25.6 is a stable update containing critical bug fixes, including
MAAS compatibility, for the 1.25 series.
[SRU Information]
juju-core has a stable release exception, including for major vers
Public bug reported:
The current package in ubuntu is old and the maintainer is no longer
able to maintain the package. I'd like to request we replace this
package with the debian version which is newer and has a maintainer.
** Affects: golang-juju-loggo (Ubuntu)
Importance: Undecided
I've restored the debhelper script to version 7 as released. The
juju-1-default.links file was present in my version, heh, but not added
and thus not in the repository. This too has been corrected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
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
@mwhudson, a new version of juju-core-1, 1.25.6, is being uploaded into
yakkety. I agree with the package removal, but given the extended
timeline for juju 2.0, it's possible yakkety retains juju-core-1. Let's
revisit this before FF. I definitely agree with not including it in Z.
--
You received
** Changed in: juju-core-1 (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: juju-core (Ubuntu)
Status: Invalid => 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/1
** Description changed:
The current package in ubuntu is old and the maintainer is no longer
able to maintain the package. I'd like to request we replace this
package with the debian version which is newer and has a maintainer.
+
+ NOTE: juju-core in xenial would like to depend on this pack
Tested on xenial. Deploys, tearsdown, installs and removes cleanly, and
works with juju-1-default as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611855
Title:
[SRU] Juju 1.25.6
To mana
** 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/1611855
Title:
[SRU] Juju 1.25.6
To manage notifications about this bug go to:
ht
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
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 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
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
** 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
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
** 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
** 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
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-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:/
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
** 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
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
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
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
** 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
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
** 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 =>
** 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 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
** 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
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
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
$ 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:
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
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
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
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
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
Marking invalid due to presence of beta12 which will go into yakkety /
xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596920
Title:
Juju 2.0-beta10 in ubuntu
To manage notifications about t
Marking invalid due to presence of beta12 which will go into yakkety /
xenial.
** Changed in: juju-core (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596920
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-core (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508122
Title:
please transition to shared libraries
To manage notifications about th
It sounds like the "fix" for this lies outside of LXD. Can we add the
affected packages and involve the right upstreams for this? Are we going
to pursue this purely upstream with systemd / kernel or are we going to
attempt a distro-patch of some sort?
--
You received this bug notification because
It should be noted we were forced to disable one test as it fails on
some architectures due to https://bugs.launchpad.net/juju-
core/+bug/1605313. As we've released the final tarball for beta12, we'd
like to land this SRU and continue working on squashing that bug
completely in the future.
--
You
** Description changed:
- Admins and developers are unable to access to the juju mongodb instance
- to investigation issues.
+ [Impact]
+ Admins and developers are unable to access to the juju mongodb instance to
investigation issues.
The mongo client is built, but not included in the juju-
Binary is present
$ ls /usr/lib/juju/mongo3.2/bin
mongo mongod mongoperf mongos mongosniff
I could invoke the binary
$ /usr/lib/juju/mongo3.2/bin/mongo
MongoDB shell version: 3.2.4
apt-cache show juju-mongodb3.2
Package: juju-mongodb3.2
Priority: optional
Section: universe/database
Installed
** Changed in: juju-core (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604137
Title:
[SRU] Juju 2.0 beta12 for Xenial
To manage notifications ab
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
1 - 100 of 736 matches
Mail list logo
