[Bug 1303880] Re: Juju 1.18.0, can not deploy local charms without series
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- 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 1306208] Re: juju scp no longer allows multiple extra arguments to pass throug
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- 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 1303697] Re: peer relation disappears during upgrade of juju
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- 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 1306296] Re: juju cannot downgrade to same major.minor version with earlier patch number
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- 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 1303735] Re: public-address change to internal bridge post juju-upgrade
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- 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 1299802] Re: upgrade-juju 1.16.6 -> 1.18 (tip) fails
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- 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 1306877] Re: sshd stops accepting new connections after configuration reload
This is the change I mentioned above: https://github.com/nya3jp/openssh-debian/commit/0334ce32304e9ba2a10ee5ca49ca6e8ff3ba6cf4 As a workaround, I commented out these two lines in /etc/init/ssh.conf: # env SSH_SIGSTOP=1 # expect stop Now "initctl reload ssh" works fine, though I'm not really sure I'm doing a "right" thing. -- 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 1306880] [NEW] virt-manager / libvirt fails to create VM due to PCI ordering bug
Public bug reported: Hi there; libvirt in trusty has a bug where VM's fail to get defined due to PCI bus ordering bugs. Redhat bug tracker info here: https://bugzilla.redhat.com/show_bug.cgi?id=823535 Appears to be the same bug. Steps to reproduce: * Open Virt-manager * Define a new VM ( I used reactos installer iso) * Attempt to run. Get something like this: " Unable to complete install: 'internal error: process exited while connecting to monitor: qemu-system-x86_64: -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:f4:4b:50,bus=pci.0,addr=0x1: PCI: slot 1 function 0 not available for rtl8139, in use by PIIX3 qemu-system-x86_64: -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:f4:4b:50,bus=pci.0,addr=0x1: Device initialization failed. qemu-system-x86_64: -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:f4:4b:50,bus=pci.0,addr=0x1: Device 'rtl8139' could not be initialized ' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1983, in do_install guest.start_install(False, meter=meter) File "/usr/lib/python2.7/dist-packages/virtinst/Guest.py", line 1246, in start_install noboot) File "/usr/lib/python2.7/dist-packages/virtinst/Guest.py", line 1314, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3199, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: qemu-system-x86_64: -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:f4:4b:50,bus=pci.0,addr=0x1: PCI: slot 1 function 0 not available for rtl8139, in use by PIIX3 qemu-system-x86_64: -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:f4:4b:50,bus=pci.0,addr=0x1: Device initialization failed. qemu-system-x86_64: -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:f4:4b:50,bus=pci.0,addr=0x1: Device 'rtl8139' could not be initialized " Attempted resolutions: Removing Devices/reordering them via virt-manager still fails to solve the issue ( you manually need to hack at the .xml definition). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 12 17:11:24 2014 InstallationDate: Installed on 2014-03-31 (11 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] ** Affects: libvirt Importance: Unknown Status: Unknown ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Bug watch added: Red Hat Bugzilla #823535 https://bugzilla.redhat.com/show_bug.cgi?id=823535 ** Also affects: libvirt via https://bugzilla.redhat.com/show_bug.cgi?id=823535 Importance: Unknown Status: Unknown -- 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/1306880 Title: virt-manager / libvirt fails to create VM due to PCI ordering bug To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1306880/+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] [NEW] sshd stops accepting new connections after configuration reload
Public bug reported: When upstart is enabled, sshd stops accepting new connections after reloading configuration by "initctl reload ssh". It looks like sshd is frozen with SIGSTOP after receiving SIGHUP. [nya@sora ~]% ps auxww | grep sshd root 10557 0.0 0.1 61364 3056 ?Ss 13:46 0:00 /usr/sbin/sshd -D [nya@sora ~]% sudo strace -p 10557 Process 10557 attached select(7, [3 4], NULL, NULL, NULL^CProcess 10557 detached [nya@sora ~]% sudo reload ssh [nya@sora ~]% sudo strace -p 10557 Process 10557 attached --- stopped by SIGSTOP --- I guess it's caused by a Debian-specific patch: debian/patches/sigstop.patch. The patch makes sshd STOP when it's ready to start and have upstart resume it by specifying "expect stop" in /etc/init/ssh.conf. On receiving SIGHUP sshd re-executes itself and STOPs again, but upstart does not perform resume. Reproduced under Ubuntu 14.04 Trusty Package version: openssh 1:6.6p1-2 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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 1218959] Re: KVM virbr# no longer forwards multicast traffic by default (U12.04)
** Also affects: linux (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/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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
This bug was fixed in the package systemd - 204-5ubuntu19 --- systemd (204-5ubuntu19) trusty; urgency=medium * cgmanager: don't call nih_dbus_setup() since we won't use the nih_mainloop(). (LP: #1303649) -- Serge HallynFri, 11 Apr 2014 10:17:04 -0500 ** Changed in: systemd (Ubuntu) Status: Confirmed => 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/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
In comment #9 you said "with vanilla kernel" - can you please list the exact kernel versions you've tried (and which qemu versions you tried with them, including whether they were hand-built from git or packages from Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+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 746114] Re: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
I still was not able to reproduce this, using virt-manager on trusty and using mostly the defaults. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/746114 Title: FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/746114/+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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
** Changed in: libnih (Ubuntu) Status: Confirmed => Invalid ** Changed in: cgmanager (Ubuntu) Status: Confirmed => 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/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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/1.18 Status: Fix Committed => Fix Released -- 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 1299802] Re: upgrade-juju 1.16.6 -> 1.18 (tip) fails
** Changed in: juju-core/1.18 Status: Fix Committed => Fix Released -- 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
** Changed in: juju-core/1.18 Status: Fix Committed => Fix Released -- 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 1303697] Re: peer relation disappears during upgrade of juju
** Changed in: juju-core/1.18 Status: Fix Committed => Fix Released -- 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 1306296] Re: juju cannot downgrade to same major.minor version with earlier patch number
** Changed in: juju-core/1.18 Status: Fix Committed => Fix Released -- 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
** Changed in: juju-core/1.18 Status: Fix Committed => Fix Released -- 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 1276714] Re: package openssh-server 1:6.2p2-6ubuntu0.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssh (Ubuntu) Status: New => Confirmed -- 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/1276714 Title: package openssh-server 1:6.2p2-6ubuntu0.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1276714/+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 1303986] Re: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly
** Also affects: cloud-init (Ubuntu Trusty) Importance: Undecided Assignee: Ben Howard (utlemming) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1303986 Title: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1303986/+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, it's been noted that this is slightly different from the desktop/ubiquity case only in that the ubiquity case presents the user up-front with the "do you want non-free stuff?" toggle on an installer page, while maas is putting it in a settings page. So, for starters, I think the settings page is the *right* place for it to live. It's a setting. That's where I should go if I want to turn it off and on. That said, it's a valid point that this is a setting most people won't go looking for, and it'll just be weirdly confusing when they go to install on certain hardware and it just doesn't work. Since we can't, apparently, talk certain hardware vendors (*cough*) into shipping free drivers, I proposed the following: 1) Keep the master toggle in the settings page. That's where it belongs. That's where I'd go to turn it off and on. 2) When installing the maas master node (ie: the maas package itself), present my with a debconf question that reads similarly to the ubiquity prompt, "blah blah non-free stuff, blah blah, you might need it for certain hardware support" (list specific HP servers and other things, if that's helpful to make people know they want/need the feature), default that to off, but set the priority high enough that they'll see the question. 3) Make the response to that debconf question twiddle the same config file that the settings page in the web UI does. 4) Profit. This would, I think, satisfy the visibility issue, while not turning this into a "do we need to take this to the TB to vote it down and then try to come up with ways to compromise our ideals against usibility" argument. -- 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
(To be clear to people following along, I'm fine with Mark's assessment and explicit ACK of the FFe, and we'll happily accept the feature being uploaded under his conditions of being heavily tested, etc, the above quibbling is only about if the feature is on or off in a default setup) -- 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
Right, so the key here (on the software freedom front), as it was with ubiquity when we discussed it, is that the option needs to be off by default. If a sysadmin turns it on (and I don't doubt that many will), that's entirely fine, but they need to be the ones explicitly making the call. If we made the call for them, and then noted "oh, by the way, there's some non-free junk installed", that's too late in the process for good- faith here. And, even if this wasn't about the software freedom aspect of "something in main installing non-free stuff by default", I'd be wary of installing anything from an external repository by default without a toggle (defaulting to off) anyway. Thankfully, most paranoid sysadmins would firewall this to oblivion and notice immediately that it's not working when it tries to call out, but we can do better than requiring people to discover weird third-party server hits via draconian firewalls. -- 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 1306484] Re: Icehouse: nova-compute-vmware requires genisoimage package
** Also affects: nova (Ubuntu) Importance: Undecided Status: New -- 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
[Bug 1305839] Re: FFe: Support for Third Party Driver Installation
Also, thank you Adam for pointing out that we need to do the same sort of ubiquity- and jockey-like calling out of the issues associated with binary blobs on servers that we do on the PC. I'll get the MAAS folks to make that very clear on the node page as a way of socialising the benefits of open drivers. -- 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 1267557] Re: [MIR] heat
** No longer affects: py-sendfile (Ubuntu) -- 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 1306178] Re: maas-region-controller-min overwrites changes to /etc/maas/maas_local_settings.py
Scott, thanks for the information. I wasn't aware of that. Given the new rationale, I think we can mark this bug as triaged. ** Changed in: maas 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/1306178 Title: maas-region-controller-min overwrites changes to /etc/maas/maas_local_settings.py To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1306178/+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
Thanks all for the comments and discussion. Responding to some key points: * building confidence in code changes both for this FFE and subsequent SRUs is important, the archive and RM teams have a mandate to seek comfort on that front before ack'ing an upload under either circumstances * in other words - thank you for calling out the late change :) * I have asked and the MAAS team have assured that all SRU changes will come with appropriate test suites * I would expect to see a test suite for this change and would expect that test suite to have been run on the appropriate hardware. Separately, we'll arrange to have MAAS CI and testing integrated to the OIL lab, which has a rapidly growing range of hardware. * installing the necessary drivers is the norm in the linux environment; warning the user about the consequences of this is the norm in the Ubuntu environment. * I'd ask that we accept this FFE once tests are in place, or if needed, with a commitment to tests as a zero-day SRU * I'd ask that the MAAS team commit to flagging the installation of such drivers in the MAAS node UI, possibly also with a flag on the node listing * all of this assumes the existence of a setting which enables a system administrator to tell MAAS not to do this by default on any given machine without explicit approval As general guidance, this is an area that will evolve fast in the coming months and years, so I've asked the MAAS team to keep developing on 14.04 LTS as their primary platform, introducing no dependencies that are not in 14.04, so we can SRU. If we need to move to universe to make that more comfortable for the release team, let's do that. We got stuck in 12.04 with old versions of key tools that should have been moved - stuck because of bad thinking on the deps front, and perceived dogma on the RM front. We can do better this time by requiring rigorous CI and testing on SRUs, and being sensible about deps. That goes for maas, juju and related tools, all of which need to be current and useful in the coming two years. -- 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 1306484] Re: Icehouse: nova-compute-vmware requires genisoimage package
** Branch linked: lp:~ubuntu-server-dev/nova/icehouse -- 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
[Bug 1304107] Re: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized
** Changed in: cloud-archive Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1304107 Title: Libvirt error launching instance - Device 'virtio-net-pci' could not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1304107/+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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
This bug was fixed in the package lxc - 1.0.3-0ubuntu2 --- lxc (1.0.3-0ubuntu2) trusty; urgency=medium * Cherry-pick upstream fix for cgmanager integration. (LP: #1303649) -- Stephane GraberFri, 11 Apr 2014 12:17:41 -0400 ** Changed in: lxc (Ubuntu) Status: Confirmed => 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/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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 1305343] Re: tgt connection issues can make it impossible to delete targets
This bug was fixed in the package tgt - 1:1.0.43-0ubuntu4 --- tgt (1:1.0.43-0ubuntu4) trusty; urgency=medium * debian/patches/fix_delayed_management_request.patch: Adjust patch to fix a FTBFS. * debian/patches/fix_leak_of_task_in_scsi_flag.patch: Adjust patch to fix a FTBFS. -- Chuck ShortFri, 11 Apr 2014 09:14:03 -0400 ** Changed in: tgt (Ubuntu Trusty) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1305343 Title: tgt connection issues can make it impossible to delete targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1305343/+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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
** Branch linked: lp:ubuntu/trusty-proposed/systemd -- 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/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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 1302575] Re: Meta bug for tracking Openstack 2013.2.3 Stable Update
** Branch linked: lp:ubuntu/saucy-proposed/ceilometer ** Branch linked: lp:ubuntu/saucy-proposed/heat ** Branch linked: lp:ubuntu/saucy-proposed/horizon -- 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/1302575 Title: Meta bug for tracking Openstack 2013.2.3 Stable Update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1302575/+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 1304135] Re: panic: runtime error: index out of range
** Changed in: juju-core Milestone: 1.18.1 => 1.19.0 ** Also affects: juju-core/1.18 Importance: Undecided Status: New ** Changed in: juju-core/1.18 Assignee: (unassigned) => Tim Penhey (thumper) ** Changed in: juju-core/1.18 Importance: Undecided => Critical ** Changed in: juju-core/1.18 Status: New => Fix Committed ** 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/1304135 Title: panic: runtime error: index out of range To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1304135/+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
FYI, python-sendfile also needs a MIR. ** Also affects: py-sendfile (Ubuntu) Importance: Undecided Status: New ** Changed in: py-sendfile (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- 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 1303986] Re: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly
The change is small and looks reasonable to me, so FFe granted. However we are in final freeze, so you'll need to justify why we need this now rather than post-release as a SRU. ** Changed in: cloud-init (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1303986 Title: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1303986/+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 1303986] Re: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly
** Description changed: Cloud Sigma has asked that we update the DataSource in Cloud-init to support the 14.04 VendorData construct. The regression potential for this change is low, as only the cloud-init Cloud-Sigma datasource is changed, a test suite has been provided and it has been tested by Cloud Sigma. - [ORIGINAL BUG REPORT] + The reason for this late-in-the-cylce change is so that Cloud Sigma can + have use the official Ubuntu Images with out conflating user and vendor- + data. Currently Cloud Sigma uses the user-data channel improperly for + transmitting vendor specific information to Cloud-init, when they should + be using the vendor-data channel. By switching to the proper channel for + vendor specific information, user-data and vendor-data will not be + mangled, preventing collisions of user-data and vendor-specific data. + + [ORIGINAL BUG REPORT] It appears as the CloudSigma datasource only has support for 'user-data', and not 'vendor-data.' -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1303986 Title: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1303986/+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 1303986] Re: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly
If this is well tested, the change looks small and sane enough to me. Go for it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1303986 Title: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1303986/+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 1208430] Re: mongodb runs as root user
So, yes, this is something that should be fixed, however, if you have access to the database, you can just add data to it to tell Juju to spin up a unit on the bootstrap node that runs as root and you can then do whatever you want with it. So, while it would be better for appearances' sake to not have mongodb running as root, it doesn't actually close any security holes to a determined attacker. In addition, it's a non-trivial change, since it means we have to create a new user to run mongo as, and in theory upgrade old environments to fix them as well. My suggestion is that we leave it as high and deal with it later. -- 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/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+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 1306710] Re: package postfix (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1306710 Title: package postfix (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1306710/+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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
Right. So to be completely clear, by calling nih_dbus_setup(), nih was registering a libdbus handler that runs on the client side such that whenever libdbus deemed necessary, it would attempt to wake up the clients main loop by calling nih_main_loop_interrupt(). However, since the client didn't have an nih main loop, the interrupt pipe was never drained and eventually filled leading to the EAGAIN tight loop. Yes, I agree - maybe it should have been called nih_dbus_main_loop_setup() to make its usage clearer. -- 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/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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
** Changed in: dnsmasq (Debian) Status: Unknown => Fix Released -- 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 1303986] Re: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly
Attached patch showing that changes only affect the Cloud Sigma DS. ** Summary changed: - CloudSigma Datasource doesn't handle vendor-data correctly + [FFe] CloudSigma Datasource doesn't handle vendor-data correctly ** Changed in: cloud-init Assignee: (unassigned) => Ben Howard (utlemming) ** Description changed: - It appears as the CloudSigma datasource only has support for 'user- - data', and not 'vendor-data.' + Cloud Sigma has asked that we update the DataSource in Cloud-init to + support the 14.04 VendorData construct. The regression potential for + this change is low, as only the cloud-init Cloud-Sigma datasource is + changed, a test suite has been provided and it has been tested by Cloud + Sigma. + + [ORIGINAL BUG REPORT] + It appears as the CloudSigma datasource only has support for 'user-data', and not 'vendor-data.' ** Project changed: cloud-init => cloud-init (Ubuntu) ** Branch linked: lp:~utlemming/ubuntu/trusty/cloud-init/lp1303986 ** Patch added: "debdiff of 0.7.5-0ubuntu1 to 0.7.5-0ubuntu2" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1303986/+attachment/4081252/+files/debdiff.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1303986 Title: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1303986/+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 1306701] Re: bootresources.yaml references daily builds for trusty
** Description changed: The current packaged version of /etc/maas/bootresources.yaml references daily builds of trusty. This is because until recently there was nothing marked 'release' (because release wasn't done yet). Having the daily stream installed by default is not acceptable as the daily builds will not recieve the same level of testing as the released builds. The fix is a config file change only and the upstream commit is at - http://bazaar.launchpad.net/~maas-maintainers/maas/1.5/revision/2241 + http://bazaar.launchpad.net/~maas-maintainers/maas/trunk/revision/2254 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas-cluster-controller 1.5+bzr2236-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 11 16:55:54 2014 InstallationDate: Installed on 2014-03-13 (28 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.maas.maas.cluster.conf: [inaccessible: [Errno 13] Permission denied: '/etc/maas/maas_cluster.conf'] modified.conffile..etc.maas.maas.local.celeryconfig.cluster.py: [inaccessible: [Errno 13] Permission denied: '/etc/maas/maas_local_celeryconfig_cluster.py'] modified.conffile..etc.maas.pserv.yaml: [modified] modified.conffile..etc.maas.templates.pxe.config.commissioning.template: [modified] modified.conffile..etc.sudoers.d.99.maas.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/99-maas-sudoers'] mtime.conffile..etc.maas.bootresources.yaml: 2014-04-11T15:27:02.782752 mtime.conffile..etc.maas.pserv.yaml: 2014-04-11T16:54:00.051030 mtime.conffile..etc.maas.templates.pxe.config.commissioning.template: 2014-04-09T19:40:57.842386 upstart.isc-dhcp-server.override: manual -- 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/1306701 Title: bootresources.yaml references daily builds for trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1306701/+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 1306710] [NEW] package postfix (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
Public bug reported: E: Could not get lock /var/cache/apt/archives/lock - open (11: Resource temporarily unavailable) E: Unable to lock directory /var/cache/apt/archives/ This is Ubuntu 12.04 LTS ProblemType: Package DistroRelease: Ubuntu 12.04 Package: postfix (not installed) ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: postfix: Configure Architecture: amd64 Date: Thu Apr 10 13:23:00 2014 DuplicateSignature: package:postfix:(not installed):subprocess installed post-installation script returned error exit status 75 ErrorMessage: subprocess installed post-installation script returned error exit status 75 InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) MarkForUpload: True SourcePackage: postfix Title: package postfix (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1306710 Title: package postfix (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1306710/+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 1303986] [NEW] [FFe] CloudSigma Datasource doesn't handle vendor-data correctly
You have been subscribed to a public bug: Cloud Sigma has asked that we update the DataSource in Cloud-init to support the 14.04 VendorData construct. The regression potential for this change is low, as only the cloud-init Cloud-Sigma datasource is changed, a test suite has been provided and it has been tested by Cloud Sigma. [ORIGINAL BUG REPORT] It appears as the CloudSigma datasource only has support for 'user-data', and not 'vendor-data.' ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: cloudsigma -- [FFe] CloudSigma Datasource doesn't handle vendor-data correctly https://bugs.launchpad.net/bugs/1303986 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init 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 1306335] Re: maas-dhcp needs to quote interface name in /etc/maas/dhcpd.conf
** Changed in: maas (Ubuntu) Importance: High => Critical -- 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/1306335 Title: maas-dhcp needs to quote interface name in /etc/maas/dhcpd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1306335/+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 1306701] [NEW] bootresources.yaml references daily builds for trusty
Public bug reported: The current packaged version of /etc/maas/bootresources.yaml references daily builds of trusty. This is because until recently there was nothing marked 'release' (because release wasn't done yet). Having the daily stream installed by default is not acceptable as the daily builds will not recieve the same level of testing as the released builds. The fix is a config file change only and the upstream commit is at http://bazaar.launchpad.net/~maas-maintainers/maas/1.5/revision/2241 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas-cluster-controller 1.5+bzr2236-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 11 16:55:54 2014 InstallationDate: Installed on 2014-03-13 (28 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.maas.maas.cluster.conf: [inaccessible: [Errno 13] Permission denied: '/etc/maas/maas_cluster.conf'] modified.conffile..etc.maas.maas.local.celeryconfig.cluster.py: [inaccessible: [Errno 13] Permission denied: '/etc/maas/maas_local_celeryconfig_cluster.py'] modified.conffile..etc.maas.pserv.yaml: [modified] modified.conffile..etc.maas.templates.pxe.config.commissioning.template: [modified] modified.conffile..etc.sudoers.d.99.maas.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/99-maas-sudoers'] mtime.conffile..etc.maas.bootresources.yaml: 2014-04-11T15:27:02.782752 mtime.conffile..etc.maas.pserv.yaml: 2014-04-11T16:54:00.051030 mtime.conffile..etc.maas.templates.pxe.config.commissioning.template: 2014-04-09T19:40:57.842386 upstart.isc-dhcp-server.override: manual ** Affects: maas Importance: High Status: Fix Committed ** Affects: maas (Ubuntu) Importance: Critical Status: Triaged ** Tags: amd64 apport-bug trusty ** Also affects: maas Importance: Undecided Status: New ** Changed in: maas Status: New => Fix Committed ** Changed in: maas Importance: Undecided => High -- 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/1306701 Title: bootresources.yaml references daily builds for trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1306701/+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 1306701] Re: bootresources.yaml references daily builds for trusty
This was fix-committed to trunk at revno 2241. ** Changed in: maas (Ubuntu) Status: New => Triaged ** Changed in: maas (Ubuntu) Importance: Undecided => Critical -- 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/1306701 Title: bootresources.yaml references daily builds for trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1306701/+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 743858] Re: sshd not appending to /var/log/btmp
This was superceded by a security upload and will need to be redone for Saucy and Precise. -- 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/743858 Title: sshd not appending to /var/log/btmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/743858/+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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
Actually the source of the problem is that I was calling nih_dbus_setup(), which actually sets up the mainloop. It is not needed - as I thought it was - for making *_sync calls from cgmanager- client.so. So the right fix is to not call that. Two comments on this. First, nih_dbus_setup() seems misleadingly named, though that may just be how I read it. The comments above that function are plenty clear and I should have seen those. Second, the default nih dbus connection is a shared one, which always does nih_dbus_setup(). So for anyone to use libcgmanager without a nih mainloop, they *must* use the dbus_connection_open_private(). We should probably mention that somewhere in the libcgmanager documentation. -- 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/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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: Prevent open recursive DNS server with dnsmasq
Thank you for taking the time to report this bug and helping to make Ubuntu better. Looks like 2.69 was released on 9 April. We have been in feature freeze for Trusty since 20 Februrary, and final freeze was yesterday, so I don't think that we'll be able to do this in time for Trusty. But as there is a security element here, I've asked a member of the security team for input. I see that 2.69 has been uploaded to Debian unstable and includes use of --local-service by default, so this should get automatically synced to Ubuntu in time for the next release. ** Bug watch added: Debian Bug tracker #732610 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732610 ** Also affects: dnsmasq (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732610 Importance: Unknown Status: Unknown ** Summary changed: - Prevent open recursive DNS server with dnsmasq + dnsmasq provides recursive answers to the Internet by default ** Changed in: dnsmasq (Ubuntu) Status: New => Triaged ** Changed in: dnsmasq (Ubuntu) Importance: Undecided => High -- 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 1306664] Re: package libkadm5srv-mit8 (not installed) failed to install/upgrade: libkadm5srv-mit8:all 1.12+dfsg-2ubuntu4 (Multi-Arch: no) kan inte installeras sida vid sida om libkadm5srv-mit8 om
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1306664 Title: package libkadm5srv-mit8 (not installed) failed to install/upgrade: libkadm5srv-mit8:all 1.12+dfsg-2ubuntu4 (Multi-Arch: no) kan inte installeras sida vid sida om libkadm5srv-mit8 om har flera installerade instanser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1306664/+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 1306664] [NEW] package libkadm5srv-mit8 (not installed) failed to install/upgrade: libkadm5srv-mit8:all 1.12+dfsg-2ubuntu4 (Multi-Arch: no) kan inte installeras sida vid sida om libkadm5srv-mit8
Public bug reported: this package fails after upgrading to ubuntu 14.04. After the upgrade I had issue same issue as know , was fixed by uninstalling and then reinstalling , but now I get the same error when starting up "cold" computer ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libkadm5srv-mit8 (not installed) ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 AptOrdering: libkadm5srv-mit8: Install libkdb5-7: Install libkadm5srv-mit8: Configure libkdb5-7: Configure Architecture: amd64 Date: Fri Apr 11 11:07:27 2014 DpkgTerminalLog: dpkg: error processing archive /var/cache/apt/archives/libkadm5srv-mit8_1.12+dfsg-2ubuntu4_all.deb (--unpack): libkadm5srv-mit8:all 1.12+dfsg-2ubuntu4 (Multi-Arch: no) kan inte installeras sida vid sida om libkadm5srv-mit8 om har flera installerade instanser DuplicateSignature: package:libkadm5srv-mit8:(not installed):libkadm5srv-mit8:all 1.12+dfsg-2ubuntu4 (Multi-Arch: no) kan inte installeras sida vid sida om libkadm5srv-mit8 om har flera installerade instanser ErrorMessage: libkadm5srv-mit8:all 1.12+dfsg-2ubuntu4 (Multi-Arch: no) kan inte installeras sida vid sida om libkadm5srv-mit8 om har flera installerade instanser InstallationDate: Installed on 2010-08-09 (1341 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) SourcePackage: krb5 Title: package libkadm5srv-mit8 (not installed) failed to install/upgrade: libkadm5srv-mit8:all 1.12+dfsg-2ubuntu4 (Multi-Arch: no) kan inte installeras sida vid sida om libkadm5srv-mit8 om har flera installerade instanser UpgradeStatus: Upgraded to trusty on 2014-04-11 (0 days ago) ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1306664 Title: package libkadm5srv-mit8 (not installed) failed to install/upgrade: libkadm5srv-mit8:all 1.12+dfsg-2ubuntu4 (Multi-Arch: no) kan inte installeras sida vid sida om libkadm5srv-mit8 om har flera installerade instanser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1306664/+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
Confirmed fix in a new install using Trusty iso 2014-apr-11 ... MAAS front end is functional on first boot. -- 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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
** Changed in: lxc (Ubuntu) Status: New => Confirmed ** Changed in: lxc (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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 1306335] Re: maas-dhcp needs to quote interface name in /etc/maas/dhcpd.conf
** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Changed in: maas (Ubuntu) Status: New => Confirmed ** Changed in: maas (Ubuntu) Importance: Undecided => High -- 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/1306335 Title: maas-dhcp needs to quote interface name in /etc/maas/dhcpd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1306335/+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] [NEW] Prevent open recursive DNS server with dnsmasq
Public bug reported: The default configuration of dnsmasq creates an open recursive name server, meaning that from anywhere on the Internet a request can be sent to dnsmasq. This is problematic as UDP packets can be spoofed and DNS has a high amplification factor, which makes it a ready tool for DDoS attacks. The latest release of dnsmasq (v2.69) includes the option "--local- service", which restricts the recursive answers to the local subnet. Please make this option default for regular installs. ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New -- 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: Prevent open recursive DNS server with dnsmasq 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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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 1305418] Re: [SRU] walinuxagent breaks sshd configuration
** Changed in: walinuxagent (Ubuntu Saucy) Importance: Undecided => Critical ** Changed in: walinuxagent (Ubuntu Saucy) Status: New => In Progress ** Changed in: walinuxagent (Ubuntu Saucy) Assignee: (unassigned) => Robert C Jennings (rcj) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1305418 Title: [SRU] walinuxagent breaks sshd configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1305418/+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 1306241] Re: swift-account and swift-container depend on down-level python-swift
The manpage moves in 1.13.1~rc1-0ubuntu1 did not have appropriate Breaks/Replaces, resulting in overrwrite errors. ** Also affects: swift-storage (Ubuntu) Importance: Undecided Status: New ** No longer affects: swift-storage (Ubuntu) ** Also affects: swift (Ubuntu) Importance: Undecided Status: New ** Also affects: swift (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: swift (Ubuntu Trusty) Status: New => Triaged ** Changed in: swift (Ubuntu Trusty) Importance: Undecided => Critical ** Changed in: swift (Ubuntu Trusty) Assignee: (unassigned) => James Page (james-page) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to swift in Ubuntu. https://bugs.launchpad.net/bugs/1306241 Title: swift-account and swift-container depend on down-level python-swift To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1306241/+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 463065] Re: package depends on python-routes
This bug was fixed in the package cherrypy3 - 3.2.2-4ubuntu5 --- cherrypy3 (3.2.2-4ubuntu5) trusty; urgency=medium * Use python3:* variables in debian/control. -- Matthias KloseTue, 25 Mar 2014 17:01:18 +0100 ** Changed in: cherrypy3 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cherrypy3 in Ubuntu. https://bugs.launchpad.net/bugs/463065 Title: package depends on python-routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cherrypy3/+bug/463065/+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 Friday 11 Apr 2014 12:26:59 Adam Conrad wrote: > Can you test the crap out of the new codepaths here, especially in any > way that they interact with existing functionality (ie: the web UI, > etc)? If you guys are satisfied that this won't make anything any more > broken than it already is, I might be inclined to be a Very Nice Person, > and let you slip it in. I'm still on the fence there, but any > reassurances you can give would go a long way. Is there a test > methodology you use to validate maas, can we see results, etc? MAAS has a CI suite in the lab which runs a few times day, but it does not have the hardware required to test this particular change. It does, however, gives us regression mitigation confidence. Andres, I think it would help folk if there were some evidence of running this code on the hardware in question that requires the driver. -- 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
Adam, This was tested yesterday both manually by us and was also tested at a customer site with successful results. We will give him another round of testing. Sorry if I've been causing too much of a headache for you! I hope you understand that me pushing this is due comes from high up. Thanks. On Apr 11, 2014 8:35 AM, "Adam Conrad" wrote: > Can you test the crap out of the new codepaths here, especially in any > way that they interact with existing functionality (ie: the web UI, > etc)? If you guys are satisfied that this won't make anything any more > broken than it already is, I might be inclined to be a Very Nice Person, > and let you slip it in. I'm still on the fence there, but any > reassurances you can give would go a long way. Is there a test > methodology you use to validate maas, can we see results, etc? > > -- > 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 > -- 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 1306575] Re: package nova-common 1:2014.1~rc2-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1306575 Title: package nova-common 1:2014.1~rc2-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1306575/+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 1306575] [NEW] package nova-common 1:2014.1~rc2-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Upgrade test from Precise AMD64 to Trusty with nearly all of main installed. Note that nova.conf has not been manually modified before upgrade. >From apt-term.log: Setting up nova-common (1:2014.1~rc2-0ubuntu1) ... Installing new version of config file /etc/logrotate.d/nova-manage ... Installing new version of config file /etc/nova/api-paste.ini ... Installing new version of config file /etc/nova/policy.json ... Installing new version of config file /etc/nova/nova.conf ... Installing new version of config file /etc/sudoers.d/nova_sudoers ... Command failed, please check log for more info 2014-04-11 12:03:57.516 57962 CRITICAL nova [-] KeyError: 2014-04-11 12:03:57.516 57962 TRACE nova Traceback (most recent call last): 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/bin/nova-manage", line 10, in 2014-04-11 12:03:57.516 57962 TRACE nova sys.exit(main()) 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/cmd/manage.py", line 1374, in main 2014-04-11 12:03:57.516 57962 TRACE nova ret = fn(*fn_args, **fn_kwargs) 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/cmd/manage.py", line 883, in sync 2014-04-11 12:03:57.516 57962 TRACE nova return migration.db_sync(version) 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/db/migration.py", line 29, in db_sync 2014-04-11 12:03:57.516 57962 TRACE nova return IMPL.db_sync(version=version) 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/migration.py", line 44, in db_sync 2014-04-11 12:03:57.516 57962 TRACE nova return versioning_api.upgrade(get_engine(), repository, version) 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/migrate/versioning/api.py", line 186, in upgrade 2014-04-11 12:03:57.516 57962 TRACE nova return _migrate(url, repository, version, upgrade=True, err=err, **opts) 2014-04-11 12:03:57.516 57962 TRACE nova File "", line 2, in _migrate 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py", line 159, in with_engine 2014-04-11 12:03:57.516 57962 TRACE nova return f(*a, **kw) 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/migrate/versioning/api.py", line 345, in _migrate 2014-04-11 12:03:57.516 57962 TRACE nova changeset = schema.changeset(version) 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 80, in changeset 2014-04-11 12:03:57.516 57962 TRACE nova changeset = self.repository.changeset(database, start_ver, version) 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/migrate/versioning/repository.py", line 225, in changeset 2014-04-11 12:03:57.516 57962 TRACE nova changes = [self.version(v).script(database, op) for v in versions] 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/migrate/versioning/repository.py", line 189, in version 2014-04-11 12:03:57.516 57962 TRACE nova return self.versions.version(*p, **k) 2014-04-11 12:03:57.516 57962 TRACE nova File "/usr/lib/python2.7/dist-packages/migrate/versioning/version.py", line 155, in version 2014-04-11 12:03:57.516 57962 TRACE nova return self.versions[VerNum(vernum)] 2014-04-11 12:03:57.516 57962 TRACE nova KeyError: 2014-04-11 12:03:57.516 57962 TRACE nova dpkg: error processing package nova-common (--configure): subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nova-common 1:2014.1~rc2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 11 12:03:58 2014 DuplicateSignature: package:nova-common:1:2014.1~rc2-0ubuntu1:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all SourcePackage: nova Title: package nova-common 1:2014.1~rc2-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-04-11 (0 days ago) mtime.conffile..etc.nova.nova.conf: 2014-04-11T12:03:56.317961 ** Affects: nova (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-package rls-t-incoming trusty uec-images ** Description changed: - Upgrade test from Precise AMD64 to Trusty + Upgrade test from Precise AMD64 to Trusty with nearly all of main + installed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nova-common 1:2014.1~rc2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.
[Bug 1305839] Re: FFe: Support for Third Party Driver Installation
Can you test the crap out of the new codepaths here, especially in any way that they interact with existing functionality (ie: the web UI, etc)? If you guys are satisfied that this won't make anything any more broken than it already is, I might be inclined to be a Very Nice Person, and let you slip it in. I'm still on the fence there, but any reassurances you can give would go a long way. Is there a test methodology you use to validate maas, can we see results, etc? -- 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
Hi Adam, Sorry for the misunderstanding but to me the answer to my question ("Yeah, I think that would satisfy me.") as to whether this was enough to get the FFe approved sounds like an unofficial ACK. So the question is now... Will this be ACK'd or NACK'd? On Apr 11, 2014 8:16 AM, "Adam Conrad" wrote: > I wouldn't say I "unofficially approved the FFe", that's twisting my > words and the content of our conversations. I gave you the reasons why > I would flat out reject the upload (FFe or not), and even petition to > have it removed from the archive if the "install non-free software by > default" feature slipped in. > > You addressed those concerns, which is great, but none of that relates > to the bit where you're trying to land new features a week before > release, and a month and a half after feature freeze. > > -- > 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 > -- 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 wouldn't say I "unofficially approved the FFe", that's twisting my words and the content of our conversations. I gave you the reasons why I would flat out reject the upload (FFe or not), and even petition to have it removed from the archive if the "install non-free software by default" feature slipped in. You addressed those concerns, which is great, but none of that relates to the bit where you're trying to land new features a week before release, and a month and a half after feature freeze. -- 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
There's no regression potential per se because this doesn't affect the current Maas operation as this will only be in effect if the user enables the capability. Other than that this has been QA'd and testes on the field. On Apr 11, 2014 4:50 AM, "Dave Walker" wrote: > I really struggle to support this change. It is a clearly impactful > change. FFe raised on the day of Final Freeze. Feels rushed. There is > no commentary on the regression potential, or the testing done. > > Not to mention that RC1 was happily released with a broken MAAS > installer, that took 2 weeks to fix. This lowers general confidence in > the attention to detail, and this upload could be similar. > > This feels like a hardware enablement change that is better suited as a > post-release SRU once it is well tested and the general churn has > calmed. I do not see a valid reason why this needs to be on the release > ISO.. it isn't an install time requirement? > > I'm stopping short of outright NACK'ing this, but am rejecting the > upload from the queue to avoid it being accepted by mistake. > > -- > 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 > -- 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 1187826] Re: Cannot upload files with maas-cli
** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- 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/1187826 Title: Cannot upload files with maas-cli To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1187826/+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 1301569] Re: Missing import in maas-ipmi-autodetect-tool
Andres, is that Fix Released in Saucy too? -- 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/1301569 Title: Missing import in maas-ipmi-autodetect-tool To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1301569/+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 1293676] Re: internal server error when marking nodes as using fast-path installer
** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- 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/1293676 Title: internal server error when marking nodes as using fast-path installer To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1293676/+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
Hi Dave, It is a certification requirement hence needs to be on the ISO. We had discussed this with Adam and he had been reviewing the code and gave us pointer to address. He unofficially approved the FFe before final freeze. On Apr 11, 2014 4:50 AM, "Dave Walker" wrote: > I really struggle to support this change. It is a clearly impactful > change. FFe raised on the day of Final Freeze. Feels rushed. There is > no commentary on the regression potential, or the testing done. > > Not to mention that RC1 was happily released with a broken MAAS > installer, that took 2 weeks to fix. This lowers general confidence in > the attention to detail, and this upload could be similar. > > This feels like a hardware enablement change that is better suited as a > post-release SRU once it is well tested and the general churn has > calmed. I do not see a valid reason why this needs to be on the release > ISO.. it isn't an install time requirement? > > I'm stopping short of outright NACK'ing this, but am rejecting the > upload from the queue to avoid it being accepted by mistake. > > -- > 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 > -- 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 1303876] Re: VPN agent dependencies are foobar
This bug was fixed in the package neutron - 1:2014.1~rc2-0ubuntu3 --- neutron (1:2014.1~rc2-0ubuntu3) trusty; urgency=medium * Fix the Breaks/Replaces from the previous version, as they were accidentally added to the wrong package (and with the wrong versioning). neutron (1:2014.1~rc2-0ubuntu2) trusty; urgency=medium * Ensure that VPN and L3 agents are not installed together (LP: #1303876): - d/control: Add Conflicts on neutron-l3-agent to neutron-vpn-agent, drop dependency from neutron-vpn-agent -> neutron-l3-agent. - d/neutron-{common,vpn-agent,l3-agent}.install: Move configuration and rootwrap filters to -common package for use by both agent types. - d/control: Add appropriate Breaks/Replaces for config file moves. - d/neutron-vpn-agent.upstart: Include fwaas_driver.ini on config file path inline with l3-agent configuration. - d/control: Align Depends of neutron-vpn-agent with neutron-l3-agent. -- Steve LangasekThu, 10 Apr 2014 23:36:09 + ** Changed in: neutron (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 neutron in Ubuntu. https://bugs.launchpad.net/bugs/1303876 Title: VPN agent dependencies are foobar To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1303876/+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 1298290] Re: [SRU] 0.67.7 release tracker
Same tests repeated for the Ubuntu Cloud Archive -proposed pocket; no problems found. Targetting 17th for release to -updates (probably alongside 2013.2.3). ** Changed in: cloud-archive Status: New => Invalid ** Changed in: cloud-archive/havana Status: New => Fix Committed ** Changed in: cloud-archive/havana Importance: Undecided => High ** Changed in: cloud-archive/havana Assignee: (unassigned) => James Page (james-page) -- 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/1298290 Title: [SRU] 0.67.7 release tracker To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1298290/+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
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided => Critical ** Changed in: juju-core (Ubuntu Trusty) 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/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 1302575] Please test proposed package
Hello Chuck, or anyone else affected, Accepted horizon into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/horizon/1:2013.2.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: ceilometer (Ubuntu Saucy) Status: New => Fix Committed -- 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/1302575 Title: Meta bug for tracking Openstack 2013.2.3 Stable Update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1302575/+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 1302575] Please test proposed package
Hello Chuck, or anyone else affected, Accepted cinder into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cinder/1:2013.2.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: heat (Ubuntu Saucy) Status: New => Fix Committed -- 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/1302575 Title: Meta bug for tracking Openstack 2013.2.3 Stable Update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1302575/+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 1302575] Please test proposed package
Hello Chuck, or anyone else affected, Accepted heat into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/heat/2013.2.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1302575 Title: Meta bug for tracking Openstack 2013.2.3 Stable Update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1302575/+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
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: juju-core (Ubuntu Trusty) 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/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 1302575] Re: Meta bug for tracking Openstack 2013.2.3 Stable Update
Hello Chuck, or anyone else affected, Accepted nova into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nova/1:2013.2.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nova (Ubuntu Saucy) Status: New => Fix Committed ** Tags added: verification-needed ** Changed in: horizon (Ubuntu Saucy) Status: New => Fix Committed -- 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/1302575 Title: Meta bug for tracking Openstack 2013.2.3 Stable Update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1302575/+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
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Trusty) Status: New => Triaged ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided => 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 1302575] Please test proposed package
Hello Chuck, or anyone else affected, Accepted ceilometer into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ceilometer/2013.2.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cinder (Ubuntu Saucy) Status: New => Fix Committed -- 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/1302575 Title: Meta bug for tracking Openstack 2013.2.3 Stable Update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1302575/+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 1284643] Re: [SRU] Meta bug for tracking Openstack 2013.2.2
Hello Chuck, or anyone else affected, Accepted neutron into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/neutron/1:2013.2.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done ** Tags added: verification-needed -- 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/1284643 Title: [SRU] Meta bug for tracking Openstack 2013.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1284643/+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
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Trusty) Status: New => Triaged ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided => Critical -- 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 1303735] Re: public-address change to internal bridge post juju-upgrade
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided => Critical ** Changed in: juju-core (Ubuntu Trusty) 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/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 1304135] Re: panic: runtime error: index out of range
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Trusty) Status: New => Triaged ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided => Critical -- 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/1304135 Title: panic: runtime error: index out of range To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1304135/+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
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided => Critical ** Changed in: juju-core (Ubuntu Trusty) 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/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 1305839] Re: FFe: Support for Third Party Driver Installation
I really struggle to support this change. It is a clearly impactful change. FFe raised on the day of Final Freeze. Feels rushed. There is no commentary on the regression potential, or the testing done. Not to mention that RC1 was happily released with a broken MAAS installer, that took 2 weeks to fix. This lowers general confidence in the attention to detail, and this upload could be similar. This feels like a hardware enablement change that is better suited as a post-release SRU once it is well tested and the general churn has calmed. I do not see a valid reason why this needs to be on the release ISO.. it isn't an install time requirement? I'm stopping short of outright NACK'ing this, but am rejecting the upload from the queue to avoid it being accepted by mistake. -- 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 1243352] Re: Installing Neutron LinuxBridge plugin configures OVS plugin instead
** Changed in: neutron (Ubuntu) Assignee: James Page (james-page) => (unassigned) -- 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/1243352 Title: Installing Neutron LinuxBridge plugin configures OVS plugin instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1243352/+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 1288841] Re: l3-agent (dis)associate floatingip only after restart
*** This bug is a duplicate of bug 1303876 *** https://bugs.launchpad.net/bugs/1303876 Having dug into the workings of the vpn-agent for icehouse, this bug report now makes alot of sense. The vpn-agent is a superset of the function of the l3-agent; so in effect, it provides both l3 services and vpn management. As a result, installing both the l3-agent and vpn-agent on the same box makes no sense - they are both trying to manage the same resources. That said, the vpn-agent relies on l3_agent.ini and potentially fwaas_driver.ini - and the associated rootwrap rules - which are provided by the l3-agent package. I've fixed this up for icehouse under bug 1303876; I'll raise a task to resolve this for havana as well. ** This bug has been marked a duplicate of bug 1303876 VPN agent dependencies are foobar -- 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/1288841 Title: l3-agent (dis)associate floatingip only after restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1288841/+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 1303876] Re: VPN agent dependencies are foobar
** Also affects: neutron (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/havana Importance: Undecided Status: New ** Changed in: neutron (Ubuntu Saucy) Status: New => Triaged ** Changed in: neutron (Ubuntu Saucy) Importance: Undecided => High ** Changed in: cloud-archive/havana Status: New => Triaged ** Changed in: cloud-archive/havana Importance: Undecided => High -- 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/1303876 Title: VPN agent dependencies are foobar To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1303876/+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