[Bug 1307208] Re: neutron-vpn-agent should wait for neutron-ovs-cleanup to complete
** Branch linked: lp:~ubuntu-server-dev/neutron/icehouse -- 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/1307208 Title: neutron-vpn-agent should wait for neutron-ovs-cleanup to complete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1307208/+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 1247912] Re: exim4 4.80-7ubuntu3 init script bug
@Serghey Fix Released means fixed in the development release, so that the next release will contain the fix. We only backport high impact bugfixes to existing stable releases. See https://wiki.ubuntu.com/StableReleaseUpdates for rationale, policy and procedure. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/1247912 Title: exim4 4.80-7ubuntu3 init script bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1247912/+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 1307104] [NEW] package samba-common-bin 2:3.6.18-1ubuntu3.1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2
You have been subscribed to a public bug: non riesco ad installare negli Aggiornamenti: common files used by both the samba server and client ProblemType: Package DistroRelease: Ubuntu 13.10 Package: nautilus-share 0.7.3-1ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 AptOrdering: unity-webapps-facebookmessenger: Install samba-common-bin: Configure nautilus-share: Configure unity-webapps-facebookmessenger: Configure Architecture: i386 Date: Sun Apr 13 00:51:58 2014 DuplicateSignature: package:nautilus-share:0.7.3-1ubuntu4:problemi con le dipendenze - lasciato non configurato ErrorMessage: problemi con le dipendenze - lasciato non configurato MarkForUpload: True SourcePackage: nautilus-share Title: package nautilus-share 0.7.3-1ubuntu4 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato UpgradeStatus: Upgraded to saucy on 2014-03-05 (38 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 saucy -- package samba-common-bin 2:3.6.18-1ubuntu3.1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2 https://bugs.launchpad.net/bugs/1307104 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 1307104] Re: package samba-common-bin 2:3.6.18-1ubuntu3.1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2
** Package changed: nautilus-share (Ubuntu) = samba (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/1307104 Title: package samba-common-bin 2:3.6.18-1ubuntu3.1 failed to install/upgrade: il sottoprocesso installato script di post- installation ha restituito lo stato di errore 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307104/+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 1287726] Re: Wrong evaluation whether json is valid or not
This also means, that unless the Ubuntu maintainer fixes it either way, then php-json has a rather important change in behaviour between 12.04 LTS and 14.04 LTS. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php-json in Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+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 1287726] Re: Wrong evaluation whether json is valid or not
So the upstream json-c developers don't consider this a bug: Oh, I see. You want json-c to validate that the input being parsed actually is UTF-8. While that might seem reasonable to do at first glance, json-c has historically supported something closer to exact, uninterpreted bytes for strings rather than strict characters, and unconditionally changing this now will be a significant change. Although not strictly to the spec, in many cases I see a value in being able to handle arbitrary data. This is also in conflict to efforts to support even less string-like data as mentioned in Issue#108. Given this, and the fact that performing the additional validation will likely add more overhead to the parsing, any checks to ensure that strings only contain valid UTF-8 sequences would need to be explicitly requested, perhaps by setting the JSON_TOKENER_STRICT flag. Do you happen to have a patch to cause this validation to be done? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php-json in Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+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 1278466] Re: [FFe] ceph firefly stable release
** Changed in: ubuntu-release-notes Status: New = Fix Released -- 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/1278466 Title: [FFe] ceph firefly stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1278466/+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 1287726] Re: Wrong evaluation whether json is valid or not
Thank you for following this up. 14.04 is just round the corner now, so it seems unlikely that any further changes can be made now. It sounds like json-c upstream are willing to have the behaviour in the presence of the flag. Does this mean that php-json could use the flag by default, and thus restore the original behaviour? Though a change in behaviour is undesirable to fix in an SRU after release. So it looks like we'll have to stick with what we have, unless anybody has a better suggestion? Mads, could you please explain the impact of this change to end-users, whether you think this should be mentioned in the release notes, and if so then suggest some appropriate text? Are there any security implications in this change? It seems to me that this is an unfortunate fallout of upstream PHP refusing to ship a free software json module by default. So Debian had to switch to an alternate version, and some behavioural change is the consequence. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php-json in Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+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 1306877] Re: sshd stops accepting new connections after configuration reload
Thank you for taking the time to report this bug and helping to make Ubuntu better. Setting Importance to Critical as this is an expected harmless operation that will render the system essentially unreachable (and thus unusable) for remote users (eg. just about all server users). It seems to me that the STOP patch should only activate on first run, not on a re-exec. I'll take a look. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1306877 Title: sshd stops accepting new connections after configuration reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1306877/+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 1306877] Re: sshd stops accepting new connections after configuration reload
(confirmed on Trusty 1:6.6p1-2) ** Changed in: openssh (Ubuntu) Status: New = Triaged ** Changed in: openssh (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1306877 Title: sshd stops accepting new connections after configuration reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1306877/+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 1306877] Re: sshd stops accepting new connections after configuration reload
** Changed in: openssh (Ubuntu) Assignee: (unassigned) = Robie Basak (racb) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1306877 Title: sshd stops accepting new connections after configuration reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1306877/+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 1307431] [NEW] LXC containers fail to start when upgraded to 14.04 LTS
Public bug reported: After running 14.04 LTS through beta etc. I updated to teh latest this morning and all was well. I then went into a running container, changed it's sources.list to pint to the trusty repos and upgraded (the container itself was running 13.10). All went well, I restart the container and it hangs on a restart. When I start it in the forground it just hangs : sudo lxc-start -n container name 4init: plymouth-upstart-bridge main process (5) terminated with status 1 4init: plymouth-upstart-bridge main process ended, respawning 4init: plymouth-upstart-bridge main process (15) terminated with status 1 4init: plymouth-upstart-bridge main process ended, respawning 4init: ureadahead main process (8) terminated with status 5 4init: plymouth-upstart-bridge main process (19) terminated with status 1 4init: plymouth-upstart-bridge main process ended, respawning * Stopping Send an event to indicate plymouth is up ...done. * Starting Mount filesystems on boot ...done. * Starting Signal sysvinit that the rootfs is mounted ...done. * Starting Clean /tmp directory ...done. * Stopping Clean /tmp directory ...done. * Starting Populate and link to /run filesystem ...done. * Starting Track if upstart is running in a container ...done. * Stopping Populate and link to /run filesystem ...done. * Starting load fallback graphics devices ...done. * Starting workaround for missing events in container ...done. * Stopping workaround for missing events in container ...done. 4init: udev-fallback-graphics main process (79) terminated with status 1 * Starting load fallback graphics devices ...fail! * Starting configure network device security ...done. * Starting set console font ...done. 4init: console-font main process (113) terminated with status 1 * Starting set console font ...fail! * Starting userspace bootsplash ...done. * Starting Initialize or finalize resolvconf ...done. 4init: setvtrgb main process (126) terminated with status 1 * Stopping userspace bootsplash ...done. * Starting Send an event to indicate plymouth is up ...done. * Starting Mount network filesystems ...done. * Stopping Send an event to indicate plymouth is up ...done. * Stopping Mount network filesystems ...done. * Starting Bridge socket events into upstart ...done. * Starting configure network device ...done. hangs forever This is in the host syslog: Apr 14 11:48:19 sentinel kernel: [59143.539884] device vethJQQMQG entered promiscuous mode Apr 14 11:48:19 sentinel kernel: [59143.609423] IPv6: ADDRCONF(NETDEV_CHANGE): vethJQQMQG: link becomes ready Apr 14 11:48:19 sentinel kernel: [59143.609526] br0: port 2(vethJQQMQG) entered forwarding state Apr 14 11:48:19 sentinel kernel: [59143.609539] br0: port 2(vethJQQMQG) entered forwarding state Apr 14 11:48:20 sentinel kernel: [59144.885192] type=1400 audit(1397472500.484:38): apparmor=DENIED operation=mount info=failed type match error=-13 profile=lxc-container-default name=/sys/fs/pstore/ pid=8430 comm=mount fstype=pstore srcname=none flags=rw Apr 14 11:48:20 sentinel kernel: [59144.885349] type=1400 audit(1397472500.484:39): apparmor=DENIED operation=mount info=failed type match error=-13 profile=lxc-container-default name=/sys/fs/pstore/ pid=8430 comm=mount fstype=pstore srcname=none flags=ro Apr 14 11:48:22 sentinel ntpd[2085]: Listen normally on 18 vethJQQMQG fe80::fc93:63ff:feb1:3c5e UDP 123 Apr 14 11:48:22 sentinel ntpd[2085]: peers refreshed Apr 14 11:48:22 sentinel ntpd[2085]: new interface(s) found: waking up resolver ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Mon Apr 14 11:49:45 2014 InstallationDate: Installed on 2012-09-05 (585 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) SourcePackage: lxc UpgradeStatus: Upgraded to trusty on 2014-02-08 (64 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = br0 lxc.network.flags = up modified.conffile..etc.lxc.default.conf: [modified] mtime.conffile..etc.lxc.default.conf: 2013-03-07T17:09:54.680483 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug trusty -- 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/1307431 Title: LXC containers fail to start when upgraded to 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1307431/+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 1306877] Re: sshd stops accepting new connections after configuration reload
openssh in Saucy (1:6.2p2-6ubuntu0.1) doesn't have this issue. Looks like its upstart job doesn't set SSH_SIGSTOP, use expect stop, and doesn't have the patch. So I think the bug is in the patch applied in Trusty. Fix attached. It seems to work. I'd appreciate a review of what I've done, though. ** Patch added: sigstop-reexec.debdiff https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1306877/+attachment/4083307/+files/sigstop-reexec.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1306877 Title: sshd stops accepting new connections after configuration reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1306877/+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] [NEW] cloudarchive-icehouse: virt-aa-helper: error: apparmor_parser exited with error
Public bug reported: With Ubuntu 12.04 Precise and Cloudarchive Icehouse libvirt 1.2.2-0ubuntu11~cloud0 is not able to spawn a VM instance due to incompatible apparmor profile with apparmor 2.8.0 (precise's version): 2014-04-11 10:27:10.997+: 8616: error : virCommandWait:2399 : internal error: Child process (/usr/lib/libvirt/virt-aa-helper -p 0 -c -u libvirt-d18f1dff-e275-4fcc-b712-2caf530aed74) unexpected exit status 1: virt-aa-helper: error: apparmor_parser exited with error Also starting apparmor with 1.2.2-0ubuntu11~cloud0 results in a apparmor_parser error: root@compute1:~# /etc/init.d/apparmor start * Starting AppArmor profiles AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in /etc/apparmor.d/usr.sbin.libvirtd at line 37: syntax error, unexpected TOK_CONDID, expecting TOK_MODE When OpenStack/Nova/libvirt tries to spawn an instance it fails due to following apparmor_parser issue: /etc/apparmor.d/libvirt/libvirt-3138433d-a124-40dd-9630-68a9e227b0bd in /etc/apparmor.d/abstractions/libvirt-qemu at line 143: syntax error, unexpected TOK_OPENPAREN, expecting TOK_MODE New offending profile entries for apparmor 2.8.0 seems to be: /etc/apparmor.d/usr.sbin.libvirtd: dbus bus=system, signal, ptrace, /etc/apparmor.d/abstractions/libvirt-qemu: signal (receive) peer=/usr/sbin/libvirtd, ptrace (tracedby) peer=/usr/sbin/libvirtd, Reverting those entries allows again to spawn a VM instance with OpenStack Icehouse RC2 from Cloudarchive-Ichouse on Ubuntu 12.04 Precise. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- 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/libvirt/+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 1306877] Re: sshd stops accepting new connections after configuration reload
** Changed in: openssh (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1306877 Title: sshd stops accepting new connections after configuration reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1306877/+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 1307431] Re: LXC containers fail to start when upgraded to 14.04 LTS
When teh container is hung and i execute an lxc-stop (from a different terminal) I see a: mount: cannot mount block device nfs server/export/lxc-lib/container name/rootfs read-only Might be connected? -- 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/1307431 Title: LXC containers fail to start when upgraded to 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1307431/+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 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
environment: jamespage machines: 11: agent-state: started agent-version: 1.18.1 dns-name: 10.5.0.26 instance-id: 24271ee3-b31d-4b7c-85ff-d027c03bd976 instance-state: ACTIVE series: trusty hardware: arch=amd64 cpu-cores=1 mem=2048M root-disk=10240M 22: agent-state: started agent-version: 1.18.1 dns-name: 10.5.0.27 instance-id: 7ecdd56a-0531-41c1-b997-c5ebd8864d69 instance-state: ACTIVE series: trusty hardware: arch=amd64 cpu-cores=1 mem=2048M root-disk=10240M services: neutron-gateway: charm: local:trusty/quantum-gateway-64 exposed: false relations: amqp: - rabbitmq-server cluster: - neutron-gateway quantum-network-service: - nova-cloud-controller shared-db: - mysql units: neutron-gateway/0: agent-state: started agent-version: 1.18.1 machine: 11 public-address: 10.5.0.26 neutron-gateway/1: agent-state: started agent-version: 1.18.1 machine: 22 public-address: 10.5.0.27 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+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 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
| 24271ee3-b31d-4b7c-85ff-d027c03bd976 | juju-jamespage-machine-11 | ACTIVE | - | Running | james-page_admin_net=10.5.0.26, 10.5.0.15| | 7ecdd56a-0531-41c1-b997-c5ebd8864d69 | juju-jamespage-machine-22 | ACTIVE | - | Running | james-page_admin_net=10.5.0.27, 10.5.0.27, 10.5.0.28 | -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+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 1307445] [NEW] openstack: instances with multiple nics on the same network don't have deterministic private-addresses
Public bug reported: Most normal users won't come across this in normal juju operation, but we do some odd things to test openstack-on-openstack in the Ubuntu Server QA lab; specifically we add additional network interfaces on the same neutron network to some types of service - neutron allocates an IP addresss, however this is never actually configured. Juju appears to see both of these via the OS API; however its a bit random as to which juju thinks is the private-address on the instance. This can result in some odd behaviour. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: juju-core 1.18.1-0ubuntu1 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Mon Apr 14 11:15:41 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 Ec2AMI: ami-0039 Ec2AMIManifest: FIXME Ec2AvailabilityZone: serverstack-az-1 Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-core Importance: Undecided Status: New ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images trusty ** Also affects: juju-core Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+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 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
This might be due to the order they are returned in in the Nova or Neutron API's I guess. In the above example the configured eth0's are on 10.5.0.15 and 10.5.0.27 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+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 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
** Changed in: juju-core (Ubuntu) Importance: Undecided = Low ** Changed in: juju-core (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+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 1307230] Re: 3.1.0 daemon infinite loop when no matched user in secrets
CVE requested: http://www.openwall.com/lists/oss-security/2014/04/14/5 ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1307230 Title: 3.1.0 daemon infinite loop when no matched user in secrets To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1307230/+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 1303903] Re: sgdisk zap/clear doesn't wipe all GPT tables
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdisk (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gdisk in Ubuntu. https://bugs.launchpad.net/bugs/1303903 Title: sgdisk zap/clear doesn't wipe all GPT tables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdisk/+bug/1303903/+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 1303903] Re: sgdisk zap/clear doesn't wipe all GPT tables
** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gdisk in Ubuntu. https://bugs.launchpad.net/bugs/1303903 Title: sgdisk zap/clear doesn't wipe all GPT tables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdisk/+bug/1303903/+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 1307473] [NEW] guest hang due to missing clock interrupt
Public bug reported: I noticed on 2 different systems that after upgrade from precise to latest trusty VMs are crashing: - in case of Windows VMs I'm getting BSOD with error message: A clock interrupt was not received on a secondary processor within the allocated time interval. - On linux VMs I'm noticing hrtimer: interrupt took 2992229 ns messages - On some proprietary virtual appliances I'm noticing crashes an due to missing timer interrupts QEMU version is: QEMU emulator version 1.7.91 (Debian 2.0.0~rc1+dfsg-0ubuntu3) Full command line: qemu-system-x86_64 -enable-kvm -name win7eval -S -machine pc- i440fx-1.7,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 -uuid 05e5089a-4aa1-6bb2-ef06-ab4d020a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7eval.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot strict=on -device piix3-usb- uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/vm/win7eval.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio- disk0,id=virtio-disk0,bootindex=1 -drive file=/home/damarion/iso/7600.16385.090713-1255_x86fre_enterprise_en- us_EVAL_Eval_Enterprise-GRMCENEVAL_EN_DVD.iso,if=none,id=drive- ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive =drive-ide0-0-0,id=ide0-0-0 -drive file=/home/damarion/iso/virtio- win-0.1-74.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:38:31:0a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa- serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -device VGA,id=video0,bus=pci.0,addr=0x2 -device virtio- balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ** Affects: qemu (Ubuntu) Importance: Undecided Status: 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/1307473 Title: guest hang due to missing clock interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1307473/+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 1306916] [NEW] cgroup-lite should be added as an explicit dependency
You have been subscribed to a public bug: Otherwise you'll get an error sudo lxc-start -n mycontainer lxc: call to cgmanager_move_pid_abs_sync(blkio) failed: invalid request lxc-start: Could not find writable mount point for cgroup hierarchy 11 while trying to create cgroup. lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/blkio/grp_1 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpu/sys_daemon lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuset/ lxc-start: failed creating cgroups lxc-start: failed to spawn 'mycontainer' Or at least let the lxc-start check of the presence of the cgroup- lite and show a meaningful error message. Ubuntu vanilla installs the cgroup-lite automatically, so it doesn't affect fresh installs. System: Ubuntu 14.04 64 bit --- ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 2813 F pulseaudio /dev/snd/pcmC0D0p: adam 2813 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-04 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) MachineType: ASUSTeK COMPUTER INC. N56VZ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=926fa7cc-6f97-4672-85a7-a1ed8f5bd842 ro rootflags=subvol=@ quiet splash intel_pstate=enable vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.216:bd12/06/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: lxc (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected trusty -- cgroup-lite should be added as an explicit dependency https://bugs.launchpad.net/bugs/1306916 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc 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 1306877] Re: sshd stops accepting new connections after configuration reload
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1306877 Title: sshd stops accepting new connections after configuration reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1306877/+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 1306916] Re: cgroup-lite should be added as an explicit dependency
Does not seem to be a kernel issue. ** Package changed: linux (Ubuntu) = lxc (Ubuntu) -- 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/1306916 Title: cgroup-lite should be added as an explicit dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1306916/+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 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
** Changed in: juju-core Status: New = Triaged ** Tags added: addressability openstack-provider ** Changed in: juju-core Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+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 1305839] Re: FFe: Support for Third Party Driver Installation
I'm in favor of the approach suggested in comment #12, whereby we prompt the user during the first install of MAAS, as to whether they want to allow the install of non-free drivers for such cases where there are no free ones available, e.g. HP example here. Once they answer, we point out that the setting can be reversed in the Settings menu if the MAAS GUI. Could we move forward with this approach? -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1305839] Re: FFe: Support for Third Party Driver Installation
Some responses to Dave's comments: * Yes, it was done quickly and isn't perfect. It's a minimum useful set of functionality to address a real use case and that improvements can be added iteratively with the benefit of getting feedback from users in the meanwhile. * fastpath can be added without a lot of extra work; we're not doing anything that prevents it from being added, I'd just rather get one install path working reasonably well before trying to get two working. * The yaml file can be edited by an admin to add additional drivers. Yes, some sort of simplestreams like approach will probably be used to replace or augment the yaml file in the future, and yes, there will be some complication in the upgrade to whatever the new source is as we'll have to maintain user additions/edits. I don't see that as insurmountable though. * I've posted a branch now that inserts the key directly into the yaml instead of retrieving it via http. Still working on a way to securely retrieve the udeb. The repo has a sha1 on the udeb; just need to work out how to validate the repo's sha1 now. * There's always a possibility for multiple drivers to be required. We've done nothing that precludes adding that capability in the future, but it isn't a supported use case for today (and I haven't seen any real use cases that require it yet). * Other arches could require it - adding support for other arches shouldn't be very difficult, but wasn't required to be useful here and is something that can added iteratively. * HWE Kernel FFe bug 1281765: I don't know what the plans are here. -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1305839] Re: FFe: Support for Third Party Driver Installation
I've posted a branch now that inserts the key directly into the yaml instead of retrieving it via http. Still working on a way to securely retrieve the udeb. The repo has a sha1 on the udeb; just need to work out how to validate the repo's sha1 now. The whole point of having the key is to give you a trusty path to the (u)debs, surely? -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1307518] [NEW] ERROR CRITICAL glance [-] AttributeError: 'NoneType' object has no attribute 'drivername' in /var/log/glance/api.log
Public bug reported: How reproducible: Steps to Reproduce: 1.Install the Ubuntu Server 12.04.4 2.Install the Keystone 3.Install the Glance 4.type glance-manage db_sync commands. Actual results: 2014-04-14 10:40:37.697 15295 CRITICAL glance [-] AttributeError: 'NoneType' object has no attribute 'drivername' The installed version: # dpkg -l |grep glance ii glance 1:2014.1~rc1-0ubuntu1~cloud0 OpenStack Image Registry and Delivery Service - Daemons ii glance-api 1:2014.1~rc1-0ubuntu1~cloud0 OpenStack Image Registry and Delivery Service - API ii glance-common1:2014.1~rc1-0ubuntu1~cloud0 OpenStack Image Registry and Delivery Service - Common ii glance-registry 1:2014.1~rc1-0ubuntu1~cloud0 OpenStack Image Registry and Delivery Service - Registry ii python-glance1:2014.1~rc1-0ubuntu1~cloud0 OpenStack Image Registry and Delivery Service - Python library ii python-glanceclient 1:0.12.0-0ubuntu1~cloud0 Client library for Openstack glance server. Workaround: # cd /etc/glance # mkdir bak # mv *.ini *.conf *.json bak/ # cd # wget https://github.com/openstack/glance/archive/master.zip # unzip master.zip # cp glance-master/etc/* /etc/glance # chown glance.glance * # ls -l /etc/glance/ total 76 drwxr-xr-x 2 glance glance 4096 Apr 14 13:46 bak -rw-r--r-- 1 glance glance 24066 Apr 14 13:54 glance-api.conf -rw-r--r-- 1 glance glance 2603 Apr 14 13:47 glance-api-paste.ini -rw-r--r-- 1 glance glance 7210 Apr 14 13:47 glance-cache.conf -rw-r--r-- 1 glance glance 6036 Apr 14 13:54 glance-registry.conf -rw-r--r-- 1 glance glance 863 Apr 14 13:47 glance-registry-paste.ini -rw-r--r-- 1 glance glance 1860 Apr 14 13:47 glance-scrubber.conf -rw-r--r-- 1 glance glance 982 Apr 14 13:47 logging.cnf.sample -rw-r--r-- 1 glance glance 611 Apr 14 13:47 policy.json -rw-r--r-- 1 glance glance 1186 Apr 14 13:47 property-protections-policies.conf.sample -rw-r--r-- 1 glance glance 1065 Apr 14 13:47 property-protections-roles.conf.sample -rw-r--r-- 1 glance glance 1259 Apr 14 13:47 schema-image.json # glance-manage db_sync ** Affects: glance (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1307518 Title: ERROR CRITICAL glance [-] AttributeError: 'NoneType' object has no attribute 'drivername' in /var/log/glance/api.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glance/+bug/1307518/+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 1306916] Re: cgroup-lite should be added as an explicit dependency
cgroup-lite isn't necessary at all now that we have cgmanager. Adding a cgmanager task to investigate what's causing it to fail for you. Can you please attach /var/log/upstart/cgmanager.log ? ** Also affects: cgmanager (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/1306916 Title: cgroup-lite should be added as an explicit dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1306916/+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 1300010] Re: heat has broken dependency on python-qpid
Fixed under bug 1296912 ** Changed in: heat (Ubuntu Trusty) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to heat in Ubuntu. https://bugs.launchpad.net/bugs/1300010 Title: heat has broken dependency on python-qpid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heat/+bug/1300010/+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 1307431] Re: LXC containers fail to start when upgraded to 14.04 LTS
So the problem here, as is shown by your kernel log is that your container even though the rootfs upgraded properly is still using an old config... That old config doesn't mount pstore which is then causing the hang at boot time which you are seeing. LXC 1.0 fixes that issue going forward through a set of config includes, but for old containers, you may have to update their config by hand to be closer to what you'd get if you just created a new container. So edit /var/lib/lxc/container/config and make it look like something like that: # Template used to create this container: /usr/share/lxc/templates/lxc-download # Parameters passed to the template: -d ubuntu -r trusty -a amd64 # For additional config options, please look at lxc.conf(5) # Distribution configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf lxc.arch = x86_64 # Container specific configuration lxc.rootfs = /var/lib/lxc/YOUR-CONTAINER-NAME/rootfs lxc.utsname = YOUR-CONTAINER-NAME # Network configuration lxc.network.type = veth lxc.network.flags = up lxc.network.link = lxcbr0 lxc.network.hwaddr = YOUR-CONTAINER-MAC-ADDRESS Then start it again and things should be back to normal. There's sadly no way we can programmatically do that for existing containers on upgrade due to all the possible combinations and hand made changes, but as I said, the new lxc.includes we added should let us cover most of those cases moving forward and hopefully we won't have a similar problem with 16.04. ** Changed in: lxc (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1307431 Title: LXC containers fail to start when upgraded to 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1307431/+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 1304167] Re: syntax error, trusty beta-2 cloud image
** Package changed: apparmor (Ubuntu) = lxc (Ubuntu) ** Changed in: lxc (Ubuntu) Importance: Undecided = High ** Changed in: lxc (Ubuntu) Status: Confirmed = Triaged -- 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/1304167 Title: syntax error, trusty beta-2 cloud image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1304167/+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 1305839] Re: FFe: Support for Third Party Driver Installation
So I was informed that prompting for non-free during installation would break unmanned installs of MAAS, which causes problems for our cloud install plans. I'm all for supporting our commitment to non-free, but at the end of the day, we're also committed to ensuring our users have a great experience with Ubuntu. If users are unable to install because their drives aren't recognized, then the entire non-free argument becomes irrelevant. The argument of telling our partners to opensource their drivers, is valid, but will take awhile, e.g. Nvidia on the desktop...and could possibly never occur. I'll leave the decision up to the engineers and release team, but I hope we can come up with something that allows our users the freedom to use Ubuntu on the hardware of their choice. -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1305839] Re: FFe: Support for Third Party Driver Installation
Would it be a better approach to simply display a notice in the MAAS Web UI and maybe when we do the initial MAAS setup, notifying the user that this setting is enabled by default? On Mon, Apr 14, 2014 at 9:24 AM, Robbie Williamson robbie.william...@canonical.com wrote: I'm in favor of the approach suggested in comment #12, whereby we prompt the user during the first install of MAAS, as to whether they want to allow the install of non-free drivers for such cases where there are no free ones available, e.g. HP example here. Once they answer, we point out that the setting can be reversed in the Settings menu if the MAAS GUI. Could we move forward with this approach? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+subscriptions -- Andres Rodriguez (RoAkSoAx) Ubuntu Server Developer MSc. Telecom Networking Systems Engineer -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1304167] [NEW] syntax error, trusty beta-2 cloud image
You have been subscribed to a public bug: sudo apt-get install lxc -y Setting up lxc (1.0.2-0ubuntu2) ... AppArmor parser error for /etc/apparmor.d/lxc-containers in /etc/apparmor.d/abstractions/lxc/container-base at line 6: syntax error, unexpected TOK_END_OF_RULE, expecting TOK_MODE AppArmor parser error for /etc/apparmor.d/usr.bin.lxc-start in /etc/apparmor.d/abstractions/lxc/start-container at line 5: syntax error, unexpected TOK_END_OF_RULE, expecting TOK_MODE lxc start/running ** Affects: lxc (Ubuntu) Importance: High Status: Triaged -- syntax error, trusty beta-2 cloud image https://bugs.launchpad.net/bugs/1304167 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc 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 1307544] Re: user and group is re-created on every upgrade
Example after a recent security upgrade: http://paste.ubuntu.com/7250004/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1307544 Title: user and group is re-created on every upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1307544/+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 1306360] Re: package libvirt-bin 0.9.8-2ubuntu17.17 failed to install/upgrade: Package is in a very bad inconsistent state - you should reinstall it before attempting a removal.
Thanks. Ideally we would be able to get to the bottom of why libvirt became unkillable, however since it isn't doing that regularly, we'll have to mark this invalid meaning 'unreproducible.' Please do reply to this if you see it happening again. ** Changed in: libvirt (Ubuntu) Status: Incomplete = Invalid -- 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/1306360 Title: package libvirt-bin 0.9.8-2ubuntu17.17 failed to install/upgrade: Package is in a very bad inconsistent state - you should reinstall it before attempting a removal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1306360/+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 1307544] [NEW] user and group is re-created on every upgrade
Public bug reported: The 'snmp' user and group is deleted and re-added on every package upgrade (of at least snmpd); this causes unnecessary churn to /etc and net-snmp is one of the few (only?) packages I'm aware of which does this. ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1307544 Title: user and group is re-created on every upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1307544/+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 1305839] Re: FFe: Support for Third Party Driver Installation
On 04/14/2014 08:45 AM, Adam Conrad wrote: The whole point of having the key is to give you a trusty path to the (u)debs, surely? Yes - we need it for the udebs, and for setting up the repository in the installed system. I'm still trying to work out the details on how to verify the udebs given the public key. The installer initrd includes gpgv to verify files/sigs against a keyring; I have a public key and need to turn that into a keyring. The public key is ascii armored and so it's easy to include it in a shell script. gpgv seems to expect a non ascii armored keyring, which can't be easily included in a shell script. There are no text-binary decoders included in the installer image, afaict (cjwatson agrees). Jason -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1307518] Re: ERROR CRITICAL glance [-] AttributeError: 'NoneType' object has no attribute 'drivername' in /var/log/glance/api.log
** Also affects: glance (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1307518 Title: ERROR CRITICAL glance [-] AttributeError: 'NoneType' object has no attribute 'drivername' in /var/log/glance/api.log To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1307518/+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 1307431] Re: LXC containers fail to start when upgraded to 14.04 LTS
Yes, that works! Many thanks for your help. -- 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/1307431 Title: LXC containers fail to start when upgraded to 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1307431/+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 1305839] Re: FFe: Support for Third Party Driver Installation
Looks like ash can support hexadecimal escaped strings - so that's a way forward for me. -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1304167] Re: syntax error, trusty beta-2 cloud image
** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New -- 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/1304167 Title: syntax error, trusty beta-2 cloud image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1304167/+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 1305839] Re: FFe: Support for Third Party Driver Installation
For context, here's the branch I'm working on. It handles the insecure key retrieval problem. I plan on handling the udeb problem by inserting the keyring into the preseed, retrieving Release/Release.gpg for the repo, using the keyring to verify the Release file, then using the sha sums to verify the Packages and udeb files. https://code.launchpad.net/~jason-hobbs/maas/use-key-text/+merge/215517 -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1302044] Re: permissions on /var/lib/glance/image* are wrong
** Also affects: glance (Ubuntu Trusty) Importance: Undecided Status: Confirmed ** Changed in: glance (Ubuntu Trusty) Importance: Undecided = Critical ** Changed in: glance (Ubuntu Trusty) Status: Confirmed = Triaged ** Changed in: glance (Ubuntu Trusty) Assignee: (unassigned) = Chuck Short (zulcss) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1302044 Title: permissions on /var/lib/glance/image* are wrong To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1302044/+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 1305839] Re: FFe: Support for Third Party Driver Installation
To Robbie's point - yes, it makes no sense to make the install break mysteriously when we can get it to work, any more so on a server or a phone. It does make sense to flag in the UI when we have used drivers outside of the normal Ubuntu kernel set. We're not installing proprietary applications, I don't see a significant moral issue. Mark -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1305839] Re: FFe: Support for Third Party Driver Installation
So I was informed that prompting for non-free during installation would break unmanned installs of MAAS, which causes problems for our cloud install plans. I'm trying to sort out what this means. Do we actually care that the maas *controller* be installable with zero intervention? Why is this an important feature? Again, this has nothing to do with installing nodes. Nodes should install with zero intervention and Just Work. Why do we expect nobody to ever need to interact with or configure the controller, however? -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1306646] Re: dnsmasq provides recursive answers to the Internet by default
Curiosity fueled a couple of tests on this. In checking 2 common scenarios, at least one use case confirms. Aside from this confirmation, a bigger-picture question could be: in principle, how is 53 being open and interactive by default any different than 80, 22, or 137-139 being open and interactive by default, when dnsmasq is not installed by default? If a user chooses to add a service, whether that is ssh, samba, apache, dnsmasq, or others, in what scenarios are we to protect the user against him/herself? One could argue that all of those protocols are subject to abuse. In other words - this could be a slippery slope. Having said that little devil's advocate bit, I am *all for* making sure our default behavior is to not have an open recursive DNS server. Here's what I found: [test0]: Trusty default server install + Virtual Machine Host package selection (ok) [test1]: Trusty default server install + install dnsmasq (CONFIRMS open recursive DNS condition) # [test0] # Trusty default server install + Virtual Machine Host package selection * This method does not result in an open recursive DNS server. * The default ip interface layout follows; eth0 is connected and has obtained an address via dhcp; libvirt has created virbr0 interface, and dnsmasq is listening only on the virbr0 interface (192.168.122.1). rbeisner@isotest0:~$ sudo ip addr | grep gl inet 10.4.5.132/24 brd 10.4.5.255 scope global eth0 inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 rbeisner@isotest0:~$ sudo netstat -taupn | egrep ':22|:53' tcp0 0 192.168.122.1:530.0.0.0:* LISTEN 1148/dnsmasq tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN 852/sshd tcp6 0 0 :::22 :::*LISTEN 852/sshd udp0 0 192.168.122.1:530.0.0.0:* 1148/dnsmasq * The default iptables firewall rules for this use case follow; Destination ports 53 tcp udp are explicitly allowed in the virbr0 interface. DNS ports are not disallowed anywhere, and there isn't a default drop or reject rule in the input chain. But because dnsmasq is only bound to the virbr0 interface, it should not be accessible on any other interface, even if all iptables rules are flushed. beisner@isotest0:~$ sudo iptables -nvL Chain INPUT (policy ACCEPT 19526 packets, 29M bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT udp -- virbr0 * 0.0.0.0/00.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- virbr0 * 0.0.0.0/00.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- virbr0 * 0.0.0.0/00.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- virbr0 * 0.0.0.0/00.0.0.0/0 tcp dpt:67 Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * virbr0 0.0.0.0/0 192.168.122.0/24 ctstate RELATED,ESTABLISHED 0 0 ACCEPT all -- virbr0 * 192.168.122.0/24 0.0.0.0/0 0 0 ACCEPT all -- virbr0 virbr0 0.0.0.0/00.0.0.0/0 0 0 REJECT all -- * virbr0 0.0.0.0/00.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- virbr0 * 0.0.0.0/00.0.0.0/0 reject-with icmp-port-unreachable Chain OUTPUT (policy ACCEPT 10169 packets, 592K bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT udp -- * virbr0 0.0.0.0/00.0.0.0/0 udp dpt:68 * Flush iptables, all traffic allowed: rbeisner@isotest0:~$ sudo iptables -F rbeisner@isotest0:~$ sudo iptables -nvL Chain INPUT (policy ACCEPT 39 packets, 2712 bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 20 packets, 1792 bytes) pkts bytes target prot opt in out source destination * Port scans from a neighboring node confirm that tcp and udp 53 are closed on the world-facing interface: rbeisner@bcu:~$ sudo nmap -sU -p 53 10.4.5.132 | grep 53 53/udp closed domain rbeisner@bcu:~$ sudo nmap -sT -p 53 10.4.5.132 | grep 53 53/tcp closed domain rbeisner@bcu:~$ sudo nmap -sT -p 22 10.4.5.132 | grep 22 22/tcp open ssh ... # [test1] # Trusty default server install + install dnsmasq (CONFIRMS open recursive DNS condition) * CONFIRMS the default condition to be an open recursive DNS server /!\. * DNS query from a neighboring host
Re: [Bug 1306646] Re: dnsmasq provides recursive answers to the Internet by default
On Mon, Apr 14, 2014 at 03:02:44PM -, Ryan Beisner wrote: Aside from this confirmation, a bigger-picture question could be: in principle, how is 53 being open and interactive by default any different than 80, 22, or 137-139 being open and interactive by default, when dnsmasq is not installed by default? If a user chooses to add a service, whether that is ssh, samba, apache, dnsmasq, or others, in what scenarios are we to protect the user against him/herself? One could argue that all of those protocols are subject to abuse. In other words - this could be a slippery slope. I think that a key difference for DNS is that there are multiple common modes of operation, and for dnsmasq an open recursive server seems to be an uncommon mode to me. Users may want dnsmasq provision for some local networking setup (this is common - see lxc and libvirt), or want to authoritatively serve a zone, and in both of these cases there's no need to serve recursively to outside requests at all. And when one does serve recursive queries, it's still considered a generally bad idea (AIUI) to serve the Internet in general. You'd want to configure it to serve a limited network instead. So the difference is where (and if) the default isn't useful in the majority of cases. This might apply to bind and unbound also, but does not apply to a public web server where the point of installing it is to serve pages publicly. An exception is that for a server that doesn't have a publicly reachable interface (via RFC1918, or as blocked by a firewall, or whatever), it might be easier to just answer recursively to all requests, given that it is separately known that these requests cannot be coming from the Internet at large. In this case, this kind of default might be useful. samba is an example of this type of case, as it typically is installed on an internal network that is already somehow unreachable from the Internet. I'm not arguing either way here, just answering your where do we draw the line? question. Perhaps dnsmasq also fits into this latter category. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1306646 Title: dnsmasq provides recursive answers to the Internet by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1306646/+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 1306646] Re: dnsmasq provides recursive answers to the Internet by default
Yep, I'm with ya Robie. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1306646 Title: dnsmasq provides recursive answers to the Internet by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1306646/+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 1306877] Re: sshd stops accepting new connections after configuration reload
This bug was fixed in the package openssh - 1:6.6p1-2ubuntu1 --- openssh (1:6.6p1-2ubuntu1) trusty; urgency=medium * Upload from Debian git repository to fix a release-critical bug. * Debconf translations: - French (thanks, Étienne Gilli; closes: #743242). * Never signal the service supervisor with SIGSTOP more than once, to prevent a hang on re-exec (thanks, Robie Basak; LP: #1306877). -- Colin Watson cjwat...@ubuntu.com Mon, 14 Apr 2014 12:20:48 +0100 ** Changed in: openssh (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1306877 Title: sshd stops accepting new connections after configuration reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1306877/+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 1304167] Re: syntax error, trusty beta-2 cloud image
Equivalent fix pushed for libvirt ** Changed in: libvirt (Ubuntu) Importance: Undecided = High ** Changed in: libvirt (Ubuntu) Status: New = In Progress -- 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/1304167 Title: syntax error, trusty beta-2 cloud image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1304167/+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 1299802] Re: upgrade-juju 1.16.6 - 1.18 (tip) fails
** Changed in: juju-core Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1299802 Title: upgrade-juju 1.16.6 - 1.18 (tip) fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1299802/+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 1303880] Re: Juju 1.18.0, can not deploy local charms without series
** Changed in: juju-core Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303880 Title: Juju 1.18.0, can not deploy local charms without series To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303880/+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 1303697] Re: peer relation disappears during upgrade of juju
** Changed in: juju-core Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303697 Title: peer relation disappears during upgrade of juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303697/+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 1172566] Re: MAAS Server ISO install fails when network is disconnected
** Summary changed: - MAAS Server install fails when network is disconnected + MAAS Server ISO install fails when network is disconnected -- 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/1172566 Title: MAAS Server ISO install fails when network is disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1172566/+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 1303735] Re: public-address change to internal bridge post juju-upgrade
** Changed in: juju-core Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303735 Title: public-address change to internal bridge post juju-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303735/+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 1306208] Re: juju scp no longer allows multiple extra arguments to pass throug
** Changed in: juju-core Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1306208 Title: juju scp no longer allows multiple extra arguments to pass throug To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1306208/+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 1298559] Re: Internal Server Error after installing MAAS from Trusty daily ISO
FYI - related bug regarding missing dependencies in a no-network scenario: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1172566 -- 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/1298559 Title: Internal Server Error after installing MAAS from Trusty daily ISO To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1298559/+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 1172566] Re: MAAS Server ISO install fails when network is disconnected
Issue confirmed on Trusty daily ISO. ** Tags added: 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/1172566 Title: MAAS Server ISO install fails when network is disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1172566/+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 1306296] Re: juju cannot downgrade to same major.minor version with earlier patch number
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1306296 Title: juju cannot downgrade to same major.minor version with earlier patch number To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1306296/+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 1303880] Re: Juju 1.18.0, can not deploy local charms without series
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303880 Title: Juju 1.18.0, can not deploy local charms without series To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303880/+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 1299802] Re: upgrade-juju 1.16.6 - 1.18 (tip) fails
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1299802 Title: upgrade-juju 1.16.6 - 1.18 (tip) fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1299802/+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 1303735] Re: public-address change to internal bridge post juju-upgrade
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303735 Title: public-address change to internal bridge post juju-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303735/+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 1261628] Re: remove-* aliases for destroy-service and destroy-machine
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1261628 Title: remove-* aliases for destroy-service and destroy-machine To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1261628/+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 1303697] Re: peer relation disappears during upgrade of juju
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303697 Title: peer relation disappears during upgrade of juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303697/+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 1299588] Re: LXC permission denied issue with 1.17.7
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1299588 Title: LXC permission denied issue with 1.17.7 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1299588/+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 1306208] Re: juju scp no longer allows multiple extra arguments to pass throug
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1306208 Title: juju scp no longer allows multiple extra arguments to pass throug To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1306208/+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 1248283] Re: juju userdata should not restart networking
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: juju userdata should not restart networking To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+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 1305839] Re: FFe: Support for Third Party Driver Installation
It has to do with automating the installation of MAAS environments, which includes automating the installation of MAAS itself. In particular this is important to our Openstack cloud-installer and for bootstrapping 'other' environments. -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1307518] Re: ERROR CRITICAL glance [-] AttributeError: 'NoneType' object has no attribute 'drivername' in /var/log/glance/api.log
This bug was fixed in the package glance - 1:2014.1~rc2-0ubuntu1 --- glance (1:2014.1~rc2-0ubuntu1) trusty; urgency=medium [ Chuck Short ] * New upstream release candidate (LP: #1299055). * debian/patches/sql_conn.patch: Refreshed. * debian/glance-api.install: Install missing schema.json file. (LP: #1307518) [ Thomas Bechtold ] * debian/glance-common.postinst: Set correct owner/group for /var/lib/glance and subdirs only on local filesystems (LP: #1302044). -- Chuck Short zul...@ubuntu.com Sat, 12 Apr 2014 08:45:20 -0400 ** Changed in: glance (Ubuntu Trusty) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1307518 Title: ERROR CRITICAL glance [-] AttributeError: 'NoneType' object has no attribute 'drivername' in /var/log/glance/api.log To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1307518/+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 1302174] Re: cgmanager and cgproxy startup is racy
This bug was fixed in the package lxc-android-config - 0.161 --- lxc-android-config (0.161) trusty; urgency=medium [ Stéphane Graber ] * e-enable cgmanager support. (LP: #1302174) -- Oliver Grawert o...@ubuntu.com Mon, 14 Apr 2014 13:23:45 +0200 ** Changed in: lxc-android-config (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1302174 Title: cgmanager and cgproxy startup is racy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1302174/+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 1172566] Re: MAAS Server ISO install fails when network is disconnected
More detail, see also attached tarball: Apr 14 17:26:05 in-target: dpkg: error processing package maas-region-controller-min (--configure): Apr 14 17:26:05 in-target: subprocess installed post-installation script returned error exit status 255 Apr 14 17:26:05 in-target: dpkg: dependency problems prevent configuration of maas-region-controller: Apr 14 17:26:05 in-target: maas-region-controller depends on maas-region-controller-min (= 1.5+bzr2236-0ubuntu1); however: Apr 14 17:26:05 in-target: Package maas-region-controller-min is not configured yet. Apr 14 17:26:05 in-target: Apr 14 17:26:05 in-target: dpkg: error processing package maas-region-controller (--configure): Apr 14 17:26:05 in-target: dependency problems - leaving unconfigured Apr 14 17:26:05 in-target: dpkg: dependency problems prevent configuration of maas: Apr 14 17:26:05 in-target: maas depends on maas-region-controller; however: Apr 14 17:26:05 in-target: Package maas-region-controller is not configured yet. Apr 14 17:26:05 in-target: Apr 14 17:26:05 in-target: dpkg: error processing package maas (--configure): Apr 14 17:26:05 in-target: dependency problems - leaving unconfigured Apr 14 17:26:05 in-target: dpkg: dependency problems prevent configuration of maas-dns: Apr 14 17:26:05 in-target: maas-dns depends on maas-region-controller-min (= 1.5+bzr2236-0ubuntu1); however: Apr 14 17:26:05 in-target: Package maas-region-controller-min is not configured yet. Apr 14 17:26:05 in-target: Apr 14 17:26:05 in-target: dpkg: error processing package maas-dns (--configure): Apr 14 17:26:05 in-target: dependency problems - leaving unconfigured Apr 14 17:26:05 in-target: Errors were encountered while processing: Apr 14 17:26:05 in-target: maas-region-controller-min Apr 14 17:26:05 in-target: maas-region-controller Apr 14 17:26:05 in-target: maas Apr 14 17:26:05 in-target: maas-dns Apr 14 17:26:06 main-menu[220]: WARNING **: Configuring 'pkgsel' failed with error code 100 Apr 14 17:26:06 main-menu[220]: WARNING **: Menu item 'pkgsel' failed. ** Attachment added: install.tgz https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1172566/+attachment/4083633/+files/install.tgz -- 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/1172566 Title: MAAS Server ISO install fails when network is disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1172566/+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 1172566] Re: MAAS Server ISO install fails when network is disconnected
so the bug here is actually in 'get_default_route_ip' of the postinst
for maas-region-controller-min and maas-region-controller.
They run with 'set -e' (which i'm never a fan of), and then have:
get_default_route_ip() {
while read Iface Destination Gateway Flags RefCnt Use Metric Mask MTU Window
IRTT; do [ $Mask = ] break
done /proc/net/route
interface=$Iface
ipaddr=$(LC_ALL=C /sbin/ip -4 addr list dev $interface scope global)
ipaddr=${ipaddr#* inet }
ipaddr=${ipaddr%%/*}
echo $ipaddr
}
That method has many issues.
a.) will stomp over global variables 'iface' 'Destination' Gateway, Flags
and 'interface'. luckily it is only run in a subshell, so thats not really a
problem here.
b.) if interface is empty it runs : ip -4 addr list dev scope global
ip fails, thus the method fails, and thus the dpkg postinst fails
(thanks to set -e).
the simpllist fix is just to add:
[ -n $interface ] || return 0
right after the loop that reads /proc/net/route.
--
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/1172566
Title:
MAAS Server ISO install fails when network is disconnected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1172566/+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 1172566] Re: MAAS Server ISO install fails when network is disconnected
** Branch linked: lp:~smoser/ubuntu/trusty/maas/lp-1172566 -- 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/1172566 Title: MAAS Server ISO install fails when network is disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1172566/+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 1172566] Re: MAAS Server ISO install fails when network is disconnected
fix in lp:~smoser/ubuntu/trusty/maas/lp-1172566. ** Changed in: maas (Ubuntu) Status: Confirmed = Triaged -- 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/1172566 Title: MAAS Server ISO install fails when network is disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1172566/+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 1304407] Re: juju bootstrap on openstack cloud defaults to i386
I would target this to a 1.18.2 if it existed. This is a change in behavior from 1.16 to 1.18. If you just do: juju-1.18 bootstrap -e amazon I end up getting a i386 target. I have to do: juju-1.18 bootstrap -e amazon --constraints=arch=amd64 for it to pick a amd64 (which was always the default in 1.16). I would probably expect the tool to default to its own architecture (so if deploying from an amd64 prefer an amd64, etc). ** Also affects: juju-core/1.18 Importance: Undecided Status: New ** Changed in: juju-core/1.18 Importance: Undecided = High ** Changed in: juju-core/1.18 Status: New = Triaged ** Summary changed: - juju bootstrap on openstack cloud defaults to i386 + juju bootstrap defaults to i386 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1304407 Title: juju bootstrap defaults to i386 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1304407/+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 1287726] Re: Wrong evaluation whether json is valid or not
Problem is that the old php-json package conforms to the json standard, and the new one does not. If someone went through the effort (we do not have the resources, unfortunately) to make json-c conform to the json standard with said flag, then yes - you could simply compile the package with that flag enabled, and all would be good. The impact of the bug? Json is used all over the place for many years, since it's a very good lightweight format for exchanging data. All of the services provided on a Ubuntu system will potentially break, since it does not conform to the json standard that everyone else does. We had to switch our servers that was running Ubuntu since 2010 to NetBSD to get a modern PHP with proper json handling. Our unit tests broke immediately when we switched to Ubuntu 13.10. There's a good thread with proper comments about the thing here, which shows several aspects of the thing: http://www.reddit.com/r/PHP/comments/1ksnzw/php_json_removed_in_php_55/ Do not forget the fact, that the reason it was removed was that it had this line together with its license: The Software shall be used for Good, not Evil. which makes it 'non-free' software. Have a look at the entire license here, and see for yourself. http://www.json.org/license.html It's still a possibility to simply ship the php-json included in php, instead of potentially breaking thousands of server setups that rely on a php-json conforming to the json standard. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php-json in Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+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 1304167] Re: syntax error, trusty beta-2 cloud image
This bug was fixed in the package lxc - 1.0.3-0ubuntu3 --- lxc (1.0.3-0ubuntu3) trusty; urgency=medium * Add a dependency on the new apparmor to make sure we have the new parser around before we attempt to load a profile requiring the new stanza support. (LP: #1304167) -- Stephane Graber stgra...@ubuntu.com Mon, 14 Apr 2014 10:10:40 -0400 ** Changed in: lxc (Ubuntu) Status: Triaged = 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/1304167 Title: syntax error, trusty beta-2 cloud image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1304167/+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 1307008] Re: cgmanager doesn't stop on shutdown
This bug was fixed in the package cgmanager - 0.24-0ubuntu5 --- cgmanager (0.24-0ubuntu5) trusty; urgency=medium * Add a 'stop on' to the upstart jobs (LP: #1307008) -- Serge Hallyn serge.hal...@ubuntu.com Mon, 14 Apr 2014 00:13:44 -0500 ** Changed in: cgmanager (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1307008 Title: cgmanager doesn't stop on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1307008/+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 1172566] Re: MAAS Server ISO install fails when network is disconnected
Thanks, Scott. Further confirmation: In previous no-network MAAS tests, the environment had no default gateway set. So, the missing dependency claim is debunked. This is not a dependency, nor an ISO issue. Dependencies are indeed met on the Trusty ISO. I confirmed this by successful installation of MAAS from ISO on a machine with a fully configured ip interface, but with no internet access. The 'no-network MAAS install failure' issue that we're seeing is specifically caused by having no default gateway set. -- 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/1172566 Title: MAAS Server ISO install fails when network is disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1172566/+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 1298559] Re: Internal Server Error after installing MAAS from Trusty daily ISO
Take note: the missing dependency claim is debunked. Dependencies are indeed met on the Trusty ISO. I confirmed this by successful installation of MAAS from ISO on a machine with a fully configured ip interface, but with no internet access. There is however, a separate MAAS installation problem when no default gateway is set. Updated bug 1172566. -- 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/1298559 Title: Internal Server Error after installing MAAS from Trusty daily ISO To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1298559/+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 1267557] Re: [MIR] heat
This bug was fixed in the package heat - 2014.1~rc2-0ubuntu3 --- heat (2014.1~rc2-0ubuntu3) trusty; urgency=medium * debian/heat-common.postinst: Fix failing autopkg test. -- Chuck Short zul...@ubuntu.com Mon, 14 Apr 2014 13:36:05 -0400 ** Changed in: heat (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to heat in Ubuntu. https://bugs.launchpad.net/bugs/1267557 Title: [MIR] heat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heat/+bug/1267557/+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
** This bug is no longer a duplicate of bug 1304167 syntax error, trusty beta-2 cloud image -- 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/libvirt/+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 1307436] Re: cloudarchive-icehouse: virt-aa-helper: error: apparmor_parser exited with error
In that case either apparmor will need to be added to the archive, or libvirt in the archive will need to carry a patch on top of the trusty version, since the apparmor policy language does not yet support versioning. ** Changed in: libvirt (Ubuntu) Importance: Undecided = High ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Importance: Undecided = High ** Changed in: apparmor (Ubuntu) Status: New = 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/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 1218959] Re: KVM virbr# no longer forwards multicast traffic by default (U12.04)
** Description changed: A recent kernel update (Apr 2013) has made it's way to U12.04.2 LTS (approx June-Aug 2013) and has stopped the (default) behaviour of automatically forwarding multicast traffic over virbr#. Some updates the bridge subsystem now, by default, disable multicast traffic without IGMP Querier being enabled on that bridge. The corresponding Fedora/RHEL bug tracks the progress/updates of this specific change in relation to Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=880035 (I have yet to find a similar bug report in Ubuntu so I have created this bug to help the Ubuntu community identify multicast issues that may arise since April 2013 in U12.04 LTS and presumably other Ubuntu releases as backports are made and break regression testing.) Using the latest patches in U12.04.2 LTS this following addition, with some modifications, can be made to the udev rules will enable multicast on virbr# bridge: https://bugzilla.redhat.com/show_bug.cgi?id=880035#c38 While this is an improvement/correction to KVM bridge networking it has broken existing functionality in U12.04.2 LTS and broke regressed functionality that once worked. + + IMPACT: multicast is broken over libvirt bridges + FIX: set a (new, introduced by a new kernel) toggle on the bridges + TEST CASE: cat /sys/devices/virtual/net/virbr0/bridge/multicast_querier - if 0, then forwarding multicast will be broken. + REGRESSION POTENTIAL: should be none. older kernels do not have the toggle, and failure to set it will be ignored ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Incomplete = 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/1218959 Title: KVM virbr# no longer forwards multicast traffic by default (U12.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1218959/+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 1266066] Re: [MIR] strongSwan
openvswitch-ipsec Depends on racoon from ipsec-tools. This comes from openvswitch-- I thought openvswitch needed packaging updates for demoting openvswitch-ipsec, but it does not. openvswitch-ipsec is demoted. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unbound in Ubuntu. https://bugs.launchpad.net/bugs/1266066 Title: [MIR] strongSwan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1266066/+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 1266066] Re: [MIR] strongSwan
ipsec-tools 1:0.8.0-14ubuntu4 in trusty: main/net - universe ipsec-tools 1:0.8.0-14ubuntu4 in trusty amd64: main/net/extra/100% - universe ipsec-tools 1:0.8.0-14ubuntu4 in trusty arm64: main/net/extra/100% - universe ipsec-tools 1:0.8.0-14ubuntu4 in trusty armhf: main/net/extra/100% - universe ipsec-tools 1:0.8.0-14ubuntu4 in trusty i386: main/net/extra/100% - universe ipsec-tools 1:0.8.0-14ubuntu4 in trusty powerpc: main/net/extra/100% - universe ipsec-tools 1:0.8.0-14ubuntu4 in trusty ppc64el: main/net/extra/100% - universe racoon 1:0.8.0-14ubuntu4 in trusty amd64: main/net/extra/100% - universe racoon 1:0.8.0-14ubuntu4 in trusty arm64: main/net/extra/100% - universe racoon 1:0.8.0-14ubuntu4 in trusty armhf: main/net/extra/100% - universe racoon 1:0.8.0-14ubuntu4 in trusty i386: main/net/extra/100% - universe racoon 1:0.8.0-14ubuntu4 in trusty powerpc: main/net/extra/100% - universe racoon 1:0.8.0-14ubuntu4 in trusty ppc64el: main/net/extra/100% - universe Override [y|N]? y 13 publications overridden. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unbound in Ubuntu. https://bugs.launchpad.net/bugs/1266066 Title: [MIR] strongSwan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1266066/+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 1266066] Re: [MIR] strongSwan
Release note added for strongswan official support and ipsec-tools community support. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unbound in Ubuntu. https://bugs.launchpad.net/bugs/1266066 Title: [MIR] strongSwan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1266066/+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 1307682] [NEW] samba full_audit reports wrong username when using force user
Public bug reported: When using force user in combination with full_audit, the %U audit marco get replaced with the wrong (forced) username. This has been fixed upstream two years ago, but is not yet in precise. https://bugzilla.samba.org/show_bug.cgi?id=8882 You be great to apply this to precise as well. https://attachments.samba.org/attachment.cgi?id=7476 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: samba 2:3.6.3-2ubuntu2.10 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Apr 14 21:51:46 2014 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) MarkForUpload: True OtherFailedConnect: Yes ProcEnviron: TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 LC_MESSAGES=en_US.utf-8 SHELL=/bin/bash SambaServerRegression: Yes SmbConfIncluded: No SourcePackage: samba UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/1307682 Title: samba full_audit reports wrong username when using force user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307682/+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 1306916] Re: cgroup-lite should be added as an explicit dependency
Here you are. $ sudo cat /var/log/upstart/cgmanager.log cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0) -- 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/1306916 Title: cgroup-lite should be added as an explicit dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1306916/+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 1266066] Re: [MIR] strongSwan
$ ./change-override -c main strongswan strongswan-ike strongswan-plugin-dhcp strongswan-plugin-eap-md5 strongswan-plugin-eap-mschapv2 strongswan-plugin-eap-peap strongswan-plugin-eap-radius strongswan-plugin-eap-tls strongswan-plugin-eap-tnc strongswan-plugin-eap-ttls strongswan-plugin-gmp strongswan-plugin-ldap strongswan-plugin-mysql strongswan-plugin-openssl strongswan-plugin-pkcs11 strongswan-plugin-radattr strongswan-plugin-sql strongswan-plugin-unbound strongswan-pt-tls-client strongswan-tnc-base strongswan-tnc-client strongswan-tnc-pdp strongswan-tnc-server Override component to main strongswan 5.1.2-0ubuntu1 in trusty amd64: universe/net/optional/100% - main strongswan 5.1.2-0ubuntu1 in trusty arm64: universe/net/optional/100% - main strongswan 5.1.2-0ubuntu1 in trusty armhf: universe/net/optional/100% - main strongswan 5.1.2-0ubuntu1 in trusty i386: universe/net/optional/100% - main strongswan 5.1.2-0ubuntu1 in trusty powerpc: universe/net/optional/100% - main strongswan 5.1.2-0ubuntu1 in trusty ppc64el: universe/net/optional/100% - main strongswan-ike 5.1.2-0ubuntu1 in trusty amd64: universe/net/optional/100% - main strongswan-ike 5.1.2-0ubuntu1 in trusty arm64: universe/net/optional/100% - main strongswan-ike 5.1.2-0ubuntu1 in trusty armhf: universe/net/optional/100% - main strongswan-ike 5.1.2-0ubuntu1 in trusty i386: universe/net/optional/100% - main strongswan-ike 5.1.2-0ubuntu1 in trusty powerpc: universe/net/optional/100% - main strongswan-ike 5.1.2-0ubuntu1 in trusty ppc64el: universe/net/optional/100% - main strongswan-plugin-dhcp 5.1.2-0ubuntu1 in trusty amd64: universe/net/optional/100% - main strongswan-plugin-dhcp 5.1.2-0ubuntu1 in trusty arm64: universe/net/optional/100% - main strongswan-plugin-dhcp 5.1.2-0ubuntu1 in trusty armhf: universe/net/optional/100% - main strongswan-plugin-dhcp 5.1.2-0ubuntu1 in trusty i386: universe/net/optional/100% - main strongswan-plugin-dhcp 5.1.2-0ubuntu1 in trusty powerpc: universe/net/optional/100% - main strongswan-plugin-dhcp 5.1.2-0ubuntu1 in trusty ppc64el: universe/net/optional/100% - main strongswan-plugin-eap-md5 5.1.2-0ubuntu1 in trusty amd64: universe/net/optional/100% - main strongswan-plugin-eap-md5 5.1.2-0ubuntu1 in trusty arm64: universe/net/optional/100% - main strongswan-plugin-eap-md5 5.1.2-0ubuntu1 in trusty armhf: universe/net/optional/100% - main strongswan-plugin-eap-md5 5.1.2-0ubuntu1 in trusty i386: universe/net/optional/100% - main strongswan-plugin-eap-md5 5.1.2-0ubuntu1 in trusty powerpc: universe/net/optional/100% - main strongswan-plugin-eap-md5 5.1.2-0ubuntu1 in trusty ppc64el: universe/net/optional/100% - main strongswan-plugin-eap-mschapv2 5.1.2-0ubuntu1 in trusty amd64: universe/net/optional/100% - main strongswan-plugin-eap-mschapv2 5.1.2-0ubuntu1 in trusty arm64: universe/net/optional/100% - main strongswan-plugin-eap-mschapv2 5.1.2-0ubuntu1 in trusty armhf: universe/net/optional/100% - main strongswan-plugin-eap-mschapv2 5.1.2-0ubuntu1 in trusty i386: universe/net/optional/100% - main strongswan-plugin-eap-mschapv2 5.1.2-0ubuntu1 in trusty powerpc: universe/net/optional/100% - main strongswan-plugin-eap-mschapv2 5.1.2-0ubuntu1 in trusty ppc64el: universe/net/optional/100% - main strongswan-plugin-eap-peap 5.1.2-0ubuntu1 in trusty amd64: universe/net/optional/100% - main strongswan-plugin-eap-peap 5.1.2-0ubuntu1 in trusty arm64: universe/net/optional/100% - main strongswan-plugin-eap-peap 5.1.2-0ubuntu1 in trusty armhf: universe/net/optional/100% - main strongswan-plugin-eap-peap 5.1.2-0ubuntu1 in trusty i386: universe/net/optional/100% - main strongswan-plugin-eap-peap 5.1.2-0ubuntu1 in trusty powerpc: universe/net/optional/100% - main strongswan-plugin-eap-peap 5.1.2-0ubuntu1 in trusty ppc64el: universe/net/optional/100% - main strongswan-plugin-eap-radius 5.1.2-0ubuntu1 in trusty amd64: universe/net/optional/100% - main strongswan-plugin-eap-radius 5.1.2-0ubuntu1 in trusty arm64: universe/net/optional/100% - main strongswan-plugin-eap-radius 5.1.2-0ubuntu1 in trusty armhf: universe/net/optional/100% - main strongswan-plugin-eap-radius 5.1.2-0ubuntu1 in trusty i386: universe/net/optional/100% - main strongswan-plugin-eap-radius 5.1.2-0ubuntu1 in trusty powerpc: universe/net/optional/100% - main strongswan-plugin-eap-radius 5.1.2-0ubuntu1 in trusty ppc64el: universe/net/optional/100% - main strongswan-plugin-eap-tls 5.1.2-0ubuntu1 in trusty amd64: universe/net/optional/100% - main strongswan-plugin-eap-tls 5.1.2-0ubuntu1 in trusty arm64: universe/net/optional/100% - main strongswan-plugin-eap-tls 5.1.2-0ubuntu1 in trusty armhf: universe/net/optional/100% - main strongswan-plugin-eap-tls 5.1.2-0ubuntu1 in trusty i386: universe/net/optional/100% - main strongswan-plugin-eap-tls 5.1.2-0ubuntu1 in trusty powerpc: universe/net/optional/100% - main strongswan-plugin-eap-tls 5.1.2-0ubuntu1 in trusty ppc64el: universe/net/optional/100% - main strongswan-plugin-eap-tnc
[Bug 1266066] Re: [MIR] strongSwan
$ ./change-override -c main host libunbound2 libstrongswan strongswan-starter libldns1 Override component to main host 1:9.9.5.dfsg-3 in trusty amd64: universe/net/optional/100% - main host 1:9.9.5.dfsg-3 in trusty arm64: universe/net/optional/100% - main host 1:9.9.5.dfsg-3 in trusty armhf: universe/net/optional/100% - main host 1:9.9.5.dfsg-3 in trusty i386: universe/net/optional/100% - main host 1:9.9.5.dfsg-3 in trusty powerpc: universe/net/optional/100% - main host 1:9.9.5.dfsg-3 in trusty ppc64el: universe/net/optional/100% - main libunbound2 1.4.22-1ubuntu4 in trusty amd64: universe/net/optional/100% - main libunbound2 1.4.22-1ubuntu4 in trusty arm64: universe/net/optional/100% - main libunbound2 1.4.22-1ubuntu4 in trusty armhf: universe/net/optional/100% - main libunbound2 1.4.22-1ubuntu4 in trusty i386: universe/net/optional/100% - main libunbound2 1.4.22-1ubuntu4 in trusty powerpc: universe/net/optional/100% - main libunbound2 1.4.22-1ubuntu4 in trusty ppc64el: universe/net/optional/100% - main libstrongswan 5.1.2-0ubuntu1 in trusty amd64: universe/net/optional/100% - main libstrongswan 5.1.2-0ubuntu1 in trusty arm64: universe/net/optional/100% - main libstrongswan 5.1.2-0ubuntu1 in trusty armhf: universe/net/optional/100% - main libstrongswan 5.1.2-0ubuntu1 in trusty i386: universe/net/optional/100% - main libstrongswan 5.1.2-0ubuntu1 in trusty powerpc: universe/net/optional/100% - main libstrongswan 5.1.2-0ubuntu1 in trusty ppc64el: universe/net/optional/100% - main strongswan-starter 5.1.2-0ubuntu1 in trusty amd64: universe/net/optional/100% - main strongswan-starter 5.1.2-0ubuntu1 in trusty arm64: universe/net/optional/100% - main strongswan-starter 5.1.2-0ubuntu1 in trusty armhf: universe/net/optional/100% - main strongswan-starter 5.1.2-0ubuntu1 in trusty i386: universe/net/optional/100% - main strongswan-starter 5.1.2-0ubuntu1 in trusty powerpc: universe/net/optional/100% - main strongswan-starter 5.1.2-0ubuntu1 in trusty ppc64el: universe/net/optional/100% - main libldns1 1.6.17-1 in trusty amd64: universe/libs/extra/100% - main libldns1 1.6.17-1 in trusty arm64: universe/libs/extra/100% - main libldns1 1.6.17-1 in trusty armhf: universe/libs/extra/100% - main libldns1 1.6.17-1 in trusty i386: universe/libs/extra/100% - main libldns1 1.6.17-1 in trusty powerpc: universe/libs/extra/100% - main libldns1 1.6.17-1 in trusty ppc64el: universe/libs/extra/100% - main Override [y|N]? y 30 publications overridden. $ ./change-override -c main -t unbound Override component to main unbound 1.4.22-1ubuntu4 in trusty: universe/net - main Override [y|N]? y 1 publication overridden. $ ./change-override -c main -t ldns Override component to main ldns 1.6.17-1 in trusty: universe/net - main Override [y|N]? y 1 publication overridden. ** Changed in: ldns (Ubuntu) Status: Fix Committed = Fix Released ** Changed in: unbound (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unbound in Ubuntu. https://bugs.launchpad.net/bugs/1266066 Title: [MIR] strongSwan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1266066/+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 1307695] [NEW] package snmpd 5.7.2~dfsg-8ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Failed Install ProblemType: Package DistroRelease: Ubuntu 13.10 Package: snmpd 5.7.2~dfsg-8ubuntu1.1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Apr 14 15:15:48 2014 DuplicateSignature: package:snmpd:5.7.2~dfsg-8ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-12-22 (113 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SNMPVersion: NET-SNMP version: 5.7.2 Web: http://www.net-snmp.org/ Email: net-snmp-cod...@lists.sourceforge.net SourcePackage: net-snmp SyslogSnmptrapd: Title: package snmpd 5.7.2~dfsg-8ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1307695 Title: package snmpd 5.7.2~dfsg-8ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1307695/+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 1306484] Re: Icehouse: nova-compute-vmware requires genisoimage package
** Changed in: nova (Ubuntu) Status: New = Triaged ** Changed in: nova (Ubuntu) Importance: Undecided = High ** Changed in: nova (Ubuntu) Assignee: (unassigned) = Chuck Short (zulcss) -- 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/1306484 Title: Icehouse: nova-compute-vmware requires genisoimage package To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1306484/+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
