Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-14.05:
[gnuoy] charm-helpers unit testing: DONE
Work items for ubuntu-14.06:
[mikemc] Simplestreams image sync charm: DONE
[niedbalski] swift-storage block device persistence through reboots: DONE
[gnuoy]
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-14.05:
[gnuoy] charm-helpers unit testing: DONE
Work items for ubuntu-14.06:
[mikemc] Simplestreams image sync charm: DONE
[niedbalski] swift-storage block device persistence through reboots: DONE
[gnuoy]
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-14.05:
[gnuoy] charm-helpers unit testing: DONE
Work items for ubuntu-14.06:
[mikemc] Simplestreams image sync charm: DONE
[niedbalski] swift-storage block device persistence through reboots: DONE
[gnuoy]
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-14.06:
get dependency gap list for calamari: DONE
resolve dependency gap for calamari: TODO
Work items for ubuntu-14.07:
Update to latest stable release of Ceph: DONE
- Package calamari and required
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-14.06:
get dependency gap list for calamari: DONE
resolve dependency gap for calamari: TODO
Work items for ubuntu-14.07:
- Update to latest stable release of Ceph: TODO
+ Update to latest stable release of Ceph:
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-14.06:
get dependency gap list for calamari: DONE
- resolve dependency gap for calamari: TODO
Work items for ubuntu-14.07:
Update to latest stable release of Ceph: DONE
[sage] Ensure kernel fixes are getting
Marking the development task as won't fix as compat mode for 8.3 is not
needed from Trusty user-space onwards. And a Trusty LTS kernel works
with the current Precise user-space.
** Changed in: drbd8 (Ubuntu)
Status: Triaged = Won't Fix
** Changed in: drbd8 (Ubuntu)
Assignee: Stefan
Override component to main
python-oslo.i18n 0.1.0-1ubuntu2 in utopic amd64: universe/python/optional/100%
- main
python-oslo.i18n 0.1.0-1ubuntu2 in utopic arm64: universe/python/optional/100%
- main
python-oslo.i18n 0.1.0-1ubuntu2 in utopic armhf: universe/python/optional/100%
- main
Yes, I saw the same restarting of Mongo, looks like every 10-15 seconds.
--
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/1318366
Title:
jujud on state server panic misses
Attached is a dump of the Juju database in this case.
** Attachment added: dump.tgz
https://bugs.launchpad.net/juju-core/+bug/1318366/+attachment/4164924/+files/dump.tgz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in
Hi Nooope, I had to restart the computer and I think I don't have it. It
didn't hapened for a while.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1336555
Title:
ovs-vswitchd
You must put libraries after the objects that need them. See:
https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries
So you probably want: gcc -O2 -Wuninitialized -Wall -D_FORTIFY_SOURCE=2
-Wformat -Wno-multichar -Wreturn-type -Wswitch -Wunused-variable -g
-pthread -o
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please state exact steps required to reproduce the bug on a fresh
system. This includes exactly what steps you followed (eg. command
lines) to uninstall, reinstall, add my user name to samba, read one
of my
** Tags added: regression-release trusty
** Changed in: irqbalance (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1348157
Title:
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
Specifically, you appear to have a modified /usr/sbin/sshd on your
system.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we
** Changed in: maas (Ubuntu)
Status: New = 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/1250435
Title:
CNAME record leaks into juju's private-address, breaks host
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The a2ensite command derives from Debian, so any changes to its
behaviour should probably be made there in the first instance.
Next steps: check if Debian is affected. If it is, then a bug should be
filed against
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I see a libpcre3-dev package - no pcre-devel. Is this what you are
referring to?
This change should be considered for Debian in the first instance,
rather than as a delta in Ubuntu specifically.
Next steps:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
3.5.0 is currently packaged (3.5.0-1 in Utopic). Presumably this bug is
fixed in Utopic, so I'm marking this bug as Fix Released.
If you need a fix for 14.04 Trusty Tahr (currently on 3.2.2-4ubuntu5),
please
This bug was fixed in the package qemu - 2.0.0+dfsg-6ubuntu2
---
qemu (2.0.0+dfsg-6ubuntu2) utopic; urgency=medium
* d/qemu-system-x86.qemu-kvm.upstart: change the early-exit check from
/usr/bin/kvm to qemu-system-x86_64. (LP: #1348551)
-- Serge Hallyn serge.hal...@ubuntu.com
Public bug reported:
Deploying juju using MAAS on a Power8 system (ppc64el) reports a
architecture miss match, saying ppc64 is not a valid architecture. The
architecture for MAAS should be ppc64el, as that is the architecture for
Ubuntu.
The archive naming is:
This bug was fixed in the package exim4 - 4.82.1-2ubuntu1
---
exim4 (4.82.1-2ubuntu1) utopic; urgency=low
* Merge from Debian unstable (LP: #1348074). Remaining changes:
- Show Ubuntu distribution on smtp:
+ debian/patches/fix_smtp_banner.patch: updated SMTP banner
Who will be your team subscriber? If this is to be ~ubuntu-server, have
you cleared it with them? I have seen no mention.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1267255
Title:
** Summary changed:
- Nut 2.7.2 has been released and has a new NUTDRV_ATCL_USB driver.
+ Please merge nut 2.7.2-1 (main) from Debian unstable (main)
** Changed in: nut (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: nut (Ubuntu)
Status: New = Triaged
** Tags added:
After some experiments in compression options, here are all the Juju
logs you could ever want :)
http://people.canonical.com/~mark/juju-server-crash-logs.tar.xz
68M compressed, about 1.9G uncompressed. That's /var/log/juju/ from
machine 0.
--
You received this bug notification because you are
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-14.05:
[gnuoy] charm-helpers unit testing: DONE
Work items for ubuntu-14.06:
[mikemc] Simplestreams image sync charm: DONE
[niedbalski] swift-storage block device persistence through reboots: DONE
[gnuoy]
Thanks, that fixed it. But I don't see why Debian systems are order
sensitive and Redhat systems aren't.
Josh
On 07/29/2014 05:44 AM, Robie Basak wrote:
You must put libraries after the objects that need them. See:
https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries
There's a Horizon patch up for changing the host name horizon is using
(see bug 1335999 / https://review.openstack.org/#/c/103672/ ) though
it's unclear to me if this will help with resolving this as well?
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This bug was fixed in the package keystone - 1:2014.2~b2-0ubuntu1
---
keystone (1:2014.2~b2-0ubuntu1) utopic; urgency=medium
[ Chuck Short ]
* New upstream version.
* debian/patches/fix-ubuntu-tests.patch: Refreshed.
* debian/patches/sql_connection.patch: Refreshed
*
Public bug reported:
As seen here: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-
maas/280, patch 02-pserv-config.patch failed to apply while building the
package.
adt-run1: testbed command ['sh', '-ec', su -s /bin/sh ubuntu -c 'exec 31
2\nset -x\ncd
** Description changed:
As seen here: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-
maas/280, patch 02-pserv-config.patch failed to apply while building the
package.
adt-run1: testbed command ['sh', '-ec', su -s /bin/sh ubuntu -c 'exec 31
2\nset -x\ncd
And the db dump (732k) of the juju db in mongo on mark's state server is at
http://chinstrap.canonical.com/~kapil/bug-13183656-juju-db.dump.tbz2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Some discussion with upstream nginx here: https://github.com/openresty
/lua-nginx-module/issues/343
If as you said there are quite a few people already using ngx_lua + lua
5.1, then linking against Lua 5.2 will probably break these people's
existing Lua code. Lua 5.2 is essentially an
Probably because redhat has an older version of gcc.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1348945
Title:
-lsensors doesn't link to libsensors
To manage notifications
Override component to main
ieee-data 20140613.1 in utopic amd64: universe/net/optional/100% - main
ieee-data 20140613.1 in utopic arm64: universe/net/optional/100% - main
ieee-data 20140613.1 in utopic armhf: universe/net/optional/100% - main
ieee-data 20140613.1 in utopic i386:
That's at the very least:
- pool/universe/t/transaction/python-transaction_1.1.1-2_all.deb
- pool/universe/t/turbogears2/python-turbogears2_2.1.5-2_all.deb
** Changed in: python-wsme (Ubuntu)
Importance: Wishlist = High
** Changed in: python-wsme (Ubuntu)
Status: Fix Released =
Broken by an upstream change.
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New = Invalid
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = Critical
** Changed in: maas
Assignee:
** Tags added: ppc64el
--
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/1349771
Title:
ppc64 architecture miss match for MAAS ppc64el
To manage notifications about this bug go to:
Juju uses golang's naming conventions. Juju *should* map ppc64el to
ppc64. Which version of Juju are you using?
This was a bug in Juju 1.18.x. where the wrong architecture was selected
for some cloud providers. I closed the bug when manual-provider and
local-kvm tests passed.
Since this issue
This was caused by an accidental removal of a trailing newline in
lp:maas r2607. It has been fixed in r2613.
** Changed in: maas
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Branch linked: lp:cloud-init
--
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/1341710
Title:
Comment placed inside of /etc/timezone
To manage notifications about this bug go
to recreate, you can either:
a.) launch instance with cloud-config specifying:
timezone: US/Eastern
b.) inside an instance run:
sudo cloud-init single --frequency=always --name=cc_timezone US/Eastern
Either way, you'll end up with something like:
$ cat /etc/timezone
# Created by
fix-committed in revno 988.
** Changed in: cloud-init
Status: Confirmed = Fix Committed
** Changed in: cloud-init (Ubuntu)
Importance: Medium = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
I've moved this to low because I looked back, and realized this has been
busted in 0.7.X (meaning everything after 12.04), so it wouldn't seem to
be high impact.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Public bug reported:
I tried the workaround from https://bugs.launchpad.net/ubuntu/+source
/juju-core/+bug/1317680, but that did not solve the issue.
The steps I am performing to get here are:
juju bootstrap
uvt-simplestreams-libvirt purge
uvt-simplestreams-libvirt sync release=trusty arch=arm64
** Attachment added: environments yaml
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1349854/+attachment/4165128/+files/environments.yaml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Attachment added: all machines log
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1349854/+attachment/4165126/+files/all-machines.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Attachment added: local jenv
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1349854/+attachment/4165129/+files/local.jenv
** Description changed:
I tried the workaround from https://bugs.launchpad.net/ubuntu/+source
/juju-core/+bug/1317680, but that did not solve the issue.
** Attachment added: cloud init log
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1349854/+attachment/4165127/+files/cloud-init-output.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Attachment added: machine 0 log
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1349854/+attachment/4165125/+files/machine-0.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Public bug reported:
As seen here: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-
maas/284, maas-common package fails with the following error:
Setting up maas-common (1.6+bzr2367+2613+288-0ubuntu3) ...
ln: failed to create symbolic link '/etc/rsyslog/99-maas.conf'Setting up
Public bug reported:
The pwgen man page states:
-B, --ambiguous
Don't use characters that could be confused by the user when
printed, such as 'l' and
'1', or '0' or 'O'. This reduces the number of possible
passwords significantly, and as
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pwgen (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pwgen in Ubuntu.
No Fedora has a later version of gcc,
/home/bjrosen gcc --version
gcc (GCC) 4.8.3 20140624 (Red Hat 4.8.3-1)
gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
RHEL 6.5 has an older version
gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4)
There is no order sensitivity in Fedora 20 or RHEL (I use the Scientific
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Was able to reproduce this issue with the newer version of juju found
here: http://juju-ci.vapour.ws:8080/job/publish-revision/711/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Using the tools from here: https://juju-dist.s3.amazonaws.com/rc-
testing/tools
--
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/1349854
Title:
kvm container creation failed: exit
Hello James, or anyone else affected,
Accepted ceph into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/ceph/0.80.4-0ubuntu0.14.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hi Scott,
Thanks for applying this fix. I really appreciate it.
In case someone arrives here from a google search who has an issue with
openjdk selecting an incorrect default timezone, you can work around the
issue by specifying the correct default timezone on the command line
string like so:
Hello Dustin, or anyone else affected,
Accepted byobu into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/byobu/5.77-0ubuntu1.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Kent, or anyone else affected,
Accepted ipmitool into trusty-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/ipmitool/1.8.13-1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- Description of problem
- ---
+ [Impact]
+
+ * cpu features list which is being sent to libvirt,
+ when creating a domain or calling compareCPU, must contain only
+ unique entries. Multiple issues arise when we are updating the
+ features
Hello Anders, or anyone else affected,
Accepted byobu into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/byobu/5.77-0ubuntu1.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
- * [2cebfd2] libvirt: convert cpu features attribute from list to
- a set (LP: #1267191)
-
- cpu features list which is being sent to libvirt,
- when creating a domain or calling compareCPU, must contain only
- unique entries.
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Diogo Matsubara (matsubara)
** Changed in: maas (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Hi,
your .JPG shows that there is a login prompt. The plymouth messages
should be harmless. Do you have any actual problems with the container,
i.e. cannot login or console is locked up?
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because
Hello James, or anyone else affected,
Accepted qemu into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/trusty-proposed/ipmitool
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1343407
Title:
Add support for Dell PowerEdge 13G servers
To manage
** Changed in: lxc (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1307829
Title:
/run/netns/* gets umounted on the host when a
** Changed in: lxc (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1299944
Title:
lxc-container-default-with-nesting is too lax
To manage
** Branch linked: lp:ubuntu/trusty-proposed/ceph
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1346166
Title:
[SRU] 0.80.4 point release
To manage notifications about this bug go
** Description changed:
[Impact]
* cpu features list which is being sent to libvirt,
when creating a domain or calling compareCPU, must contain only
unique entries. Multiple issues arise when we are updating the
features attribute in LibvirtConfigCPU class (for example during
** Changed in: nova (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1267191
Title:
openstack-nova-compute service fails with - libvirtError:
** Description changed:
[Impact]
* The original fix for bug 1219658 introduced a factor of 1024 error
in the resulting rbd image size. Big impact.
[Test Case]
- * To be provided.
+ * To have icehouse openstack using rbd image backend for libvirt:
+
+ Images seem to be 1024
** Changed in: nova (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1219658
Title:
Wrong image size using rbd backend for libvirt
To
Hello Kashyap, or anyone else affected,
Accepted nova into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/nova/1:2014.1.1-0ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Haomai, or anyone else affected,
Accepted nova into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/nova/1:2014.1.1-0ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
qemu ppc fails to execute even a simple hello world app.
jruble@jruble-linux:~/ppc_qemu_test$ cat test.c
#include stdio.h
int main(){
printf(asdf\n);
return 0;
}
jruble@jruble-linux:~/ppc_qemu_test$ powerpc-linux-gnu-gcc --version
powerpc-linux-gnu-gcc (Ubuntu
Marking this wont-fix. cloud-init no longer uses boto, and there wasnt
really enough info here to do anything.
** Changed in: python-boto (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Hi Robie,
this is a ubuntu specific bug because ipv6 support is added by
backuppc_3.3.0-1ubuntu1.diff.gz
Unless ping6-variable is defined hosts which have an ipv4 and ipv6 dns record
will fail!
See LP #782890
Best,
Alex
--
You received this bug notification because you are a member of
@Julie Thanks for linking the Horizon bug and review. That one will
solve the problem of live migrate not working at all through Horizon,
and it's anyway preferred to provide service host name. It won't however
change the fact that we can't use hypervisor_hostname as a migration
target argument.
This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.2
---
libvirt (1.2.2-0ubuntu13.1.2) trusty; urgency=low
* debian/apparmor/usr.sbin.libvirtd: allow libvirtd to run
libxl-save-helper (required for save restore through libxl).
(LP: #1334195)
*
This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.2
---
libvirt (1.2.2-0ubuntu13.1.2) trusty; urgency=low
* debian/apparmor/usr.sbin.libvirtd: allow libvirtd to run
libxl-save-helper (required for save restore through libxl).
(LP: #1334195)
*
This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.2
---
libvirt (1.2.2-0ubuntu13.1.2) trusty; urgency=low
* debian/apparmor/usr.sbin.libvirtd: allow libvirtd to run
libxl-save-helper (required for save restore through libxl).
(LP: #1334195)
*
i had the same problem with icehouse on ubuntu 14.04 LTS and fixed it with the
following change in
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py
at line 4338 ff i removed
for f in info['features']:
cpu.add_feature(vconfig.LibvirtConfigCPUFeature(f))
and
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1297218
Title:
guest hangs after live migration due to tsc jump
To
What this tested on the MAAS provider? As a customer is seeing this
issue with MAAS and Power8 hardware.
The version was newer than 1.18, I will have to check with the customer
to get the exact version.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Thanks. I see IPv6 references in the diff between 3.3.0-1 and
3.3.0-1ubuntu1, but these don't seem to be mentioned in the changelog.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to backuppc in Ubuntu.
Does installing the qemu-slof package solve the problem?
status: incomplete
** Changed in: qemu (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Tested on Dell Hardware, paying particular attention to existing 12G
systems so that nothing 'broke' with the update. Looking good.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: python-boto (Ubuntu)
Status: Confirmed = Invalid
--
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/525675
Title:
20100222 images fail to boot in UEC (HTTP
Here is a snippet of syslog showing two cycles of Mongo starts and
restarts. This is happening constantly!
Gustavo and I are wondering whether the numactl advice might be
relevant.
** Attachment added: syslog.mongorestarts.log
** Changed in: python-boto (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to euca2ools in Ubuntu.
https://bugs.launchpad.net/bugs/495618
Title:
euca-describe-image-attribute does not show
--- Comment From fno...@us.ibm.com 2014-07-29 17:16 EDT---
One of the dup'd bugs mentions:
--
This is an regression issue which we had even for Ubuntu 14.04, later got fixed
when the working virtio-scsi driver was provided..
Looks like 14.10 is broken again.
-
This is odd.
$ https_proxy=http://bogus:/ http_proxy=http://bogus:/ euca-
describe-images
that seems to work fine.
it seems that euca-describe-images completely ignores http_proxy and
https_proxy.
$ dpkg-query --show euca2ools
euca2ools 3.0.2-1ubuntu1
** Changed in: python-boto
On 29 July 2014 20:12, Mark Shuttleworth 1318...@bugs.launchpad.net
wrote:
Gustavo and I are wondering whether the numactl advice might be
relevant.
I humbly suggest that's a red herring. Note this happened on an Orange Box
(see log attached in
Hi Robie,
I can't comment on that. All I did was follow the process for filing the
MIR bug; I'm not sure how to progress it from here. If I need to post on
the ubuntu-server list to get attention I'm happy to do so.
I believe this bug is at step 4 of
https://wiki.ubuntu.com/MainInclusionProcess,
Having said that I see on that wiki page New binary packages from
existing source packages, where the source package is already in main,
do not require reports. But who to notify about this bug so php5-fpm
can move to main?
--
You received this bug notification because you are a member of Ubuntu
Digging in further, it appears that jujud is writing to /etc/init/juju-
db.conf (the Upstart job for its database) every few seconds. I'll file
a separate bug about this because it plausibly is the root cause of the
mongo restarts we're seeing.
--
You received this bug notification because you
I'm referring to https://wiki.ubuntu.com/UbuntuMainInclusionRequirements
Packages that deliver major new headline features in Ubuntu need to
have commitment from Ubuntu developers willing to spend substantial time
on them.
In particular, I'm not sure who you are. Are you volunteering to look
1 - 100 of 1233 matches
Mail list logo
