Confirmed with Drew that this bug has not been hit since the pacemaker
fix released.
Can remove field-high team, but keep for the discussion on init-system-
helpers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes it obviously works for login shells.
To make it work for non-login shells /etc/environment would need to
include /snap/bin -- an issue for foundations to decide upon.
Thanks for the insight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Still hitting this with...
jenkins@juju-6f7422-solutions-qa-integration-1:~$ snap version
snap2.27.6
snapd 2.27.6
series 16
ubuntu 16.04
kernel 4.4.0-83-generic
jenkins@juju-6f7422-solutions-qa-integration-1:~$ snap list
Name VersionRev DeveloperNotes
conjure-up 2.3.1
*** This bug is a duplicate of bug 1594904 ***
https://bugs.launchpad.net/bugs/1594904
** This bug has been marked a duplicate of bug 1594904
Snaps fail to run when user's home directory is not under /home
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Good find cxreg!
Indeed does look the same, happens when I am running chromium, cxreg
found bug happens in Chrome. So some path with the i915 there does
appear to be flaky.
Workaround seems to not be super effective given post
https://bugs.freedesktop.org/show_bug.cgi?id=99295#c27 unfortunately.
Public bug reported:
Sometimes upon boot mouse is not responsive. I get spammed the following in
syslog every time I move the pointer:
elan_i2c i2c-ELAN1000:00: invalid report id data (1)
workaround:
sudo rmmod elan_i2c
sudo modprobe elan_i2c
fixes it until next reboot, then it is a crapshoot
And in some cases squashfuse may not have the proper dep of fuse. And
you may need to manually:
apt install fuse # in addition to squashfuse
looks like squashfuse is missing a dependency on "fuse"
which is part of the official Ubuntu images but not in the community
images
so if you use "lxc
Hitting this with zesty
Linux doe 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER:
Only time I have been able to cause it was high load with lxcs and
graphics load (via unity). The mainline does not seem to let my lxd
instance load.
Unfortunately my lxd setup does not work with the mainline, [due to
snaps/lxd/zfs, one of the above probably](so it will make repro much
harder,
Speak of the devil... happened again on, will try with upstream kernel.
Linux doe 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
** Attachment added: "kern.log"
Unable to reproduce unfortunately. In fact it has not reoccurred, since
I filed this bug. Will reopen if it happens again, but I am moving to
the more recent released kernel... 4.10.0-15 -> 4.10.0-19.
Not sure what status to mark this bug as until I can get a repro of it.
--
You received this
Public bug reported:
Upgraded to zesty about a week ago. Ran into this on latest kernel.
(during high load, nothing in particular seems to cause it to happen).
Did not happen with previous (4.10.0.14.16) kernel. Only after update to
4.10.0.15.17, has happened about 3 times since then (or other
Thanks for the well thought out explanation.
I would proffer and alternative until either #1 or #2 can be decided
upon.
Refresh for all snaps that stay in the same confinement mode. I.e. one
--devmode snap to a more recent --devmode snap, which currently does not
happen.
I agree that upgrades
Thanks for quick reply. Documentation is ambiguous on this point and
therefore confused me.
Filed a bug @ https://github.com/ubuntudesign/snapcraft.io/issues/281
Appreciate the awesomeness that is snap*!
** Bug watch added: github.com/ubuntudesign/snapcraft.io/issues #281
Public bug reported:
So yesterday I installed the juju snap...
$ sudo snap install juju --edge --devmode
then today... https://paste.ubuntu.com/24002666/
Does snap refresh just not work on devmode snaps, what is going on here?
And why are they not auto-downloaded.
lutostag@cia:~$ snap
Steps:
1) Proceed with normal rpi2 install with working dongle (and verified bad
dongle still saw problem).
2) Enabled user-password login.
3) Was on core rev 396, changed to edge (645).
4) Plug in bad dongle
5) reboot
6) login locally
7) sudo console-conf
Confirmed there is no crash (could not
Sorry, seems you are on latest, there is just a regression in the
upstream...
** Changed in: debhelper (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639031
Public bug reported:
When building a package for a ppa I ran into an issue where I expected
the functionality from https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=438601, fixed upstream in 2011.
The dh_link I was hoping for is the same version from
Public bug reported:
We should sync from 1.8.3 version
https://packages.debian.org/search?keywords=pepperflashplugin%2Dnonfree
which works for me.
** Affects: pepperflashplugin-nonfree (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621336
Title:
snapd.boot-ok.service hangs eternally on cloud image upgrades
To manage notifications about this bug go to:
Public bug reported:
Ran into this with deploying a juju charm to a local lxd controller.
Recreates with:
https://paste.ubuntu.com/23147333/
Related bugs:
* bug 1576692: fully support package installation in systemd
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
Showed up when I tested with Wily, which I know did not previously have
the issue. Will consider it a hardware fault. Sorry for the
inconvenience.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu)
Importance: High => Undecided
--
You received
Setting governor to performance did not help. Problem also evident with
Xenial installation media (kernel 4.4.0.21 I believe). Going to try with
Wily installation media to ensure it is not there and it is not a newly
found hardware issue (like if I bumped my laptop touchpad cable loose).
--
You
Also looking at https://lists.launchpad.net/kernel-
packages/msg17719.html, my governor is set to powersave. And I can
confirm that scaling is actively happening in the background when I see
this issue of the sync bytes lost (well at least /proc/cpuinfo shows
different MHz before and after I see
Nope, just in xenial. Did not happen in wily.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
Title:
mouse lost sync
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673685/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673677/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673684/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673681/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673675/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673678/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673683/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673682/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673680/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673674/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673679/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673676/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673671/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
Title:
mouse
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673673/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673672/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1587594/+attachment/4673670/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587594
Public bug reported:
Running xenial.
Relevant details from dmesg:
[ 2458.075708] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at
byte 1
[ 2458.085063] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at
byte 1
[ 2458.086384] psmouse serio1: TouchPad at
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580279
Title:
maas-cli 2.0 doesn't find 1.0 api
To manage notifications about this bug go to:
Public bug reported:
Build for IBM z-series (s390x) is broken as shown by
https://bugs.launchpad.net/ubuntu/+source/quassel/0.12.2-0ubuntu1/+build/8381039
that should be removed from the list of arch supported by the quassel
package until the build can be fixed for it.
I'll see if I can get a
Public bug reported:
So similarly to bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579917, I am also
not able to get into pc10, as described there.
I am using a sata drive, and after setting min_power to
/sys/class/scsi_host/*/link_power_management_policy still does not get
me into
Public bug reported:
Seeing a number of failed deployments on the SM15K:
This is from console log for a failed deployment this morning:
[ 3310.700695] Call Trace:^M
[ 3310.700698] [81057180] ? try_to_free_pmd_page+0x50/0x50^M
[ 3310.700700] [8105709fff^M
[ 3310.700707]
** Attachment added: Full conserver log from one of the affected machines.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444003/+attachment/4375352/+files/hayward-45-deployment-failure-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1382632
Title:
Insecure key file permissions
To manage notifications about this bug go to:
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382632
Title:
Insecure key file permissions
To manage notifications about this bug go to:
Public bug reported:
openstack-dashboard 2014.2-0ubuntu1~cloud0 from cloud:trusty-
updates/juno fails install (exit status 1)
full stack trace:
2014-10-27 20:40:42 INFO install Setting up openstack-dashboard
(1:2014.2-0ubuntu1~cloud0) ...
2014-10-27 20:40:43 INFO install Adding system user
Looks like it installed fine on a clean trusty lxc with cloud:trusty-
updates/juno -- so moving it this bug to the charm.
** Package changed: horizon (Ubuntu) = openstack-dashboard (Juju Charms
Collection)
** Summary changed:
- openstack-dashboard 2014.2-0ubuntu1~cloud0 from
Public bug reported:
openstack-dashboard 2014.2-0ubuntu1~cloud0 from cloud:trusty-
updates/juno fails install (exit status 1)
full stack trace:
2014-10-27 20:40:42 INFO install Setting up openstack-dashboard
(1:2014.2-0ubuntu1~cloud0) ...
2014-10-27 20:40:43 INFO install Adding system user
Looks like it installed fine on a clean trusty lxc with cloud:trusty-
updates/juno -- so moving it this bug to the charm.
** Package changed: horizon (Ubuntu) = openstack-dashboard (Juju Charms
Collection)
** Summary changed:
- openstack-dashboard 2014.2-0ubuntu1~cloud0 from
Blueprint changed by Greg Lutostanski:
Work items changed:
Work items:
- SRU version 1.5.4 of MAAS into Trusty: INPROGRESS
- MIR amtterm: TODO
- Add maas-samba as optional dep: TODO
+ SRU version 1.5.4 of MAAS into Trusty: DONE
+ Remove celery deps from 1.7 in Utopic: DONE
Testing for maas
** Description changed:
- enlist the chassis with Glenn m700 cartridges of moonshot with 1.5.4
- MAAS in proposed using the command below sudo maas admin node-group
- probe-and-enlist-mscm 24b0fe1a-1e59-47d6-b446-d0711ee0c81c
- host=172.16.1.102 username=Administrator password=password
+ [Impact]
** Description changed:
- enlist the chassis with Glenn m700 cartridges of moonshot with 1.5.4
- MAAS in proposed using the command below sudo maas admin node-group
- probe-and-enlist-mscm 24b0fe1a-1e59-47d6-b446-d0711ee0c81c
- host=172.16.1.102 username=Administrator password=password
+ [Impact]
** Description changed:
- No support for armhf/keystone architecture for ProLiant m800 Server
- Cartridges from HP.
+ [Impact]
+ * Add hardware enablement for armhf/keystone.
+
+ [Testcase]
+ * Enlist/Commission armhf/keystone hardware and make sure install proceeds
correctly.
+
+
** Description changed:
- No support for armhf/keystone architecture for ProLiant m800 Server
- Cartridges from HP.
+ [Impact]
+ * Add hardware enablement for armhf/keystone.
+
+ [Testcase]
+ * Enlist/Commission armhf/keystone hardware and make sure install proceeds
correctly.
+
+
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu)
Importance: Undecided = High
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1315154
Title:
[SRU] doesn't support booting ppc64el
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Medium
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
--
You received this bug notification because you
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Low
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: Fix Released = 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/1315154
Title:
[SRU] doesn't support booting ppc64el hardware
To
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Medium
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
--
You received this bug notification because you
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Low
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Summary changed:
- doesn't support booting ppc64el hardware
+ [SRU] doesn't support booting ppc64el hardware
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1315154
Title:
[SRU]
** Description changed:
+ [Impact]
+ * Previously Django's aggressive connection closing policy would prevent
session-level locks from being maintained.
+
+ [Testcase]
+ * Run included tests
+
+ [Regression Potential]
+ * Minimal, potentially an issue as it deals with releasing a lock (it
** Description changed:
+ [Impact]
+ * When using new locking code, this is used to prevent an error on maas
server startup when asking for a lock when not in a transaction
+
+ [Testcase]
+ * Run included tests in test_start_up.py
+
+ [Regression Potential]
+ * Minimal
+
mod_wsgi
** Summary changed:
- Missing dependency on python-paramiko
+ [SRU] Missing dependency on python-paramiko
** Description changed:
- As seen here: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-
- maas/131/console, maas package can't be installed on utopic due to a
- missing dependency
** Summary changed:
- ImportError: No module named pexpect when setting up maas-region-controller
+ [SRU] ImportError: No module named pexpect when setting up
maas-region-controller
** Description changed:
+ [Impact]
+ * Install required deps for maas-provisioningserver (move from
** Summary changed:
- doesn't support booting ppc64el hardware
+ [SRU] doesn't support booting ppc64el hardware
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315154
Title:
[SRU] doesn't support
** Description changed:
+ [Impact]
+ * Previously Django's aggressive connection closing policy would prevent
session-level locks from being maintained.
+
+ [Testcase]
+ * Run included tests
+
+ [Regression Potential]
+ * Minimal, potentially an issue as it deals with releasing a lock (it
** Description changed:
+ [Impact]
+ * When using new locking code, this is used to prevent an error on maas
server startup when asking for a lock when not in a transaction
+
+ [Testcase]
+ * Run included tests in test_start_up.py
+
+ [Regression Potential]
+ * Minimal
+
mod_wsgi
** Summary changed:
- Missing dependency on python-paramiko
+ [SRU] Missing dependency on python-paramiko
** Description changed:
- As seen here: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-
- maas/131/console, maas package can't be installed on utopic due to a
- missing dependency
** Summary changed:
- ImportError: No module named pexpect when setting up maas-region-controller
+ [SRU] ImportError: No module named pexpect when setting up
maas-region-controller
** Description changed:
+ [Impact]
+ * Install required deps for maas-provisioningserver (move from
** Description changed:
+
+ SRU for secondary fix (branch lp:~julian-edwards/maas/nonce-fix-bug-1190986)
+ [Impact]
+ * Minimize possibility of hitting a nonce collision by using a longer nonce
(uuid4) in both python-maas-client and commissioning scripts.
+
+ [Testcase]
+ * Do some api calls
** Description changed:
- It looks like maas needs support added for utopic. Could you also
- consider implementing this so that it is configurable in a config file?
- It would be much better than needing a hard-coded update each release.
+ [Impact]
+ * Remove no longer supported distro
** Description changed:
+
+ SRU for secondary fix (branch lp:~julian-edwards/maas/nonce-fix-bug-1190986)
+ [Impact]
+ * Minimize possibility of hitting a nonce collision by using a longer nonce
(uuid4) in both python-maas-client and commissioning scripts.
+
+ [Testcase]
+ * Do some api calls
** Description changed:
- It looks like maas needs support added for utopic. Could you also
- consider implementing this so that it is configurable in a config file?
- It would be much better than needing a hard-coded update each release.
+ [Impact]
+ * Remove no longer supported distro
Since it was hit while running juju I'm inclined to believe that it is
because
http://bazaar.launchpad.net/~juju/gomaasapi/trunk/view/head:/oauth.go is
still using the old nonce generation method ([0-9]{8} rather than uuid)
which is much more collision prone.
--
You received this bug
Since it was hit while running juju I'm inclined to believe that it is
because
http://bazaar.launchpad.net/~juju/gomaasapi/trunk/view/head:/oauth.go is
still using the old nonce generation method ([0-9]{8} rather than uuid)
which is much more collision prone.
--
You received this bug
1 - 100 of 170 matches
Mail list logo
