[Bug 766242] Re: lp:ubuntu/cloud-init is not buildable by bzr-builder
** No longer affects: launchpad -- 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/766242 Title: lp:ubuntu/cloud-init is not buildable by bzr-builder To manage notifications about this bug go to: https://bugs.launchpad.net/bzr-builder/+bug/766242/+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 1348551] Update Released
The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1348551 Title: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1348551/+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 1348551] Re: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm
This bug was fixed in the package qemu - 2.0.0+dfsg-2ubuntu1.2 --- qemu (2.0.0+dfsg-2ubuntu1.2) trusty-proposed; urgency=medium * d/qemu-system-x86.qemu-kvm.upstart: change the early-exit check from /usr/bin/kvm to qemu-system-x86_64. (LP: #1348551) -- Serge HallynFri, 25 Jul 2014 08:59:57 -0500 ** Changed in: qemu (Ubuntu Trusty) Status: Fix Committed => Fix Released -- 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/1348551 Title: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1348551/+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 1353269] [NEW] "celery worker" crashes on startup when python-librabbitmq is used
Public bug reported: On a vanilla trusty install with rabbitmq-server and celeryd installed, "celery worker" crashes as follows: $ dpkg-query -W python-librabbitmq rabbitmq-server python-amqp librabbitmq1 celeryd celeryd 3.1.6-1ubuntu1 librabbitmq10.4.1-1 python-amqp 1.3.3-1ubuntu1 python-librabbitmq 1.0.3-0ubuntu1 rabbitmq-server 3.2.4-1 $ celery worker [2014-08-06 05:19:00,142: WARNING/MainProcess] /usr/lib/python2.7/dist-packages/celery/apps/worker.py:159: CDeprecationWarning: Starting from version 3.2 Celery will refuse to accept pickle by default. The pickle serializer is a security concern as it may give attackers the ability to execute any command. It's important to secure your broker from unauthorized access when using pickle, so we think that enabling pickle should require a deliberate action and not be the default choice. If you depend on pickle then you should set a setting to disable this warning and to be sure that everything will continue working when you upgrade to Celery 3.2:: CELERY_ACCEPT_CONTENT = ['pickle', 'json', 'msgpack', 'yaml'] You must only enable the serializers that you will actually use. warnings.warn(CDeprecationWarning(W_PICKLE_DEPRECATED)) -- celery@juju-pjdc-lcy02-machine-4 v3.1.6 (Cipater) - --- * *** * -- Linux-3.13.0-32-generic-x86_64-with-Ubuntu-14.04-trusty -- * - --- - ** -- [config] - ** -- .> broker: amqp://guest@localhost:5672// - ** -- .> app: default:0x7ff5367585d0 (.default.Loader) - ** -- .> concurrency: 1 (prefork) - *** --- * --- .> events: OFF (enable -E to monitor this worker) -- *** --- * - [queues] -- .> celery exchange=celery(direct) key=celery Segmentation fault (core dumped) If I remove python-librabbitmq so that celery falls back to python-amqp, "celery worker" starts up and works correctly. I have also discovered that a python-rabbitmq built from version 1.5.2 sources with its embedded copy of rabbitmq-c 0.5.0 also works correctly. I have attached a backtrace but it is not too useful as python- librabbitmq does not appear to make debug symbols available, and it occupies the second and third frames in the stack when the crash happens. ** Affects: python-librabbitmq (Ubuntu) Importance: Undecided Status: New ** Attachment added: "celery-vs-python-librabbitmq-backtrace.txt" https://bugs.launchpad.net/bugs/1353269/+attachment/4170851/+files/celery-vs-python-librabbitmq-backtrace.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-librabbitmq in Ubuntu. https://bugs.launchpad.net/bugs/1353269 Title: "celery worker" crashes on startup when python-librabbitmq is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-librabbitmq/+bug/1353269/+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 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
With the latest firmware all the nodes should work. I think he did not download the correct freeimpi version. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1324992 Title: freeipmi patch for HP moonshot ARM cartridges with I2c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+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
Re: [Bug 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
pradeep which node? It needs node 2, 3, and 4 need some extra step as per shashi. Can you try it node 1 if it is not node one. Otherwise you need to get the steps from shashi to enabled i2c on those nodes. Thanks and Regards, Narinder Gupta (PMP) narinder.gu...@canonical.com Canonical, Ltd.narindergupta [irc.freenode.net] +1.281.736.5150narindergupta2007[skype] Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com On Tue, Aug 5, 2014 at 10:16 PM, Kodamati Pradeep Vinesh Reddy < pradeep.red...@hp.com> wrote: > I am seeing the error like mentioned by manoj above comment #4 > > root@ubuntu:~# bmc-info --no-probing --driver-type=SSIF > --driver-address=0x10 --driver-device=/dev/i2c-2 --get-device-id --debug > = > Get Device ID Request > = > SSIF Header: > > [ 0h] = lun[ 2b] > [ 6h] = net_fn[ 6b] > IPMI Command Data: > -- > [ 1h] = cmd[ 8b] > ipmi_cmd_get_device_id: internal system error > root@ubuntu:~# > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1324992 > > Title: > freeipmi patch for HP moonshot ARM cartridges with I2c > > Status in “freeipmi” package in Ubuntu: > Fix Released > Status in “freeipmi” source package in Trusty: > Fix Committed > Status in “freeipmi” package in Debian: > New > > Bug description: > [Impact] > freeipmi is unable to reliable communicate with the BMC on ARM HP > Moonshot cartridges > [Test Case] > > [Regression Potential] > Should be minimal, given the new code only runs in a case that would've > previous resulted in a failure. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1324992 Title: freeipmi patch for HP moonshot ARM cartridges with I2c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+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 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
I loaded the driver manually, now I see the devices but the command fails with "internal system error. See below root@ubuntu:~# ls /dev/i2c-* /dev/i2c-0 /dev/i2c-1 /dev/i2c-2 root@ubuntu:~# bmc-info --no-probing --driver-type=SSIF --driver-address=0x10 --driver-device=/dev/i2c-2 --get-device-id ipmi_cmd_get_device_id: internal system error -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1324992 Title: freeipmi patch for HP moonshot ARM cartridges with I2c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+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 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
I am seeing the error like mentioned by manoj above comment #4 root@ubuntu:~# bmc-info --no-probing --driver-type=SSIF --driver-address=0x10 --driver-device=/dev/i2c-2 --get-device-id --debug = Get Device ID Request = SSIF Header: [ 0h] = lun[ 2b] [ 6h] = net_fn[ 6b] IPMI Command Data: -- [ 1h] = cmd[ 8b] ipmi_cmd_get_device_id: internal system error root@ubuntu:~# -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1324992 Title: freeipmi patch for HP moonshot ARM cartridges with I2c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+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
RE: [Bug 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
You need to manual load the i2c-dev driver Narinder Gupta Kodamati Pradeep Vinesh Reddy wrote: null -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1324992 Title: freeipmi patch for HP moonshot ARM cartridges with I2c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+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 1324992] Re: freeipmi patch for HP moonshot ARM cartridges with I2c
After installing the freeipmi from the proposed repositories, I see the below error ubuntu@ubuntu:~$ sudo bmc-info --no-probing --driver-type=SSIF --driver-address=0x10 --driver-device=/dev/i2c-2 --get-device-id [sudo] password for ubuntu: insufficient permission on driver device '/dev/i2c-2' When I looked into the /dev/ I dont see i2c-2 device. ubuntu@ubuntu:~$ dpkg --list | grep freeipmi ii freeipmi1.1.5-3ubuntu3.1 all GNU implementation of the IPMI protocol ii freeipmi-bmc-watchdog 1.1.5-3ubuntu3.1 armhf GNU implementation of the IPMI protocol - BMC watchdog ii freeipmi-common 1.1.5-3ubuntu3.1 all GNU implementation of the IPMI protocol - common files ii freeipmi-ipmidetect 1.1.5-3ubuntu3.1 armhf GNU IPMI - IPMI node detection tool ii freeipmi-tools 1.1.5-3ubuntu3.1 armhf GNU implementation of the IPMI protocol - tools ii libfreeipmi12 1.1.5-3ubuntu3.1 armhf GNU IPMI - libraries ubuntu@ubuntu:~$ Please let me know if I am missing something. Thanks, Pradeep. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1324992 Title: freeipmi patch for HP moonshot ARM cartridges with I2c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+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 1342000] Re: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw
Hmmm seems this change has slipped through the net. I've ported it over to the utopic kernel. Will review further before uploading. ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- 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/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342000/+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 1352993] Re: pserv.yaml shouldn't need manual configuration to point at your region controller
** Package changed: maas (Ubuntu) => maas ** Tags added: canonical-is -- 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/1352993 Title: pserv.yaml shouldn't need manual configuration to point at your region controller To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1352993/+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 1352923] Re: MAAS 1.5 requires arbitrary high-numbered port connections between cluster and region controllers
** Package changed: maas (Ubuntu) => maas -- 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/1352923 Title: MAAS 1.5 requires arbitrary high-numbered port connections between cluster and region controllers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1352923/+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 1350810] Re: Shift-F2 no longer working in Byobu in Ubuntu 14.10 (utopic) with tmux 1.9
FWIW, I have pushed a test build of tmux_1.9-5ubuntu1~ppa1_source.changes to ppa:kirkland/ppa, that simply reverts upstream commit 193b6bcf36dda3754c99beb0dcc3dfdfceebdb09. Please give that a shot on a Utopic/tmux-1.9 system, and report back here if that gets your Shift-F* hotkeys working again. I'll talk to upstream about that, if you can confirm it solves the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tmux in Ubuntu. https://bugs.launchpad.net/bugs/1350810 Title: Shift-F2 no longer working in Byobu in Ubuntu 14.10 (utopic) with tmux 1.9 To manage notifications about this bug go to: https://bugs.launchpad.net/tmux/+bug/1350810/+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 1350813] Re: New windows don't open in the current working directory
** Changed in: byobu (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tmux in Ubuntu. https://bugs.launchpad.net/bugs/1350813 Title: New windows don't open in the current working directory To manage notifications about this bug go to: https://bugs.launchpad.net/tmux/+bug/1350813/+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 1347954] Re: build slapd-sha2 module for strong passwords
awesome, many thanks Ryan, super quick! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1347954 Title: build slapd-sha2 module for strong passwords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1347954/+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 1287224] Re: MAAS random generated hostnames are not pronounceable
You can find a representative sample at http://paste.ubuntu.com/7963780/ -- 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/1287224 Title: MAAS random generated hostnames are not pronounceable To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287224/+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 1287224] Re: MAAS random generated hostnames are not pronounceable
** Changed in: maas Status: Opinion => In Progress ** Changed in: maas Assignee: (unassigned) => Dustin Kirkland (kirkland) -- 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/1287224 Title: MAAS random generated hostnames are not pronounceable To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287224/+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 1287224] Re: MAAS random generated hostnames are not pronounceable
We had a discussion with sabdfl at the cloud sprint this week, and in fact, he is 100% behind this change. See this branch: lp:~kirkland/maas/1287224 revno: 2652 fixes bug: https://launchpad.net/bugs/1287224 committer: Dustin Kirkland branch nick: maas timestamp: Tue 2014-08-05 20:35:26 +0200 message: Enable MAAS to produce friendly, pronounceable hostnames, LP: #1287224 Ship two culled word lists -- 1,315 adjectives, and 977 nouns. This gives us a possible 1,284,755 combinations of adjective-noun, which is more than enough to cover any Class B, /12 network (255.240.0.0) and its 1,048,576 unique IP addresses. You might notice that this model is quite similar to Ubuntu's friendly release naming scheme, such as "Warty Warthog". These word lists are shipped and installed in /etc/maas/adjectives.txt and /etc/maas/nouns.txt, such that they are easily customized, edited, or overwritten by any MAAS administrator. The modified code updates the generate_hostname() hostname function to try and generate an 'adjective-noun' hostname, but if any exception occurs (such as a wordlist read exception), it will fall back to the legacy 5-random-non-ambiguous-character hostname. A test is included to ensure that all randomly generated hostnames fit the model of "word hyphen word". However, note that it's probably not able to open and read the word lists, since they're installed on disk. -- 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/1287224 Title: MAAS random generated hostnames are not pronounceable To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287224/+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 1353011] Re: Trusty's "crm configure load" fails to update cluster configuration
Created one public PPA so the SRU proposal can be tested before asking for sponsorship: https://launchpad.net/~inaddy/+archive/ubuntu/lp1353011 # apt-add-repository ppa:inaddy/lp1353011 # apt-get update # apt-get dist-upgrade * attention: this will replace current trusty crmsh version: crmsh_1.2.5+hg1034-1ubuntu3 * to version: crmsh_1.2.5+hg1034-1ubuntu4 * because versioning is already ready for the SRU proposal. * to get back to current trusty version you will have to remove * the crmsh by hand and install it again (maybe ignoring * dependencies if you don't want to reinstall hole clustering * packages). After upgrading to version: crmsh_1.2.5+hg1034-1ubuntu4 Anyone who is suffering for this issue can try to # "crm configure load ..." again. Tks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to crmsh in Ubuntu. https://bugs.launchpad.net/bugs/1353011 Title: Trusty's "crm configure load" fails to update cluster configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1353011/+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 1353011] Re: Trusty's "crm configure load" fails to update cluster configuration
## After applying the fix I could successfully load my previous cluster configuration: root@trustycluster01:~# crm configure load xml replace ./cluster.xml root@trustycluster01:~# crm resource crm(live)resource# list p_fence_cluster01 (stonith:external/vcenter): Stopped p_fence_cluster02 (stonith:external/vcenter): Stopped p_fence_cluster03 (stonith:external/vcenter): Stopped p_fence_cluster04 (stonith:external/vcenter): Stopped clusterip (ocf::heartbeat:IPaddr2): Started crm(live)resource# start all ERROR: 2: resource all does not exist crm(live)resource# start p_fence_cluster01 crm(live)resource# start p_fence_cluster02 crm(live)resource# start p_fence_cluster03 crm(live)resource# start p_fence_cluster04 crm(live)resource# end crm(live)# end crm(live)# quit bye ## and resources were active again: root@trustycluster01:~# crm_mon -1 Last updated: Tue Aug 5 14:22:38 2014 Last change: Tue Aug 5 14:22:20 2014 via cibadmin on trustycluster02 Stack: corosync Current DC: trustycluster02 (739246088) - partition with quorum Version: 1.1.10-42f2063 4 Nodes configured 5 Resources configured Online: [ trustycluster01 trustycluster02 trustycluster03 trustycluster04 ] p_fence_cluster01 (stonith:external/vcenter): Started trustycluster02 p_fence_cluster02 (stonith:external/vcenter): Started trustycluster01 p_fence_cluster03 (stonith:external/vcenter): Started trustycluster04 p_fence_cluster04 (stonith:external/vcenter): Started trustycluster03 clusterip (ocf::heartbeat:IPaddr2): Started trustycluster01 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to crmsh in Ubuntu. https://bugs.launchpad.net/bugs/1353011 Title: Trusty's "crm configure load" fails to update cluster configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1353011/+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 1353011] Re: Trusty's "crm configure load" fails to update cluster configuration
** Description changed: It was brought to me (~inaddy) the following situation: "" * Environment Ubuntu 14.04 LTS Pacemaker 1.1.10+git20130802-1ubuntu2 * Issue I cannot use "crm configure load update". It cause an error as below. # crm configure load update settings.crm ERROR: elements cib-bootstrap-options already exist My pacemaker settings. property no-quorum-policy="ignore" \ stonith-enabled="true" \ startup-fencing="false" \ crmd-transition-delay="2s" rsc_defaults resource-stickiness="INFINITY" \ migration-threshold="1" group grpStonith1 \ prmStonith1-2 group grpStonith2 \ prmStonith2-2 fencing_topology \ A1MB101: prmStonith1-2 \ A1MB102: prmStonith2-2 primitive prmStonith1-2 stonith:external/ssh \ params \ pcmk_reboot_timeout="300s" \ hostlist="A1MB101" \ op start interval="0s" timeout="60s" on-fail="restart" \ op monitor interval="10s" timeout="60s" on-fail="restart" \ op stop interval="0s" timeout="60s" on-fail="ignore" primitive prmStonith2-2 stonith:external/ssh \ params \ pcmk_reboot_timeout="300s" \ hostlist="A1MB102" \ op start interval="0s" timeout="60s" on-fail="restart" \ op monitor interval="10s" timeout="60s" on-fail="restart" \ op stop interval="0s" timeout="60s" on-fail="ignore" location rsc_location-grpStonith1 grpStonith1 \ rule -INFINITY: #uname eq A1MB101 location rsc_location-grpStonith2 grpStonith2 \ rule -INFINITY: #uname eq A1MB102 * Request 1. It may be a bug. Can you fix it? I found this thread. http://www.gossamer-threads.com/lists/linuxha/dev/87790 "" I was able to reproduce the following error: root@trustycluster01:~# crm configure load xml replace ./cluster.xml ERROR: elements 739246090,739246088,739246089,739246087,cib-bootstrap-options already exist Exporting and trying to re-import my personal cluster configuration. And based on the public discussion (when this was reported): http://www.gossamer-threads.com/lists/linuxha/dev/87790 I could see developer "fixed" this behavior on Aug 8 2013. After digging a little on crm configure load I could find that this error came from a file on the package crmsh and on crmsh upstream tree I found this: inaddy@trusty.00070402:/bugs/00070402/sources/upstream/crmsh$ git log --since 2013-08-06 --until 2013-08-12 --pretty=format:'%ad %an | %h ||| %s' --date=local --date-order --graph | cat * Thu Aug 8 09:55:23 2013 Dejan Muhamedagic | b146349 ||| Medium: cibconf: repair configure load update - So I'm assuming this will fix the issue... Opening the public bug for - the fix. + So I'm assuming (and testing right now) this will fix the issue... + Opening the public bug for the fix I'll provide after tests. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to crmsh in Ubuntu. https://bugs.launchpad.net/bugs/1353011 Title: Trusty's "crm configure load" fails to update cluster configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1353011/+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 1353011] [NEW] Trusty's "crm configure load" fails to update cluster configuration
Public bug reported: It was brought to me (~inaddy) the following situation: "" * Environment Ubuntu 14.04 LTS Pacemaker 1.1.10+git20130802-1ubuntu2 * Issue I cannot use "crm configure load update". It cause an error as below. # crm configure load update settings.crm ERROR: elements cib-bootstrap-options already exist My pacemaker settings. property no-quorum-policy="ignore" \ stonith-enabled="true" \ startup-fencing="false" \ crmd-transition-delay="2s" rsc_defaults resource-stickiness="INFINITY" \ migration-threshold="1" group grpStonith1 \ prmStonith1-2 group grpStonith2 \ prmStonith2-2 fencing_topology \ A1MB101: prmStonith1-2 \ A1MB102: prmStonith2-2 primitive prmStonith1-2 stonith:external/ssh \ params \ pcmk_reboot_timeout="300s" \ hostlist="A1MB101" \ op start interval="0s" timeout="60s" on-fail="restart" \ op monitor interval="10s" timeout="60s" on-fail="restart" \ op stop interval="0s" timeout="60s" on-fail="ignore" primitive prmStonith2-2 stonith:external/ssh \ params \ pcmk_reboot_timeout="300s" \ hostlist="A1MB102" \ op start interval="0s" timeout="60s" on-fail="restart" \ op monitor interval="10s" timeout="60s" on-fail="restart" \ op stop interval="0s" timeout="60s" on-fail="ignore" location rsc_location-grpStonith1 grpStonith1 \ rule -INFINITY: #uname eq A1MB101 location rsc_location-grpStonith2 grpStonith2 \ rule -INFINITY: #uname eq A1MB102 * Request 1. It may be a bug. Can you fix it? I found this thread. http://www.gossamer-threads.com/lists/linuxha/dev/87790 "" I was able to reproduce the following error: root@trustycluster01:~# crm configure load xml replace ./cluster.xml ERROR: elements 739246090,739246088,739246089,739246087,cib-bootstrap-options already exist Exporting and trying to re-import my personal cluster configuration. And based on the public discussion (when this was reported): http://www.gossamer-threads.com/lists/linuxha/dev/87790 I could see developer "fixed" this behavior on Aug 8 2013. After digging a little on crm configure load I could find that this error came from a file on the package crmsh and on crmsh upstream tree I found this: inaddy@trusty.00070402:/bugs/00070402/sources/upstream/crmsh$ git log --since 2013-08-06 --until 2013-08-12 --pretty=format:'%ad %an | %h ||| %s' --date=local --date-order --graph | cat * Thu Aug 8 09:55:23 2013 Dejan Muhamedagic | b146349 ||| Medium: cibconf: repair configure load update So I'm assuming this will fix the issue... Opening the public bug for the fix. ** Affects: crmsh (Ubuntu) Importance: Undecided Assignee: Rafael David Tinoco (inaddy) Status: Confirmed ** Tags: crmsh pacemaker trusty ** Description changed: - it was brought to me the following situation: + It was brought to me (~inaddy) the following situation: "" - * Environment - Ubuntu 14.04 LTS - Pacemaker 1.1.10+git20130802-1ubuntu2 + * Environment + Ubuntu 14.04 LTS + Pacemaker 1.1.10+git20130802-1ubuntu2 - * Issue - I cannot use "crm configure load update". - It cause an error as below. + * Issue + I cannot use "crm configure load update". + It cause an error as below. - # crm configure load update settings.crm - ERROR: elements cib-bootstrap-options already exist + # crm configure load update settings.crm + ERROR: elements cib-bootstrap-options already exist + My pacemaker settings. + + property no-quorum-policy="ignore" \ + stonith-enabled="true" \ + startup-fencing="false" \ + crmd-transition-delay="2s" - My pacemaker settings. - - property no-quorum-policy="ignore" \ - stonith-enabled="true" \ - startup-fencing="false" \ - crmd-transition-delay="2s" + rsc_defaults resource-stickiness="INFINITY" \ + migration-threshold="1" - rsc_defaults resource-stickiness="INFINITY" \ - migration-threshold="1" + group grpStonith1 \ + prmStonith1-2 - group grpStonith1 \ - prmStonith1-2 + group grpStonith2 \ + prmStonith2-2 - group grpStonith2 \ - prmStonith2-2 + fencing_topology \ + A1MB101: prmStonith1-2 \ + A1MB102: prmStonith2-2 - fencing_topology \ - A1MB101: prmStonith1-2 \ - A1MB102: prmStonith2-2 + primitive prmStonith1-2 stonith:external/ssh \ + params \ + pcmk_reboot_timeout="300s" \ + hostlist="A1MB101" \ + op start interval="0s" timeout="60s" on-fail="restart" \ + op monitor interval="10s" timeout="60s" on-fail="restart" \ + op stop interval="0s" timeout="60s" on-fail="ignore" - primitive prmStonith1-2 stonith:external/ssh \ - params \ - pcmk_reboot_timeout="300s" \ - hostlist="A1MB101" \ - op start interval="0s" timeout="60s" on-fail="restart" \ - op monitor interval="10s" timeout="60s" on-fail="restart" \ - op stop interval="0s" timeout="60s" on-fail="ignore" + primitive prmStonith2-2 stonith:external/ssh \ + params \ + pcmk_reboot_timeout="300s" \ + hostlist=
[Bug 1352993] [NEW] pserv.yaml shouldn't need manual configuration to point at your region controller
Public bug reported: When a MAAS cluster controller is configured to talk to a central region controller, it should be trivial to do in one place and have everything else fall out from that. RIght now the "generator" setting is a URL that includes the string "localhost". I just had to run around and change that to the hostname of our region controller, but other pieces of the cluster controller clearly already knew to talk to this host. This is a poor default, and should probably be negotiated via the celery service if nothing is specified in /etc/. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 5 17:12:15 2014 InstallationDate: Installed on 2014-05-29 (67 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1352993 Title: pserv.yaml shouldn't need manual configuration to point at your region controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1352993/+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 1251563] Re: netstat command returns nozero even if successively executing
** Branch linked: lp:ubuntu/trusty-proposed/net-tools -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1251563 Title: netstat command returns nozero even if successively executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1251563/+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 1343407] Update Released
The verification of the Stable Release Update for ipmitool has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1343407 Title: Add support for Dell PowerEdge 13G servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+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 1311919] Re: [SRU] pressing F5 throws errors about windows.tmux missing
This bug was fixed in the package byobu - 5.77-0ubuntu1.2 --- byobu (5.77-0ubuntu1.2) trusty-proposed; urgency=medium * usr/bin/byobu-ctrl-a.in: LP: #1274720 - cherry pick upstream r2338, r2363 - revert r2317, as this is breaking ctrl-a in byobu-screen in a bad way + add bindkey line back, this line is *essential*; there was a syntax error in it previously, but removing the line was not the correct fix; fix a missing double quote in last upload * usr/bin/byobu-janitor.in: LP: #1311919 - cherry pick upstream r2337 - ensure that windows.tmux exists; fixes nasty warning with F5 -- Dustin KirklandWed, 23 Apr 2014 18:28:16 -0500 ** Changed in: byobu (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1311919 Title: [SRU] pressing F5 throws errors about windows.tmux missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1311919/+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 1274720] Re: [SRU] screen server process can be crashed by byobu
This bug was fixed in the package byobu - 5.77-0ubuntu1.2 --- byobu (5.77-0ubuntu1.2) trusty-proposed; urgency=medium * usr/bin/byobu-ctrl-a.in: LP: #1274720 - cherry pick upstream r2338, r2363 - revert r2317, as this is breaking ctrl-a in byobu-screen in a bad way + add bindkey line back, this line is *essential*; there was a syntax error in it previously, but removing the line was not the correct fix; fix a missing double quote in last upload * usr/bin/byobu-janitor.in: LP: #1311919 - cherry pick upstream r2337 - ensure that windows.tmux exists; fixes nasty warning with F5 -- Dustin KirklandWed, 23 Apr 2014 18:28:16 -0500 ** Changed in: byobu (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1274720 Title: [SRU] screen server process can be crashed by byobu To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1274720/+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 1274720] Update Released
The verification of the Stable Release Update for byobu has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1274720 Title: [SRU] screen server process can be crashed by byobu To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1274720/+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 1311919] Update Released
The verification of the Stable Release Update for byobu has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1311919 Title: [SRU] pressing F5 throws errors about windows.tmux missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1311919/+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 1343407] Re: Add support for Dell PowerEdge 13G servers
This bug was fixed in the package ipmitool - 1.8.13-1ubuntu0.1 --- ipmitool (1.8.13-1ubuntu0.1) trusty; urgency=low * debian/patches/113_add-support-for-Dell-PowerEdge-13G.patch: Add support for Dell PowerEdge 13G (LP: #1343407) -- Kent BaxleyThu, 17 Jul 2014 11:00:26 -0500 ** Changed in: ipmitool (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1343407 Title: Add support for Dell PowerEdge 13G servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+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 1341638] Update Released
The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1341638 Title: New upstream bugfix release 1.0.5 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1341638/+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 1341638] Re: New upstream bugfix release 1.0.5 (LXC MRE)
This bug was fixed in the package lxc - 1.0.5-0ubuntu0.1 --- lxc (1.0.5-0ubuntu0.1) trusty; urgency=medium * New upstream bugfix release. (MRE tracking bug: LP: #1341638) - Changelog at: https://linuxcontainers.org/news/ * Sync packaging with utopic: - Enable ppc64el adt as we now have ppc64el images available for download. -- Stephane GraberMon, 14 Jul 2014 11:49:20 -0400 ** Changed in: lxc (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1341638 Title: New upstream bugfix release 1.0.5 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1341638/+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 1251563] Re: netstat command returns nozero even if successively executing
Hello Vincent, or anyone else affected, Accepted net-tools into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/net- tools/1.60-25ubuntu2.1 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! ** Changed in: net-tools (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1251563 Title: netstat command returns nozero even if successively executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1251563/+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 1350435] Re: tcg.c:1693: tcg fatal error
Well, it won't make anything any worse, so it's your call based on how much it actually improves your failure rate I guess. -- 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/1350435 Title: tcg.c:1693: tcg fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1350435/+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 1257186] Re: memory leakage messages
Just updated to latest samba on trusty repositories today as a new samba was released and this is re-broken. -- 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/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+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 1342000] Re: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- 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/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342000/+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 1350435] Re: tcg.c:1693: tcg fatal error
Right, I can absolutely understand that. The question would I suppose be whether you think this is a completely unreasonable thing to put in a distro patch; I think SUSE are doing so for basically the same reason we would be, that is, a setup such as PPAs where virtualisation isn't available directly on the architecture in question but we can use qemu- user to run foreign-arch binaries reasonably transparently. My understanding is that this patch would make a pretty huge dent in our failure rate for that setup. -- 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/1350435 Title: tcg.c:1693: tcg fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1350435/+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 1307215] Re: destroy-environment fails to clear lxc containers
The fix for this is applied in lxc's git HEAD. ** Changed in: lxc (Ubuntu) Status: Triaged => Fix Committed -- 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/1307215 Title: destroy-environment fails to clear lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307215/+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 1346166] Re: [SRU] 0.80.5 point release
Hello James, or anyone else affected, Accepted ceph into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ceph/0.80.5-0ubuntu0.14.04.1 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! ** Changed in: ceph (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1346166 Title: [SRU] 0.80.5 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1346166/+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 1349433] Re: AppArmor breaks seccomp @ Apache mpm-itk
I add mailman, as I think this issue affects mailman's python scripts when running with apache-mpm-itk. Running any of the python's scripts on a site protected with apache-mpm- itk gives a "Operation not permitted" error ** Also affects: mailman (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in Ubuntu. https://bugs.launchpad.net/bugs/1349433 Title: AppArmor breaks seccomp @ Apache mpm-itk To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1349433/+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 1341638] Re: New upstream bugfix release 1.0.5 (LXC MRE)
I've been running LXC 1.0.5 for a while here without any issue, the upstream test suite and our adt tests have all passed, marking verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1341638 Title: New upstream bugfix release 1.0.5 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1341638/+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 1342000] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1342000 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (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/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342000/+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 1352923] Re: MAAS 1.5 requires arbitrary high-numbered port connections between cluster and region controllers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: maas (Ubuntu) Status: New => Confirmed -- 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/1352923 Title: MAAS 1.5 requires arbitrary high-numbered port connections between cluster and region controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1352923/+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 1352923] [NEW] MAAS 1.5 requires arbitrary high-numbered port connections between cluster and region controllers
Public bug reported: MAAS's separation of regions and clusters allows network admins to centralise policy and interface while erecting management presence in isolated networks. This feature is most useful in situations where the firewall policy walls off clusters more strictly. MAAS 1.5 seems to require that the cluster controllers call back to the region controller via arbitrary high-numbered ports. I checked our installation and could not find any specification of whcih ports in the code or our local configuration, and only spotted them because our firewall denied this traffic and caused node commissioning to fail. I'm not familiar enough with twisted or the MAAS source enough to work out why this is, but I suspected there were no defined ports when I found the comment here: http://bazaar.launchpad.net/~maas- maintainers/maas/1.5/view/head:/src/maasserver/rpc/regionservice.py#L177 """Start listening on an ephemeral port.""" Unfortunately the exact situation that makes splitting out your cluster controllers attractive is going to make this behaviour a deal-breaker. Getting all unprivileged ports opened on a firewall is not something to be done lightly. I do not believe that MAAS 1.4 exhibited this behaviour. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 5 15:24:02 2014 InstallationDate: Installed on 2014-05-29 (67 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug canonical-is trusty -- 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/1352923 Title: MAAS 1.5 requires arbitrary high-numbered port connections between cluster and region controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1352923/+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 1350352] Re: nova-novncproxy and nova-spiceproxy need patched websockify
** No longer affects: nova (Ubuntu Trusty) ** No longer affects: nova (Ubuntu Utopic) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to websockify in Ubuntu. https://bugs.launchpad.net/bugs/1350352 Title: nova-novncproxy and nova-spiceproxy need patched websockify To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/websockify/+bug/1350352/+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 1352794] Re: Null pointer dereference in mmu_set_spte.isra
** Package changed: kvm (Ubuntu) => linux (Ubuntu) ** Summary changed: - Null pointer dereference in mmu_set_spte.isra + Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic -- 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/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+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 1342000] Re: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw
I notice that in the netg3 command, one drive is specified as scsi-hd, while the other is virtio-blk-pci. Was that intended? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: Incomplete => New -- 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/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342000/+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 1292548] Re: smb.conf contains valid users = %S in [global]
*** This bug is a duplicate of bug 1261873 *** https://bugs.launchpad.net/bugs/1261873 You also might want this. === chuck@ubuntucomp:~/share$ cat /etc/os-release NAME="Ubuntu" VERSION="14.04, Trusty Tahr" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 14.04 LTS" VERSION_ID="14.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; === -- 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/1292548 Title: smb.conf contains valid users = %S in [global] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1292548/+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 1292548] Re: smb.conf contains valid users = %S in [global]
*** This bug is a duplicate of bug 1261873 *** https://bugs.launchpad.net/bugs/1261873 I can confirm this bug on a new install of 14.04 LTS under a Virtual Machine (vSphere). # Samba 4.1.6-Ubuntu (via samba -V) # Server: Ubuntu 14.04 LTS is set up as a VM under vSphere # Client: Windows 7 with Putty and an ssh connection. === chuck@ubuntucomp:/etc/samba$ smbstatus Samba version 4.1.6-Ubuntu PID Username Group Machine --- Failed to initialize session_global: NT_STATUS_ACCESS_DENIED Service pid machine Connected at --- Failed to initialize session_global: NT_STATUS_ACCESS_DENIED Failed to traverse sessions: NT_STATUS_ACCESS_DENIED No locked files === -- 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/1292548 Title: smb.conf contains valid users = %S in [global] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1292548/+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 1008385] Re: apache-mpm-itk writes wrong process name in /proc/$$/status
This patch doesn't appear to have been committed upstream. What's the submission or upstream inclusion status of this, please? Removing the mpm-itk task as it seems clear that this bug is in mod- perl2. If this is wrong, please speak up. ** No longer affects: apache2-mpm-itk (Ubuntu) ** Summary changed: - apache-mpm-itk writes wrong process name in /proc/$$/status + libapache2-mod-perl2 writes wrong process name in /proc/$$/status ** Package changed: apache2 (Ubuntu) => libapache2-mod-perl2 (Ubuntu) ** Changed in: libapache2-mod-perl2 (Ubuntu) Status: Confirmed => Triaged ** Tags added: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1008385 Title: libapache2-mod-perl2 writes wrong process name in /proc/$$/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-perl2/+bug/1008385/+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 1329719] Re: cloud-init does not bring up all bridge interfaces created with openvswitch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openvswitch (Ubuntu) Status: New => Confirmed -- 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/1329719 Title: cloud-init does not bring up all bridge interfaces created with openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1329719/+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 1327147] Re: openvswitch-datapath-dkms 2.0.1+git20140120-0ubuntu2: openvswitch kernel module failed to build
*** This bug is a duplicate of bug 1266749 *** https://bugs.launchpad.net/bugs/1266749 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openvswitch (Ubuntu) Status: New => Confirmed -- 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/1327147 Title: openvswitch-datapath-dkms 2.0.1+git20140120-0ubuntu2: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1327147/+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 1008385] Re: apache-mpm-itk writes wrong process name in /proc/$$/status
** Changed in: libapache2-mod-perl2 (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1008385 Title: apache-mpm-itk writes wrong process name in /proc/$$/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1008385/+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 1319595] Re: upstart script ignores some php-fpm.conf parameters, cannot be bypassed in preference of SystemV init script.
> This causes several options from the config file to be ignored Well, I see only "error_log" being ignore in this case and not "several options". You should really fill this bug with upstream (in PHP bug tracker), since it's wrong behaviour on FPM side to ignore configuration settings. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1319595 Title: upstart script ignores some php-fpm.conf parameters, cannot be bypassed in preference of SystemV init script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1319595/+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 1008385] Re: apache-mpm-itk writes wrong process name in /proc/$$/status
A patch for this issue is on the Fedora bug tracker: https://bugzilla.redhat.com/attachment.cgi?id=567625&action=diff ** Bug watch added: Debian Bug tracker #754702 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754702 ** Also affects: libapache2-mod-perl2 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754702 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #782369 https://bugzilla.redhat.com/show_bug.cgi?id=782369 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=782369 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1008385 Title: apache-mpm-itk writes wrong process name in /proc/$$/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1008385/+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 1352794] Re: Null pointer dereference in mmu_set_spte.isra
** Description changed: Dear all, We faced a kernel oops on KVM from a null pointer derefence on one of - our hypervisors (running several KVM VMs). This lead us to a serie of + our hypervisors (running several KVM VMs). This led us to a serie of kernel oops affecting all the VMs and finally, the host crash. We couldn't really establish where from the first oops was comming (in order to reproduce the crash). You'll find attach the extract of syslog where you have the really first oops, and all the followings. We're using Ubuntu 12.04LTS. We're using latest releases available on it, including for KVM. We're using kernel 3.8 due to hardware constraints. And we're using kernel 3.8.0-33-generic due to regressions in newer kernels (not yet reported). -- 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/1352794 Title: Null pointer dereference in mmu_set_spte.isra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1352794/+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 1352794] [NEW] Null pointer dereference in mmu_set_spte.isra
Public bug reported: Dear all, We faced a kernel oops on KVM from a null pointer derefence on one of our hypervisors (running several KVM VMs). This lead us to a serie of kernel oops affecting all the VMs and finally, the host crash. We couldn't really establish where from the first oops was comming (in order to reproduce the crash). You'll find attach the extract of syslog where you have the really first oops, and all the followings. We're using Ubuntu 12.04LTS. We're using latest releases available on it, including for KVM. We're using kernel 3.8 due to hardware constraints. And we're using kernel 3.8.0-33-generic due to regressions in newer kernels (not yet reported). ** Affects: kvm (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Kernel oops" https://bugs.launchpad.net/bugs/1352794/+attachment/4170197/+files/syslog -- 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/1352794 Title: Null pointer dereference in mmu_set_spte.isra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1352794/+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 1346825] Re: Winbind panic
Still doing this with Winbind Version: 2:4.1.6+dfsg-1ubuntu2.14.04.3 -- 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/1346825 Title: Winbind panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1346825/+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 1350435] Re: tcg.c:1693: tcg fatal error
I think it's likely to happen eventually; it depends rather on the balance between this and other work priorities (at least if it's going to be Linaro doing the work). Regardless, I'm not taking hacky workarounds like this into mainline (hacks are hard to get out once you let them in, and they remove any motivation anybody might have had for fixing things properly). -- 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/1350435 Title: tcg.c:1693: tcg fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1350435/+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 1330408] Re: ucfr fails if smb.conf is not owned by samba
** Branch linked: lp:~filip-sohajek/ubuntu/utopic/samba/fix-for-1330408 -- 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/1330408 Title: ucfr fails if smb.conf is not owned by samba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1330408/+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 1307215] Re: destroy-environment fails to clear lxc containers
** Tags added: ubuntu-engineering ** Changed in: juju-core Importance: Medium => High ** Changed in: juju-core Milestone: None => next-stable -- 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/1307215 Title: destroy-environment fails to clear lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307215/+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 1350435] Re: tcg.c:1693: tcg fatal error
Peter: While this is true, is it actually likely to happen? I thought in our conversations in the past (when I previously attempted to escalate this class of problems via Linaro) it had been fairly clear that this was a very difficult task that isn't likely to be scheduled for the foreseeable future. ** Changed in: launchpad-buildd Status: New => Triaged ** Changed in: launchpad-buildd Importance: Undecided => High -- 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/1350435 Title: tcg.c:1693: tcg fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1350435/+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
