** Tags added: kernel-da-key
--
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/1551419
Title:
Fix UUID endianness patch breaks cloud-init on Azure
To manage notifications about
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.5
Public bug reported:
If a machine has a hostname made up entirely of numbers, install and
start will fail reporting:
ERROR: epmd error for host "1234": badarg (unknown POSIX error)
This can be duplicated:
hostame 1234
echo 127.0.0.1 localhost 1234 > /etc/hosts
apt-get install rabbitmq-server
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1524069
Title:
Xenial KVM: updating Trusty guest from 3.13.0-68 to
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3
** Branch linked: lp:~josephbisch/vmbuilder/debian
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/235562
Title:
Add ability to build Debian virtual machines
To manage
I added the Debian guest related commits to
https://code.launchpad.net/~josephbisch/vmbuilder/debian. I also added
Debian Stretch and tested out creating a KVM image of it.
I notice that my full name doesn't show up in the list of revisions like
it does for other people. I guess I don't have my
I just tried filling out the contributor agreement (so far I am the sole
author of the changes), but I'm not sure what to put for the project
contact and it is required. Do I put you, Serge?
Thanks for the comments on GitHub. I'll address them asap and get the
changes into bzr.
--
You received
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in
I have a fork that intends to add Debian guest support. Right now it is
only tested with KVM (because that is just what I need). Also I only
tested it with Jessie images, so it might not work with every Debian
suite as the guest, particularly with older suites.
It serves my purpose of adding
Public bug reported:
ackage mailman (not installed) failed to install/upgrade: subprocess new
pre-installation script returned error exit status 1
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: mailman (not installed)
ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
Thanks for posting the fix here it was a big help.
--
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/1396740
Title:
etherwake does not wake up machines
To manage notifications about
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.2
** Also affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu)
Status: New = Triaged
** Changed in: iproute2 (Ubuntu Trusty)
Status: New = Triaged
** Changed in: iproute2 (Ubuntu)
Importance: Undecided = High
** Changed in:
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/1471358
Title:
lxc-checkconfig shows Mainline PPA Wily-4.0.7
This bug affects gitian-builder when used with lxc. Gitian-builder is
the reproducible build tools used by Bitcoin Core and other projects.
The relevant gitian-builder bug is https://github.com/devrandom/gitian-
builder/issues/95.
I have confirmed this bug with a 15.04 chroot. As you can see from
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: kernel-da-key trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to iproute2 in Ubuntu.
** Description changed:
Ubuntu 15.04 fails with Kernel Panic.
Installer used is latest dated 24-March 2015
http://archive.ubuntu.com/ubuntu/dists/vivid/main/installer-
amd64/current/images/netboot/ubuntu-installer/amd64/
Below is the kernel panic message seen during the
Very similar issue upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=85885
** Bug watch added: freedesktop.org Bugzilla #85885
https://bugs.freedesktop.org/show_bug.cgi?id=85885
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I found a way to reproduce this bug and am currently bisecting it.
15.04 can be installed using the Fast Installer. This will work
without causing a panic on install.
I then installed the intel-gpu-tools test package. Using the following
test from intel-gpu-tools will cause the panic:
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: High
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Also affects: maas (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You
I can't seem to make this happen again so closing for now.
** Changed in: cloud-init (Ubuntu)
Status: New = 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/1429976
Wrong package!
** Changed in: cloud-init (Ubuntu)
Status: New = 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/1429976
Title:
Unattended install fails with
okay I'm an idiot: 'grub-legacy-ec2' is a binary package. This bug has
been assigned to its source package 'cloud-init' instead. so this is the
right spot
** Changed in: cloud-init (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Trying to update to today's update-grub-legacy-ec2 causes my unattended
installs to fail.
Running:
14.04 latest AMI: ami-968ad1fe
apt-get -y -q update
apt-get -y -q upgrade
dpkg.log says:
2015-03-09 18:13:32 status half-configured grub-legacy-ec2:all
0.7.5-0ubuntu1.4
ps
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) = Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu
@James
Just curious if you had a chance to test the kernel posted in comment
#9?
--
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/1408972
Title:
openvswitch: failed to flow_del
** Tags added: kernel-da-key
--
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/1412887
Title:
unable to start lxc on ubuntu
To manage notifications about this bug go to:
Also, you need to install the linux-image and linux-image-extra .deb
packages.
--
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/1408972
Title:
openvswitch: failed to flow_del (No
I created a backport of commit 4a46b24 and built a test kernel. The
test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1408972/
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: linux (Ubuntu)
Importance: Medium = High
--
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/1408972
Title:
openvswitch: failed to flow_del (No such file or
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
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/1408972
Title:
openvswitch: failed
Looks like this is the commit that fixes the issue in the 3.16 kernel:
commit 4a46b24e147dfa9b858026da02cad0bdd4e149d2
Author: Alex Wang al...@nicira.com
Date: Mon Jun 30 20:30:29 2014 -0700
openvswitch: Use exact lookup for flow_get and flow_del.
--
You received this bug notification
There seems to be a few commits that are needed to cherry-pick 4a46b24
cleanly, or a considerable backport is needed.
Is using the Utopic backport kernel for Trusty(14.04.2) an option?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Commit 4a46b24e1 does not cherry-pick cleanly in Trusty, so some other
commits may be needed.
--
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/1408972
Title:
openvswitch: failed
** Tags added: kernel-da-key
--
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/1369294
Title:
openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel
module failed
** Also affects: openvswitch (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: openvswitch (Ubuntu Vivid)
Importance: Medium
Status: In Progress
** Changed in: openvswitch (Ubuntu Utopic)
Importance: Undecided = Medium
** Changed in: openvswitch (Ubuntu
I am also getting this error, and like Eugene says, it seems to be
dependent on the environment in which the mount command is executed.
I attempted to mount from inside a tmux session, and the mount failed.
I detached from the tmux session, issued the very same mount command in
a plain ssh
** Changed in: openvswitch (Ubuntu)
Importance: Undecided = Medium
--
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/1369294
Title:
openvswitch-datapath-dkms
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.17 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.17 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
This bug was nominated against a series that is no longer supported, ie
quantal. The bug task representing the quantal nomination is being
closed as Won't Fix.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu Quantal)
This bug was nominated against a series that is no longer supported, ie
raring. The bug task representing the raring nomination is being closed
as Won't Fix.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu Raring)
This bug was nominated against a series that is no longer supported, ie
quantal. The bug task representing the quantal nomination is being
closed as Won't Fix.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu Quantal)
** Tags added: kernel-da-key
--
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/1362199
Title:
[FFe] apparmor abstract, anonymous and netlink socket mediation
To manage notifications
how to we fix ? seems same issues
--
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/1110567
Title:
Openstack Ubuntu Testing: nova-common dpkg --configure broken
To manage notifications
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived doesn't load any ipv6 virtual servers
To manage notifications about this
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived doesn't load
I can verify that the bug still occurs with libsdl1.2debian
1.2.15-8ubuntu1 and is fixed by libsdl1.2debian 1.2.15-8ubuntu1.1.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libsdl1.2 in Ubuntu.
https://bugs.launchpad.net/bugs/1280665
It should be noted that upstream is not planning on making another SDL
1.2 release. They are building a compatibility API for SDL 2.0 instead.
We should apply this patch until that compatibility API is ready.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
libsdl1.2 always enables backingstore when it is present in the X
server. For modern X servers, backingstore is implemented by redirecting
through the composite extension. This causes tearing on SDL applications
such as xbmc because the redirected rendering is not guaranteed
** Description changed:
libsdl1.2 always enables backingstore when it is present in the X
server. For modern X servers, backingstore is implemented by redirecting
through the composite extension. This causes tearing on SDL applications
such as xbmc because the redirected rendering is not
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.13 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of the
introduction of a regression, and when this regression was introduced.
If this is a
** Tags removed: kernel-key
--
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/1263738
Title:
login console 0 in user namespace container is not configured right
To manage notifications
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.13 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
This bug appears to be related to the mysql test suite versus the
kernel, so adding mysql bug task.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: kernel-da-key ppc64el
** Also affects: mysql-5.5 (Ubuntu)
Importance: Undecided
Status: New
--
You
One additional question, do you happen to know if this is a regression?
Did this not happen with previous releases/kernels?
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-key trusty
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Do you happen to know if this is also an issue in the latest mainline
kernel[0]?
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
** Also affects: linux (Ubuntu Trusty)
Importance: High
Status:
Assuming I should use the init script for this, attached output from
running the following in the container:
strace -o iscsi-start.txt service open-iscsi start
** Attachment added: iscsi-start.txt
Aha! Attached: strace -f -o iscsi-start_f.txt service open-iscsi start
** Attachment added: iscsi-start_f.txt
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855/+attachment/3855848/+files/iscsi-start_f.txt
--
You received this bug notification because you are a member of Ubuntu
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
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/1196295
Title:
lxc-start enters uninterruptible sleep
To manage
192.0.2.69 is the IP of the qemu VM that the LXC container is attempting
to provision.
I'll load up my test instance soon to get that additional strace.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Thanks for your reply, I'll chat with Robert and Clint to see if any of
these solutions is reasonable for us.
As a reference point, here's the setup we're using:
Host has 2 VMs: An LXC and an qemu VM
The host has the iscsi_tcp module loaded, which then can be seen and
used for the iscsi daemon
Public bug reported:
Trying to use open-iscsi from within an LXC container, but the iscsi
netlink socket does not support multiple namespaces, causing: iscsid:
sendmsg: bug? ctrl_fd 6 error and failure.
Command attempted: iscsiadm -m node -p $ip:$port -T $target --login
Results in:
Exit code:
Thanks for the info, James. So in 3.10 and earlier the kernel did not
register a protocol hander for GRE and now it does?
--
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/1213879
@James Page, Did this bug just start happening after a new kernel
update? Was there a prior kernel that did not get this fault? If so,
we can perform a bisect to identify the commit that introduced the
regression.
Also, the 3.11.0-3.7 kernel is now available, which is rebased to
upstream
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Title:
general protection fault running apt-get inside double
** Also affects: kvm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
** Tags removed: performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1201092
Title:
Cannot load kvm_amd module - (says disabled by bios)
To manage notifications about
Per comment #13, it sounds like this issue is resolved in the 3.11
kernel, which is what Saucy will be rebased to. Does this issue only
exist in Saucy, or should the bug be targeted to other releases as well?
** Also affects: linux (Ubuntu Saucy)
Importance: High
Status: Incomplete
**
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Thanks for testing the upstream kernel. One additional question. Was
there a previous kernel version that did not exhibit this issue? It
would be good to know if this is a regression. If it is, we can perform
a bisect to identify the commit that introduced it.
--
You received this bug
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
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/1196295
Title:
lxc-start enters uninterruptible sleep
To manage
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.10 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Changed in: linux
Importance: Undecided = High
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-da-key raring
--
You received this bug notification because you are a member of
davewalker - can we get this packaged for precise as well?
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1167421
Title:
Upgrading from folsom to grizzly
Can you also test the latest v3.8.4 stable kernel?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.4-raring/
If the bug still exits in 3.8.4, we will need to perform a reverse
bisect to identify the commit that fixes in this bug in v3.9-rc4.
--
You received this bug notification because you
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.9 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1109029
Title:
Depend on linux-initramfs-tools
To manage
Hi Nate,
It appears FIFREEZE AND FITHAW are already built into the kernel.
Here is the defines in ~/linux/include/linux/fs.h(Also in
~linux/include/uapi/linux/fs.h):
#define FIFREEZE_IOWR('X', 119, int)/* Freeze */
#define FITHAW _IOWR('X', 120, int)/* Thaw */
In
This could be an issue:
/var/lib/dkms/open-vm-tools/2012.10.14/build/vmsync/sync.c: In function
‘VmSyncThawDevices’:
/var/lib/dkms/open-vm-tools/2012.10.14/build/vmsync/sync.c:165:37: error:
‘struct super_block’ has no member named ‘s_frozen’
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1088053
Title:
Kernel needs to provide FIFREEZE/FITHAW ioctl
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1088053
Title:
Kernel needs to provide FIFREEZE/FITHAW ioctl so
man page is generated in packaging - not part of the upstream keystone
repo
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Changed in: keystone
Status: Triaged = Invalid
** Changed in: keystone
Assignee: Adam Gandelman (gandelman-a) = (unassigned)
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1079212
Title:
network slow when 2 VMs using virtio net bridged to
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.7 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
@Paul,
Can you also confirm this bug no longer exists in the latest quantal
images? If so, please mark this bug as Fix Released.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
@Paul, were you able to test the kernel mentioned in comment #22 ? The
3.5.0-17 kernel is now available as well.
** Changed in: linux (Ubuntu Quantal)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
also linking to python-keystoneclient project since it's CLI related
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Importance: Undecided = High
** Changed in: python-keystoneclient
Status: New = Triaged
**
russel - description is good, run with it.
** Description changed:
Admin API /v2.0/tenants/{tenant_id}/users/{user_id}/roles doesn't
- validate token
+ validate the authentication token before returning a response.
- we can get the same result without a token in HTTP head.
+ i.e. we can get
Good description, ack.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/988920
Title:
Token authentication for a user in a disabled tenant does not raise
Unauthorized error
To
Thanks, Serge. It would be good to know if the bug goes away if you
boot the precise kernel in the quantal vm. That will tell us if this is
a regression. If it is, we can perform a kernel bisect to identify the
commit in Quantal that introduced the regression.
--
You received this bug
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.6 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
Once you've tested the
Does this issue go away if you boot into the kernel prior to the
upgrade?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1054129
Title:
reboot with -vga cirrus can result in
1 - 100 of 200 matches
Mail list logo
