[Bug 832507] Re: console.log grows indefinitely
I think the blueprint https://blueprints.launchpad.net/nova/+spec /serial-ports is just a workaround for this bug, and currently we have no way to disable console.log . -- 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/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+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 1378738] [NEW] guest os boot stuck with mount operation error
Public bug reported:
I'm trying to migrate an OS running on a physical machine to an LXC container,
but no luck so far. Right now the system gets stuck somewhere during lxc-start:
...
* Stopping cgroup management proxy ...done.
* Starting load modules from /etc/modules ...done.
* Stopping Mount network filesystems ...done.
* Starting set sysctls from /etc/sysctl.conf ...done.
* Stopping set sysctls from /etc/sysctl.conf ...done.
* Stopping load modules from /etc/modules ...done.
* Starting configure network device ...done.
* Starting Bridge socket events into upstart ...done.
hangs indefinitely here
Both host and guest are running ubuntu 14.04 LTS and same guest boots
properly via VirtualBox... kern.log shows some issues with mounts:
Oct 7 10:35:45 ares kernel: [138643.960789] device veth0RG5HU entered
promiscuous mode
Oct 7 10:35:45 ares kernel: [138643.961450] IPv6: ADDRCONF(NETDEV_UP):
veth0RG5HU: link is not ready
Oct 7 10:35:45 ares kernel: [138643.987832] EXT4-fs (dm-5): couldn't mount as
ext3 due to feature incompatibilities
Oct 7 10:35:45 ares kernel: [138643.987967] EXT4-fs (dm-5): couldn't mount as
ext2 due to feature incompatibilities
Oct 7 10:35:45 ares kernel: [138643.988322] EXT4-fs (dm-5): mounted filesystem
with ordered data mode. Opts: (null)
Oct 7 10:35:45 ares kernel: [138644.002660] IPv6: ADDRCONF(NETDEV_CHANGE):
veth0RG5HU: link becomes ready
Oct 7 10:35:45 ares kernel: [138644.002702] lxcbr0: port 1(veth0RG5HU) entered
forwarding state
Oct 7 10:35:45 ares kernel: [138644.002719] lxcbr0: port 1(veth0RG5HU) entered
forwarding state
Oct 7 10:35:46 ares kernel: [138644.340780] type=1400
audit(1412670946.254:113): apparmor=DENIED operation=mount info=failed
type match error=-13 profile=lxc-container-default
name=/run/cgmanager/fs/none,name=systemd/ pid=399 comm=cgmanager
fstype=cgroup srcname=none,name=systemd flags=rw
Oct 7 10:36:00 ares kernel: [138659.015558] lxcbr0: port 1(veth0RG5HU) entered
forwarding state
Here is the container's configuration file:
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.utsname = myvm
lxc.autodev = 1
lxc.tty = 4
lxc.pts = 1024
lxc.rootfs = /dev/mapper/ubuntu--vmvg-lvroot
lxc.arch = x86_64
lxc.cap.drop = sys_module mac_admin
#lxc.aa_profile = lxc-container-default-with-mounting
lxc.cgroup.devices.deny = a
# Allow any mknod (but not using the node)
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
#lxc.cgroup.devices.allow = c 4:0 rwm
#lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
#fuse
lxc.cgroup.devices.allow = c 10:229 rwm
#tun
lxc.cgroup.devices.allow = c 10:200 rwm
#full
lxc.cgroup.devices.allow = c 1:7 rwm
#hpet
lxc.cgroup.devices.allow = c 10:228 rwm
#kvm
lxc.cgroup.devices.allow = c 10:232 rwm
#lxc.cgroup.devices.allow = b 7:* rwm
Any suggestions?
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1378738
Title:
guest os boot stuck with mount operation error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1378738/+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 1090223] Re: The directory ubuntu-kvm disappeared after creating vms failed
Well, today is Oct 8th 2014 and I just lost three VMs because of this. That the tyrget folder (/var/lib/libvirt/images) wasn't backed-up is my fault but the documentation SHOULD BE CLEARER about what happens when you pass the -o option to vmbuilder. And yes, overwriting the whole directory is not that clever when overwriting the disk image with the same name is enough. Just lost hours (even days) worth of hard work :-( -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1090223 Title: The directory ubuntu-kvm disappeared after creating vms failed To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1090223/+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
[Blueprint servercloud-u-openstack-charms] OpenStack Charm work for Utopic
Blueprint changed by James Page: Work items changed: Work items for ubuntu-14.05: [gnuoy] charm-helpers unit testing: DONE Work items for ubuntu-14.06: [mikemc] Simplestreams image sync charm: DONE [niedbalski] swift-storage block device persistence through reboots: DONE [gnuoy] Split neutron API from nova-cloud-controller: DONE [gnuoy] New neutron-openvswitch subordinate charm: DONE [corey.bryant] amulet testing approach for openstack charms: DONE [james-page] network reference architecture for openstack charms: DONE [james-page] nova-compute-vmware charm: DONE [james-page] cinder-vmware charm: DONE [zulcss] nova-compute-power charm: DONE Work items for ubuntu-14.07: [corey.bryant] amulet tests - keystone: DONE [corey.bryant] amulet tests - quantum-gateway: DONE [1chb1n] amulet tests - glance: DONE [corey.bryant] amulet tests - nova-compute: DONE [corey.bryant] amulet tests - nova-cloud-controller: DONE [corey.bryant] amulet tests - swift-proxy, swift-storage: DONE [james-page] Multiple network support across openstack charms: DONE Backport haproxy 1.5.x to trusty: DONE Work items for ubuntu-14.09: [james-page] HTTPS support with network-split configurations: DONE [james-page] hacluster charm updates to support reconfiguration: DONE amulet tests - cinder: DONE [corey.bryant] amulet tests - ceph-*: DONE [james-page] Updates to neutron charms for hyper-v integration: DONE [xianghui] Add IPv6 support to the charms: DONE Enable haproxy backport for 14.04 (supporting IPv6 backends + TLS): DONE Work items: [james-page] nvp-transport-node - nsx-transport-node rename: INPROGRESS - worker configuration - cinder, glance, keystone, neutron-api: INPROGRESS + worker configuration - cinder, glance, keystone, neutron-api: DONE juno release review across openstack charms: INPROGRESS Add support to mysql charm for network-splits: TODO Add support to heat charm for network-splits: POSTPONED Add support to mongodb charm for network-splits: TODO [james-page] Charm developer documentation: POSTPONED [james-page] Charm template for charm-tools: POSTPONED swift-proxy unit testing: POSTPONED nova-compute unit testing: POSTPONED nova-cloud-controller unit testing: POSTPONED HA cluster in-depth monitoring: POSTPONED [hopem] Ephemeral ceph backend for nova-compute: INPROGRESS [gnuoy] Spice/VNC support in nova charms: DONE Nagios nrpe sub-ordinate support for OpenStack charms: POSTPONED (stretch) MS-SQLServer as a backend for OpenStack: POSTPONED [corey.bryant] keystone deploy from git: INPROGRESS make openstack-charm-testing a project: TODO -- OpenStack Charm work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-openstack-charms -- 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 1377142] Re: Bcache doesn't allow full unregistering without rebooting
There does not seem to be clear documentation on this. Just a note that from your description I was not completely sure whether you did unmount before starting the release procedure. I would say unmount is a must. Doing so, I also ended up in the state where bcache0 still existed. But I was able to get rid of that by echo 1 /sys/block/bcache0/bcache/stop -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+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 1377130] Re: Crash at creation of bcache if caching size backing size
+1 on the fail to reproduce. Followed the steps and everything worked without issues (using kvm/qemu VM with emulated devices and even sda being backed by a real ssd, but I am not sure the difference gets propagated). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377130 Title: Crash at creation of bcache if caching size backing size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377130/+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 1371291] Re: FTBFS caused by PEP 466
** Changed in: python-eventlet (Ubuntu) Importance: Undecided = High ** Changed in: python-eventlet (Ubuntu) Milestone: None = ubuntu-14.10 ** Also affects: python-eventlet (Ubuntu Utopic) Importance: High Status: Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-eventlet in Ubuntu. https://bugs.launchpad.net/bugs/1371291 Title: FTBFS caused by PEP 466 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-eventlet/+bug/1371291/+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 1377142] Re: Bcache doesn't allow full unregistering without rebooting
In fact whether you unmount before stopping the bcache or not doesn't change the behaviour. I did that this way in the description, to show the process. You just stop the caching device with the echo 1 ... But, the backing is still in use, but you have no control over it. Le 08/10/2014 13:15, Stefan Bader a écrit : There does not seem to be clear documentation on this. Just a note that from your description I was not completely sure whether you did unmount before starting the release procedure. I would say unmount is a must. Doing so, I also ended up in the state where bcache0 still existed. But I was able to get rid of that by echo 1 /sys/block/bcache0/bcache/stop -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+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 1377142] Re: Bcache doesn't allow full unregistering without rebooting
Yes you can get rid of bcache0, but you can't re-use the device for anything unless you reboot ( re bcache or just plain fdisk/parted ). Le 08/10/2014 13:15, Stefan Bader a écrit : There does not seem to be clear documentation on this. Just a note that from your description I was not completely sure whether you did unmount before starting the release procedure. I would say unmount is a must. Doing so, I also ended up in the state where bcache0 still existed. But I was able to get rid of that by echo 1 /sys/block/bcache0/bcache/stop -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+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 1377130] Re: Crash at creation of bcache if caching size backing size
Yes you can get rid of bcache0, but you can't re-use the device for anything unless you reboot ( re bcache or just plain fdisk/parted ). In fact whether you unmount before stopping the bcache or not doesn't change the behaviour. I did that this way in the description, to show the process. You just stop the caching device with the echo 1 ... But, the backing is still in use and you have no control over it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377130 Title: Crash at creation of bcache if caching size backing size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377130/+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 1377130] Re: Crash at creation of bcache if caching size backing size
Strange, I can reproduce each time, I'm using the iso: ubuntu-14.10-beta2-desktop-amd64.iso from http://releases.ubuntu.com/utopic/ I'm on utopic, with vrit-manager. Regards. Le 08/10/2014 13:17, Stefan Bader a écrit : +1 on the fail to reproduce. Followed the steps and everything worked without issues (using kvm/qemu VM with emulated devices and even sda being backed by a real ssd, but I am not sure the difference gets propagated). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377130 Title: Crash at creation of bcache if caching size backing size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377130/+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 1378810] [NEW] swift unit tests fail on i386 buildd
Public bug reported:
==
FAIL: test_COPY_account_source_larger_than_max_file_size
(test.unit.proxy.test_mem_server.TestObjectController)
--
Traceback (most recent call last):
File /build/buildd/swift-2.2.0~rc1/test/unit/proxy/test_server.py, line
3577, in test_COPY_account_source_larger_than_max_file_size
resp = controller.COPY(req)
File /usr/lib/python2.7/contextlib.py, line 24, in __exit__
self.gen.next()
File /build/buildd/swift-2.2.0~rc1/test/unit/proxy/test_server.py, line
2989, in controller_context
unused_status_list)
AssertionError: UN-USED STATUS CODES: [200, 200]
begin captured stdout -
proxy-ut ERROR: ERROR with Account server 10.0.0.2:1002/sdc re: Trying to HEAD
/v1/a1:
Traceback (most recent call last):
File /build/buildd/swift-2.2.0~rc1/swift/proxy/controllers/base.py, line
767, in _get_source_and_node
query_string=self.req_query_string)
File /build/buildd/swift-2.2.0~rc1/test/unit/__init__.py, line 765, in
connect
body = static_body or ''
OverflowError: long int too large to convert to int
proxy-ut ERROR: ERROR with Account server 10.0.0.0:1000/sda re: Trying to HEAD
/v1/a1:
Traceback (most recent call last):
File /build/buildd/swift-2.2.0~rc1/swift/proxy/controllers/base.py, line
767, in _get_source_and_node
query_string=self.req_query_string)
File /build/buildd/swift-2.2.0~rc1/test/unit/__init__.py, line 765, in
connect
body = static_body or ''
OverflowError: long int too large to convert to int
proxy-ut ERROR: ERROR with Account server 10.0.0.1:1001/sdb re: Trying to HEAD
/v1/a1:
Traceback (most recent call last):
File /build/buildd/swift-2.2.0~rc1/swift/proxy/controllers/base.py, line
767, in _get_source_and_node
query_string=self.req_query_string)
File /build/buildd/swift-2.2.0~rc1/test/unit/__init__.py, line 765, in
connect
body = static_body or ''
OverflowError: long int too large to convert to int
proxy-ut ERROR: Account HEAD returning 503 for []
- end captured stdout --
Fail immediately, with the given message.
raise self.failureException('UN-USED STATUS CODES: [200, 200]')
==
FAIL: test_COPY_account_source_larger_than_max_file_size
(test.unit.proxy.test_server.TestObjectController)
--
Traceback (most recent call last):
File /build/buildd/swift-2.2.0~rc1/test/unit/proxy/test_server.py, line
3577, in test_COPY_account_source_larger_than_max_file_size
resp = controller.COPY(req)
File /usr/lib/python2.7/contextlib.py, line 24, in __exit__
self.gen.next()
File /build/buildd/swift-2.2.0~rc1/test/unit/proxy/test_server.py, line
2989, in controller_context
unused_status_list)
AssertionError: UN-USED STATUS CODES: [200, 200]
begin captured stdout -
proxy-ut ERROR: ERROR with Account server 10.0.0.2:1002/sdc re: Trying to HEAD
/v1/a1:
Traceback (most recent call last):
File /build/buildd/swift-2.2.0~rc1/swift/proxy/controllers/base.py, line
767, in _get_source_and_node
query_string=self.req_query_string)
File /build/buildd/swift-2.2.0~rc1/test/unit/__init__.py, line 765, in
connect
body = static_body or ''
OverflowError: long int too large to convert to int
proxy-ut ERROR: ERROR with Account server 10.0.0.0:1000/sda re: Trying to HEAD
/v1/a1:
Traceback (most recent call last):
File /build/buildd/swift-2.2.0~rc1/swift/proxy/controllers/base.py, line
767, in _get_source_and_node
query_string=self.req_query_string)
File /build/buildd/swift-2.2.0~rc1/test/unit/__init__.py, line 765, in
connect
body = static_body or ''
OverflowError: long int too large to convert to int
proxy-ut ERROR: ERROR with Account server 10.0.0.1:1001/sdb re: Trying to HEAD
/v1/a1:
Traceback (most recent call last):
File /build/buildd/swift-2.2.0~rc1/swift/proxy/controllers/base.py, line
767, in _get_source_and_node
query_string=self.req_query_string)
File /build/buildd/swift-2.2.0~rc1/test/unit/__init__.py, line 765, in
connect
body = static_body or ''
OverflowError: long int too large to convert to int
proxy-ut ERROR: Account HEAD returning 503 for []
** Affects: swift (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to swift in Ubuntu.
https://bugs.launchpad.net/bugs/1378810
Title:
swift unit tests fail on i386 buildd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1378810/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
[Bug 1378819] [NEW] FTBFS on Utopic, all architectures
Public bug reported: Symbols file mismatch: https://launchpad.net/ubuntu/+archive/test- rebuild-20140914/+build/6371580/+files/buildlog_ubuntu- utopic-i386.libecap_0.2.0-1ubuntu4_FAILEDTOBUILD.txt.gz The attached patch fixes it, but I'm not comfortable uploading since I don't see how I can verify that these symbols aren't part of the public interface. If we just update the symbols file to match without checking, then what's the point of having the symbols file present at all? ** Affects: libecap (Ubuntu) Importance: Undecided Status: Triaged ** Tags: ftbfs ** Patch added: libecap.patch https://bugs.launchpad.net/bugs/1378819/+attachment/4228463/+files/libecap.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libecap in Ubuntu. https://bugs.launchpad.net/bugs/1378819 Title: FTBFS on Utopic, all architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1378819/+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 1377964] Re: maas-proxy logrotate permission denied
** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Changed in: maas (Ubuntu) Status: New = Fix Committed -- 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/1377964 Title: maas-proxy logrotate permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1377964/+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 1378819] Re: FTBFS on Utopic, all architectures
** Changed in: libecap (Ubuntu) Status: Triaged = In Progress ** Changed in: libecap (Ubuntu) Assignee: (unassigned) = Robie Basak (racb) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libecap in Ubuntu. https://bugs.launchpad.net/bugs/1378819 Title: FTBFS on Utopic, all architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1378819/+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 1378841] [NEW] FTBFS due to removed DW_TAG_mutable_type constant in elfutils
Public bug reported: The latest libelf removed DW_TAG_mutable_type in upstream commit af1e6ed9b4c0160a6a5c6f59d9443ae4f6f20a14, causing an FTBFS on Utopic (Trusty still builds). ** Affects: dwarves-dfsg (Ubuntu) Importance: Undecided Assignee: Robie Basak (racb) Status: In Progress ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dwarves-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1378841 Title: FTBFS due to removed DW_TAG_mutable_type constant in elfutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1378841/+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 1378810] Re: swift unit tests fail on i386 buildd
** Also affects: swift Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to swift in Ubuntu. https://bugs.launchpad.net/bugs/1378810 Title: swift unit tests fail on i386 buildd To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/1378810/+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 1378819] Re: FTBFS on Utopic, all architectures
13:53 rbasak doko: sorry, I'm still not comfortable with this. I don't really follow the bigger picture of how to determine that these symbols really aren't n eeded. 13:53 rbasak The package includes all the headers, which makes it awkward. 13:54 rbasak doko: if you're happy with my diff, then I guess I can upload tha t. 13:54 rbasak Or else, I don't really see the point of having the symbols file in the first place if we just change it to accomodate when needed. 14:20 doko rbasak, agreed for c++ symbols files, but c symbol files should be fine 14:20 doko go ahead with the upload 14:20 doko my libabigail upload is still stuck in NEW 14:22 rbasak doko: OK - you mean an upload to drop this c++ symbols file entirely, or just to mark the disappearing symbols as optional as in my diff? 14:23 doko well, optional shouldn't hurt from my point of view 14:23 rbasak OK 14:23 rbasak Thanks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libecap in Ubuntu. https://bugs.launchpad.net/bugs/1378819 Title: FTBFS on Utopic, all architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1378819/+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 1377142] Re: Bcache doesn't allow full unregistering without rebooting
Hm, it was helping in my case. So here from my re-run with utopic KVM host: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 16G 0 disk └─bcache0 251:008G 0 disk /mnt sdb 8:16 08G 0 disk └─bcache0 251:008G 0 disk /mnt # bcache-super-show /dev/sda sb.magicok sb.first_sector 8 [match] sb.csum 29533C7B4D0F16EA [match] sb.version 3 [cache device] dev.label (empty) dev.uuid91706fc8-39ae-4cbd-b0a0-8a202ee6a377 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.cache.first_sector 1024 dev.cache.cache_sectors 33553408 dev.cache.total_sectors 33554432 dev.cache.ordered yes dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid a8f70bd1-48df-462f-9a2c-ca4b8af9059c # bcache-super-show /dev/sdb sb.magicok sb.first_sector 8 [match] sb.csum 81BB0342C7270559 [match] sb.version 1 [backing device] dev.label (empty) dev.uuid4ae46f48-d11d-45ca-a1ec-905eaf8e1da8 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state1 [clean] cset.uuid a8f70bd1-48df-462f-9a2c-ca4b8af9059c -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+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 1378841] Re: FTBFS due to removed DW_TAG_mutable_type constant in elfutils
** Bug watch added: Debian Bug tracker #764484 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764484 ** Also affects: dwarves-dfsg (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764484 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dwarves-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1378841 Title: FTBFS due to removed DW_TAG_mutable_type constant in elfutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1378841/+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 1377142] Re: Bcache doesn't allow full unregistering without rebooting
# umount /mnt # echo 1 /sys/fs/bcache/a8f70bd1-48df-462f-9a2c-ca4b8af9059c/unregister # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 16G 0 disk sdb 8:16 08G 0 disk └─bcache0 251:008G 0 disk # echo 1 /sys/block/bcache0/bcache/stop # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 16G 0 disk sdb 8:16 08G 0 disk # wipefs -a /dev/sda /dev/sda: 16 bytes were erased at offset 0x1018 (bcache): c6 85 73 f6 4e 1a 45 ca 82 65 f5 7f 48 ba 6d 81 # wipefs -a /dev/sdb /dev/sdb: 16 bytes were erased at offset 0x1018 (bcache): c6 85 73 f6 4e 1a 45 ca 82 65 f5 7f 48 ba 6d 81 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+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 1377142] Re: Bcache doesn't allow full unregistering without rebooting
Interesting note: echo 1 /sys/block/bcache0/bcache/stop from a point where the bcache is registered and running (but not mounted) directly releases both devices for me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+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 1377142] Re: Bcache doesn't allow full unregistering without rebooting
which can be fixed by unregistering via /sys/fs/bcache... what a horrible interface. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+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 1377142] Re: Bcache doesn't allow full unregistering without rebooting
Ok, but that leaves sda in a state which looks unclaimed but is still in use. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+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 1378738] [NEW] guest os boot stuck with mount operation error
Thanks for reporting this bug. To fix the cgmanager issue, add the line lxc.mount.auto = cgroup:mixed to your container configuration file. That shouldn't explain your hang however. Assuming it doesn't, please run lxc-start -n container -l trace -o debug.out -- /sbin/init debug verbose --debug --verbose And append both the console output and the file debug.out status: incomplete ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1378738 Title: guest os boot stuck with mount operation error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1378738/+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 1298552] Re: bluetooth enabled after resume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pm-utils (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1298552 Title: bluetooth enabled after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1298552/+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 1377142] Re: Bcache doesn't allow full unregistering without rebooting
Thanks, I didn't wrote to /sys/block/bcache0/bcache/stop, I missed this as I was only looking in /dev/bcache* and in /sys/fs/bcache; which explains why I was left with an used device. I agree that the interface is not very user-fiendly, we may need to improve the bcache-tools command to simplify this. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+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 1378446] [NEW] dovecot-lda crashes (exits with status code 134) when message is passed to pipe backend
You have been subscribed to a public bug:
I first reported this issue on the Dovecot mailing list, but nobody
there was able to help me identify the source of the problem (no less
how to fix it). And that's a pretty sharp group! Here's the full thread:
http://www.mail-archive.com/dovecot@dovecot.org/msg58938.html
I will preface this by saying that this bug could very well be with
dovecot-deliver and not the antispam plugin, specifically. I'm still
trying to make that determination, definitively. Any assistance in that
regard is much appreciated.
One aspect that I would like to point-out immediately is that the
dovecot deliver manual at http://wiki2.dovecot.org/LDA#logging states
very clearly, If dovecot-lda fails to write to log files it exits with
temporary failure. That's a curious note, because I believe that a
temporary failure exit code is precisely what we're dealing with here.
Anyhow, without further ado...
On Ubuntu 12.04, I used this plug-in with great success, so when I
upgraded to 14.04 (using dist-upgrade), I had hoped to be able to
continue using it in exactly the same way.
I consulted the manpages for Ubuntu 12.04 LTS and 14.04 LTS and they are
identical -- verbatim, right down to the last letter. As such, I assumed
that my antispam-related configuration directives would not need to be
changed.
However, on Ubuntu 14.04, when the pipe script that the antispam
plugin calls executes dovecot-deliver (this is how I pass the ham or
spam message to a dedicated training mailbox), dovecot-deliver exits
with status code 134, every time. Dovecot seems not to log anything with
regard to the segfault in its logs, despite my efforts to configure
deliver to log any issues:
protocol lda {
..
# remember to give proper permissions for these files as well
log_path = /var/log/dovecot-lda-errors.log
info_log_path = /var/log/dovecot-lda.log
}
These are the permissions I assigned to those two log files:
# ls -lah /var/log | grep dovecot
-rw-r--r-- 1 vmail vmail 0 Sep 19 14:21 dovecot-lda-errors.log
-rw-r--r-- 1 vmail vmail 0 Sep 19 14:21 dovecot-lda.log
When I restart dovecot with these LDA logging efforts in-place, I still
don't see the log file sizes grow beyond zero bytes.
The exit code, 134, isn't mentioned at all in the documentation at
http://wiki2.dovecot.org/LDA , either.
By adding the following to the top of my pipe script (thank you to
Steffen Kaiser on the mailing list for the suggestion)
exec /tmp/trace 21
set -vx
I've been able to capture the following output when the pipe script is
called (pardon the wrapping); this is just the most relevant bit:
+ /usr/lib/dovecot/deliver -d sa-train...@localhost.com -m Training.SPAM
^A^H22212 prefix=lda:
^A^F22212 io_add(0x1) called twice fd=7, callback=0x7f020f5486f0 -
0x7f020f4f7530
^A^D22212 Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x5e271)
[0x7f020f536271] - /usr/lib/dovecot/libdovecot.so.0(+0x5e34e) [0x7f020f53634e]
- /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f020f4f1a9e] -
/usr/lib/dovecot/libdovecot.so.0(ioloop_iolist_add+0x83) [0x7f020f546533] -
/usr/lib/dovecot/libdovecot.so.0(io_loop_handle_add+0x3b) [0x7f020f546cbb] -
/usr/lib/dovecot/libdovecot.so.0(io_add+0x9b) [0x7f020f5459fb] -
/usr/lib/dovecot/libdovecot.so.0(master_service_io_listeners_add+0x69)
[0x7f020f4f6e49] -
/usr/lib/dovecot/libdovecot.so.0(master_service_init_finish+0xb0)
[0x7f020f4f6f90] - /usr/lib/dovecot/deliver(main+0x1cb) [0x7f020feea69b] -
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f020f131ec5] -
/usr/lib/dovecot/deliver(+0x31de) [0x7f020feeb1de]
/usr/local/bin/sa-learn-pipe.sh: line 52: 22212 Aborted (core
dumped) /usr/lib/dovecot/deliver -d sa-train...@localhost.com -m
Training.$mode
+ echo 'Exit status was 134'
The steps I took to obtain a core-dump are as follows:
# ulimit -c unlimited
# ulimit -c
unlimited
# vim /etc/sysctl.d/20-coredump.conf
(added the following contents to the above new file and saved the file)
kernel.core_uses_pid = 1
kernel.core_pattern = /tmp/core-%e-%s-%u-%g-%p-%t
fs.suid_dumpable = 2
# sysctl -p
# service dovecot stop
# /usr/sbin/dovecot -F -c /etc/dovecot/dovecot.conf
[1] 28150
At this point, when I drag a message from Inbox to Junk, a core-dump is
created in /tmp. Here is the gdb output for the core-dump:
# gdb /usr/lib/dovecot/deliver /tmp/core-deliver-6-5000-5000-29807-141115
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources
[Bug 1378446] Re: dovecot-lda crashes (exits with status code 134) when message is passed to pipe backend
** Package changed: ubuntu = dovecot (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1378446 Title: dovecot-lda crashes (exits with status code 134) when message is passed to pipe backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1378446/+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 1310629] Re: Nova configuration template has deprecated items ( grizzly )
** Tags added: cts -- 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/1310629 Title: Nova configuration template has deprecated items ( grizzly ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1310629/+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 1378819] Re: FTBFS on Utopic, all architectures
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/libecap/utopic- proposed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libecap in Ubuntu. https://bugs.launchpad.net/bugs/1378819 Title: FTBFS on Utopic, all architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1378819/+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 1378841] Re: FTBFS due to removed DW_TAG_mutable_type constant in elfutils
This bug was fixed in the package dwarves-dfsg - 1.10-2ubuntu1 --- dwarves-dfsg (1.10-2ubuntu1) utopic; urgency=medium * d/p/DW_TAG_mutable_type: fix FTBFS due to newer elfutils (LP: #1378841). -- Robie Basak robie.ba...@ubuntu.com Wed, 08 Oct 2014 14:05:27 + ** Changed in: dwarves-dfsg (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dwarves-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1378841 Title: FTBFS due to removed DW_TAG_mutable_type constant in elfutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1378841/+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 1038139] Re: Missing running check on init script
** Branch linked: lp:debian/haproxy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1038139 Title: Missing running check on init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1038139/+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 1378819] Re: FTBFS on Utopic, all architectures
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libecap in Ubuntu. https://bugs.launchpad.net/bugs/1378819 Title: FTBFS on Utopic, all architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1378819/+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 1108935] Re: [MIR] websockify
Michael After some discussion with contributors to this project and within the Ubuntu Server team, I'm withdrawing this MIR for now; I'm not happy that enough QA goes on upstream prior to releases - the broken test suite is just one symptom of this. For now, we will skip the websockify dependent tests in nova, and continue to provide the console proxy related packages from universe. ** Changed in: websockify (Ubuntu) Status: Incomplete = Won't Fix -- 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/1108935 Title: [MIR] websockify To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/websockify/+bug/1108935/+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 1370628] Re: [FFe] MAAS New 1.7 Upstream Release
@Andres: A debdiff from utopic to utopic might have been easier to review than the 7MB (!) diff from trusty. :P -- 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/1370628 Title: [FFe] MAAS New 1.7 Upstream Release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1370628/+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 1370628] Re: [FFe] MAAS New 1.7 Upstream Release
I'm not convinced the two FFes are actually tied to each other, but some confirmation from the MaaS team would be nice. ie: I don't see why this new MaaS version would suddenly be more or less broken with or without the psycopg2 change. -- 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/1370628 Title: [FFe] MAAS New 1.7 Upstream Release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1370628/+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 1378819] Re: FTBFS on Utopic, all architectures
This bug was fixed in the package libecap - 0.2.0-1ubuntu5 --- libecap (0.2.0-1ubuntu5) utopic; urgency=medium * d/libecap2.symbols: mark four more symbols optional to fix FTBFS, as these don't appear to form part of the formal ABI but have disappeared (LP: #1378819). -- Robie Basak robie.ba...@ubuntu.com Wed, 08 Oct 2014 14:27:20 + ** Changed in: libecap (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libecap in Ubuntu. https://bugs.launchpad.net/bugs/1378819 Title: FTBFS on Utopic, all architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1378819/+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 1370628] Re: [FFe] MAAS New 1.7 Upstream Release
He he oops! I'll attach one once o get my hands to a computer! On Oct 8, 2014 6:45 PM, Adam Conrad adcon...@0c3.net wrote: @Andres: A debdiff from utopic to utopic might have been easier to review than the 7MB (!) diff from trusty. :P -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1370628 Title: [FFe] MAAS New 1.7 Upstream Release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1370628/+subscriptions -- 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/1370628 Title: [FFe] MAAS New 1.7 Upstream Release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1370628/+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 1378955] [NEW] package mysql-server-5.6 (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Public bug reported: On ubuntu 14.04 instaled MariaDb 5.5. Mysql server 5.6 install returned this error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: mysql-server-5.6 (not installed) ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 AptOrdering: mysql-server-5.6: Install mysql-server-5.6: Configure Architecture: amd64 Date: Wed Oct 8 21:23:32 2014 DuplicateSignature: package:mysql-server-5.6:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-29 (161 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: mysql-5.6 Title: package mysql-server-5.6 (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1378955 Title: package mysql-server-5.6 (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1378955/+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 1370628] Re: [FFe] MAAS New 1.7 Upstream Release
These two FFe's are not tied together. The psycopg issue only affects MAAS by preventing it from uploading large objects to the database (larger than 2gb). In MAAS terms it prevents from uploading OS images larger than 2gb, that don't affect Ubuntu deployments, but do affect third part OS image upload. On Oct 8, 2014 6:45 PM, Adam Conrad adcon...@0c3.net wrote: I'm not convinced the two FFes are actually tied to each other, but some confirmation from the MaaS team would be nice. ie: I don't see why this new MaaS version would suddenly be more or less broken with or without the psycopg2 change. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1370628 Title: [FFe] MAAS New 1.7 Upstream Release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1370628/+subscriptions -- 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/1370628 Title: [FFe] MAAS New 1.7 Upstream Release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1370628/+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 1378955] Re: package mysql-server-5.6 (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1378955 Title: package mysql-server-5.6 (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1378955/+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 1375252] Re: Hostname change is not preserved across reboot on Azure Ubuntu VMs
** Changed in: walinuxagent (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1375252 Title: Hostname change is not preserved across reboot on Azure Ubuntu VMs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1375252/+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 1370628] Re: [FFe] MAAS New 1.7 Upstream Release
On Wednesday, October 08, 2014 17:28:13 you wrote: These two FFe's are not tied together. The psycopg issue only affects MAAS by preventing it from uploading large objects to the database (larger than 2gb). In MAAS terms it prevents from uploading OS images larger than 2gb, that don't affect Ubuntu deployments, but do affect third part OS image upload. Does the proposed upload guard against use of objects larger than 2GB to avoid crashing pyscopg2? Given we're unlikely to go forward with the psycopg2 change this cycle, it'd make sense to protect against use off excessively large objects instead of just exploading. -- 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/1370628 Title: [FFe] MAAS New 1.7 Upstream Release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1370628/+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 (no talloc stackframe)
Just adding more griping :) would be nice to see this fixed in Trusty sometime before next February bladernr@klaatu:~$ ftp transit Connected to transit.lanes. 220 (vsFTPd 3.0.2) Name (transit:bladernr): bladernr 331 Please specify the password. Password: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Login failed. Remote system type is Login. -- 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 (no talloc stackframe) 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 1379030] [NEW] Extra lxc.mount.auto entry being added to config file
Public bug reported: I'm using the Python API to append entries to the LXC config file. When I do the following: container.set_config_item(lxc.mount.auto, cgroup:mixed) I get an extra lxc.mount.auto entry in the config file. This is what it looks like: lxc.mount.auto = lxc.mount.auto = cgroup:mixed This keeps the container from starting. I have to remove the first lxc.mount.auto to get the container to start. Also, this seems to have started fairly recently. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc 1.1.0~alpha2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 8 16:40:40 2014 SourcePackage: lxc UpgradeStatus: Upgraded to utopic on 2014-06-16 (114 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug utopic -- 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/1379030 Title: Extra lxc.mount.auto entry being added to config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379030/+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 1324393] Re: Force off fails with Permission denied after upgrading to 14.04
** Changed in: libvirt (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1324393 Title: Force off fails with Permission denied after upgrading to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1324393/+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 1307436] Re: cloudarchive-icehouse: virt-aa-helper: error: apparmor_parser exited with error
I advise against backporting apparmor and suggest you simply adjust debian/rules to filter out the offending rules or to ship a different profile. ** Changed in: apparmor (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1307436 Title: cloudarchive-icehouse: virt-aa-helper: error: apparmor_parser exited with error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1307436/+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 997269] Re: dovecot imap broken by apparmor policy
** Changed in: apparmor (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+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 1379030] [NEW] Extra lxc.mount.auto entry being added to config file
Thanks for submitting this bug status: confirmed importance: high ** Changed in: lxc (Ubuntu) Importance: Undecided = High ** Changed in: lxc (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1379030 Title: Extra lxc.mount.auto entry being added to config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379030/+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 1379065] [NEW] Ubuntu 14.04.1: irqbalance not working
You have been subscribed to a public bug: -- Problem Description -- irqbalance is not working properly in Ubuntu 14.04.1, all the interrupts are going exclusively to one CPU instead of being spread. # service irqbalance status irqbalance start/running, process 832 # cat /proc/interrupts | grep -e CPU\|eth2 CPU0 CPU1 CPU2 CPU3 35: 71814 0 0 0 XICS 4115 Level eth2-q0 36: 63648 0 0 2 XICS 4116 Level eth2-q1 37: 60697 0 0 0 XICS 4117 Level eth2-q2 38: 67828 0 0 0 XICS 4118 Level eth2-q3 Even after an apt-get upgrade / distro-upgrade that updated both kernel and irqbalance packages, it still isn't working properly. # uname -r 3.13.0-36-generic # dpkg -s irqbalance | grep Version Version: 1.0.6-2ubuntu0.14.04.1 ** Affects: irqbalance (Ubuntu) Importance: Undecided Status: New ** Tags: architecture-ppc64le bugnameltc-117308 severity-high targetmilestone-inin--- -- Ubuntu 14.04.1: irqbalance not working https://bugs.launchpad.net/bugs/1379065 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1323729] Fix proposed to neutron (master)
Fix proposed to branch: master Review: https://review.openstack.org/127082 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1323729 Title: Remove Open vSwitch and Linuxbridge plugins from the Neutron tree To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1323729/+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 1379065] Re: Ubuntu 14.04.1: irqbalance not working
** Package changed: ubuntu = irqbalance (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1379065 Title: Ubuntu 14.04.1: irqbalance not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1379065/+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 1379065] Re: Ubuntu 14.04.1: irqbalance not working
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1404 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1379065 Title: Ubuntu 14.04.1: irqbalance not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1379065/+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 1379080] [NEW] update-grub-legacy-ec2 fails to detect xen kernel
Public bug reported: The update-grub-legacy-ec2 script (which ships with grub-legacy-ec2, which is presumably included under cloud-init umbrella) includes a check to determine whether a kernel is Xen-capable or not. It uses this check in a feature designed to ignore non-Xen kernels on Xen guests, presumably as a safety mechanism. The way in which the check is executed is flawed - it matches against the kernel name. This means that if you are loading a kernel that has an 'unexpected' name, update-grub-legacy- ec2 will ignore the new kernel, regardless of whether or not it is actually Xen-capable. Output looks like this: Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Ignoring non-Xen Kernel on Xen domU host: vmlinuz-3.13.0-36-custom Found kernel: /boot/vmlinuz-3.13.0-36-generic Updating /boot/grub/menu.lst ... done This has been fixed on grub-legacy. Instead of matching the kernel name, it checks the config for CONFIG_XEN=y. In addition, Linux kernels come with CONFIG_XEN=y by default for some time now, and it is perfectly safe to run a Xen-capable kernel on non-Xen hosts. Steps to reproduce: 1. Compile and generate debs for custom kernel with version string not including '-generic' or '-virtual' 2. Install debs on ec2 system (ami-a94e0c99) 3. Reboot Expected results: System comes up with new kernel Actual results: System comes up with old kernel, and new kernel is not present in /boot/grub/menu.lst Impact: Running ami-a94e0c99, and likely many others, a user can not install a custom kernel without manually editing files. Furthermore, those writes will likely be overwritten by administrative operations in the future. Recommendation: Update detection logic to search for CONFIG_XEN=y in the kernel config, and remove version string detection. Please let me know how I can help this along. I can submit a proposed fix, but am not sure where to send it. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- 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/1379080 Title: update-grub-legacy-ec2 fails to detect xen kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1379080/+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 1073147] Re: Python version mismatch, expected '2.7.2+', found '2.7.3'
The re-compile by Robert also requires you to enable the module with apache2 at the end. # a2enmod wsgi # service apache2 restart # ls -lah /etc/apache2/mods-enabled/ lrwxrwxrwx 1 root root 27 Oct 9 02:57 wsgi.conf - ../mods-available/wsgi.conf lrwxrwxrwx 1 root root 27 Oct 9 02:57 wsgi.load - ../mods-available/wsgi.load Note: Done on Ubuntu 12.04.5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libapache2-mod-python in Ubuntu. https://bugs.launchpad.net/bugs/1073147 Title: Python version mismatch, expected '2.7.2+', found '2.7.3' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-python/+bug/1073147/+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 1379132] [NEW] openvpn has a poor choice of default cipher, and does not negotiate
Public bug reported: all versions The default cipher for openvpn is BF-CBC (blowfish), which was likely once a good choice. Virtually all modern hardware has hardware acceleration/support for AES instructions, and can therefore do AES-128-CBC far faster and more efficiently than it can blowfish. Unfortunately, it also appears that openvpn doesn't negotiate the cipher at all, so it must match on both ends. 1) please enhance openvpn so that there is at least some negotiation (if the server specifies a cipher, and the client does not, then use the server's cipher) 2) change the default to be AES. thanks, lamont ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1379132 Title: openvpn has a poor choice of default cipher, and does not negotiate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1379132/+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 1379132] Re: openvpn has a poor choice of default cipher, and does not negotiate
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openvpn (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1379132 Title: openvpn has a poor choice of default cipher, and does not negotiate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1379132/+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 1379144] Re: maas-proxy package won't install when upgrading from older version
I just got this by building my own package against trunk using the trunk packaging. -- 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/1379144 Title: maas-proxy package won't install when upgrading from older version To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1379144/+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 1379144] [NEW] maas-proxy package won't install when upgrading from older version
Public bug reported: Snippet from the terminal: Selecting previously unselected package maas-proxy. dpkg: regarding maas-proxy_1.7.0~beta4+bzr3127-0ubuntu1_all.deb containing maas-proxy: maas-proxy breaks squid-deb-proxy squid-deb-proxy (version 0.8.6) is present and installed. dpkg: error processing archive maas-proxy_1.7.0~beta4+bzr3127-0ubuntu1_all.deb (--install): installing maas-proxy would break squid-deb-proxy, and deconfiguration is not permitted (--auto-deconfigure might help) ** Affects: maas Importance: Undecided Assignee: Andres Rodriguez (andreserl) Status: New ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Also affects: maas Importance: Undecided Status: New ** Changed in: maas Assignee: (unassigned) = Andres Rodriguez (andreserl) -- 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/1379144 Title: maas-proxy package won't install when upgrading from older version To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1379144/+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 1379144] Re: maas-proxy package won't install when upgrading from older version
Tagging Andres! -- 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/1379144 Title: maas-proxy package won't install when upgrading from older version To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1379144/+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 1368030] Re: nova-manage command when executed by non-root user, should give authorization error instead of low level database error
** Changed in: nova (Ubuntu) Status: In Progress = Confirmed ** Changed in: nova (Ubuntu) Assignee: Kanchan Gupta (kanchan-gupta1) = (unassigned) -- 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/1368030 Title: nova-manage command when executed by non-root user, should give authorization error instead of low level database error To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1368030/+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
