[Bug 1071865] [NEW] Keystone PKI token length hits cookie size limit
You have been subscribed to a public bug: When Keystone's PKI tokens are enabled the length of the token itself is 3.95kb, nearly exceeding the cookie size limit without any additional data. This makes PKI tokens incompatible with the cookie session backend in Horizon. We need a way to detect/configure support for this so it doesn't bite users in unexpected ways. ** Affects: keystone (Ubuntu) Importance: Critical Assignee: Gabriel Hurley (gabriel-hurley) Status: Fix Released ** Affects: keystone Importance: High Assignee: Adam Young (ayoung) Status: Fix Released -- Keystone PKI token length hits cookie size limit https://bugs.launchpad.net/bugs/1071865 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1071865] Re: Keystone PKI token length hits cookie size limit
** Project changed: horizon = keystone (Ubuntu) ** Changed in: keystone (Ubuntu) Milestone: grizzly-1 = None -- 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/1071865 Title: Keystone PKI token length hits cookie size limit To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1071865/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 967410] Re: Windows clients cannot connect to shared printers
What happened to the fix? On 2013-03-09 23:20:24 /var/log/apt/history.log shows samba:i386 (3.6.3-2ubuntu2.3) being installed, and I could once again access printer shares from windows. However, this morning, I could not! The history.log shows 2013-03-23 23:27:26 samba:i386 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4). I wanted to downgrade to samba:i386 (3.6.3-2ubuntu2.3) but could not. apt-cache showpkg samba shows: Provides: 2:3.6.3-2ubuntu2.4 - 2:3.6.3-2ubuntu2.1 - 2:3.6.3-2ubuntu2 - Do we open a new bug report or continue with this one? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/967410 Title: Windows clients cannot connect to shared printers To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/967410/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1153364] Re: trouble with guest network connectivity when host is using a bonded interface
apport information ** Description changed: i'm seeing poor/intermittent/degrading network connectivity for guests, when the host is using a bonded interface. in a nutshell, the network configuration is as follows: the physical interfaces [eth0 and eth1] are bonded together as bond0 [i've tried various bond modes - see below]. a bridge interface [br0] is configured with bond0 attached to it. all guests use br0 as their forward interface. my tests have generally included a single host, with two guests running on it. both guests are running ubuntu 12.10. it depends slightly on the particulars of the configuration, but the most prevalent symptom is that a newly booted guest will at first respond to pings [with little to no loss], and the guest will be able to ping other hosts on the network, but as time passes, more and more packets are dropped. eventually, virtually all ping requests go unanswered. in some cases, it appears that restarting networking on the guest will fix this, partially and temporarily. the guest will begin to reply 4-5 packets after restarting networking, but does not respond consistently, eventually failing again as before. i've also noticed that in some cases where ping against the guest has not yet begun to fail, if i ping something else on the network from the guest, this causes the pings against the guest to abruptly fail. i know this is all quite abstract - i've spent quite a bit a time trying to isolate various variables, and while i've made some progress, i think some guidance would be helpful. what i have noticed specifically is if i attach a physical device [e.g. eth0 or eth1] to the bridge [instead of bond0], things seem to work ok. also, if i use active-backup as the bonding mode, things seem to work ok. i was initially using balance-alb as the bonding mode, and have also tested balance-rr as the bonding mode. both exhibit the above symptoms. i've also tried various network card models for the guests [realtek, e1000, and virtio]. this has not had any impact on the symptoms. lastly, the two guests have been able to ping each other, with no issues, regardless of the various network settings. at the moment, i have switched back to active-backup, so this is reflected in the below information. here is a bit of configuration info: host os/package info: lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 apt-cache policy qemu-kvm qemu-kvm: Installed: 1.2.0+noroms-0ubuntu2.12.10.3 Candidate: 1.2.0+noroms-0ubuntu2.12.10.3 Version table: *** 1.2.0+noroms-0ubuntu2.12.10.3 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.0+noroms-0ubuntu2.12.10.2 0 500 http://security.ubuntu.com/ubuntu/ quantal-security/main amd64 Packages 1.2.0+noroms-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages dpkg -l | grep -i virt ii libvirt-bin0.9.13-0ubuntu12.2 amd64programs for the libvirt library ii libvirt0 0.9.13-0ubuntu12.2 amd64library for interfacing with different virtualization systems ii python-libvirt 0.9.13-0ubuntu12.2 amd64libvirt Python bindings ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.3 amd64Full virtualization on supported hardware ii virtinst 0.600.2-1ubuntu1 all Programs to create and clone virtual machines dpkg -l | grep -i qemu ii qemu-common1.2.0+noroms-0ubuntu2.12.10.3 all qemu common functionality (bios, documentation, etc) ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.3 amd64Full virtualization on supported hardware ii qemu-utils 1.2.0+noroms-0ubuntu2.12.10.3 amd64qemu utilities ii vgabios0.7a-3ubuntu2 all VGA BIOS software for the Bochs and Qemu emulated VGA card host network config: egrep -v '(^[[:space:]]*#|^[[:space:]]*$)' /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet manual bond-master bond0 auto eth1 iface eth1 inet manual bond-master bond0 auto bond0 iface bond0 inet manual bond-mode active-backup bond-slaves eth0 eth1 bond-primary eth0 bond-primary_reselect better auto br0 iface br0 inet static bridge_ports bond0 bridge_stp off bridge_waitport 0 bridge_maxwait 0 bridge_maxage 0 bridge_fd 0 bridge_ageing 0
[Bug 1041070] Re: 802.3ad bond interface have show high RX dropped packets
I am also seeing lot of RX packet drops for some off reason in Ubuntu 12.10. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1041070 Title: 802.3ad bond interface have show high RX dropped packets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1041070/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1157589] Re: kvm hangs for freebsd guests since raring upgrade
** 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 kvm in Ubuntu. https://bugs.launchpad.net/bugs/1157589 Title: kvm hangs for freebsd guests since raring upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1037055] Re: winbind does not refresh kerberos tickets
Although inconvenient, personally I'm ok with quantal being skipped. Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1037055 Title: winbind does not refresh kerberos tickets To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1037055/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
