[Bug 1884940] Re: after login to gnome, kern.log slowly fills with snd_hda_intel 0000:00:1f.3: No response from codec

[Martin Packman]

@chihchun see bug 1879389 for the apport dump.

Because the kernel logs fill up with
WARN_ON(intel_wait_for_register(...))/hsw_wait_for_power_well_enable
it's hard to find specific other issues.

I have observed the sound driver being crashy/sad on the same hardware
but it's possibly improved with subsequent updates? Hard to tell with
intermittent issues.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884940

Title:
  after login to gnome, kern.log slowly fills with snd_hda_intel
  :00:1f.3: No response from codec

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1884940/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

[Martin Packman]

Well, similar experience for me today, booted and logged in okay, but
then the desktop session died leaving monitor backlight and keyboard
lights on, but no other sign of life. Shutting lid to suspend then
resume didn't help, had to hard power off. Then on next boot, it hung
after login, but recovered and was fine thereafter. More oddness, but
not the gpu in the blame this time.


Log sequence extracts:


May 26 09:28:03 xps2020 systemd[1]: Startup finished in 5.461s (firmware) + 
3.431s (loader) + 14.216s (kernel) + 20.511s (userspace) = 43.620s.

...

May 26 09:29:14 xps2020 update-notifier.desktop[4555]: 
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:30: PyGIWarning: Gtk was 
imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
May 26 09:29:14 xps2020 update-notifier.desktop[4555]:   from gi.repository 
import Gtk
May 26 09:29:14 xps2020 update-notifier.desktop[4555]: WARNING:root:timeout 
reached, exiting
May 26 09:29:14 xps2020 gnome-session[1422]: gnome-session-binary[1422]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
May 26 09:29:14 xps2020 gnome-session-binary[1422]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
May 26 09:29:14 xps2020 gnome-session-binary[1422]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
May 26 09:29:14 xps2020 gnome-session[1422]: gnome-session-binary[1422]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
May 26 09:29:14 xps2020 gnome-session-binary[1422]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

...

May 26 09:29:15 xps2020 systemd[1]: Stopped User Manager for UID 121.
May 26 09:29:15 xps2020 systemd[1]: Removed slice User Slice of gdm.
May 26 09:29:54 xps2020 PackageKit[1605]: get-updates transaction /309_bcbe 
from uid 1001 finished with success after 398ms
May 26 09:29:57 xps2020 org.gnome.Shell.desktop[3032]: ###!!! 
[Parent][RunMessage] Error: Channel closing: too late to send/recv, messages 
will be lost
May 26 09:29:57 xps2020 org.gnome.Shell.desktop[3032]: ###!!! 
[Parent][RunMessage] Error: Channel closing: too late to send/recv, messages 
will be lost
May 26 09:30:09 xps2020 systemd-logind[1187]: Lid closed.
May 26 09:30:09 xps2020 systemd-logind[1187]: Suspending...


...

May 26 09:30:13 xps2020 systemd-logind[1187]: Lid opened.
May 26 09:30:23 xps2020 systemd-logind[1187]: Power key pressed.
May 26 09:30:31 xps2020 systemd-logind[1187]: Power key pressed.
May 26 09:30:39 xps2020 systemd-logind[1187]: Delay lock is active (UID 
1001/martin, PID 3032/gnome-shell) but inhibitor timeout is reached.
May 26 09:30:39 xps2020 systemd[1]: Starting TLP suspend/resume...
May 26 09:30:39 xps2020 systemd[1]: Started TLP suspend/resume.
May 26 09:30:39 xps2020 systemd[1]: Reached target Sleep.
May 26 09:30:39 xps2020 systemd[1]: Starting Suspend...
May 26 09:30:39 xps2020 systemd-sleep[4909]: Suspending system...
May 26 09:30:39 xps2020 kernel: PM: suspend entry (s2idle)
May 26 09:30:41 xps2020 kernel: PM: Syncing filesystems ... done.
May 26 09:30:41 xps2020 kernel: Freezing user space processes ... (elapsed 
0.002 seconds) done.
May 26 09:30:41 xps2020 kernel: OOM killer disabled.
May 26 09:30:41 xps2020 kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
May 26 09:30:41 xps2020 kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
May 26 09:30:41 xps2020 kernel: psmouse serio1: Failed to disable mouse on 
isa0060/serio1
May 26 09:30:41 xps2020 kernel: PM: Some devices failed to suspend, or early 
wake event detected
May 26 09:30:41 xps2020 kernel: OOM killer enabled.
May 26 09:30:41 xps2020 kernel: Restarting tasks ... done.
May 26 09:30:41 xps2020 kernel: thermal thermal_zone6: failed to read out 
thermal zone (-61)
-- Reboot --

...

May 26 09:32:03 xps2020 systemd[1]: Startup finished in 5.443s
(firmware) + 3.530s (loader) + 11.642s (kernel) + 33.978s (userspace) =
54.594s.

...

May 26 09:33:37 xps2020 kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20170500
May 26 09:33:38 xps2020 kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370500
May 26 09:33:39 xps2020 kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20470500
May 26 09:33:40 xps2020 gnome-session[2043]: gnome-session-binary[2043]: 
WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout
May 26 09:33:40 xps2020 gnome-session-binary[2043]: WARNING: Application 
'org.gnome.Shell.desktop' failed to register before timeout
May 26 09:33:40 xps2020 gnome-session-binary[2043]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
May 26 09:33:40 xps2020 gnome-session[2043]: gnome-session-binary[2043]: 
CRITICAL: We failed, but the fail whale is 

[Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

[Martin Packman]

Okay, pretty sure have found the right upstream bug, and have what looks
like a good workaround.

$ gsettings set org.gnome.settings-daemon.plugins.xsettings antialiasing
'grayscale'

https://gitlab.freedesktop.org/mesa/mesa/issues/2183

The steps to reproduce does kill the session with a gpu hang on the text
drawing benchmark, after changing the antialiasing font mode and logging
in again, it completes. Will run for the next few days and see if daily
crashes continue or not.

** Summary changed:

- [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << 
((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]
+ Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #2183
   https://gitlab.freedesktop.org/mesa/mesa/issues/2183

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878670

Title:
  Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8
  GT2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]

[Martin Packman]

Captured one, context from journalctl:

May 21 14:13:51 xps2020 kernel: [drm] GPU HANG: ecode 11:0:0x85db, in Xorg 
[1985], reason: hang on rcs0, action: reset
May 21 14:13:51 xps2020 kernel: i915 :00:02.0: Resetting rcs0 for hang on 
rcs0
May 21 14:13:54 xps2020 kernel: Asynchronous wait on fence 
i915:gnome-shell[2119]/1:27478 timed out 
(hint:intel_atomic_commit_ready+0x0/0x54 [i915])
May 21 14:13:59 xps2020 kernel: i915 :00:02.0: Resetting rcs0 for hang on 
rcs0
May 21 14:13:59 xps2020 /usr/lib/gdm3/gdm-x-session[1983]: (II) modeset(0): 
EDID vendor "SHP", prod id 5324
May 21 14:13:59 xps2020 /usr/lib/gdm3/gdm-x-session[1983]: (II) modeset(0): 
Printing DDC gathered Modelines:
May 21 14:13:59 xps2020 /usr/lib/gdm3/gdm-x-session[1983]: (II) modeset(0): 
Modeline "3840x2400"x0.0  592.50  3840 3888 3920 4000  2400 2403 2409 2469 
-hsync -vsync (148.1 kHz eP)
May 21 14:13:59 xps2020 /usr/lib/gdm3/gdm-x-session[1983]: (II) modeset(0): 
Modeline "3840x2400"x0.0  474.00  3840 3888 3920 4000  2400 2403 2409 2469 
-hsync -vsync (118.5 kHz e)


And head of /sys/class/drm/card0/error:

GPU HANG: ecode 11:0:0x85db, in Xorg [1985], reason: hang on rcs0, action: 
reset
Kernel: 5.0.0-1052-oem-osp1
Time: 1590066831 s 42118 us
Boottime: 17262 s 908428 us
Uptime: 17259 s 317934 us
Epoch: 4299206488 jiffies (250 HZ)
Capture: 4299207993 jiffies; 121328 ms ago, 6020 ms after epoch
Active process (on ring rcs0): Xorg [1985], score 0
Reset count: 0
Suspend count: 0
Platform: ICELAKE

( the rest is attached, dump of a bunch of things from the graphics card
buffers)

** Attachment added: "/sys/class/drm/card0/error"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670/+attachment/5375189/+files/gfx_error.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878670

Title:
  [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver,
  (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from
  i915/intel_runtime_pm.c:308]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]

[Martin Packman]

>From similar-but-maybe-not-the-same drm issues, seems capturing the GPU
crash dump (if there is one) would be useful

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/2
https://gitlab.freedesktop.org/drm/intel/issues/673

I have a dmesg full of "WARNING ... [i915]" but no gpu failures since
last restart yet.

** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #673
   https://gitlab.freedesktop.org/drm/intel/issues/673

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878670

Title:
  [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver,
  (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from
  i915/intel_runtime_pm.c:308]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]

[Martin Packman]

Both posted journalctl logs feature sections like this:

May 21 11:03:29 asgard kernel: [drm] GPU HANG: ecode 11:0:0x85db, in Xorg 
[2421], reason: hang on rcs0, action: reset
May 21 11:03:29 asgard kernel: i915 :00:02.0: Resetting rcs0 for hang on 
rcs0
May 21 11:03:37 asgard kernel: i915 :00:02.0: Resetting rcs0 for hang on 
rcs0
May 21 11:03:45 asgard kernel: i915 :00:02.0: Resetting rcs0 for hang on 
rcs0
May 21 11:03:53 asgard kernel: i915 :00:02.0: Resetting rcs0 for hang on 
rcs0
May 21 11:04:01 asgard kernel: i915 :00:02.0: Resetting rcs0 for hang on 
rcs0
May 21 11:04:01 asgard /usr/lib/gdm3/gdm-x-session[2419]: i965: Failed to 
submit batchbuffer: Input/output error
May 21 11:04:01 asgard gnome-calendar[3680]: gnome-calendar: Fatal IO error 11 
(Resource temporarily unavailable) on X server :0.
May 21 11:04:01 asgard seahorse[3679]: seahorse: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.

The GPU stopped responding, so the session falls over. Which makes
sense.

SO, this does look very much like bug 1872001 - did a bad graphics
driver update get backported to the 5.0.0 OEM kernel?

@lihow731 Do you need anything else to progress 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/1878670

Title:
  [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver,
  (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from
  i915/intel_runtime_pm.c:308]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]

[Martin Packman]

I am experiencing similar issues with a brand new Dell Inc. XPS 13
9300/077Y9N.

Perhaps this bug should be renamed for the symptoms and user impact, as
there are bunch of linked bugs for specific crashes related to packages?


@vanvugt If it's helpful, I have also uploaded (with some struggle apport is 
failing) the following oopses which are likely related to the symptoms 
experienced:

linux-image-5.0.0-1050-oem-osp1 https://errors.ubuntu.com/oops/bf9d4f57
-9b4f-11ea-aa30-fa163ee63de6 https://errors.ubuntu.com/oops/b9fc3920
-9b4f-11ea-aa30-fa163ee63de6

xwayland https://errors.ubuntu.com/oops/a1951eb0-9b4f-11ea-a4d2-fa163e6cac46
gnome-shell https://errors.ubuntu.com/oops/e502d63d-9b4b-11ea-9b64-fa163e102db1


@gilbert-fernandes As a workaround, or at least to see if it helps, I've 
disabled wayland, which is pretty pointless on 18.04 anyway, you may want to 
try as well:
https://askubuntu.com/a/975098

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878670

Title:
  [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver,
  (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from
  i915/intel_runtime_pm.c:308]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1604988] Re: Inconsistent licence in github.com/juju/utils/series

[Martin Packman]

The file headers for this package should be changed to say LGPL, which I
believe is the choice we made for all library-type projects from juju.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604988

Title:
  Inconsistent licence in github.com/juju/utils/series

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1604988/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1613864] Re: Missing "juju-2"/"juju2" command.

[Martin Packman]

Ideally we don't have that many aliases for the same thing (and some of
those /usr/bin files are not from our latest packaging)?

I think what you really want is to just run `/usr/bin/juju` but realise
having juju-1-default makes that more complicated as well. So, I see
some benefit in a any-2-series juju alias, but think we'll get pushback
on usability of having too many similarly named commands installed by
default.

See thread from when this was originally being discussed for some more
info:



** Changed in: juju-core
   Importance: Undecided => High

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
Milestone: None => 2.1.0

** 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/1613864

Title:
  Missing "juju-2"/"juju2" command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1613864/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570650] Re: Use juju-mongodb2.6 for 1.25 on xenial

[Martin Packman]

Per the upstream support policy:



2.4 has been end of life since March, so I'm not sure we can won't-fix
this without a serious discussion about what our plans for supporting
Juju 1.25 over the coming years are. That said, 2.6 will soon be in the
same situation, so we may be in a bind regardless.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570650

Title:
  Use juju-mongodb2.6 for 1.25 on xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570650/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1564662] Re: Juju binaries should be stripped

[Martin Packman]

** Changed in: juju-core
   Status: Triaged => Fix Released

** Changed in: juju-core
Milestone: 2.1.0 => 2.0.0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564662

Title:
  Juju binaries should be stripped

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1564662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1604988] [NEW] Inconsistent licence in github.com/juju/utils/series

[Martin Packman]

Public bug reported:

The per-file copyright headers in the series/ package of the juju/utils
project all state:

// Licensed under the AGPLv3, see LICENCE file for details.

However the top level LICENCE file is LGPLv3 with exception. This
confuses the issue for distribution.

** Affects: juju-core
 Importance: High
 Status: Triaged

** Affects: juju-core/1.25
 Importance: High
 Status: Triaged

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: jujuqa packaging

** Also affects: juju-core
   Importance: Undecided
   Status: New

** Changed in: juju-core
   Importance: Undecided => High

** Changed in: juju-core
   Status: New => Triaged

** Also affects: juju-core/1.25
   Importance: Undecided
   Status: New

** Changed in: juju-core/1.25
   Importance: Undecided => High

** Changed in: juju-core/1.25
   Status: New => Triaged

** Changed in: juju-core/1.25
Milestone: None => 1.25.7

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604988

Title:
  Inconsistent licence in github.com/juju/utils/series

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1604988/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600257] Re: Broken bash completion with old ppa packages present

[Martin Packman]

Thinking about it, CI debs of that vintage should do, eg:



Can try installing on of those in a fresh vm then installing new
packaging over the top.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600257

Title:
  Broken bash completion with old ppa packages present

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1600257/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600257] Re: Broken bash completion with old ppa packages present

[Martin Packman]

Old versions of the ppa packaging, eg:




-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600257

Title:
  Broken bash completion with old ppa packages present

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1600257/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600257] Re: Broken bash completion with old ppa packages present

[Martin Packman]

Hm, does it count as a purge-removed only conf file even if was placed
there by dh_install as part of override_dh_auto_install in rules? If
that's the case, what do you recommend we do to clean up?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600257

Title:
  Broken bash completion with old ppa packages present

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1600257/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600257] Re: The tab completion on juju yields KeyError: 'services'

[Martin Packman]

I think all we really want to do is make sure we conflict correctly with
the old ppa package names, then dpkg will handle the removal of the old
completion files before starting the install of the new juju-2.0
package.

** Summary changed:

- The tab completion on juju yields KeyError: 'services'
+ Broken bash completion with old ppa packages present

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600257

Title:
  Broken bash completion with old ppa packages present

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1600257/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600257] Re: Broken bash completion with old ppa packages present

[Martin Packman]

See irc log for more context:



In particular, the completion files come from multiple old ppa packages:



juju2: /etc/bash_completion.d/juju2
juju-core2: /etc/bash_completion.d/juju-core2
juju-2.0: /usr/share/bash-completion/completions/juju-2.0
juju-2.0: /usr/share/bash-completion/completions/juju-version

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600257

Title:
  Broken bash completion with old ppa packages present

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1600257/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600311] Re: Juju 2.0 Bootstrap Fails on Ubuntu Trusty Power machine.

[Martin Packman]

The interesting problems here all seem to be at the lxd level, from the
second log in comment #2:

lxc 20160714064249.306 INFO lxc_apparmor - 
lsm/apparmor.c:apparmor_process_label_set:238 - changed apparmor profile to 
lxd-juju-47a009-0_
lxc 20160714064249.306 ERRORlxc_seccomp - seccomp.c:lxc_seccomp_load:615 - 
Error loading the seccomp policy
lxc 20160714024249.306 ERRORlxc_sync - sync.c:__sync_wait:57 - An error 
occurred in another process (expected sequence number 5)
lxc 20160714024249.306 ERRORlxc_start - start.c:__lxc_start:1353 - failed 
to spawn 'juju-47a009-0'
lxc 20160714024249.306 INFO lxc_conf - conf.c:run_script_argv:367 - 
Executing script '/usr/share/lxcfs/lxc.reboot.hook' for container 
'juju-47a009-0', config section 'lxc'
lxc 20160714024249.812 INFO lxc_conf - conf.c:run_script_argv:367 - 
Executing script '/usr/bin/lxd callhook /var/lib/lxd 3 stop' for container 
'juju-47a009-0', config section 'lxc'
lxc 20160714024249.963 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:172 
- command get_cgroup failed to receive response
lxc 20160714024249.964 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:172 
- command get_cgroup failed to receive response

** Also affects: lxd (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/1600311

Title:
  Juju 2.0 Bootstrap Fails on Ubuntu Trusty Power machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1600311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600257] Re: The tab completion on juju yields KeyError: 'services'

[Martin Packman]

Part of the issue here is having a mix of ppa packages and archive
packages leads to a bunch of bash completion files on disk that may not
correspond to the correct version of juju. We should make our
conflicts/replaces robust on the ppa and archive packages so users can't
have old ppa versions lying around confusing things.

** Tags added: bash-completion packaging

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600257

Title:
  The tab completion on juju yields KeyError: 'services'

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1600257/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600257] Re: The tab completion on juju yeilds KeyError: 'services'

[Martin Packman]

** 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/1600257

Title:
  The tab completion on juju yields KeyError: 'services'

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1600257/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1596920] [NEW] Juju 2.0-beta10 in ubuntu

[Martin Packman]

Public bug reported:

New upstream release 2.0-beta10 should be packaged in yakkety.

The 2.0 version of juju is still not quite final, see FFE bug 1545913
for Xenial for background. The agreement was we would include upstream
releases as they came in the development version of juju, and SRU back
to xenial as appropriate.

For more information, see:



** 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/1596920

Title:
  Juju 2.0-beta10 in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1596920/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570657] Re: Bash completion needed for versioned juju commands

[Martin Packman]

** Tags added: bash-completion

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570657

Title:
  Bash completion needed for versioned juju commands

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1588403] Re: Tab completion missing in Juju 2.0 betas

[Martin Packman]

** Tags added: bash-completion packaging

** Changed in: juju-core
   Importance: Undecided => High

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
Milestone: None => 2.0.0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588403

Title:
  Tab completion missing in Juju 2.0 betas

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1588403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1588403] Re: Tab completion missing in Juju 2.0 betas

[Martin Packman]

Basic problem seems to be the naming of the file under /usr/share/bash-
completion/completions/ - currently the juju 2.0 packages have it as
'juju2' which bash won't invoke for the `juju` name. However, the script
is not (yet) relevantly different from the juju 1.25 bash completion, so
older versions still existing will make it work 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/1588403

Title:
  Tab completion missing in Juju 2.0 betas

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1588403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1588403] Re: Tab completion missing in Juju 2.0 betas

[Martin Packman]

** 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/1588403

Title:
  Tab completion missing in Juju 2.0 betas

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1588403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538764] Re: needs dependency on python-novaclient

[Martin Packman]

Versions of juju < 1.0 are long out of support, and juju in ubuntu does
not require novaclient to work with openstack.

** Changed in: juju
   Status: New => Won't Fix

** Changed in: juju (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/1538764

Title:
  needs dependency on python-novaclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1538764/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576318] Re: juju register not clear that you're creating a new password

[Martin Packman]

** Also affects: juju-core
   Importance: Undecided
   Status: New

** Tags added: usability

** Changed in: juju-core
   Importance: Undecided => Medium

** Changed in: juju-core
   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/1576318

Title:
  juju register not clear that you're creating a new password

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1576318/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570657] Re: Bash completion needed for versioned juju commands

[Martin Packman]

** Tags added: landscape

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570657

Title:
  Bash completion needed for versioned juju commands

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576778] Re: juju2 tab-completion for sub commands is broken in beta6

[Martin Packman]

*** This bug is a duplicate of bug 1570657 ***
https://bugs.launchpad.net/bugs/1570657

Thanks, see the existing bug (on juju-core in ubuntu, confusing), for
this.

** This bug has been marked a duplicate of bug 1570657
   Bash completion needed for versioned juju commands

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576778

Title:
  juju2 tab-completion for sub commands is broken in beta6

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1576778/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576241] Re: juju returns command not found with no helpers

[Martin Packman]

Looks like the command-not-found-data package was last updated before
the new juju package got out of proposed:



 command-not-found (0.3ubuntu16.04) xenial; urgency=medium

   * update data to latest xenial

  -- Michael Vogt   Thu, 14 Apr 2016 09:15:31
+0200

** Also affects: command-not-found (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/1576241

Title:
  juju returns command not found with no helpers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1576241/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1574076] Re: juju package should suggest juju-1.25 not juju-core

[Martin Packman]

The Suggests is dual purpose for Xenial. Both does the normal job of
informing the user of the new juju 1.X specific package, but is also a
tricky upgrade hack. The release team noted that the upgrade process now
autoremoves packages in its default behaviour, so going to Xenial and
2.0 juju would take away everyone's working client. The Suggests on the
old package name avoids that. A Suggests on the new package name would
not, and 2.0 juju doesn't really want to Depends or Recommends on 1.X
juju.

For Y, the old aliases and other transitional elements related to
package upgrades from 1.X should be removed.

** Changed in: juju-core
   Importance: Undecided => High

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
Milestone: None => 2.1.0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574076

Title:
  juju package should suggest juju-1.25 not juju-core

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1574076/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571072] Re: autopkgtest future-manual-provider fails on armhf for 2.0

[Martin Packman]

For this case, skipping this particular test on 32 bit arches is the
right thing.

** 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/1571072

Title:
  autopkgtest future-manual-provider fails on armhf for 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1571072/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570654] Re: Manpage still refers to 1.X config for 2.0

[Martin Packman]

** 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/1570654

Title:
  Manpage still refers to 1.X config for 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570654/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570759] Re: apt-get install juju does not install /usr/bin/juju

[Martin Packman]

Please run apt-get update and apt-get upgrade, this issue should now be
resolved.

We have a few pending changes to make the first upgrade experience
clearer, for now note that you can run 1.25 with the 'juju-1' name, and
'juju' will be 2.0.

** Changed in: juju-core
   Status: Triaged => Fix Released

** Changed in: juju-core (Ubuntu)
   Status: Confirmed => 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/1570759

Title:
  apt-get install juju does not install /usr/bin/juju

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1570759/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570654] Re: Manpage still refers to 1.X config for 2.0

[Martin Packman]

Fix proposed: 

** Changed in: juju-core
   Status: Triaged => 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/1570654

Title:
  Manpage still refers to 1.X config for 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570654/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

[Martin Packman]

I have some changes from Friday to address these test failures and the
armhf one, that I've now committed and put in the packaging branch:




As the lxd changes are mostly about making the test cleaner and adding
some extra debug information, and not actually addressing the failure
seen, I was hesitant to push for a new upload just to get more results.

However, they may well be useful for showing how your test failed, as
it's distinctly unclear why from the pasted log.

I agree that migrating from proposed without understanding this better
is needless risk, even with the slightly confused state of the archive
given the adoption of the new 1.25 packaging.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571082

Title:
  autopkgtest lxd provider tests fail for 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1571082/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

The juju-core-1 autopkgtests are all green:



We have bug 1570759 reported for the slightly weird state of the xenial
archive with 1.25.5 in main but 2.0-beta4 stuck in proposed.

I filed a bunch of bugs.

The autopkgtest problems for 2.0: bug 1571082, bug 1571072
The mongodb dependency for 1.25:  bug 1570650
Usability stuff with manpages and bash completion: bug 1570654, bug 1570651, 
bug 1570660, bug 1570657

There's also some potential for confusion for people who've installed
juju betas from our development ppa this cycle, that some additional
Breaks/Replaces may help with.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571082] [NEW] autopkgtest lxd provider tests fail for 2.0

[Martin Packman]

Public bug reported:

The new autopkgtests for the lxd provider are still not passing yet. The
bridge setup looks like it works, but when juju comes to try and connect
to lxd it is rejected on an http url.





+ juju bootstrap my-controller lxd --upload-tools --debug --config 
default-series=xenial
2016-04-15 07:59:35 INFO juju.cmd supercommand.go:60 running juju [2.0-beta4 gc 
go1.6.1]
2016-04-15 07:59:35 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a 
provider name
2016-04-15 07:59:35 INFO cmd cmd.go:141 no credentials found, checking 
environment
2016-04-15 07:59:35 DEBUG juju.cmd.juju.commands bootstrap.go:365 preparing 
controller with config: 
map[controller-uuid:644108a3-a3fc-4769-8e4f-c236232d4764 default-series:xenial 
type:lxd name:admin uuid:644108a3-a3fc-4769-8e4f-c236232d4764]
2016-04-15 07:59:39 DEBUG juju.tools.lxdclient client.go:73 connecting to LXD 
remote "local": ""
2016-04-15 07:59:46 DEBUG juju.tools.lxdclient client.go:73 connecting to LXD 
remote "juju-remote": "10.0.8.1"
2016-04-15 07:59:47 ERROR cmd supercommand.go:448 Get 
https://10.0.8.1:8443/1.0/profiles: Forbidden
adt-run [07:59:48]: test current-lxd-provider: ---]
adt-run [07:59:48]: test current-lxd-provider:  - - - - - - - - - - results - - 
- - - - - - - -
current-lxd-provider FAIL non-zero exit status 1


This is particularly confusing, as the exact same test passes if run on a 
canonistack machine using the ssh runner:




Test scripts are in the debian/tests directory of this packaging branch:




>From discussion on irc earlier, the only way Tycho thought we could hit the 
>Forbidden here:

[16:18]  mgz: so juju configures LXD to listen over HTTPS
[16:18]  and if it accesses LXD via https, it needs to also configure 
LXD to recognize juju's cert
[16:18]  it strikes me that that cert configuration has failed
[16:19]  and that's why you get a 403
[16:19]  i'm not sure why you'd get it for any other reason

** Affects: juju-core
 Importance: Critical
 Status: Triaged

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: lxd-provider packaging

** Also affects: juju-core
   Importance: Undecided
   Status: New

** Changed in: juju-core
   Importance: Undecided => Critical

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
Milestone: None => 2.0-rc1

** Tags added: lxd-provider packaging

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571082

Title:
  autopkgtest lxd provider tests fail for 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1571082/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571072] [NEW] autopkgtest future-manual-provider fails on armhf for 2.0

[Martin Packman]

Public bug reported:

The current-manual-provider test passes everywhere, which relies on
setting up a state server in place in the same test vm. However, on
armhf only the future-manual-provider variant, which first munges the
machine series to emulate the next development release, fails.





357bb2f3e2cfa9d7c28aff2ac22beb403ddb5bf2d249522016014df25584db3b  
/var/lib/juju/tools/2.0-beta4.1-yenial-armhf/tools.tar.gz
2016-04-15 09:15:57 INFO juju.cmd supercommand.go:60 running jujud [2.0-beta4.1 
gc go1.6.1]
2016-04-15 09:15:57 DEBUG juju.agent agent.go:524 read agent config, format 
"1.18"
2016-04-15 09:15:57 INFO juju.network network.go:351 setting prefer-ipv6 to 
false
2016-04-15 09:16:01 INFO juju.agent identity.go:22 writing system identity file
2016-04-15 09:16:01 DEBUG juju.cmd.jujud bootstrap.go:322 starting mongo
2016-04-15 09:16:01 DEBUG juju.cmd.jujud bootstrap.go:347 calling 
ensureMongoServer
2016-04-15 09:16:01 INFO juju.mongo mongo.go:394 Ensuring mongo server is 
running; data directory /var/lib/juju; port 37017
2016-04-15 09:16:01 INFO juju.mongo mongo.go:559 installing [juju-mongodb3.2]
2016-04-15 09:16:01 INFO juju.utils.packaging.manager utils.go:57 Running: 
apt-get --option=Dpkg::Options::=--force-confold 
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install 
juju-mongodb3.2
2016-04-15 09:16:02 ERROR juju.utils.packaging.manager utils.go:103 packaging 
command failed: encountered fatal error: unable to locate package; cmd: 
"apt-get --option=Dpkg::Options::=--force-confold 
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install 
juju-mongodb3.2"; output: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package juju-mongodb3.2
E: Couldn't find any package by glob 'juju-mongodb3.2'
E: Couldn't find any package by regex 'juju-mongodb3.2'


This is a product of two deliberate choices. Firstly, per bug 1557852 we don't 
build juju-mongodb3.2 on 32 bit arches. Secondly, juju will only try to install 
the latest mongodb in post-xenial series.


This is the given logic in github.com/juju/juju/mongo/mongo.go 
packagesForSeries:

func packagesForSeries(series string) ([]string, []string) {
switch series {
case "precise", "quantal", "raring", "saucy", "centos7":
return []string{"mongodb-server"}, []string{}
case "trusty", "wily", "xenial":
return []string{JujuMongoPackage}, []string{"juju-mongodb"}
default:
// y and onwards
return []string{JujuMongoPackage}, []string{}
}
}

The test should either be skipped on armhf or we need a way to access
another arch to setup a state server for the armhf client to talk to.

** 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/1571072

Title:
  autopkgtest future-manual-provider fails on armhf for 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1571072/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

Well, mixed news.

The 1.25.5 upload yesterday got bopped by the keyserver failing, but has
now been reuploaded and we're waiting on the autopkgtest run.

The 2.0-beta4 upload happened, and we have test results:



Things are in a better state (s390x is actually green) but the
substrates that can run the lxd test all failed with:



+ juju bootstrap my-controller lxd --upload-tools --debug --config 
default-series=xenial
2016-04-15 04:44:46 INFO juju.cmd supercommand.go:60 running juju [2.0-beta4 gc 
go1.6.1]
2016-04-15 04:44:46 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a 
provider name
2016-04-15 04:44:46 INFO cmd cmd.go:141 no credentials found, checking 
environment
2016-04-15 04:44:46 DEBUG juju.cmd.juju.commands bootstrap.go:365 preparing 
controller with config: map[type:lxd name:admin 
uuid:2bf2d716-0a36-46a3-8b77-83dc8fc66507 
controller-uuid:2bf2d716-0a36-46a3-8b77-83dc8fc66507 default-series:xenial]
2016-04-15 04:44:50 DEBUG juju.tools.lxdclient client.go:73 connecting to LXD 
remote "local": ""
2016-04-15 04:44:52 DEBUG juju.tools.lxdclient client.go:73 connecting to LXD 
remote "juju-remote": "10.0.8.1"
2016-04-15 04:44:52 ERROR cmd supercommand.go:448 Get 
https://10.0.8.1:8443/1.0/profiles: Forbidden
adt-run [04:44:53]: test current-lxd-provider: ---]
adt-run [04:44:53]: test current-lxd-provider:  - - - - - - - - - - results - - 
- - - - - - - -
current-lxd-provider FAIL non-zero exit status 1

I'm not sure what is different here, from the setup I got to pass
successfully, using a canonistack machine:



The 30 mins fetching stuff from the archive into the container there
is... suspect, but also well after the autopkgtest.ubuntu.com setup
fails.

I'm not sure how to debug further, given I can't exactly reproduce the
real setup.

Additionally, and easier to fix, the armhf future-manual-provider test
fails because it can't install juju-mongodb3.2:



2016-04-15 09:16:01 DEBUG juju.cmd.jujud bootstrap.go:322 starting mongo
2016-04-15 09:16:01 DEBUG juju.cmd.jujud bootstrap.go:347 calling 
ensureMongoServer
2016-04-15 09:16:01 INFO juju.mongo mongo.go:394 Ensuring mongo server is 
running; data directory /var/lib/juju; port 37017
2016-04-15 09:16:01 INFO juju.mongo mongo.go:559 installing [juju-mongodb3.2]
2016-04-15 09:16:01 INFO juju.utils.packaging.manager utils.go:57 Running: 
apt-get --option=Dpkg::Options::=--force-confold 
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install 
juju-mongodb3.2
2016-04-15 09:16:02 ERROR juju.utils.packaging.manager utils.go:103 packaging 
command failed: encountered fatal error: unable to locate package; cmd: 
"apt-get --option=Dpkg::Options::=--force-confold 
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install 
juju-mongodb3.2"; output: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package juju-mongodb3.2

This is fun, but not an unexpected result from other choices. We're not
building mongo 3 on 32 bit arches, and the fallback to the old package
in juju was explicitly only for xenial and lower series.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570759] Re: apt-get install juju does not install /usr/bin/juju

[Martin Packman]

** Also affects: juju-core (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: juju-release-tools

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570759

Title:
  apt-get install juju does not install /usr/bin/juju

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570759/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570660] [NEW] Plugins not included in juju manpages

[Martin Packman]

Public bug reported:

Currently juju plugins neither have their own manpages, nor are they
included in the main juju manpage.

There is also not a `juju plugins` command or similar, so installed
plugins are completely undiscoverable from the command line. If we give
each plugin an autogenerated manpage, which seems reasonable, the main
manpage should also reference the default installed plugins.

** Affects: juju-core
 Importance: High
 Status: Triaged

** Affects: juju-core/1.25
 Importance: Medium
 Status: Triaged

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: docs packaging usability

** Also affects: juju-core
   Importance: Undecided
   Status: New

** Tags added: docs packaging usability

** Also affects: juju-core/1.25
   Importance: Undecided
   Status: New

** Changed in: juju-core
   Importance: Undecided => High

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
Milestone: None => 2.0-rc1

** Changed in: juju-core/1.25
   Importance: Undecided => Medium

** Changed in: juju-core/1.25
   Status: New => Triaged

** Changed in: juju-core/1.25
Milestone: None => 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/1570660

Title:
  Plugins not included in juju manpages

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570660/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570657] Re: Bash completion needed for versioned juju commands

[Martin Packman]

There's a pending pull request for other 2.0 improvements to the bash
completion script here:



-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570657

Title:
  Bash completion needed for versioned juju commands

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570657] [NEW] Bash completion needed for versioned juju commands

[Martin Packman]

Public bug reported:

The new juju packaging in xenial includes 'juju-1' and 'juju-2.0'
commands that are currently not covered by the bash-completion script.

This means no completion for 1.X is available at all at present, and is
otherwise confusing when needing to use the specific version commands.

** Affects: juju-core
 Importance: High
 Status: Triaged

** Affects: juju-core/1.25
 Importance: High
 Status: Triaged

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: packaging usability

** Also affects: juju-core
   Importance: Undecided
   Status: New

** Also affects: juju-core/1.25
   Importance: Undecided
   Status: New

** Changed in: juju-core/1.25
   Importance: Undecided => High

** Changed in: juju-core/1.25
   Status: New => Triaged

** Changed in: juju-core/1.25
Milestone: None => 1.25.6

** Changed in: juju-core
   Importance: Undecided => High

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
Milestone: None => 2.0-rc1

** Tags added: packaging usability

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570657

Title:
  Bash completion needed for versioned juju commands

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570654] [NEW] Manpage still refers to 1.X config for 2.0

[Martin Packman]

Public bug reported:

The 2.0 manpage still includes text about environments.yaml and nothing
about new configuration files:

FILES
   ~/.config/juju/environments.yaml
  This  is the Juju config file, which you can use to specify mul‐
  tiple models in which to deploy.

  A config file can be created using juju init which you can  then
  edit to provide the secret keys, or use environment variables to
  provide the secret values.

This should be updated to be accurate and useful before release.

** Affects: juju-core
 Importance: High
 Status: Triaged

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: docs packaging

** Also affects: juju-core
   Importance: Undecided
   Status: New

** Changed in: juju-core
   Importance: Undecided => High

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
Milestone: None => 2.0-rc1

** Tags added: docs packaging

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570654

Title:
  Manpage still refers to 1.X config for 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570654/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570651] Re: Manpages for juju aliases drop version

[Martin Packman]

** Tags added: docs

** Tags added: packaging

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570651

Title:
  Manpages for juju aliases drop version

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570651] [NEW] Manpages for juju aliases drop version

[Martin Packman]

Public bug reported:

With xenial, we now provide juju version specific wrappers named
'juju-1' and 'juju-2.0' that have corresponding manpages. However, the
text inside the pages just uses 'juju' as the name, not the alias, which
is particularly confusing for juju-1 where the commands will often
differ.

The documentation generation step should ideally take a name which juju
will be invoked as and use that in place of 'juju' throughout.

** Affects: juju-core
 Importance: Medium
 Status: Triaged

** Affects: juju-core/1.25
 Importance: Medium
 Status: Triaged

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: juju-core
   Importance: Undecided
   Status: New

** Also affects: juju-core/1.25
   Importance: Undecided
   Status: New

** Changed in: juju-core/1.25
   Importance: Undecided => Medium

** Changed in: juju-core/1.25
   Status: New => Triaged

** Changed in: juju-core/1.25
Milestone: None => 1.25.6

** Changed in: juju-core
   Importance: Undecided => Medium

** Changed in: juju-core
   Status: New => Triaged

** Changed in: juju-core
Milestone: None => 2.0-rc1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570651

Title:
  Manpages for juju aliases drop version

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570650] [NEW] Use juju-mongodb2.6 for 1.25 on xenial

[Martin Packman]

Public bug reported:

Now xenial has a juju-mongodb2.6 package that has better support
expectations than our existing (2.4) juju-mongodb package, we should
install and use that by preference for the local provider.

* The juju-local package should depend on juju-mongodb2.6 instead of 
juju-mongodb
* On bootstrap, the local provider should try to install juju-mongodb2.6 on 
xenial
* The init scripts should look in the 2.6 specific location when starting 
mongodb

This doesn't need to include upgrading existing running local providers
to mongo 2.6, but some sane selection needs to happen if both can be
installed.

** Affects: juju-core
 Importance: Undecided
 Status: Fix Released

** Affects: juju-core/1.25
 Importance: High
 Status: Triaged

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: local-provider packaging

** Also affects: juju-core
   Importance: Undecided
   Status: New

** Also affects: juju-core/1.25
   Importance: Undecided
   Status: New

** Changed in: juju-core/1.25
   Importance: Undecided => High

** Changed in: juju-core/1.25
   Status: New => Triaged

** Changed in: juju-core/1.25
Milestone: None => 1.25.6

** Tags added: local-provider packaging

** Changed in: juju-core
   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/1570650

Title:
  Use juju-mongodb2.6 for 1.25 on xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1570650/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

Have updated packaging and upstream for both juju 2.0 and 1.25 ready to
upload.


https://code.launchpad.net/~juju-qa/ubuntu/xenial/juju/juju-1.25.5

New 1.25.5 bugfix release. Fixed the adt tests, including making them
run with isolation-container rather than isolation-machine.

adt-run [18:19:14]:  summary
client   PASS
current-local-provider PASS
future-local-provider PASS
current-manual-provider PASS
future-manual-provider PASS

Final note, I have for now reverted the dependency change to use juju-
mongodb2.6 as upstream code doesn't correctly detect its existence and
continues to use juju-mongodb (2.4) anyway. I will follow up with a bug
against 1.25.6 for this.


https://code.launchpad.net/~juju-qa/ubuntu/xenial/juju/xenial-2.0-beta4

New 2.0-beta4 release. Fixed a bunch of issues with the tests, including
the requirement for manual lxd configuration. Unfortunately, lxd
currently doesn't work in the nested container setup of these tests, so
I have not been able to verify everything works yet.

adt-run [23:53:12]:  summary
current-lxd-provider SKIP Test requires machine-level isolation but testbed 
does not provide that
client   PASS
current-manual-provider PASS
future-manual-provider PASS

The juju-2.0 package now recommends lxd as suggested.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

...and I refresh the page and see someone has now reviewed both mongodb
packages. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

Sorry, should have been clearer. Yes, I am working on fixing those
issues with the tests. We're also trying to get a new source release
this week that can be put the the archive, this package can't move
forward without that.

"LXD v2.0.0-rc8 does not work with Juju v2.0-beta3"


Also as of this morning our unit tests on master break because the
xenial daily image now includes lxd 2.0.0 rather than rc9, which again
changes behaviour.

Martin Pitt: We currently don't have lxd as a dep on this package
because it's included by default on the image. If I add it (as a
depends, or recommends), does that mean our autopkgtests including the
lxd provider ones will run on new lxd package uploads and prevent them
entering the archive in future?

The image import can likely be dropped, the 'yenial' is a test about
catching breakage due to a new ubuntu development release, but we
probably don't need to actually start lxd containers in the fake new
release for the coverage we want.

Thanks for the info on the meaning of the various flags. For now I think
we do need isolation-machine (keep having bugs where networking
interfaces etc get created wrongly) but will look at just using
restriction-container later.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

It seems juju-core-1 is just stuck on the juju-mongodb2.6 package lying
around unreviewed in the new queue:



juju-core-1 (- to 1.25.4-0ubuntu5) 
  Maintainer: Ubuntu Developers 
  Section: universe/devel 
  3 days old 
  juju-local/amd64 unsatisfiable Depends: juju-mongodb2.6 
  juju-local-kvm/amd64 unsatisfiable Depends: juju-mongodb2.6 
  Not considered

Is there a reason that hasn't been tackled yet?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

Sadly, being stuck in -proposed is probably correct for beta3, due to
the above mentioned lxd breakages.

Note that the future-lxd-provider gets futher, but still breaks due to
changes in lxd since the test was last modified with beta2:

+ lxd-images import ubuntu yenial --alias ubuntu-yenial
debian/tests/lxd-provider: line 8: lxd-images: command not found

Also, we don't have coverage for lxd on armhf or s390x as they can't
provide machine-level isolation. That's probably fine, but can maybe be
improved when we have more confidence lxd/juju won't blow things up as
much as the dev versions have tended to.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

>   - juju-2.0 is shipping a link named 'juju-upgrade-mondo' instead of
> 'juju-upgrade-mongo'.  This probably needs fixing.

Fixed in the packaging branch.

>   - juju-2.0 uses and src/github.com/lxc/lxd/ (expected) and does not
> build-depend on the golang-github-lxc-lxd-dev package in the archive.  This
> definitely needs fixing; this will be tracked in bug #1568148.

This is a deliberate omission for beta3. Since we did the tarball
release, there have been two new lxd rcs uploaded that change their api
and break compatibility. It will be included with our rc packaging, by
which time they will hopefully be stable.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

Packaging branches have been updated based on review feedback, new
versions need uploading:

lp:~juju-qa/ubuntu/xenial/juju/juju-1.25.4
lp:~juju-qa/ubuntu/xenial/juju/xenial-2.0-beta3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

The proposed packaging updates are now available in Adam's PPA:



This includes:

* Switch from golang-go.net-dev to golang-x-net-dev as mentioned by ~jdstrand
* Use of Suggests to keep Juju 1.X tools around through upgrade from ~adconrad

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

The proposed packaging updates are now available in Adam's PPA:



This includes:

* Switch from golang-go.net-dev to golang-x-net-dev as mentioned by ~jdstrand
* Use of Suggests to keep Juju 1.X tools around through upgrade from ~adconrad

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1564670] [NEW] After upgrade Juju 1.X should still be the default

[Martin Packman]

Public bug reported:

When upgrading to Xenial the new default Juju version is going to be
2.0.

Because 2.0 clients are not compatible with 1.X environments, this means
existing environments will be inaccessible unless the 1.X client is
switched to. The plan is to give a warning when creating Juju 2
configuration for the first time, something along the lines of:

$ sudo apt-get update
$ juju status
WARNING Creating new juju 2 configuration.
Use `update-alternatives --config juju` to switch for 1.X environments.
$ juju status
ERROR Unable to connect to model "".
Please check your credentials or use 'juju bootstrap' to create a new model.

There has been some concern that this is still too confusing and 1.X
should remain the default juju without explicit user intervention.

** 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/1564670

Title:
  After upgrade Juju 1.X should still be the default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1564670] [NEW] After upgrade Juju 1.X should still be the default

[Martin Packman]

Public bug reported:

When upgrading to Xenial the new default Juju version is going to be
2.0.

Because 2.0 clients are not compatible with 1.X environments, this means
existing environments will be inaccessible unless the 1.X client is
switched to. The plan is to give a warning when creating Juju 2
configuration for the first time, something along the lines of:

$ sudo apt-get update
$ juju status
WARNING Creating new juju 2 configuration.
Use `update-alternatives --config juju` to switch for 1.X environments.
$ juju status
ERROR Unable to connect to model "".
Please check your credentials or use 'juju bootstrap' to create a new model.

There has been some concern that this is still too confusing and 1.X
should remain the default juju without explicit user intervention.

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1564670

Title:
  After upgrade Juju 1.X should still be the default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1564662] [NEW] Juju binaries should be stripped

[Martin Packman]

Public bug reported:

Previously the juju team has been asked to strip the go binaries in the
distro packaging. Per bug 1265970 that was not possible as with go 1.2
it introduced bugs such as bug 1200255.

With go 1.6 in xenial, it may now be safe to strip the juju binaries,
but this needs testing on all architectures, including exercising the
reflect code.

See irc log for more background:



** 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/1564662

Title:
  Juju binaries should be stripped

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1564662] [NEW] Juju binaries should be stripped

[Martin Packman]

Public bug reported:

Previously the juju team has been asked to strip the go binaries in the
distro packaging. Per bug 1265970 that was not possible as with go 1.2
it introduced bugs such as bug 1200255.

With go 1.6 in xenial, it may now be safe to strip the juju binaries,
but this needs testing on all architectures, including exercising the
reflect code.

See irc log for more background:



** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1564662

Title:
  Juju binaries should be stripped

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

I've edited the bug the clarify the juju-mongodb situation. There's a
change to both tweak the version of mongodb and make the unit tests more
reliable, which was held from landing for beta3 waiting on the package
in ubuntu. It will be included in the rc.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

I've edited the bug the clarify the juju-mongodb situation. There's a
change to both tweak the version of mongodb and make the unit tests more
reliable, which was held from landing for beta3 waiting on the package
in ubuntu. It will be included in the rc.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

** Description changed:

  The juju team is requesting an FFE for juju-core. Juju2 represents API
  changes and new features and bugfixes for juju.  We are NOT requesting a
  place on any image for xenial. This FFE is intended to cover the
  acceptance of the updated juju-core package, as well as the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  Related FFes
  
  
  Required for Juju 2.0:
  
  juju-mongodb3.2: bug 1557852
  juju-mongodb2.6: bug 1557830
  juju-mongo-tools3.2: bug 1558336
+ 
+ (see note below about mongodb for details)
  
  Required consumers:
  
  conjure: bug 1561037
  bigdata: bug 1561043
  openstack: Already in universe, dep wait on conjure -> juju 2.0
  charm-tools: bug 1546776
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
  Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
  scenarios:
  
  New Xenial:
  No juju, apt-get install juju, juju version will be 2.0.
  Example using ppa: 
  
  Upgrading Trusty/Wily/old Xenial:
  Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
  Example using ppa: 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
  
  The community has also been actively involved with testing, providing
  feedback, and adopting 2.0 throughout the development cycle.
  
  * 250 bugs and wishlist items filed
  * 4 bugs fixed by community members
  * ~100-125 downloads for each ppa release
  
  Community Adoption
  --
  The community has already begun 

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

** Description changed:

  The juju team is requesting an FFE for juju-core. Juju2 represents API
  changes and new features and bugfixes for juju.  We are NOT requesting a
  place on any image for xenial. This FFE is intended to cover the
  acceptance of the updated juju-core package, as well as the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  Related FFes
  
  
  Required for Juju 2.0:
  
  juju-mongodb3.2: bug 1557852
  juju-mongodb2.6: bug 1557830
  juju-mongo-tools3.2: bug 1558336
+ 
+ (see note below about mongodb for details)
  
  Required consumers:
  
  conjure: bug 1561037
  bigdata: bug 1561043
  openstack: Already in universe, dep wait on conjure -> juju 2.0
  charm-tools: bug 1546776
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
  Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
  scenarios:
  
  New Xenial:
  No juju, apt-get install juju, juju version will be 2.0.
  Example using ppa: 
  
  Upgrading Trusty/Wily/old Xenial:
  Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
  Example using ppa: 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
  
  The community has also been actively involved with testing, providing
  feedback, and adopting 2.0 throughout the development cycle.
  
  * 250 bugs and wishlist items filed
  * 4 bugs fixed by community members
  * ~100-125 downloads for each ppa release
  
  Community Adoption
  --
  The community has already begun 

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

Updated the description with the example upgrade testing using the test
packages in the ppa.

** Description changed:

  The juju team is requesting an FFE for juju-core. Juju2 represents API
  changes and new features and bugfixes for juju.  We are NOT requesting a
  place on any image for xenial. This FFE is intended to cover the
  acceptance of the updated juju-core package, as well as the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
- Users upgrading from trusty will find their juju2 version updated. The 
current juju-core package will become juju-core1. Users upgrading from wily and 
trusty will get juju2 as part of the upgrade. Update-alternatives will provide 
support for toggling /usr/bin/juju between juju1 and juju2 binaries.
+ Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
- scenarios;
+ scenarios:
  
- Trusty
- No juju -> install juju on xenial, juju-core is installed.
- Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives 
toggles
+ New Xenial:
+ No juju, apt-get install juju, juju version will be 2.0.
+ Example using ppa: 
  
- Wily
- No juju -> install juju on xenial, juju-core is installed.
- Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives 
toggles
+ Upgrading Trusty/Wily/old Xenial:
+ Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
+ Example using ppa: 
+ 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
 

[Bug 1545913] Re: [FFe] juju-core 2.0

[Martin Packman]

Updated the description with the example upgrade testing using the test
packages in the ppa.

** Description changed:

  The juju team is requesting an FFE for juju-core. Juju2 represents API
  changes and new features and bugfixes for juju.  We are NOT requesting a
  place on any image for xenial. This FFE is intended to cover the
  acceptance of the updated juju-core package, as well as the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
- Users upgrading from trusty will find their juju2 version updated. The 
current juju-core package will become juju-core1. Users upgrading from wily and 
trusty will get juju2 as part of the upgrade. Update-alternatives will provide 
support for toggling /usr/bin/juju between juju1 and juju2 binaries.
+ Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
- scenarios;
+ scenarios:
  
- Trusty
- No juju -> install juju on xenial, juju-core is installed.
- Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives 
toggles
+ New Xenial:
+ No juju, apt-get install juju, juju version will be 2.0.
+ Example using ppa: 
  
- Wily
- No juju -> install juju on xenial, juju-core is installed.
- Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives 
toggles
+ Upgrading Trusty/Wily/old Xenial:
+ Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
+ Example using ppa: 
+ 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
 

[Bug 1560315] Re: [needs packaging] juju2 beta is not in xenial

[Martin Packman]

Hm, looks like the adventures with reworking the packaging yesterday
(which I didn't follow the reasoning behind, but ended up basing the
beta2 packaging branch on an existing xnox branch) lost the Build-
Depends we had on archive golang packages.

What we had:



Missing here:



So, they should be added back in.

That said, the juju qa team hasn't spent any time this cycle on
adventures with golang packaging. What time we have had on distro tasks
has been sucked up basically packaging mongo 3 (and mongo 2.6 for
migration purposes).

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1560315

Title:
  [needs packaging] juju2 beta is not in xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1560315] Re: [needs packaging] juju2 beta is not in xenial

[Martin Packman]

Hm, looks like the adventures with reworking the packaging yesterday
(which I didn't follow the reasoning behind, but ended up basing the
beta2 packaging branch on an existing xnox branch) lost the Build-
Depends we had on archive golang packages.

What we had:



Missing here:



So, they should be added back in.

That said, the juju qa team hasn't spent any time this cycle on
adventures with golang packaging. What time we have had on distro tasks
has been sucked up basically packaging mongo 3 (and mongo 2.6 for
migration purposes).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560315

Title:
  [needs packaging] juju2 beta is not in xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1557830] Re: [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

[Martin Packman]

> Ubuntu mongodb 1:2.6.10-0ubuntu1 introduced --use-system-v8, but you haven't
> carried this forward. Is this expected (not described in changelog)? Perhaps 
> it
> is because of --disable-scripting but I'm not sure.

Indeed. We have always built juju-mongodb without the javascript engine
because the security team had concerns and we didn't need it anyway.
Note in 3.2 V8 has gone, and they're back to spidermonkey:



-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557830

Title:
  [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1557830] Re: [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

[Martin Packman]

> Ubuntu mongodb 1:2.6.10-0ubuntu1 introduced --use-system-v8, but you haven't
> carried this forward. Is this expected (not described in changelog)? Perhaps 
> it
> is because of --disable-scripting but I'm not sure.

Indeed. We have always built juju-mongodb without the javascript engine
because the security team had concerns and we didn't need it anyway.
Note in 3.2 V8 has gone, and they're back to spidermonkey:



-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1557830

Title:
  [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

[Martin Packman]

"Are you saying you want to use the embedded code copy? Has anyone
looked at the testsuite issue to fix it? Embedded code copies should be
avoided at all costs per MIR guidelines -- we are making huge
concessions for the juju and lxd teams already, can someone take a look
at this ftbfs and report back?"

Short version, these extended-standard library packages are in practice
pretty closely tied to the golang minor version.

Debian currently has go 1.4 and the go-x-text package is from May,
before the go 1.5 release:



In go 1.5 the unicode package, which includes generation of various data
tables, was updated to use Unicode 8.0.0 - which amongst other changes
introduces the Ahom script:



This means the test in golang.org/x/text which uses the data from the
standard library unicode package now finds its own data out of sync with
the system golang on wily. Specifically, the new character U+11730 AHOM
DIGIT ZERO should be numerically equal to 0, but is not. Obviously there
are other failures as well.

There's an easy fix for wily, which is just update the package to use a
current revision of golang.org/x/text for go 1.5 compatibility. I've
proposed a debian/experimental branch that does that:



(Minor wrinkle, still a test failure even with the latest code, I
patched it in the packaging but presumably needs resolving upstream.)

Anyway, where this gets really fun is when we start considering
backports of latest juju. None of these packages existed when trusty was
released, and their current versions will generally be incompatible with
go 1.2.1. We could pick out the revisions that worked for specific
backport packaging, but won't have support upstream for security fixes
to random older checkouts so won't really gain anything.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267393

Title:
  [MIR] juju-core, juju-mongodb, gccgo, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1267393/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

[Martin Packman]

"Are you saying you want to use the embedded code copy? Has anyone
looked at the testsuite issue to fix it? Embedded code copies should be
avoided at all costs per MIR guidelines -- we are making huge
concessions for the juju and lxd teams already, can someone take a look
at this ftbfs and report back?"

Short version, these extended-standard library packages are in practice
pretty closely tied to the golang minor version.

Debian currently has go 1.4 and the go-x-text package is from May,
before the go 1.5 release:



In go 1.5 the unicode package, which includes generation of various data
tables, was updated to use Unicode 8.0.0 - which amongst other changes
introduces the Ahom script:



This means the test in golang.org/x/text which uses the data from the
standard library unicode package now finds its own data out of sync with
the system golang on wily. Specifically, the new character U+11730 AHOM
DIGIT ZERO should be numerically equal to 0, but is not. Obviously there
are other failures as well.

There's an easy fix for wily, which is just update the package to use a
current revision of golang.org/x/text for go 1.5 compatibility. I've
proposed a debian/experimental branch that does that:



(Minor wrinkle, still a test failure even with the latest code, I
patched it in the packaging but presumably needs resolving upstream.)

Anyway, where this gets really fun is when we start considering
backports of latest juju. None of these packages existed when trusty was
released, and their current versions will generally be incompatible with
go 1.2.1. We could pick out the revisions that worked for specific
backport packaging, but won't have support upstream for security fixes
to random older checkouts so won't really gain anything.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
https://bugs.launchpad.net/bugs/1267393

Title:
  [MIR] juju-core, juju-mongodb, gccgo, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1267393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

[Martin Packman]

> * golang-go.crypto
>  - needs a bug subscriber

Looks like it's ~ubuntu-server now.

> * golang-gocheck
>  - can be dropped when bug #1504821 is fixed (comment #82)
> * golang-goyaml
>  - can be dropped when bug #1504821 is fixed (comment #82)

To clarify, I am making these changes on master. Backporting the code
changes required to change the dependency for 1.24 carries considerable
risk to application-level api compatibility, as yaml.v2 changes some
serialisation behaviour. I would prefer if for 1.24 we relied on the
bundled yaml.v1 package that been consistently used in testing through
this cycle.

> * golang-x-text
>  - ftbfs (comment 115)
>  - needs a bug subscriber

This package is not a dependency of juju. It's used by
golang.org/x/net/html/charset only, so is just pulled in as a side
effect of taking the debian package. My preference would be to drop the
juju packaging dependency on golang-go.net-dev for 1.24 instead.

> * juju-core
>  - what is the status of
>
> https://code.launchpad.net/~james-page/ubuntu/wily/juju-core/mir-fixes/+merge/274052
>  ? jamespage said it is 'pending testing by the juju qa team'.

We have manually tested the packaging change, but it is not yet included
in our automated testing and release process. We have work in progress
to break out our series-independent packaging branch. That said, the
merge should not be considered blocked on our verification.

> * dep8 question (comments 86, 93, 99, 100, 101, 117)
>  - pitti's comment in #99 needs to be done. It could be done as an SRU. If 
> that is the approach, please file a bug on this and comment here

I would appreciate if someone who has a clear understanding for the work
pitti is requesting (such as pitti himself) could file the bug and
subscribe me. We'll happily update our packaging to use any such new
mechanism if it's provided.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
https://bugs.launchpad.net/bugs/1267393

Title:
  [MIR] juju-core, juju-mongodb, gccgo, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1267393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

[Martin Packman]

> * golang-go.crypto
>  - needs a bug subscriber

Looks like it's ~ubuntu-server now.

> * golang-gocheck
>  - can be dropped when bug #1504821 is fixed (comment #82)
> * golang-goyaml
>  - can be dropped when bug #1504821 is fixed (comment #82)

To clarify, I am making these changes on master. Backporting the code
changes required to change the dependency for 1.24 carries considerable
risk to application-level api compatibility, as yaml.v2 changes some
serialisation behaviour. I would prefer if for 1.24 we relied on the
bundled yaml.v1 package that been consistently used in testing through
this cycle.

> * golang-x-text
>  - ftbfs (comment 115)
>  - needs a bug subscriber

This package is not a dependency of juju. It's used by
golang.org/x/net/html/charset only, so is just pulled in as a side
effect of taking the debian package. My preference would be to drop the
juju packaging dependency on golang-go.net-dev for 1.24 instead.

> * juju-core
>  - what is the status of
>
> https://code.launchpad.net/~james-page/ubuntu/wily/juju-core/mir-fixes/+merge/274052
>  ? jamespage said it is 'pending testing by the juju qa team'.

We have manually tested the packaging change, but it is not yet included
in our automated testing and release process. We have work in progress
to break out our series-independent packaging branch. That said, the
merge should not be considered blocked on our verification.

> * dep8 question (comments 86, 93, 99, 100, 101, 117)
>  - pitti's comment in #99 needs to be done. It could be done as an SRU. If 
> that is the approach, please file a bug on this and comment here

I would appreciate if someone who has a clear understanding for the work
pitti is requesting (such as pitti himself) could file the bug and
subscribe me. We'll happily update our packaging to use any such new
mechanism if it's provided.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267393

Title:
  [MIR] juju-core, juju-mongodb, gccgo, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1267393/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1498655] Re: Steam Controller support: need read-write access to Valve-owned input event device nodes.

[Martin Packman]

** Branch linked: lp:~gz/ubuntu/wily/steam/new_rel_udev_rules

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498655

Title:
  Steam Controller support: need read-write access to Valve-owned input
  event device nodes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1498655/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1498658] Re: Steam Controller support: need read-write access to /dev/uinput for controller emulation

[Martin Packman]

** Branch linked: lp:~gz/ubuntu/wily/steam/new_rel_udev_rules

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498658

Title:
  Steam Controller support: need read-write access to /dev/uinput for
  controller emulation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1498658/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1500981] Re: juju-db segfault while syncing with replicas

[Martin Packman]

This package hasn't changed in trusty in more than a year.

 Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500981

Title:
  juju-db segfault while syncing with replicas

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1500981] Re: juju-db segfault while syncing with replicas

[Martin Packman]

This package hasn't changed in trusty in more than a year.

 Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1500981

Title:
  juju-db segfault while syncing with replicas

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494441] Re: ppc64el: cannot find package "encoding"

[Martin Packman]

This has been temporarily addressed on master by backing out the change
responsible:



-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494441

Title:
  ppc64el: cannot find package "encoding"

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1494441/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1029471] Re: Apport add_info hook should not add ppa version as tag

[Martin Packman]

** Changed in: unity (Ubuntu)
   Status: In Progress = New

** Changed in: unity (Ubuntu)
 Assignee: Martin Packman (gz) = (unassigned)

** Changed in: unity
   Status: In Progress = New

** Changed in: unity
 Assignee: Martin Packman (gz) = (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029471

Title:
  Apport add_info hook should not add ppa version as tag

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1029471/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1330504] Re: strongSwan 5.1.3

[Martin Packman]

** Project changed: strongswan = obsolete-junk

** No longer affects: obsolete-junk

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to strongswan in Ubuntu.
https://bugs.launchpad.net/bugs/1330504

Title:
  strongSwan 5.1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1330504/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1330504] Re: strongSwan 5.1.3

[Martin Packman]

** Project changed: strongswan = obsolete-junk

** No longer affects: obsolete-junk

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1330504

Title:
  strongSwan 5.1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1330504/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1381671] Re: reboot tests fail to build on gccgo

[Martin Packman]

Thanks Michael! I guess I'll need to be pretty conservative about
removing the workaround in juju as we're testing on multiple ubuntu
releases.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381671

Title:
  reboot tests fail to build on gccgo

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1381671/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1393825] [NEW] Juju testsuite fails in random ways

[Martin Packman]

Public bug reported:

Two parts of the juju-core test suite panic or segfault when run with
-compiler gccgo on amd64.

Some examples, in provider/openstack:

ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test 
./... -compiler gccgo -gocheck.v -v)
3
=== RUN Test
...
PASS: local_test.go:1207: 
com_juju_juju_provider_openstack_test.TestFetchFromToolsMetadataSources.pN66_github.com_juju_juju_provider_openstack_test.localHTTPSServerSuite
   0.243s
munmap of stack space failed: errno 22
Aborted
...

ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test 
./... -compiler gccgo -gocheck.v -v)
3
=== RUN Test
...
PASS: local_test.go:1207: 
com_juju_juju_provider_openstack_test.TestFetchFromToolsMetadataSources.pN66_github.com_juju_juju_provider_openstack_test.localHTTPSServerSuite
   0.295s
signal: segmentation fault (core dumped)
FAILgithub.com/juju/juju/provider/openstack 12.746s

And in environs/simplestreams:

ubuntu@go:~/go/src/github.com/juju/juju$ (cd environs/simplestreams go test 
./... -compiler gccgo -gocheck.v -v)
=== RUN Test
...
PASS: datasource_test.go:79: 
com_juju_juju_environs_simplestreams_test.TestNonVerifyingClientSucceeds.pN69_github.com_juju_juju_environs_simplestreams_test.datasourceHTTPSSuite
0.014s
unexpected fault address 0x7f330011
fatal error: fault
[signal 0xb code=0x1 addr=0x7f330011]
...

This one looks a bit like bug 1381671 but the same run can just pass:

$ (cd environs/simplestreams go test ./... -compiler gccgo -gocheck.v -v)
=== RUN Test
...
OK: 46 passed
--- PASS: Test (0.27 seconds)
PASS


Some investigations from IRC:
http://irclogs.ubuntu.com/2014/10/31/%23juju-dev.html#t17:29

** Affects: gccgo-go (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gccgo-go in Ubuntu.
https://bugs.launchpad.net/bugs/1393825

Title:
  Juju testsuite fails in random ways

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1393825/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1393825] [NEW] Juju testsuite fails in random ways

[Martin Packman]

Public bug reported:

Two parts of the juju-core test suite panic or segfault when run with
-compiler gccgo on amd64.

Some examples, in provider/openstack:

ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test 
./... -compiler gccgo -gocheck.v -v)
3
=== RUN Test
...
PASS: local_test.go:1207: 
com_juju_juju_provider_openstack_test.TestFetchFromToolsMetadataSources.pN66_github.com_juju_juju_provider_openstack_test.localHTTPSServerSuite
   0.243s
munmap of stack space failed: errno 22
Aborted
...

ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test 
./... -compiler gccgo -gocheck.v -v)
3
=== RUN Test
...
PASS: local_test.go:1207: 
com_juju_juju_provider_openstack_test.TestFetchFromToolsMetadataSources.pN66_github.com_juju_juju_provider_openstack_test.localHTTPSServerSuite
   0.295s
signal: segmentation fault (core dumped)
FAILgithub.com/juju/juju/provider/openstack 12.746s

And in environs/simplestreams:

ubuntu@go:~/go/src/github.com/juju/juju$ (cd environs/simplestreams go test 
./... -compiler gccgo -gocheck.v -v)
=== RUN Test
...
PASS: datasource_test.go:79: 
com_juju_juju_environs_simplestreams_test.TestNonVerifyingClientSucceeds.pN69_github.com_juju_juju_environs_simplestreams_test.datasourceHTTPSSuite
0.014s
unexpected fault address 0x7f330011
fatal error: fault
[signal 0xb code=0x1 addr=0x7f330011]
...

This one looks a bit like bug 1381671 but the same run can just pass:

$ (cd environs/simplestreams go test ./... -compiler gccgo -gocheck.v -v)
=== RUN Test
...
OK: 46 passed
--- PASS: Test (0.27 seconds)
PASS


Some investigations from IRC:
http://irclogs.ubuntu.com/2014/10/31/%23juju-dev.html#t17:29

** Affects: gccgo-go (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/1393825

Title:
  Juju testsuite fails in random ways

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1393825/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1393825] Re: Juju testsuite fails in random ways

[Martin Packman]

** Description changed:

  Two parts of the juju-core test suite panic or segfault when run with
  -compiler gccgo on amd64.
  
  Some examples, in provider/openstack:
  
  ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test 
./... -compiler gccgo -gocheck.v -v)
  3
  === RUN Test
  ...
  PASS: local_test.go:1207: 
com_juju_juju_provider_openstack_test.TestFetchFromToolsMetadataSources.pN66_github.com_juju_juju_provider_openstack_test.localHTTPSServerSuite
 0.243s
  munmap of stack space failed: errno 22
  Aborted
  ...
  
  ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test 
./... -compiler gccgo -gocheck.v -v)
  3
  === RUN Test
  ...
  PASS: local_test.go:1207: 
com_juju_juju_provider_openstack_test.TestFetchFromToolsMetadataSources.pN66_github.com_juju_juju_provider_openstack_test.localHTTPSServerSuite
 0.295s
  signal: segmentation fault (core dumped)
  FAIL  github.com/juju/juju/provider/openstack 12.746s
  
  And in environs/simplestreams:
  
  ubuntu@go:~/go/src/github.com/juju/juju$ (cd environs/simplestreams go test 
./... -compiler gccgo -gocheck.v -v)
  === RUN Test
  ...
  PASS: datasource_test.go:79: 
com_juju_juju_environs_simplestreams_test.TestNonVerifyingClientSucceeds.pN69_github.com_juju_juju_environs_simplestreams_test.datasourceHTTPSSuite
  0.014s
  unexpected fault address 0x7f330011
  fatal error: fault
  [signal 0xb code=0x1 addr=0x7f330011]
  ...
  
- This one looks a bit like bug 1381671 but the same run can just pass:
+ This one looks a bit like bug 1287879 but the same run can just pass:
  
  $ (cd environs/simplestreams go test ./... -compiler gccgo -gocheck.v -v)
  === RUN Test
  ...
  OK: 46 passed
  --- PASS: Test (0.27 seconds)
  PASS
  
- 
  Some investigations from IRC:
  http://irclogs.ubuntu.com/2014/10/31/%23juju-dev.html#t17:29

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393825

Title:
  Juju testsuite fails in random ways

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1393825/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1393825] Re: Juju testsuite fails in random ways

[Martin Packman]

The HTTPS side of this I can reproduce (inconsistently) running just one
test:

ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test 
./... -compiler gccgo -v -gocheck.v -gocheck.f=TestMustDisableSSLVerify)
3
=== RUN Test
unexpected fault address 0x7f6b0011
fatal error: fault
[signal 0xb code=0x1 addr=0x7f6b0011]
...

ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test 
./... -compiler gccgo -v -gocheck.v -gocheck.f=TestMustDisableSSLVerify)
3
=== RUN Test
signal: segmentation fault (core dumped)
FAILgithub.com/juju/juju/provider/openstack 1.324s

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393825

Title:
  Juju testsuite fails in random ways

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1393825/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1393825] Re: Juju testsuite fails in random ways

[Martin Packman]

Another part of this is from a panic in a later test:

ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test 
./... -compiler gccgo -v -gocheck.v 
-gocheck.f=TestStartInstanceWithUnknownAZError)
3
=== RUN Test

--
PANIC: local_test.go:1530: 
com_juju_juju_provider_openstack_test.TestStartInstanceWithUnknownAZError.pN61_github.com_juju_juju_provider_openstack_test.localServerSuite
...
[LOG] 0:01.158 INFO juju.provider.openstack started instance 2
... Panic: runtime error: invalid memory address or nil pointer dereference 
(PC=0x7FC0CCED367F)

This is at least partly because of a coding error in that test - the err
value is not nil checked before being used:

provider/openstack/local_test.go l1563-1565
_, _, _, err = testing.StartInstance(env, 1)
errString := strings.Replace(err.Error(), \n, , -1)
c.Assert(errString, gc.Matches, .*Some unknown error.*)

The test does not fail on ppc however.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393825

Title:
  Juju testsuite fails in random ways

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1393825/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1381671] Re: reboot tests fail to build on gccgo

[Martin Packman]

As this is blocking developers landing code, I am going ahead and
working around this by not building the problem test file. There is
almost certainly a ppc64/gccgo bug in need of fixing here.

** Also affects: gccgo-go (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: juju-core
   Status: Triaged = In Progress

** Changed in: juju-core
 Assignee: (unassigned) = Martin Packman (gz)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gccgo-go in Ubuntu.
https://bugs.launchpad.net/bugs/1381671

Title:
  reboot tests fail to build on gccgo

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1381671/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1381671] Re: reboot tests fail to build on gccgo

[Martin Packman]

** Changed in: juju-core
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gccgo-go in Ubuntu.
https://bugs.launchpad.net/bugs/1381671

Title:
  reboot tests fail to build on gccgo

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1381671/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1381671] Re: reboot tests fail to build on gccgo

[Martin Packman]

As this is blocking developers landing code, I am going ahead and
working around this by not building the problem test file. There is
almost certainly a ppc64/gccgo bug in need of fixing here.

** Also affects: gccgo-go (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: juju-core
   Status: Triaged = In Progress

** Changed in: juju-core
 Assignee: (unassigned) = Martin Packman (gz)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381671

Title:
  reboot tests fail to build on gccgo

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1381671/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1381671] Re: reboot tests fail to build on gccgo

[Martin Packman]

** 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/1381671

Title:
  reboot tests fail to build on gccgo

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1381671/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1381671] Re: reboot tests fail to build on gccgo

[Martin Packman]

** 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/1381671

Title:
  reboot tests fail to build on gccgo

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1381671/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1248283] Re: juju userdata should not restart networking

[Martin Packman]

** Changed in: juju-core
Milestone: 1.20.0 = 1.18.0

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1248283

Title:
  juju userdata should not restart networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1248283/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1248283] Re: juju userdata should not restart networking

[Martin Packman]

** Changed in: juju-core
Milestone: 1.20.0 = 1.18.0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248283

Title:
  juju userdata should not restart networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1248283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1268913] Re: Loading state on bootstrap ignores ssl-hostname-verification setting

[Martin Packman]

Now merged in Curtis, thanks.

** Changed in: juju-core
   Status: In Progress = Fix Committed

** Changed in: juju-core
Milestone: 1.18.0 = 1.17.4

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1268913

Title:
  Loading state on bootstrap ignores ssl-hostname-verification setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1268913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1261628] Re: remove-* aliases for destroy-service and destroy-machine

[Martin Packman]

** Changed in: juju-core
   Status: In Progress = Fix Committed

** Changed in: juju-core
Milestone: 1.18.0 = 1.17.4

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1261628

Title:
  remove-* aliases for destroy-service and destroy-machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1261628/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1268913] Re: Loading state on bootstrap ignores ssl-hostname-verification setting

[Martin Packman]

Now merged in Curtis, thanks.

** Changed in: juju-core
   Status: In Progress = Fix Committed

** Changed in: juju-core
Milestone: 1.18.0 = 1.17.4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268913

Title:
  Loading state on bootstrap ignores ssl-hostname-verification setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1268913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1261628] Re: remove-* aliases for destroy-service and destroy-machine

[Martin Packman]

** Changed in: juju-core
   Status: In Progress = Fix Committed

** Changed in: juju-core
Milestone: 1.18.0 = 1.17.4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261628

Title:
  remove-* aliases for destroy-service and destroy-machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1261628/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs