Sorry this took so long. Finally found the time to test the 12.04
package and it works. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-boto in Ubuntu.
https://bugs.launchpad.net/bugs/962046
Title:
EC2 metadata
** Package changed: cloud-utils (Ubuntu) = cloud-init (Ubuntu)
--
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/894279
Title:
cloud-init fails to fetch metadata with OpenStack
To
I agree that Nova needs to be fixed but we need a cloud-init fix for the
current Nova as well. As for running an API server on each compute node,
I don't think that's a viable solution for our environment. We've
modified memcached to cache the metadata requests and that seems to help
make things
nova boot --flavor FLAVOR_ID --image IMAGE_ID --key_name 'my key'
INSTANCE_NAME
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-boto in Ubuntu.
https://bugs.launchpad.net/bugs/962046
Title:
EC2 metadata retrieval fails with
What does the MD look like on EC2? Curious, can you send a dump? Yes it
seems to be a problem with the nova MD service in that it's different
from EC2 but I still think boto should be able to handle special
characters in MD URLs or is there an EC2 spec that this will never
happen with EC2?
--
Hmm... On the hp cloud I get:
ubuntu@juergh-8419-5531:~$ curl 169.254.169.254/2009-04-04/meta-data
local-ipv4
reservation-id
local-hostname
placement/
ami-launch-index
public-hostname
mpi/
hostname
ami-id
public-keys/
instance-action
public-ipv4
block-device-mapping/
ami-manifest-path
mpi/ was present in diablo but removed subsequently:
commit 8ecdc44690ced882205112e017f79dc98cd6aaca
Author: Jesse Andrews anotherje...@gmail.com
Date: Tue Mar 6 20:49:16 2012 -0800
remove undocumented, unused mpi 'extension' to ec2 metadata
--
You received this bug notification because
Public bug reported:
The growroot script doesn't correctly determine the root device name if
the device name itself ends with a digit and partitions are named root
devicep1, root devicep2 aso. For example, when using an SD card:
$ ls -l /dev/mmcblk0*
brw-rw 1 root disk 179, 0 Oct 7 16:04
Scott,
Looks good but could be simplified to:
+if [ ${rootdisk%[0-9]p} != ${rootdisk} ] ; then
+rootdisk=${rootdisk%p}
+fi
I don't think you need to adjust $partnum.
Also, can you apply the patch to
growroot/dracut/modules.d/50growroot/growroot.sh as well?
Note that the following (old)
Can we have this patch applied to
growroot/dracut/modules.d/50growroot/growroot.sh as well?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1236380
Title:
growroot
Public bug reported:
On OpenStack, the CloudStack handler is retyring even if the response is
404, resulting in a 2 min timeout.
IMHO, readurl() should abort in this case.
ci-info: | Route | Destination | Gateway |Genmask| Interface | Flags |
ci-info:
** Branch linked: lp:~juergh/cloud-init/lp1298921
--
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/1298921
Title:
cloud-init should give up on 404 errors
To manage notifications
In one way or another, the CloudStack datasource was explicitly enabled.
You or something explicitly configured this datasource on, and to be run
before the Ec2 datasource, so generally its functioning as designed.
Well it wasn't explicitly disabled :-)
Additionally, its not a 404 that we
Public bug reported:
All tests from test_smartos.py fail in a chroot as follows (only first
failure shown):
$ nosetests tests/unittests/test_datasource/test_smartos.py
F
==
FAIL: test_b64_keys
Public bug reported:
$ virt-install --version
0.600.0
$ /usr/bin/virt-install --connect qemu:///session --name
fedora-16-server-x86_64 --ram 2048 --location
http://192.168.1.11//os/fedora/linux/releases/16/Fedora/x86_64/os/ --disk
I agree that Nova needs to be fixed but we need a cloud-init fix for the
current Nova as well. As for running an API server on each compute node,
I don't think that's a viable solution for our environment. We've
modified memcached to cache the metadata requests and that seems to help
make things
Public bug reported:
I pulled natty-server-cloudimg-amd64.tar.gz, extracted the archive and
then extracted the initrd from the image file. I then registered the
three files (image, kernel, ramdisk) with Nova (2011.2-0ubuntu1) and
launched an instance. The console log threw the following errors:
Public bug reported:
Tested the UEC Lucid, Maverick, Natty and Oneiric images with OpenStack
Diablo. When launching multiple (20+) instances at the same time the
OpenStack metadata server becomes quite slow and cloud-init fails to
fetch the metadata due to its short timeout of 2 (3 for Oneiric)
** Package changed: cloud-utils (Ubuntu) = cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894279
Title:
cloud-init fails to fetch metadata with OpenStack
To manage notifications
Who do I need to assign this to?
** Package changed: sysvinit (Ubuntu) = pam (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1006349
Title:
last and lastb not working in precise and oneiric
Same problem and solution as mentioned in the previous comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581566
Title:
udevd inotify_add_watch no such directory error for physical volumes
To
Public bug reported:
The growroot script doesn't correctly determine the root device name if
the device name itself ends with a digit and partitions are named root
devicep1, root devicep2 aso. For example, when using an SD card:
$ ls -l /dev/mmcblk0*
brw-rw 1 root disk 179, 0 Oct 7 16:04
Can't run apport-collect on these machines.
** 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/979498
Title:
Critical: Natty kernel
On one machine, this affected the /tmp logical volume. Any command/task
that touched /tmp hung and never completed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979498
Title:
Critical: Natty
Trying to find a reproducer to test the kernel. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979498
Title:
Critical: Natty kernel hangs in xlog_grant_log_space
To manage notifications
I logged a case #00029027 through the HP landscape account. Do you have
access to that? It contains instructions and some scripts that I use to
force the hang. Can you try the Natty kernel? That one hangs within a
few seconds.
--
You received this bug notification because you are a member of
I reproduces the issue on 4 different machines with different HW
configurations (SE1170/P410, SE2170/P212, SL390/P212, z400 no RAID
controller).
Do you have a machine that I can access to give it a try? Or would it
help if I gave you access to one of our machines?
--
You received this bug
I finally managed to create a reproducer for the XFS hang but the provided
kernel does not solve the problem. It hangs within a few seconds, just like the
original 2.6.38-8-server kernel. I also tried the following Ubuntu kernels but
they both hang within a few minutes. Do run a little longer
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/979498/+attachment/3101284/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979498
Title:
Critical:
Scott,
Looks good but could be simplified to:
+if [ ${rootdisk%[0-9]p} != ${rootdisk} ] ; then
+rootdisk=${rootdisk%p}
+fi
I don't think you need to adjust $partnum.
Also, can you apply the patch to
growroot/dracut/modules.d/50growroot/growroot.sh as well?
Note that the following (old)
Can we have this patch applied to
growroot/dracut/modules.d/50growroot/growroot.sh as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236380
Title:
growroot fails for images on SD cards
To
Sorry this took so long. Finally found the time to test the 12.04
package and it works. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962046
Title:
EC2 metadata retrieval fails with spaces
Public bug reported:
Virt-viewer 0.5.4-1 for Raring doesn't support the SPICE protocol.
Trying to connect to a SPICE'd VM results in 'Unknown graphic type for
the guest'.
$ ldd /usr/bin/virt-viewer | grep spice
$
After adding SPICE support and recompiling the package, I can successfully
Yeah I didn't think it was a sysvinit bug but I didn't know which
package to attach the bug report to. I couldn't figure out how to mark
it as a generic 'cloud images' problem rather than a package-specific
problem. The pam modules obviously are installed in the images. All
works well if I create
What does the MD look like on EC2? Curious, can you send a dump? Yes it
seems to be a problem with the nova MD service in that it's different
from EC2 but I still think boto should be able to handle special
characters in MD URLs or is there an EC2 spec that this will never
happen with EC2?
--
Hmm... On the hp cloud I get:
ubuntu@juergh-8419-5531:~$ curl 169.254.169.254/2009-04-04/meta-data
local-ipv4
reservation-id
local-hostname
placement/
ami-launch-index
public-hostname
mpi/
hostname
ami-id
public-keys/
instance-action
public-ipv4
block-device-mapping/
ami-manifest-path
mpi/ was present in diablo but removed subsequently:
commit 8ecdc44690ced882205112e017f79dc98cd6aaca
Author: Jesse Andrews anotherje...@gmail.com
Date: Tue Mar 6 20:49:16 2012 -0800
remove undocumented, unused mpi 'extension' to ec2 metadata
--
You received this bug notification because
Can I get a copy of the source so that I can check what other patches
are in that kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979498
Title:
Critical: Natty kernel hangs in
Can this be backported to Oneiric?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972207
Title:
virt-install fails to inject a file into the initrd
To manage notifications about this bug go to:
Good catch. I missed the 'Unaligned AIO/DIO' message. However, why would
this cause other processes to start hogging the CPU? Also, I created a
new Windows image and I still get the 'Unaligned AIO/DIO' message but
the system does not get into the same state where multiple processes
will comsume
Public bug reported:
We're seeing the following stack traces on different production machines
that are running Natty 2.6.38-8-server. The machines need to be
rebooted to recover.
http://oss.sgi.com/archives/xfs/2011-11/msg00401.html claims that this
bug is fixed in 3.0. Can this patch be
Public bug reported:
I'm running a Windows7 guest in KVM via libvirt/virt-manager on a
Oneiric desktop 64-bit. Every once in a while (2-3 times a week,
sometimes daily) the CPU usage goes berserk and the host becomes very
unresponsive and unusable. This also happened once with a Breezy guest
so
** Attachment added: top
https://bugs.launchpad.net/bugs/973536/+attachment/3003952/+files/top
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
Title:
kvm brings Oneiric host to a grinding
** Attachment added: lsof
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/973536/+attachment/3003954/+files/lsof
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
Title:
kvm brings
** Attachment added: 1624.strace
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/973536/+attachment/3003955/+files/1624.strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
Title:
** Attachment added: 1644.strace
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/973536/+attachment/300/+files/1644.strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
Title:
** Attachment added: 2110.strace
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/973536/+attachment/3004445/+files/2110.strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
Title:
** Attachment added: 2419.strace
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/973536/+attachment/3004448/+files/2419.strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
Title:
** Attachment added: 9156.strace
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/973536/+attachment/3004449/+files/9156.strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
Title:
** Attachment added: 27462.strace
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/973536/+attachment/3004450/+files/27462.strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
** Attachment added: 27898.strace
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/973536/+attachment/3004457/+files/27898.strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
Once in this state, the system doesn't recover by itself. When I kill
kvm, things seem to go back to normal but if I start it up again the CPU
usage of the same couple of processes goes up again, almost
immeditately. Only a reboot fixes it so that it stays stable for a
longer amount of time.
Only
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008733/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
apport information
** Tags added: apport-collected oneiric running-unity
** Description changed:
I'm running a Windows7 guest in KVM via libvirt/virt-manager on a
Oneiric desktop 64-bit. Every once in a while (2-3 times a week,
sometimes daily) the CPU usage goes berserk and the host
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008734/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008735/+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/973536
Title:
kvm
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008737/+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/973536
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008738/+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/973536
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008740/+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/973536
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008742/+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/973536
Title:
kvm
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008743/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973536
Title:
kvm
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008736/+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/973536
Title:
kvm
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008739/+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: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/973536/+attachment/3008741/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Because the files /var/log/wtmp and /var/log/btmp are missing.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This affects:
http://cloud-images.ubuntu.com/releases/oneiric/release/
http://cloud-images.ubuntu.com/releases/precise/release/
** Package changed: ubuntu = sysvinit (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
nova boot --flavor FLAVOR_ID --image IMAGE_ID --key_name 'my key'
INSTANCE_NAME
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962046
Title:
EC2 metadata retrieval fails with spaces in a resource
Public bug reported:
On OpenStack, the CloudStack handler is retyring even if the response is
404, resulting in a 2 min timeout.
IMHO, readurl() should abort in this case.
ci-info: | Route | Destination | Gateway |Genmask| Interface | Flags |
ci-info:
** Branch linked: lp:~juergh/cloud-init/lp1298921
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298921
Title:
cloud-init should give up on 404 errors
To manage notifications about this bug go to:
In one way or another, the CloudStack datasource was explicitly enabled.
You or something explicitly configured this datasource on, and to be run
before the Ec2 datasource, so generally its functioning as designed.
Well it wasn't explicitly disabled :-)
Additionally, its not a 404 that we
Public bug reported:
All tests from test_smartos.py fail in a chroot as follows (only first
failure shown):
$ nosetests tests/unittests/test_datasource/test_smartos.py
F
==
FAIL: test_b64_keys
Public bug reported:
Nothing happens when clicking 'Sound Settings...' in the indicator
applet on a fresh install of Lubuntu 17.04.
This is probably because of the following code in src/sound-service-
dbus.c:
static void
show_sound_settings_dialog (DbusmenuMenuitem *mi,
that the current kernel driver does not
support.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Juerg Haefliger (juergh)
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because
** Summary changed:
- Backport more recent Broadcom bnxt driver
+ Backport more recent Broadcom bnxt_en driver
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711056
Title:
Backport more recent
Every-day usage on Artful is successful so far. And I can confirm that
Fedora VMs can now be built properly (i.e. #1683747 is fixed).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667114
Title:
** Changed in: linux-raspi2 (Ubuntu Yakkety)
Status: New => Fix Committed
** Changed in: linux-raspi2 (Ubuntu Zesty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
nel-team) => Juerg Haefliger
(juergh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701017
Title:
linux-raspi2: 4.10.0-1011.14 -proposed tracker
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu Zesty)
Status: New => 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/1699651
Title:
KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device
To
** Changed in: linux (Ubuntu Zesty)
Status: New => 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/1699627
Title:
XDP eBPF programs fail to verify on Zesty ppc64el
To manage
eam) => Juerg Haefliger
(juergh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701013
Title:
linux: 4.10.0-28.32 -proposed tracker
To manage notifications about this bug go to:
https://bugs.launchp
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received
I can offer to do some testing if somebody provides an updated package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667114
Title:
Merge 1:1.4.0-5 from Debian unstable to zesty
To manage
Debian stable is at upstream 1.4.0. Artful is still 1.3.2. Can we please
move?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683747
Title:
libvirtError: unsupported configuration: unknown input
Public bug reported:
We're adding a backported bnxt driver to Xenial (LP #1711056). It's an
alternate for the regular Xenial driver that only manages NICs that are
not supported by the regular Xenial driver. But it's a boot-critical
driver so it needs to be added to the initramfs.
---
Public bug reported:
I'm trying to build a foreign architecture chroot (on artful) using
qemu-debootstrap but the result is an indefinite hang during the second
stage.
To reproduce:
$ sudo qemu-debootstrap --arch=s390x xenial /tmp/chroot-xenial
I: Extracting perl-base...
I: Extracting
1 - 100 of 1115 matches
Mail list logo
