[Bug 1440265] Re: CloudStack sshkey reset
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed -- 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/1440265 Title: CloudStack sshkey reset To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1440265/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1241498] Re: package libapache2-mod-php5 5.5.3+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This seems to be a dependency issue if you install libapache2-mod-php5 after apache2. I fixed this using the following after installing apache2 sudo service apache2 stop sudo service mysql stop sudo apt-get purge libapache2-mod-php5 sudo apt-get autoremove sudo apt-get clean sudo apt-get install libapache2-mod-php5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1241498 Title: package libapache2-mod-php5 5.5.3+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1241498/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1446906] Re: lxc container with postfix, permission denied on mailq
*** This bug is a duplicate of bug 1390223 *** https://bugs.launchpad.net/bugs/1390223 nearly correct - the rule needs to be /public/showq r, (note the leading "/") -- 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/1446906 Title: lxc container with postfix, permission denied on mailq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446906/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1446906] Re: lxc container with postfix, permission denied on mailq
*** This bug is a duplicate of bug 1390223 ***
https://bugs.launchpad.net/bugs/1390223
The issue is that the path is disconnected from the namespace. Currently
the only way to deal with this is by using the attach_disconnect flag in
the profile, and then place rules for the attached files into the
profile
eg.
profile lxc-container-default flags=(attach_disconnected) {
public/showq r,
...
}
--
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/1446906
Title:
lxc container with postfix, permission denied on mailq
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446906/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1517219] [NEW] Attempt to create an SL5.5 virtual machine using virt-manager in Kubuntu 15.10. fails.
Public bug reported: Real result: Install fails shortly after anaconda probes for vga adapter Expected result: Install succeeds and OS is installed on vm. Iso: SL.55.051810.DVD.x86_64.disc1.iso Error message in anaconda within console of VM: running install... install exited abnormally [0/0] --received signal 5 >From vm's log file: qemu: terminating on signal 15 from pid 815 Source package: qemu version: 2.3.0 (Debian 1:2.3+dfsg-5ubuntu9) (from log below) apt-cache policy qemu qemu: Installed: 1:2.3+dfsg-5ubuntu9 Candidate: 1:2.3+dfsg-5ubuntu9 Version table: *** 1:2.3+dfsg-5ubuntu9 0 Ubuntu release: Distributor ID: Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename: wily Failure happens whether app is run as root or as normal user with secondary group kvm. This could be a defect within anaconda installer on iso. However, kvm supposedly works with RHEL5.5 and later versions. Log file: 2015-11-13 16:06:00.584+: starting up libvirt version: 1.2.16, package: 1.2.16-2ubun tu11, qemu version: 2.3.0 (Debian 1:2.3+dfsg-5ubuntu9) LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DR V=spice /usr/bin/kvm-spice -name SL5-5-hack -S -machine pc-i440fx-vivid,accel=kvm,usb=of f -cpu Opteron_G5 -m 2048 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 3 0da0139-4623-4a49-8517-a187b0ebb030 -no-user-config -nodefaults -chardev socket,id=charm onitor,path=/var/lib/libvirt/qemu/SL5-5-hack.monitor,server,nowait -mon chardev=charmoni tor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy =discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4 =1 -boot order=c,menu=on,strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/var/lib/libvirt/images/SL5-5-hack.qcow2,if=none,id=drive-scsi0-0-0-0,format=qcow2 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0 -drive file=/data/SL.55.051810.DVD.x86_64.disc1.iso,if=none,id=drive-ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5c:9c:9d,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,i d=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1 -chardev spicevmc,id=charredir2,name=usbredir -device usb-redir,chardev=charredir2,id=redir2 -chardev spicevmc,id=charredir3,name=usbredir -device usb-redir,chardev=charredir3,id=redir3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on char device redirected to /dev/pts/1 (label charserial0) main_channel_link: add main channel client main_channel_handle_parsed: net test: latency 0.912000 ms, bitrate 12412121212 bps (11837.121212 Mbps) inputs_connect: inputs channel client create red_dispatcher_set_cursor_peer: qemu: terminating on signal 15 from pid 815 red_channel_client_disconnect_dummy: rcc=0x55d300793ec0 (channel=0x55d2ff5fe100 type=5 id=0) snd_channel_put: SndChannel=0x55d2ff2d41f0 freed red_channel_client_disconnect_dummy: rcc=0x55d2ffe46820 (channel=0x55d2ff6001a0 type=6 i d=0) snd_channel_put: SndChannel=0x55d300143480 freed 2015-11-13 16:10:19.272+: shutting down ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- 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/1517219 Title: Attempt to create an SL5.5 virtual machine using virt-manager in Kubuntu 15.10. fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1517219/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-se
[Bug 1501651] Re: ARM chroot issues: fatal error: rt_sigaction failure
Oops I got confused about version numbers. Trying again. ** Patch added: "golang_1.5.1-0ubuntu3_1.5.1-0ubuntu4.diff" https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1501651/+attachment/4520885/+files/golang_1.5.1-0ubuntu3_1.5.1-0ubuntu4.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1501651 Title: ARM chroot issues: fatal error: rt_sigaction failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1501651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID
** Tags added: 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/1506187 Title: [SRU] Azure: cloud-init should use VM unique ID To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1506187/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID
During review of the proposed patch, the concern was raised that cloud- init will migrate to using the new instance ID and thus run first-boot provisioning. In order to mitigate this, cloud-init needs to migrate existing instances to the new instance ID during installation of the upgraded package. Attached patch is proposed for debian/cloud-init.postinst ** Description changed: - The Azure datasource currently uses the InstanceID from the - SharedConfig.xml file. On our new CRP stack, this ID is not guaranteed - to be stable and could change if the VM is deallocated. If the - InstanceID changes then cloud-init will attempt to reprovision the VM, - which could result in temporary loss of access to the VM. + SRU JUSTIFICATION + + [IMPACT] On Azure, the InstanceID is currently detected via a fabric + provided XML file. With the new CRP stack, this ID is not guaranteed to + be stable. As a result instances may go re-provision upon reboot. + + [FIX] Use DMI data to detect the instance ID and migrate existing + instances to the new ID. + + [REGRESSION POTENTIAL] The fix is both in the cloud-init code and in the + packaging. If the instance ID is not properly migrated, then a reboot + may trigger re-provisioning. + + [TEST CASES] + 1. Boot instance on Azure. + 2. Apply cloud-init from -proposed. A migration message should apply. + 3. Get the new instance ID: +$ sudo cat /sys/class/dmi/id/product_uuid + 4. Confirm that /var/lib/cloud/instance is a symlink to /var/lib/cloud/instances/ + 5. Re-install cloud-init and confirm that migration message is NOT displayed. + + [TEST CASE 2] + 1. Build new cloud-image from -proposed + 2. Boot up instance + 3. Confirm that /sys/class/dmi/id/product_uuid is used to get instance ID (see /var/log/cloud-init.log) + + + [ORIGINAL REPORT] + The Azure datasource currently uses the InstanceID from the SharedConfig.xml file. On our new CRP stack, this ID is not guaranteed to be stable and could change if the VM is deallocated. If the InstanceID changes then cloud-init will attempt to reprovision the VM, which could result in temporary loss of access to the VM. Instead cloud-init should switch to use the VM Unique ID, which is guaranteed to be stable everywhere for the lifetime of the VM. The VM unique ID is explained here: https://azure.microsoft.com/en-us/blog /accessing-and-using-azure-vm-unique-id/ In short, the unique ID is available via DMI, and can be accessed with the command 'dmidecode | grep UUID' or even easier via sysfs in the file "/sys/devices/virtual/dmi/id/product_uuid". Steve ** Patch added: "cloud-init postinst patch for applying new instance ID to existing instances" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+attachment/4520856/+files/lp-1506187-postinst.diff -- 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/1506187 Title: [SRU] Azure: cloud-init should use VM unique ID To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1506187/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1517182] [NEW] package libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: i dont know. it appeared on startup ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.14 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 Date: Mon Nov 16 23:00:45 2015 DuplicateSignature: package:libapache2-mod-php5:5.5.9+dfsg-1ubuntu4.14:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-02 (46 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: php5 Title: package libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apache2.mods.available.php5.conf: [deleted] modified.conffile..etc.apache2.mods.available.php5.load: [deleted] ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1517182 Title: package libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1517182/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516037] Re: lxc-start fails with 1.1.5-0ubuntu1
AppArmor 2.7 is _very_ old - especially given the fact that the tools were rewritten in python for 2.9. I just checked the perl code (which was used in 2.8.x and older) - it _sets_ the flags (instead of adding or removing them), so it's not surprising that attach_disconnected gets lost. (This is one of the fixes that went into the 2.9 during the rewrite to python.) If someone is interested to fix this - the code is in Immunix/AppArmor.pm, sub complain() and sub enforce(), which both call setprofileflags(). -- 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/1516037 Title: lxc-start fails with 1.1.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516037/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1302963] Re: Calendar() class can not be initialized
parsedatetime 1.4-1~ubuntu14.04.1 has now been backported to Trusty (LP: #1510329) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to parsedatetime in Ubuntu. https://bugs.launchpad.net/bugs/1302963 Title: Calendar() class can not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parsedatetime/+bug/1302963/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516971] Re: devel-proposed mako 350 - android lxc container fails to start
This affects LXC 1.1.5 and LXC 1.0.8, so both current stable releases. A fix is being worked on upstream. -- 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/1516971 Title: devel-proposed mako 350 - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516971/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516971] Re: devel-proposed mako 350 - android lxc container fails to start
** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1516971 Title: devel-proposed mako 350 - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516971/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516971] Re: devel-proposed mako 350 - android lxc container fails to start
** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Xenial) Importance: Undecided Assignee: Stéphane Graber (stgraber) Status: New ** Also affects: lxc (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Wily) Assignee: (unassigned) => Stéphane Graber (stgraber) ** Changed in: lxc (Ubuntu Vivid) Assignee: (unassigned) => Stéphane Graber (stgraber) ** Changed in: lxc (Ubuntu Trusty) Assignee: (unassigned) => Stéphane Graber (stgraber) ** Changed in: lxc (Ubuntu Trusty) Status: New => Triaged ** Changed in: lxc (Ubuntu Vivid) Status: New => Triaged ** Changed in: lxc (Ubuntu Wily) Status: New => Triaged ** Changed in: lxc (Ubuntu Xenial) Status: New => Triaged ** Changed in: lxc (Ubuntu Trusty) Importance: Undecided => High ** Changed in: lxc (Ubuntu Vivid) Importance: Undecided => High ** Changed in: lxc (Ubuntu Wily) Importance: Undecided => High ** Changed in: lxc (Ubuntu Xenial) 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/1516971 Title: devel-proposed mako 350 - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516971/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516971] Re: devel-proposed mako 350 - android lxc container fails to start
** This bug is no longer a duplicate of bug 1516037 lxc-start fails with 1.1.5-0ubuntu1 ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Stéphane Graber (stgraber) -- 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/1516971 Title: devel-proposed mako 350 - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516971/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1506244] Re: [SRU] support SSH key value over fingerprint for Azure
Backported changes and uploaded; pending acceptance into -proposed. -- 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/1506244 Title: [SRU] support SSH key value over fingerprint for Azure To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1506244/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup
Another workaround for folks still waiting for the real patch to be released...bind to LDAP through SSSD instead of using ldap-client. Then purge autofs-ldap off your system and install libpam-sss, then autofs will use sssd to get the ldap netgroups and you won't run into this segfault. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1503034 Title: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1503330] Re: New upstream bugfix release 1.1.4 (LXC MRE)
Oops, we used the wrong bug number for 1.1.5 it looks like. Anyway, 1.1.5 verification failed due to a regression in kernel support, so keeping this one as verification-failed to prevent releasing. ** Tags removed: verification-needed -- 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/1503330 Title: New upstream bugfix release 1.1.4 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1503330/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1514558] Re: New upstream bugfix release 1.1.5 (LXC MRE)
Ran into another small regression with this one, we'll very likely be pushing out a 1.1.6 with a few of the fixes bundled. -- 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/1514558 Title: New upstream bugfix release 1.1.5 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514558/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1514623] Re: New upstream bugfix release 1.0.8 (LXC MRE)
We had a report from Jean-Baptiste that a recent change in this stable release makes it fail on older kernels (pre-3.8). Not a problem with the generic kernel but a problem for folks using the Android kernels, so we'll need to push an update (probably a new upstream bugfix release). ** Tags removed: verification-needed ** Tags added: verification-failed -- 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/1514623 Title: New upstream bugfix release 1.0.8 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514623/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516037] Re: lxc-start fails with 1.1.5-0ubuntu1
Oh, the phone problem is different I think, there the problem is that your kernel is pretty old and doesn't have the right /proc/self/ns files available. Looks like that's an actual bug with the new implementation. I'll report it upstream. Jean-Baptiste, can you un-duplicate the phone bug and open a lxc task for it? It's a different issue from what was reported in this bug report. -- 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/1516037 Title: lxc-start fails with 1.1.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516037/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516037] Re: lxc-start fails with 1.1.5-0ubuntu1
Note that Jean-Baptiste's problem will only be seen on kernels higher than 3.2 and lower than 3.8. So it's not affecting any official distro kernel but it does affect those outdated android kernels. -- 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/1516037 Title: lxc-start fails with 1.1.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516037/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501651] Re: ARM chroot issues: fatal error: rt_sigaction failure
Looks like this got uploaded already. Unsubscribing sponsors. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1501651 Title: ARM chroot issues: fatal error: rt_sigaction failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1501651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1511899] Re: init-system-helpers and upstart need to conflict/replace
** Changed in: init-system-helpers (Ubuntu) Status: Triaged => In Progress ** Changed in: init-system-helpers (Ubuntu) Assignee: (unassigned) => Robie Basak (racb) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1511899 Title: init-system-helpers and upstart need to conflict/replace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1511899/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1517107] [NEW] $PATH is getting clobbered when starting a container with Upstart
Public bug reported: I have a script using the Python3 LXC API that starts up a container. If I use an Upstart job to call the script, the $PATH env var is getting clobbered and the container fails to start. ** 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/1517107 Title: $PATH is getting clobbered when starting a container with Upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1517107/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1511899] Re: init-system-helpers and upstart need to conflict/replace
FTR, this was moved to init-system-helpers in bug 1442228. Can't say I'm happy about this, but that's what it is right now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1511899 Title: init-system-helpers and upstart need to conflict/replace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1511899/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1511899] Re: init-system-helpers and upstart need to conflict/replace
Confirmed when test dist-upgrading from Trusty to Xenial. This blocks me from upgrade testing other packages in Xenial before upload. ** Changed in: init-system-helpers (Ubuntu) Status: New => Triaged ** Changed in: init-system-helpers (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1511899 Title: init-system-helpers and upstart need to conflict/replace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1511899/+subscriptions -- Ubuntu-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 1514960] Re: lxc-test-checkpoint-restore fails with no explanation why
Hi, Not sure this is still an issue, Stephane informed me that those tests are not meant to be run stand alone and could fail in spectacular ways when run outside of autopkgtest. if this is not the case, let me know and when I'm home next week, I'll dig into this further... otherwise, you can mark this as 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/1514960 Title: lxc-test-checkpoint-restore fails with no explanation why To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514960/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1459724] Re: live-migration causes lack of access to instance
** Changed in: nova Assignee: (unassigned) => lvmxh (shaohef) -- 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/1459724 Title: live-migration causes lack of access to instance To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1459724/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516037] Re: lxc-start fails with 1.1.5-0ubuntu1
apparmor 2.7.102-0ubuntu3.10 running Ubuntu 12.04 LTS. -- 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/1516037 Title: lxc-start fails with 1.1.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516037/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1310340] Re: live migration fails when use long hostname of a nova compute target host
** Changed in: nova Assignee: (unassigned) => lvmxh (shaohef) -- 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/1310340 Title: live migration fails when use long hostname of a nova compute target host To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1310340/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498370] Re: [SRU] DHCP agent: interface unplug leads to exception
** Patch removed: "lp1498370.patch" https://bugs.launchpad.net/neutron/+bug/1498370/+attachment/4516816/+files/lp1498370.patch ** Patch added: "lp1498370.patch" https://bugs.launchpad.net/neutron/+bug/1498370/+attachment/4520585/+files/lp1498370.patch ** Changed in: neutron (Ubuntu Trusty) Status: Incomplete => In Progress ** Changed in: neutron (Ubuntu Vivid) Status: Won't Fix => In Progress ** Changed in: neutron (Ubuntu Trusty) Status: In Progress => New ** Changed in: neutron (Ubuntu Trusty) Assignee: Edward Hope-Morley (hopem) => (unassigned) ** Changed in: neutron (Ubuntu Vivid) Assignee: (unassigned) => Edward Hope-Morley (hopem) -- 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/1498370 Title: [SRU] DHCP agent: interface unplug leads to exception To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1498370/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498370] Re: [SRU] DHCP agent: interface unplug leads to exception
@pitti Apologies, this SRU was incorrectly targeted. It is intended as an SRU for Openstack Kilo and therefore should be targeted at Ubuntu Vivid (then implicitly Trusty Kilo Ubuntu Cloud Archive). The current Kilo version in Vivid is 1:2015.1.2-0ubuntu1 so this SRU should have version 1:2015.1.2-0ubuntu2. I will resubmit an updated debdiff. -- 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/1498370 Title: [SRU] DHCP agent: interface unplug leads to exception To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1498370/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498370] Re: [SRU] DHCP agent: interface unplug leads to exception
** Changed in: neutron (Ubuntu Trusty) 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/1498370 Title: [SRU] DHCP agent: interface unplug leads to exception To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1498370/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501651] Re: ARM chroot issues: fatal error: rt_sigaction failure
** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1501651 Title: ARM chroot issues: fatal error: rt_sigaction failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1501651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1454273] Re: irqbalance should not run in container - add systemd unit
irqbalancing should be done on the container host, not from within the container - I suspect that we just end up with lots of irqbalance processing doing nothing in containers esp when they are running unpriviledged. ** Changed in: irqbalance (Ubuntu) Status: Confirmed => Triaged ** Changed in: irqbalance (Ubuntu) Importance: Low => High ** Changed in: irqbalance (Ubuntu) Milestone: None => ubuntu-15.11 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1454273 Title: irqbalance should not run in container - add systemd unit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1454273/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516037] Re: lxc-start fails with 1.1.5-0ubuntu1
I confirm that the phone boots successfully after downgrading liblxc1, lxc and python3-lxc to version 1.1.4-0ubuntu3 ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1516037 Title: lxc-start fails with 1.1.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516037/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516037] Re: lxc-start fails with 1.1.5-0ubuntu1
It is also affecting devel-proposed phone images cf bug 1516971 -- 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/1516037 Title: lxc-start fails with 1.1.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1516037/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1514731] Re: OpenStack Installation Guide for Ubuntu in Installation Guide Executable not found: conntrack (filter match = conntrack)
Hi James,
Following is the full stacktrace.
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack
[req-69a3ea03-f2bc-4d88-9fc7-485ebc3722b3 - - - - -] Failed execute conntrack
command ['conntrack', '-D', '-f', 'ipv4', '-d', 'x.y.z.148', '-w', 6, '-s',
'x.y.z.145']
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack Traceback
(most recent call last):
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack File
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_conntrack.py", line
72, in _delete_conntrack_state
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack
extra_ok_codes=[1])
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack File
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 159, in
execute
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack raise
RuntimeError(m)
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack
RuntimeError:
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack Command:
['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf',
'conntrack', '-D', '-f', 'ipv4', '-d', 'x.y.z.148', '-w', '6', '-s',
'x.y.z.145']
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack Exit code:
96
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack Stdin:
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack Stdout:
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack Stderr:
/usr/bin/neutron-rootwrap: Executable not found: conntrack (filter match =
conntrack)
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack
2015-11-04 20:17:01.391 4333 ERROR neutron.agent.linux.ip_conntrack
2015-11-04 20:17:02.484 4333 INFO neutron.agent.securitygroups_rpc
[req-2b633c95-430d-415b-9d0c-f0687f1656ae 4fee825c04e04bcc8779fbc0e1c75154
d8c1e9ee4f6e429199a85389ab64868d - - -] Security group member updated
[u'04641584-d2eb-45e3-b6b9-a5e6d38bbb9b']
2015-11-04 20:17:02.729 4333 INFO neutron.agent.securitygroups_rpc
[req-69a3ea03-f2bc-4d88-9fc7-485ebc3722b3 - - - - -] Refresh firewall rules
To completely disable L3 I had to set all following settings to False in
/etc/openstack-dashboard/local_settings.py
OPENSTACK_NEUTRON_NETWORK = {
'enable_router': False,
'enable_quotas': False,
'enable_ipv6': False,
'enable_distributed_router': False,
'enable_ha_router': False,
'enable_lb': False,
'enable_firewall': False,
'enable_vpn': False,
'enable_fip_topology_check': False
}
--
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/1514731
Title:
OpenStack Installation Guide for Ubuntu in Installation Guide
Executable not found: conntrack (filter match = conntrack)
To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-manuals/+bug/1514731/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
