[Bug 252245] Re: Unable to see Windows share hostnames in Nautilus when on WiFi
** Summary changed: - Unable to see Windows share hostnames in Nautilus + Unable to see Windows share hostnames in Nautilus when on WiFi -- 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/252245 Title: Unable to see Windows share hostnames in Nautilus when on WiFi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/252245/+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 252245] Re: unable to connect to windows network pc's
James Walters, this phenomenon is verified in Trusty attempting to discover a Windows 7 share with Nautilus via a WiFi router connection. Strangely enough, if I spun up a Vista virtual local to the Trusty install (which uses a virtual switch, not a router) I could see its share by hostname with no modification. What allowed me to see the Windows share over WiFi: sudo nano /etc/nsswitch.conf hosts: files wins Restarted and now the Windows 7 share is discoverable via hostname in Nautilus. Thank you for reporting this to Ubuntu. Please feel free to report any future bugs you may find. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: samba (Ubuntu) Status: Confirmed => Invalid ** Summary changed: - unable to connect to windows network pc's + Unable to see Windows share hostnames in Nautilus -- 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/252245 Title: Unable to see Windows share hostnames in Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/252245/+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 1402137] [NEW] nginx-full
Public bug reported: I'm running Ubuntu 14.04 on Vagrant using the "ubuntu/trusty64" image from vagrantcloud. When I try to install nginx-full, I face a version mismatch issue. I did a bit of digging. The issue is nginx-full depends on nginx common. Now: vagrant@sandbox:~$ aptitude show nginx-full Package: nginx-full State: not installed Version: 1.4.6-1ubuntu3 Priority: optional Section: universe/httpd Maintainer: Ubuntu Developers Architecture: amd64 Uncompressed Size: 1,030 k Depends: nginx-common (= 1.4.6-1ubuntu3), libc6 (>= 2.14), libexpat1 (>= 2.0.1), libgd3 (>= 2.1.0~alpha~), libgeoip1, libpam0g (>= 0.99.7.1), libpcre3, libssl1.0.0 (>= 1.0.1), libxml2 (>= 2.7.4), libxslt1.1 (>= 1.1.25), zlib1g (>= 1:1.2.0) Suggests: nginx-doc (= 1.4.6-1ubuntu3) While: vagrant@sandbox:~$ aptitude show nginx-common Package: nginx-common State: not installed Version: 1.4.6-1ubuntu3.1 So nginx-full is 1.4.6-1ubuntu3 and it depends on nginx-common 1.4.6-1ubuntu3 while there's newer version of nginx-common (1.4.6-1ubuntu3.1) in the repo. I think that needs to be updated ASAP since nginx is a very common package. ** Affects: nginx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1402137 Title: nginx-full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1402137/+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 1266749] Re: openvswitch-datapath-dkms fails to build with 3.13 kernel [error: conflicting types for ‘genl_notify’ extern void genl_notify]
[Expired for openvswitch (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openvswitch (Ubuntu) Status: Incomplete => Expired -- 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/1266749 Title: openvswitch-datapath-dkms fails to build with 3.13 kernel [error: conflicting types for ‘genl_notify’ extern void genl_notify] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1266749/+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 1374011] Re: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build [configure: error: Linux kernel source in /lib/modules/3.11.0-26-generic/build is not conf
[Expired for openvswitch (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openvswitch (Ubuntu) Status: Incomplete => Expired -- 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/1374011 Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build [configure: error: Linux kernel source in /lib/modules/3.11.0-26-generic/build is not configured] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1374011/+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 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
Also (because it is a different result from one posted earlier):
echo ${SSH_AUTH_SOCK}
/run/user/1000/keyring-X8I7Ly/ssh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1380084
Title:
SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't
use key auth without SSH_AUTH_SOCK=0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+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 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
This bug has hit me quite hard in the last week, breaking a number of automated ssh processes that have been working without a hitch prior to sometime after Monday evening (8 December, UTC+8) this week. I can pin it down to that because each Monday and Friday evening I use a scripted ssh tunnel to connect a pgAdmin III client to a remote Postgres database. It worked last Monday, it didn't in between. Sometime after Monday this week, other ssh processes also broke. I'm providing this info in case it helps someone pin down what changed to cause this problem. I'm surprised it's only flagged as affecting 4 people! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+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 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
I forgot to mention: uname -a Linux robs-tosh-L50-a 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ssh -V OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+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 1396210] Re: Backporting the mysql_no_login plugin to 5.6
As a side note, an extra large +1 to upstream for taking this to the distros before breaking the micro update policy. Thanks a lot for that, guys. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1396210 Title: Backporting the mysql_no_login plugin to 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1396210/+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 1396210] Re: Backporting the mysql_no_login plugin to 5.6
17:16 < slangasek> infinity, bdmurray: so rbasak asked for input on bug #1396210; I'm on the fence about it and looking for second opinions 17:19 < infinity> slangasek: I'm +1 for backporting, building, and packaging. As noted, it still needs to be explicitly enabled and leveraged by the DBA. 17:19 < slangasek> infinity: ok. Can you put a comment to that effect on the bug? 17:19 < infinity> slangasek: And if RH is cool with it too, we're not on the hook as the only distro supporting it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1396210 Title: Backporting the mysql_no_login plugin to 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1396210/+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 1367782] Re: endpoint_type being ignored
** Changed in: python-glanceclient Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-glanceclient in Ubuntu. https://bugs.launchpad.net/bugs/1367782 Title: endpoint_type being ignored To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1367782/+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 1352570] Re: ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()
There are numerous reports that this is still not resolved in the latest packages available in trusty. http://openvswitch.org/pipermail/discuss/2014-December/015931.html ** Tags added: cts -- 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/1352570 Title: ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1352570/+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 1402005] Re: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response'
The host machine is trusty and was missing updated. We have updated the lxc and other packages. We will watch the processes to see if the issue is resolved or still exists. ** Changed in: juju-core Status: New => Triaged ** Changed in: juju-core Importance: Undecided => High ** Tags added: lxc packaging -- 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/1402005 Title: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1402005/+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 1402005] Re: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response'
lxc*1.0.3 looks odd. That is one version I don't expect to see. trusty has 1.0.6 which is what I think the host is and should be using. a precise host has 1.0.4 found in the cloud tools archive http://ubuntu-cloud.archive.canonical.com/ubuntu/pool/main/l/lxc/ juju stable ppa provides 1.0.0-alpha1, a copy of what was formerly in clout-tools. Does the host need to be upgraded or if precise, use the correct archive? -- 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/1402005 Title: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1402005/+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 1402005] Re: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response'
I don't have an easy way to repro, all this occurs fairly regularly on our jenkins slave. Ubuntu 14.04 LTS (GNU/Linux 3.13.0-29-generic x86_64) juju version: 1.20.13-trusty-amd64 1 ppa installed: http://ppa.launchpad.net/juju/stable/ubuntu $ dpkg -l | egrep -e "(lxc|apparmor|cgmanager)" ii apparmor 2.8.95~2430-0ubuntu5 amd64User-space parser utility for AppArmor ii cgmanager0.24-0ubuntu7 amd64Central cgroup manager daemon ii dh-apparmor 2.8.95~2430-0ubuntu5.1 all AppArmor debhelper routines ii libapparmor-perl 2.8.95~2430-0ubuntu5 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5 amd64changehat AppArmor library ii libcgmanager0:amd64 0.24-0ubuntu6 amd64Central cgroup manager daemon (client library) ii liblxc1 1.0.3-0ubuntu3 amd64Linux Containers userspace tools (library) ii lxc 1.0.3-0ubuntu3 amd64Linux Containers userspace tools ii lxc-templates1.0.3-0ubuntu3 amd64Linux Containers userspace tools (templates) ii python3-lxc 1.0.3-0ubuntu3 amd64Linux Containers userspace tools (Python 3.x bindings) $ ps -ef | egrep -e "(cgproxy|cgmanager)" root 348 1 0 Nov03 ?00:07:44 /sbin/cgmanager --sigstop -m name=systemd jenkins 10661 9679 0 18:36 pts/14 00:00:00 egrep -e (cgproxy|cgmanager) There are many containers on this host and I'm not sure which one(s) are being used, but regardless of which I pick I get the same result: jenkins@charm-bundle-slave:/var/lib/juju/containers$ sudo lxc-start -P /var/lib/juju/containers -n juju-trusty-lxc-template -L -l trace -o outout lxc-start: Permission denied - Failed to make / rslave lxc-start: failed to setup rootfs for 'juju-trusty-lxc-template' lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'juju-trusty-lxc-template' Advice? -- 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/1402005 Title: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1402005/+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 1402005] Re: agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive response'
Thanks for reporting this bug.
If there is a simple way to reproduce this ("spin up ami-xx on
amazon and do 'juju deploy whatzit"), please show it here.
Which release are you on, and which ppas do you have installed?
What do the following show:
dpkg -l | egrep -e "(lxc|apparmor|cgmanager)"
ps -ef | egrep -e "(cgproxy|cgmanager)"
Can you find the lxcpath juju uses and the container name, and try
starting the container by hand? I.e. if it is /var/lib/juju/lxc and
the container name is foo, then do
sudo lxc-start -P /var/lib/juju/lxc -n foo -F -l trace -o outout
and attach 'outout' to this bug.
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
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/1402005
Title:
agent-state-info: 'error executing "lxc-start": command get_cgroup
failed to receive response'
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1402005/+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 1398952] Please test proposed package
Hello Corey, or anyone else affected, Accepted heat into utopic-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/heat/2014.2.1-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1398952 Title: [SRU] juno 2014.2.1 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1398952/+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 1398952] Re: [SRU] juno 2014.2.1 point release
** Branch linked: lp:~ubuntu-server-dev/heat/juno -- 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/1398952 Title: [SRU] juno 2014.2.1 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1398952/+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 1391322] Re: [ubuntu- 14.10] librtas: fixes for LE support
** Tags removed: targetmilestone-inin1410 ** Tags added: targetmilestone-inin1504 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to librtas in Ubuntu. https://bugs.launchpad.net/bugs/1391322 Title: [ubuntu- 14.10] librtas: fixes for LE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librtas/+bug/1391322/+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 1398952] Re: [SRU] juno 2014.2.1 point release
** Branch linked: lp:~corey.bryant/heat/2014.2.1-2 -- 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/1398952 Title: [SRU] juno 2014.2.1 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1398952/+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 1378708] Re: VNC based installation does not interpret key strokes correctly.
** Tags removed: targetmilestone-inin1410 ** Tags added: targetmilestone-inin1504 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1378708 Title: VNC based installation does not interpret key strokes correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1378708/+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 1025244] Re: qcow2 image increasing disk size above the virtual limit
Is anyone even looking at this? been years and the problem still persists! -- 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/1025244 Title: qcow2 image increasing disk size above the virtual limit To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1025244/+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 1359421] Re: Update librtas for LE support
** Tags removed: targetmilestone-inin1410 ** Tags added: targetmilestone-inin1504 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to librtas in Ubuntu. https://bugs.launchpad.net/bugs/1359421 Title: Update librtas for LE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librtas/+bug/1359421/+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 1349986] Re: Ubuntu fails to boot with multipath
** Tags removed: targetmilestone-inin1410 ** Tags added: targetmilestone-inin1504 -- 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/1349986 Title: Ubuntu fails to boot with multipath To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1349986/+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 1401808] Re: package qemu-system-misc 2.1+dfsg-4ubuntu6.1 failed to install/upgrade: cannot copy extracted data for './usr/bin/qemu-system-or32' to '/usr/bin/qemu-system-or32.dpkg-new': unexpecte
Thanks for reporting this bug. It looks like your host has downloaded some corrupted or truncated package files. Could you please re-try by doing: sudo apt-get clean sudo apt-get update sudo apt-get install -f sudo apt-get dist-upgrade and let us know whether that succeeds. ** 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. https://bugs.launchpad.net/bugs/1401808 Title: package qemu-system-misc 2.1+dfsg-4ubuntu6.1 failed to install/upgrade: cannot copy extracted data for './usr/bin/qemu- system-or32' to '/usr/bin/qemu-system-or32.dpkg-new': unexpected end of file or stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1401808/+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 1401658] Re: Host veth mtu not preserved during container reboot
So the problem for you is that juju creates the containers with the wrong mtu? I don't know where juju gets its config file, (that it passes to 'lxc- create -f" but the best solution appears to be to update that to set the mtu before the containers are ever created. ** Also affects: juju (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: New => Invalid -- 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/1401658 Title: Host veth mtu not preserved during container reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1401658/+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 1308523] Re: trove-conductor needs packaging
Oddly, the Cloud archive repository for Juno still contains Icehouse packages for trove. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openstack-trove in Ubuntu. https://bugs.launchpad.net/bugs/1308523 Title: trove-conductor needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1308523/+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 1350947] Re: apparmor: no working rule to allow making a mount private
I confirm that this works fine under systemd: mount options=(rw, make-slave) -> **, Thanks! -- 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/1350947 Title: apparmor: no working rule to allow making a mount private To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1350947/+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 1350947] Re: apparmor: no working rule to allow making a mount private
Bumped priority for this bug as this is part of priority activity for reference OpenStack deployments for the vivid cycle . ** Changed in: lxc (Ubuntu) Importance: Medium => High ** Changed in: linux (Ubuntu) Importance: Medium => High ** Tags added: landscape -- 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/1350947 Title: apparmor: no working rule to allow making a mount private To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1350947/+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 1355813] Re: LXC containers reset bridge MTU on start/restart
I've re-titled this bug to be about effective interface MTU management across MAAS and Juju; enabling Jumbo frames is something that we should support in our core tooling and is critical for the successful operation of a Neutron based OpenStack Cloud. Combine this with LXC container spread across physical servers and right now this is fiddly and error prone. ** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu) Importance: Undecided => High ** Changed in: juju-core (Ubuntu) Status: New => Triaged ** Changed in: maas Status: Incomplete => New ** Summary changed: - LXC containers reset bridge MTU on start/restart + Interface MTU management across MAAS/juju ** Tags added: landscape -- 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/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1401808] Re: package qemu-system-misc 2.1+dfsg-4ubuntu6.1 failed to install/upgrade: cannot copy extracted data for './usr/bin/qemu-system-or32' to '/usr/bin/qemu-system-or32.dpkg-new': unexpecte
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1401808 Title: package qemu-system-misc 2.1+dfsg-4ubuntu6.1 failed to install/upgrade: cannot copy extracted data for './usr/bin/qemu- system-or32' to '/usr/bin/qemu-system-or32.dpkg-new': unexpected end of file or stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1401808/+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 1401658] Re: Host veth mtu not preserved during container reboot
I think I see what the problem is; the containers on these hosts where created with mtu 1500; i then updated the configuration files to set the mtu to 9000 + set the veth mtu's to 9000 using: ip link set veth mtu 9000 This means that the container was started using an mtu of 1500 not 9000. Rebooting the container internally results in the host mtu re-setting to 1500. This is a general side effect of trying to massage mtu's to 9000 to support jumbo frames in openstack deployments. ** Changed in: lxc (Ubuntu) Status: Incomplete => 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/1401658 Title: Host veth mtu not preserved during container reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1401658/+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 1401808] [NEW] package qemu-system-misc 2.1+dfsg-4ubuntu6.1 failed to install/upgrade: cannot copy extracted data for './usr/bin/qemu-system-or32' to '/usr/bin/qemu-system-or32.dpkg-new': unexpec
Public bug reported: $ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 $ apt-cache policy qemu qemu: Installé : 2.1+dfsg-4ubuntu6.3 Candidat : 2.1+dfsg-4ubuntu6.3 Table de version : *** 2.1+dfsg-4ubuntu6.3 0 500 http://fr.archive.ubuntu.com/ubuntu/ utopic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ utopic-security/universe amd64 Packages 100 /var/lib/dpkg/status 2.1+dfsg-4ubuntu6 0 500 http://fr.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages ProblemType: Package DistroRelease: Ubuntu 14.10 Package: qemu-system-misc 2.1+dfsg-4ubuntu6.1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Fri Dec 12 09:42:33 2014 DuplicateSignature: package:qemu-system-misc:2.1+dfsg-4ubuntu6.1:cannot copy extracted data for './usr/bin/qemu-system-or32' to '/usr/bin/qemu-system-or32.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/bin/qemu-system-or32' to '/usr/bin/qemu-system-or32.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2012-05-05 (951 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120425-15:28 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 584 2 0.0 [kvm-irqfd-clean] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=63ca7fe0-c60a-4843-8dc7-66abbdcc710a ro quiet splash SourcePackage: qemu Title: package qemu-system-misc 2.1+dfsg-4ubuntu6.1 failed to install/upgrade: cannot copy extracted data for './usr/bin/qemu-system-or32' to '/usr/bin/qemu-system-or32.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1805 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Crosshair III Formula dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1805:bd08/20/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCrosshairIIIFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1401808 Title: package qemu-system-misc 2.1+dfsg-4ubuntu6.1 failed to install/upgrade: cannot copy extracted data for './usr/bin/qemu- system-or32' to '/usr/bin/qemu-system-or32.dpkg-new': unexpected end of file or stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1401808/+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 1355813] Re: LXC containers reset bridge MTU on start/restart
** Tags added: smoosh -- 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/1355813 Title: LXC containers reset bridge MTU on start/restart To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1358835] new libnuma.so with fix
--- Comment on attachment From thierry.fa...@fr.ibm.com 2014-11-18 15:55 EDT--- Please have a test ** Attachment added: "new libnuma.so with fix" https://bugs.launchpad.net/bugs/1358835/+attachment/4279238/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to numactl in Ubuntu. https://bugs.launchpad.net/bugs/1358835 Title: numa_node_of_cpu() returns warning when cpu_index > 79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1358835/+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 1358835] libnuma.so.1 sum 55709
--- Comment (attachment only) From thierry.fa...@fr.ibm.com 2014-11-19 14:45 EDT--- ** Attachment added: "libnuma.so.1 sum 55709" https://bugs.launchpad.net/bugs/1358835/+attachment/4279239/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to numactl in Ubuntu. https://bugs.launchpad.net/bugs/1358835 Title: numa_node_of_cpu() returns warning when cpu_index > 79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1358835/+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
