After installing kernel 3.15.1-031501-generic from kernel-ppa, both
machines work without issues from 2014-06-25. Seems it's kernel issue
that have already been solved upstream.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in
I can confirm that it's more kernel issue than qemu. I run kernel
3.11.0-24-generic which is left after upgrade from Saucy and have no
issues for at least two days. Before that with current 3.13.0-30-generic
kernel my Windows guests crashed every 3-4 hours.
--
You received this bug notification
** Branch linked: lp:ubuntu/utopic-proposed/libunwind
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1336912
Title:
linunwind unable to find some lzma_ symbols
To manage
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-14.06:
- [james-page] Update mongodb from 2.4-2.6: INPROGRESS
+ [james-page] Update mongodb from 2.4-2.6: DONE
[james-page] PXC update for 14.04: DONE
Work items for ubuntu-14.07:
[mattgriffin] address automated
** Branch linked: lp:ubuntu/utopic-proposed/mongodb
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1294455
Title:
mongodb-server leaks debug information during remove
To manage
** Branch linked: lp:ubuntu/utopic-proposed/mongodb
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1295723
Title:
libv8-dev backport breaks some dependencies
To manage
Simple patch to skip already bzip compressed logs in the cron job is
attached here.
** Patch added: skip already compressed logs
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1280654/+attachment/4144498/+files/maas_remote_syslog_compress.diff
--
You received this bug notification
The verification of the Stable Release Update for pacemaker has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package corosync - 1.4.2-2ubuntu0.2
---
corosync (1.4.2-2ubuntu0.2) precise; urgency=medium
* Fixed consensus being empty in case failed_to_recv is set (LP: #1318441)
-- Rafael David Tinoco rafael.tin...@canonical.com Mon, 12 May 2014
09:37:06 -0500
This bug was fixed in the package pacemaker - 1.1.6-2ubuntu3.3
---
pacemaker (1.1.6-2ubuntu3.3) precise; urgency=high
* Removed buggy logic that tried to prevent rare secondary dc fencing (LP:
#1312156)
-- Rafael David Tinoco rafael.tin...@canonical.com Fri, 02 May 2014
The verification of the Stable Release Update for corosync has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
Public bug reported:
kmod should permit use of compressed modules. This enables images that
boot from RAM to be much smaller. In essence this requires only changing
a build option. Uncompressed modules are still supported.
A patch is here:
gah this got filed under apache2 even though I said affects kmod. -
apologies all
** Package changed: apache2 (Ubuntu) = kmod (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
This bug was fixed in the package libunwind - 1.1-3ubuntu1
---
libunwind (1.1-3ubuntu1) utopic; urgency=medium
* Merge with Debian; remaining changes:
- Enable test suite for amd64 architecture:
+ d/rules: Execute test suite when building for amd64 only.
+
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
My 14.04 machine that runs Nginx with PHP-FPM received updates for PHP
and somehow Apache was automatically installed.
Please could you expand on this? How exactly did you receive updates?
Once you've
hello i have a similar problem. im booting fatclients (ltsp). after
configuring the ldap client (installing libnss ldap) and adding the
paramater ldap to nsswitch.conf, the fatclient doesnt boot! if i
removeing ldap all works fine, but this is no solution for me!
by the way, the same
** Changed in: pacemaker (Ubuntu Precise)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1312156
Title:
[Precise]
** Changed in: corosync (Ubuntu Precise)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1318441
Title:
Precise corosync
The attachment skip already compressed logs seems to be a patch. If
it isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
I ran apt-get update and apt-get dist-upgrade on the machine, the apt
history excerpt shows that new packages that got installed during this
event. php5-fpm is from the repositories and nginx-extras from
https://launchpad.net/~nginx/+archive/development.
** Changed in: php5 (Ubuntu)
Verified with included testcase in an lxc container, and edited a node's
power type with the cluster controller (in a separate container)
offline.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Verified fix with given testcase, install completes successfully with no
errors.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Associated a maas endpoint with two different cluster controllers, the
new version synced known images much faster.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Tried to change architecture without appropriate images installed, got
error without python list/string cruft.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas
new backdooring code works correctly if the user enters the backdoor-
image directory before running suggested code.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Thanks, that's great to know!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
To manage notifications about this bug go to:
Verified in maas lab with tests as shown by Diogo, also ran the two
integration tests manually, and both passed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Verified fix by running command in container, given noted testcase
above; passed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
The bug affects me though the fix for glance is already in my source !
ubuntu@ubuntu-ThinkCentre-M92p:~$ glance --version
0.12.0.79
The above workaround by Lee Thompsonhelped me to solve it !
I will investigate further on this. Please correct me if my
understanding is incorrect (Devstack: All
Hi Chris,
Testing of 2014.1.1 from the trusty-proposed repository has completed
successfully.
Thanks,
Corey
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova
The changes are in 3.15, so Utopic/development branch should be fixed
already.
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
This bug was fixed in the package maas - 1.5.2+bzr2282-0ubuntu0.2
---
maas (1.5.2+bzr2282-0ubuntu0.2) trusty-proposed; urgency=medium
* debian/control:
- Add missing dependency in maas-cluster-controller for grub-common
(LP: #1328231)
- Move dependency from
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
** Changed in: juju-quickstart (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1329049
Title:
quickstart fails, hardcodes
Here is an updated patch with some changes from the original. Sponsoring
this.
** Patch added: net-tools_1.60-25ubuntu2.1.debdiff
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1251563/+attachment/4144813/+files/net-tools_1.60-25ubuntu2.1.debdiff
--
You received this bug
We should not use a static file for this, that's why we have python-
distro-info. We should use it to automatically figure out the supported
Ubuntu releases.
in 1.5.: Support for trusty should be added manually and SRU'd.
In 1.6., we should switch to use python-distro-info.
This additionally
The merge report is here:
https://merges.ubuntu.com/s/strongswan/REPORT
$ grep-merges strongswan
strongswan Marc Deslauriers marc.deslauri...@ubuntu.com
I would sync with Marc, see if you can help with the merge.
--
You received this bug notification because you are a member of Ubuntu
** Patch added: Patch to fix future and broken instances
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1336855/+attachment/4144896/+files/precise.deb.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in
Worked out a postinst script that 1) detects if the root device and the
grub-pc install device is mismatched; 2) if so, re-sets the grub-pc
device and then installs grub to the device in question. The changes
should be safe, but I want a through to be safe.
** Branch linked:
Public bug reported:
Hi,
I'd like to monitor my running processes on my server with snmp. Snmp offers
this feature but when you have process running like: perl /usr/sbin/mysql-snmp
--daemon-pid /var/run/mysql-snmp.pid -c /etc/mysql-snmp/my.cnf the process
name detected by snmp is perl...
Debian has 5.1.3-4, so shouldn't this be a merge instead of an
-0ubuntu1?
The Debian and Ubuntu packages have significant difference between them.
They came about as I revamped the Ubuntu packaging and then the Debian
guys decided to do something else with regards to plugin management and
they
HP was able to figure out the issue. IPMItool is required to be
installed on the cluster controller in order for the moonshot nodes to
be powered on. Please add that to the documentation thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1336855
Title:
[SRU] non-interactive grub updates for 12.04 break on AWS
To manage notifications about this
** Patch added: Modified patch that is chroot safe
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1336855/+attachment/4144962/+files/precise.deb.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
I have reviewed the patch (lp:~utlemming/ubuntu/precise/cloud-
init/lp1336855 through r211) and tested it on EC2 and an OpenStack cloud
and it performed well. The upgrade of cloud-init forced a grub-install
and it ran with the correct root device.
--
You received this bug notification because
That should have been with the correct *boot* device
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1336855
Title:
[SRU] non-interactive grub updates for 12.04 break on AWS
To
I was able to workaround the issue by modifying /etc/default/grub and
issuing update-grub ( post apt-get upgrade ). I assume it has something
to do with the console settings?
- bad grub -
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full
This patch to the preseed should fix it
=== modified file 'contrib/preseeds_v2/generic'
--- contrib/preseeds_v2/generic 2014-04-14 22:40:43 +
+++ contrib/preseeds_v2/generic 2014-07-04 00:21:11 +
@@ -2,7 +2,7 @@
{{def proxy}}
d-i mirror/country string manual
-{{if
That diff is bogus, it won't apply to trunk as the enum was moved.
Also, we should *not* be using python-distro-info please; the list of
OSes and releases is driven by images imported on the clusters and thus
ultimately the simplestreams data for available images.
There's another bug somewhere
** Changed in: maas
Status: Confirmed = Triaged
--
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/1337437
Title:
maas needs utopic support
To manage notifications about this bug
78 matches
Mail list logo
