Re: [Bug 1513698] [NEW] $HOME variable set incorrectly inside container
Right, this is mentioned in the manpage. You can force environment to be cleared by passing --clear-env. Actually setting HOME to what a login shell would do would require lxc-attach to make assumptions about the container. However you can lxc-attach -n trusty-vimprobable --clear-env -- su - root to get su (inside the container) to do the things you want. -- 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/1513698 Title: $HOME variable set incorrectly inside container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1513698/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
You're still getting dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address What does sudo netstat -lap| grep LISTEN show? -- 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/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513698] [NEW] $HOME variable set incorrectly inside container
Public bug reported: I have lxc containers set up as an unprivileged user. When I start my containers, the root user has the $HOME environmental variable set, pointing at the unprivileged user. This is the faulty session: sputnik is the host, lamp2 is the lxc container ruben@sputnik:~$ echo $HOME /home/ruben ruben@sputnik:~$ lxc-start -n lamp2 -d ruben@sputnik:~$ lxc-attach -n lamp2 root@lamp2:/# echo $HOME /home/ruben root@lamp2:/# exit ruben@sputnik:~$ TEST_VAR="THIS IS A TEST" ruben@sputnik:~$ lxc-stop -n lamp2 ruben@sputnik:~$ lxc-start -n lamp2 -d ruben@sputnik:~$ lxc-attach -n lamp2 root@lamp2:/# echo $TEST_VAR root@lamp2:/# echo $HOME /home/ruben at least the $HOME variable is set incorrectly inside the container, whilte TEST_VAR is correcty unset inside. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu in the host: ruben@sputnik:~$ lsb_release LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch in the container: root@lamp2:/# lsb_release No LSB modules are available. this is a trusty container, created with a downloaded template (lxc- create ... -t download) 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ruben@sputnik:~$ apt-cache policy lxc lxc: Instalados: 1.0.7-0ubuntu0.9 Candidato: 1.0.7-0ubuntu0.9 Tabla de versión: 1.1.4-0ubuntu1.1~ubuntu14.04.2 0 100 http://mx.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 Packages *** 1.0.7-0ubuntu0.9 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.7-0ubuntu0.7 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 1.0.3-0ubuntu3 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen The user root should have it's $HOME set to /root inside the container 4) What happened instead The user root has it's $HOME set to the unprivileged user's ** 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/1513698 Title: $HOME variable set incorrectly inside container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1513698/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
Thanks again. kevin@awabi:~/tmp$ sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop kevin@awabi:~/tmp$ sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. kevin@awabi:~/tmp$ sudo brctl show bridge name bridge id STP enabled interfaces virbr0 8000.52540063031d yes virbr0-nic No luck with starting it. Here is /etc/default/lxc-net # This file is auto-generated by lxc.postinst if it does not # exist. Customizations will not be overridden. # Leave USE_LXC_BRIDGE as "true" if you want to use lxcbr0 for your # containers. Set to "false" if you'll use virbr0 or another existing # bridge, or mavlan to your host's NIC. USE_LXC_BRIDGE="true" # USE_LXC_BRIDGE="false" # If you change the LXC_BRIDGE to something other than lxcbr0, then # you will also need to update your /etc/lxc/default.conf as well as the # configuration (/var/lib/lxc//config) for any containers # already created using the default config to reflect the new bridge # name. # If you have the dnsmasq daemon installed, you'll also have to update # /etc/dnsmasq.d/lxc and restart the system wide dnsmasq daemon. LXC_BRIDGE="lxcbr0" LXC_ADDR="10.0.3.1" LXC_NETMASK="255.255.255.0" LXC_NETWORK="10.0.3.0/24" LXC_DHCP_RANGE="10.0.3.2,10.0.3.254" LXC_DHCP_MAX="253" # Uncomment the next line if you'd like to use a conf-file for the lxcbr0 # dnsmasq. For instance, you can use 'dhcp-host=mail1,10.0.3.100' to have # container 'mail1' always get ip address 10.0.3.100. #LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf # Uncomment the next line if you want lxcbr0's dnsmasq to resolve the .lxc # domain. You can then add "server=/lxc/10.0.3.1' (or your actual ) # to /etc/dnsmasq.conf, after which 'container1.lxc' will resolve on your # host. #LXC_DOMAIN="lxc" -- 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/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513676] [NEW] vxlan tunneling not working correctly
Public bug reported: I have an openstack setup with dedicated network node (using neutron- gateway charm) and a compute-only node (nova-compute charm). With this configuration: nova-cloud-controller: openstack-origin: cloud:trusty-liberty network-manager: Neutron neutron-external-network: "ext-net" console-access-protocol: vnc neutron-api: openstack-origin: cloud:trusty-liberty neutron-external-network: "ext-net" neutron-security-groups: true overlay-network-type: vxlan network-device-mtu: 9000 neutron-gateway: openstack-origin: cloud:trusty-liberty ext-port: eth1 neutron-openvswitch: # enable-local-dhcp-and-metadata: true nova-compute: openstack-origin: cloud:trusty-liberty the ml2_conf.ini on the network node ends up with: [ml2] type_drivers = gre,vxlan,vlan,flat tenant_network_types = gre,vxlan,vlan,flat mechanism_drivers = openvswitch,hyperv,l2population [ml2_type_gre] tunnel_id_ranges = 1:1000 [ml2_type_vxlan] vni_ranges = 1001:2000 [ml2_type_vlan] network_vlan_ranges = physnet1:1000:2000 [ml2_type_flat] flat_networks = [ovs] enable_tunneling = True local_ip = 10.0.0.2 bridge_mappings = physnet1:br-data [agent] tunnel_types = vxlan l2_population = True enable_distributed_routing = False veth_mtu = 9000 [securitygroup] firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver whilst the compute node has: # icehouse ### # [ WARNING ] # Configuration file maintained by Juju. Local changes may be overwritten. ### [ml2] type_drivers = gre,vxlan tenant_network_types = gre,vxlan mechanism_drivers = openvswitch [ml2_type_gre] tunnel_id_ranges = 1:1000 [ml2_type_vxlan] vni_ranges = 1001:2000 [ovs] enable_tunneling = True local_ip = 10.0.0.3 [agent] tunnel_types = gre [securitygroup] enable_security_group = True firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver Which results in inability to spin up any machines (they try to use vxlan which is not available on the compute node). ** Affects: neutron-gateway (Juju Charms Collection) Importance: Undecided Status: New ** Affects: nova-compute (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Package changed: nova (Ubuntu) => nova-compute (Juju Charms Collection) -- 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/1513676 Title: vxlan tunneling not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/charms/+source/neutron-gateway/+bug/1513676/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1509817] Re: libxml_disable_entity_loader is not theadsafe
I'll include this in the next php5 security update. -- 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/1509817 Title: libxml_disable_entity_loader is not theadsafe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1509817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513647] [NEW] vmhfgs (shared folders) module is not built
Public bug reported: Since I needed an updated version of the tools, running on my Ubuntu 15.10 VM build with VMWare Fusion Pro 8.0.2, I have downloaded the Xenial Sources and built the DEBs from scratch. However, altough the build went smoothly, when installing the new packages (10.0.0-3000743) the shared folders module (vmhgfs) is not built. Would you mind to look into this issue ? Regards, Arturo ** Affects: open-vm-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1513647 Title: vmhfgs (shared folders) module is not built To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1513647/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177432] Re: [SRU] cloud-init archive template should match Ubuntu Server
Hello Ben, or anyone else affected, Accepted cloud-init into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/0.7.5-0ubuntu1.14 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-failed ** Tags added: verification-needed -- 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/1177432 Title: [SRU] cloud-init archive template should match Ubuntu Server To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1177432/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177432] Please test proposed package
Hello Ben, or anyone else affected, Accepted cloud-init into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/0.7.7~bzr1091-0ubuntu11 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 cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1177432 Title: [SRU] cloud-init archive template should match Ubuntu Server To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1177432/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177432] Please test proposed package
Hello Ben, or anyone else affected, Accepted cloud-init into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/0.7.7~bzr1149-0ubuntu3 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 cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1177432 Title: [SRU] cloud-init archive template should match Ubuntu Server To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1177432/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177432] Re: [SRU] cloud-init archive template should match Ubuntu Server
** Changed in: cloud-init (Ubuntu Precise) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu Vivid) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu Trusty) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu Wily) Importance: Undecided => High -- 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/1177432 Title: [SRU] cloud-init archive template should match Ubuntu Server To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1177432/+subscriptions -- Ubuntu-server-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: DHCP agent: interface unplug leads to exception
Reviewed: https://review.openstack.org/242003 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a27b30d7263aefce0ffbae95316e4e5cd48165a5 Submitter: Jenkins Branch:stable/kilo commit a27b30d7263aefce0ffbae95316e4e5cd48165a5 Author: Gary Kotton Date: Sun Sep 27 00:24:31 2015 -0700 DHCP: protect against case when device name is None There are edge cases when the agent attempts to unplug an interface and the device does not exist. Closes-bug: #1498370 (cherry picked from commit caebc8fb8e8d9782746c3cc3ddc86f786342c819) (cherry picked from commit 0b07910f33ed26fbdd13530eafbdefd74104424d) Change-Id: I6917ec94f685f3dd3bff6aa1d43dc56aab76274a ** Tags added: in-stable-kilo -- 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: 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 1512497] Re: package nagios3-common 3.5.1-1ubuntu4 failed to install/upgrade: 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 nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1512497 Title: package nagios3-common 3.5.1-1ubuntu4 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/nagios3/+bug/1512497/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512961] Re: package mysql-server-5.6 5.6.27-0ubuntu0.14.04.1 failed to install/upgrade: 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 mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1512961 Title: package mysql-server-5.6 5.6.27-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1512961/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513569] Re: net-snmp-config --base-lib-cflags is broken
The attachment "Replacement patch proposition." seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1513569 Title: net-snmp-config --base-lib-cflags is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1513569/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1499510] Re: Fix Typo in socket attribute name in TCPKeepAliveAdapter
alright I'm happy to just have this one be the TCPKeepAlive typo. I noticed a bit of extra text in the debdiff so I removed that, otherwise it was only fixing the typo bug anyway. ** Description changed: - 2.23 included 2 high priority fixes which will make the nova client not - very useful for those cases. The one I'm particularly running into now - is 1430935, but does it make sense to just SRU them all together? - #1430935 Typo in socket attribute name in TCPKeepAliveAdapter HighDavid Moreau Simard Fix Released - #1431154 volumes python api calls route incorrectly High melanie wittFix Released - #1423885 nova flavor-show inconsistent with mixed case in names Low Abhishek Talwar Fix Released - #1430415 nova volume-show commands does not support volume name Low Anand Shanmugam Fix Released - #1430354 nova secgroup-list-default-rules help text is misleading WishlistChris St. PierreFix Released - - https://launchpad.net/python-novaclient/+milestone/2.23.0 + -from https://launchpad.net/python-novaclient/+milestone/2.23.0 Ubuntu 14.04 with Kilo Cloud Archive.. I have a debdiff that just fixes the typo. Alternative is to just upgrade to 15.10 or Libery Cloud Archive. - ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-novaclient 1:2.22.0-0ubuntu1~cloud0 [origin: Canonical] ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CrashDB: { "impl": "launchpad", "project": "cloud-archive", "bug_pattern_url": "http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml";, } Date: Thu Sep 24 19:39:14 2015 Ec2AMI: ami-0f4d Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.tiny Ec2Kernel: aki-0548 Ec2Ramdisk: ari-0548 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-novaclient UpgradeStatus: No upgrade log present (probably fresh install) ** Patch added: "python-novaclient_2.22.0-0ubuntu2.debdiff" https://bugs.launchpad.net/cloud-archive/+bug/1499510/+attachment/4513673/+files/python-novaclient_2.22.0-0ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/1499510 Title: Fix Typo in socket attribute name in TCPKeepAliveAdapter To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1499510/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1506058] Re: [SRU] Openstack 2015.1.2 point release
** Branch linked: lp:~ubuntu-server-dev/glance/kilo -- 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/1506058 Title: [SRU] Openstack 2015.1.2 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1506058/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177432] Re: [SRU] cloud-init archive template should match Ubuntu Server
** Summary changed: - [SRU] Enable backports in cloud-init archive template + [SRU] cloud-init archive template should match Ubuntu Server ** Description changed: [SRU Justification] - Ubuntu Cloud Images are inconsistent with desktop and bare-metal server installations since backports are not enabled. This is effected via cloud-init that uses a template to select an in-cloud archive. + Ubuntu Cloud Images are inconsistent with desktop and bare-metal server installations since backports, restricted and multiverse are not enabled. This is effected via cloud-init that uses a template to select an in-cloud archive. - [FIX] Include the Ubuntu backports in the template. + [FIX] Make the cloud-init template match that of Ubuntu-server. [REGRESION] The potential for regression is low. However, all users will experience slower fetch times on apt-get updates especially on slower or high latency networks. [TEST] 1. Build image from -proposed 2. Boot up image - 3. Confirm that "sudo apt-get update" pulls in backports. + 3. Confirm that "sudo apt-get update" pulls in backports, restricted and multiverse. Backports are currently not enabled in the cloud-init template. This is needed in order to get the backport kernels on cloud images. Related bugs: * bug 997371: Create command to add "multiverse" and "-backports" to apt sources - * bug 1513529: cloud image built-in /etc/apt/sources.list needs updating + * bug 1513529: cloud image built-in /etc/apt/sources.list needs updating -- 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/1177432 Title: [SRU] cloud-init archive template should match Ubuntu Server To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1177432/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1499510] Re: Fix Typo in socket attribute name in TCPKeepAliveAdapter
Note that bug #1431154 does have a work-around (see upstream bug) so we might consider marking that with medium importance if it is split into a separate bug. ** Changed in: cloud-archive Status: New => Triaged ** Changed in: cloud-archive Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/1499510 Title: Fix Typo in socket attribute name in TCPKeepAliveAdapter To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1499510/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177432] Re: [SRU] Enable backports in cloud-init archive template
This bug was fixed in the package cloud-init - 0.7.7~bzr1154-0ubuntu1 --- cloud-init (0.7.7~bzr1154-0ubuntu1) xenial; urgency=medium * New upstream snapshot. * create the same /etc/apt/sources.list that is present in default server ISO installs. This change adds restricted, multiverse, and -backports (LP: #1177432). -- Scott Moser Thu, 05 Nov 2015 12:10:00 -0500 ** Changed in: cloud-init (Ubuntu Xenial) Status: In Progress => Fix Released -- 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/1177432 Title: [SRU] cloud-init archive template should match Ubuntu Server To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1177432/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1499510] Re: Fix Typo in socket attribute name in TCPKeepAliveAdapter
Bryan I'd prefer to split this into two bugs/SRUs. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/1499510 Title: Fix Typo in socket attribute name in TCPKeepAliveAdapter To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1499510/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Tags added: sts -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]
Fixed changelog mistake in commit 3595280d8803319f71b53a22e39c386fab1577bf of the tree. The changelog in the merge of 9.10.3-3167576 accidentally dropped history and pulled in content from a dead development branch. This patch fixes the changelog to reflect actual changes. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1500581 Title: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’] To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1503305] Comment bridged from LTC Bugzilla
--- Comment From gbert...@br.ibm.com 2015-11-05 18:20 EDT--- Tested package from Willy-Proposed. Bug seems to be fixed there. Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1503305 Title: iLab: power kvm client after svc node reboot error inject test, multipath output show missing path and missing storage name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1503305/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1506058] Re: [SRU] Openstack 2015.1.2 point release
** Branch linked: lp:~ubuntu-server-dev/nova/kilo -- 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/1506058 Title: [SRU] Openstack 2015.1.2 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1506058/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1508087] Re: Unhandled UDP error during manual enlistment of xgene-2
After testing the updated grub, I was able to manually enlist the xgene-2 SOC without the above stacktrace error. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-tx-tftp in Ubuntu. https://bugs.launchpad.net/bugs/1508087 Title: Unhandled UDP error during manual enlistment of xgene-2 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1508087/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513569] [NEW] net-snmp-config --base-lib-cflags is broken
Public bug reported: The --base-lib-cflags option to net-snmp-config added by Debian developers is broken as it outputs @LIBCFLAGS@ among others. The problem comes from the fact that when it was introduced (version 5.4.2.1~dsfg-4), the original patch modified the configure.in file as well. In the meantime, the structure of configure.ac has changed and when the patch was adapted, the modification to configure.ac was dropped, resulting in a substitution left aside. The attached patch is an attempt to restore the original behavior. It is meant as a replacement of debian/patches/62_add_lib_cflags.patch . Nevertheless, the way information output by net-snmp-config --base-lib- cflags is gathered is wrong. There shouldn't IMHO be any GCC optimization flags like -O2 in the substitution, among others. The variable to substitute @LIBCFLAGS@ should be carefully constructed during the configure process instead. ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New ** Patch added: "Replacement patch proposition." https://bugs.launchpad.net/bugs/1513569/+attachment/4513607/+files/62_add_lib_cflags.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1513569 Title: net-snmp-config --base-lib-cflags is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1513569/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1506652] Re: [needs-packaging] Juju 1.24.7 is not in Ubuntu
** Description changed: Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated the m1* instance types and users of older Jujus are seeing cases where EC2 does not have enough instances. Juju 1.24.7 will ask for newer instance types. Juju 1.24.7 has a dhcp related fix to work with MAAS 1.9. [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. [Devel Fix] [sinzui] Prepare source package and diffs: DONE [rbasak] Review package and upload of new upstream release with packaging review: TODO [Stable Fix] [sinzui] backport wily source package and prepare diffs for vivid: DONE [rbasak] Review package for vivid-proposed: DONE [sinzui] backport source package and prepare diffs for trusty: DONE [rbasak] Review package for trusty-proposed: DONE [Pre-QA tasks] [rbasak] Upload to the current supported release (vivid-proposed): DONE [rbasak] Upload to the current LTS release (trusty-proposed): DONE [QA Status] Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-TODO or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. [sinzui] Upstream QA test against Vivid: DONE - [sinzui] Upstream QA test against Trusty: TODO + [sinzui] Upstream QA test against Trusty: DONE [sinzui] Upstream release process complete: DONE Manual tests required: [sinzui] Test juju-quickstart against vivid-proposed: DONE [sinzui] Test juju-deployer against vivid-proposed: DONE [sinzui] Test client and cloud server upgrade against vivid-proposed: DONE [sinzui] Test client manual bootstrap and add-machine against vivid-proposed: DONE - [sinzui] Test juju-quickstart against trusty-proposed: TODO - [sinzui] Test juju-deployer against trusty-proposed: TODO - [sinzui] Test client and cloud server upgrade against trusty-proposed: TODO - [sinzui] Test client manual bootstrap and add-machine against trusty-proposed: TODO + [sinzui] Test juju-quickstart against trusty-proposed: DONE + [sinzui] Test juju-deployer against trusty-proposed: DONE + [sinzui] Test client and cloud server upgrade against trusty-proposed: DONE + [sinzui] Test client manual bootstrap and add-machine against trusty-proposed: DONE ** Description changed: Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated the m1* instance types and users of older Jujus are seeing cases where EC2 does not have enough instances. Juju 1.24.7 will ask for newer instance types. Juju 1.24.7 has a dhcp related fix to work with MAAS 1.9. [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. [Devel Fix] [sinzui] Prepare source package and diffs: DONE - [rbasak] Review package and upload of new upstream release with packaging review: TODO + [rbasak] Review package and upload of new upstream release with packaging review: DONE [Stable Fix] [sinzui] backport wily source package and prepare diffs for vivid: DONE [rbasak] Review package for vivid-proposed: DONE [sinzui] backport source package and prepare diffs for trusty: DONE [rbasak] Review package for trusty-proposed: DONE [Pre-QA tasks] [rbasak] Upload to the current supported release (vivid-proposed): DONE [rbasak] Upload to the current LTS release (trusty-proposed): DONE [QA Status] Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-TODO or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. [sinzui] Upstream QA test against Vivid: DONE [sinzui] Upstream QA test against Trusty: DONE [sinzui] Upstream release process complete: DONE Manual tests required: [sinzui] Test juju-quickstart against vivid-proposed: DONE [sinzui] Test juju-deployer against vivid-proposed: DONE [sinzui] Test client and cloud server upgrade against vivid-proposed: DONE [sinzui] Test client manual bootstrap and add-machine against vivid-proposed: DONE [sinzui] Test juju-quickstart against trusty-proposed: DONE [sinzui] Test juju-deployer against trusty-proposed: DONE [sinzui] Test client and cloud server upgrade against trusty-proposed: DONE [sinzui] Test client manual bootstrap and add-machine against trusty-proposed: DONE -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to
[Bug 1506652] Re: [needs-packaging] Juju 1.24.7 is not in Ubuntu
I certify that juju 1.24.7 is suitable for local charm development and testing. Users of trusty juju 1.24.7 can create new environments in private and public clouds. Trusty juju 1.24.7 can maintain environments back to 1.18.1 (including 1.22.8 which trusty currently has). Upgrades of clients and environments from juju 1.22.8 to 1.24.7 work without need of configuration changes. Trusty juju 1.24.7 can manually provision environments and add-machines. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- 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/1506652 Title: [needs-packaging] Juju 1.24.7 is not in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1506652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1495895] Re: Unable to attach rados block device to instances
** Also affects: cloud-archive Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Fix Released ** Changed in: cloud-archive Importance: Undecided => High -- 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/1495895 Title: Unable to attach rados block device to instances To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1495895/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1509817] Re: libxml_disable_entity_loader is not theadsafe
Oh, it's a security bug. Un-triaging as I don't want to step on the security team triaging this. ** Changed in: php5 (Ubuntu Trusty) Status: Triaged => New -- 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/1509817 Title: libxml_disable_entity_loader is not theadsafe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1509817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1509817] Re: libxml_disable_entity_loader is not theadsafe
This is fixed in 5.6.14+dfsg-1ubuntu1 based on the NEWS file in there reporting upstream 64938 fixed so I'm marking this Fix Released in Xenial. It looks like this does still affect Trusty and was committed to 5.5.22 upstream and can be cherry-picked from http://git.php.net/?p=php- src.git;a=commit;h=de31324c221c1791b26350ba106cc26bad23ace9 ** Changed in: php5 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: php5 (Ubuntu Trusty) Status: Confirmed => Triaged -- 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/1509817 Title: libxml_disable_entity_loader is not theadsafe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1509817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes
Vincent Bernat (vbernat) is the Debian maintainer for haproxy. His PPA assumes a version of dpkg that is newer than 1.17.7. I'll try to open a Debian bug on that. The problem lies in the use of start-stop-daemon's new --pid option that is only available after wily. If 1.6 is backported to any version earlier than wily, this bug will exist and the fix for it will need to be applied. I just got the fix for 1.4 uploaded so I should be able to fix the 1.5 backport in the near future. ..Louis -- 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/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]
** Changed in: open-vm-tools (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1500581 Title: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’] To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
Ok, so the error msg is simply misleading - it says 'permission denied', but the bridge does not exist. Can you please show: sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start sudo brctl show and see if your container now starts? Please also paste /etc/default/lxc-net. -- 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/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513531] [NEW] Error while installing
Public bug reported: Ubuntu 15.10 ___ Got following Message while installing. Failed to get unit file state for run-vmblockx2dfuse.mount: No such file or directory run-vmblock\x2dfuse.mount is a disabled or a static unit, not starting it. First Installation: checking all kernels... Building only for 4.2.0-16-generic Building initial module for 4.2.0-16-generic Error! Build of vmhgfs.ko failed for: 4.2.0-16-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/open-vm-tools/9.10.2/build/ for more information. Mounting shared Folder not working. ** Affects: open-vm-tools (Ubuntu) Importance: Undecided Status: New ** Tags: guest open-vm-tools-dkms tools vmhgfs vmware ** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1513531/+attachment/4513557/+files/make.log ** Description changed: + Ubuntu 15.10 + ___ + Got following Message while installing. Failed to get unit file state for run-vmblockx2dfuse.mount: No such file or directory run-vmblock\x2dfuse.mount is a disabled or a static unit, not starting it. First Installation: checking all kernels... Building only for 4.2.0-16-generic Building initial module for 4.2.0-16-generic Error! Build of vmhgfs.ko failed for: 4.2.0-16-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/open-vm-tools/9.10.2/build/ for more information. - Mounting shared Folder not working. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1513531 Title: Error while installing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1513531/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177432] Re: [SRU] Enable backports in cloud-init archive template
** Description changed: [SRU Justification] Ubuntu Cloud Images are inconsistent with desktop and bare-metal server installations since backports are not enabled. This is effected via cloud-init that uses a template to select an in-cloud archive. [FIX] Include the Ubuntu backports in the template. [REGRESION] The potential for regression is low. However, all users will experience slower fetch times on apt-get updates especially on slower or high latency networks. [TEST] 1. Build image from -proposed 2. Boot up image 3. Confirm that "sudo apt-get update" pulls in backports. Backports are currently not enabled in the cloud-init template. This is needed in order to get the backport kernels on cloud images. Related bugs: * bug 997371: Create command to add "multiverse" and "-backports" to apt sources + * bug 1513529: cloud image built-in /etc/apt/sources.list needs updating -- 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/1177432 Title: [SRU] Enable backports in cloud-init archive template To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1177432/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1505576] Re: internal error: Failed to initialize a valid firewall backend
** This bug is no longer a duplicate of bug 1512749 lxcbr0 dissappears on Ubuntu 15.10 -- 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/1505576 Title: internal error: Failed to initialize a valid firewall backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1505576/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1505576] Re: internal error: Failed to initialize a valid firewall backend
*** This bug is a duplicate of bug 1512749 *** https://bugs.launchpad.net/bugs/1512749 Because AIUI the upgrade will install the fix but not restart network manager. ** This bug has been marked a duplicate of bug 1512749 lxcbr0 dissappears on Ubuntu 15.10 -- 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/1505576 Title: internal error: Failed to initialize a valid firewall backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1505576/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes
Ha, sorry about that - I crossed the wires in my head a bit. (ppa:vbernat/haproxy-1.6, for what it's worth.) Anyway, should this work for 1.6? -- 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/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177432] Re: [SRU] Enable backports in cloud-init archive template
Marking as verification-failed pending a rebase on the new upstream trunk. ** 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 cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1177432 Title: [SRU] Enable backports in cloud-init archive template To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1177432/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1244026] Re: curtin block-meta selects first entry in unordered list
** Changed in: curtin Status: Fix Committed => Fix Released ** Changed in: cloud-archive Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1244026 Title: curtin block-meta selects first entry in unordered list To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1244026/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes
Greg, 1.6.2 is not packaged for Trusty. I don't know where it comes from. -- 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/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1295498] Re: [SRU] bootable disk isn't found for instance with 8 disks
** Changed in: cloud-archive Importance: Undecided => High ** Changed in: cloud-archive Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to seabios in Ubuntu. https://bugs.launchpad.net/bugs/1295498 Title: [SRU] bootable disk isn't found for instance with 8 disks To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1295498/+subscriptions -- Ubuntu-server-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: DHCP agent: interface unplug leads to exception
** Summary changed: - DHCP agent: interface unplug leads to exeception + DHCP agent: interface unplug leads to exception -- 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: 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 1342580] Re: tftpd-hpa doesn't start on boot
I did NOT need to edit TFTP_ADDRESS in /etc/default/tftpd-hpa. I only needed to change the 'start on' condition in /etc/init/tftpd-hpa.conf to: start on (filesystem and net-device-up IFACE!=lo) The service started successfully after I made this change, and rebooted. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tftp-hpa in Ubuntu. https://bugs.launchpad.net/bugs/1342580 Title: tftpd-hpa doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1342580/+subscriptions -- Ubuntu-server-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: DHCP agent: interface unplug leads to exeception
** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu Vivid) Status: New => Fix Released ** Changed in: neutron (Ubuntu Wily) Status: New => Fix Released ** Changed in: neutron (Ubuntu Vivid) Status: Fix Released => In Progress ** Changed in: neutron (Ubuntu Xenial) Status: New => Fix Released ** 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: DHCP agent: interface unplug leads to exeception 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 1496210] Re: multipath-tools lacks the default settings for IBM 2810XIV storage system
@mathieu-tl I think so; afaik queue_if_no_path is not enabled by default. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1496210 Title: multipath-tools lacks the default settings for IBM 2810XIV storage system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1496210/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512178] Re: after upgrade to mysql-5.6 database stopped working
I deleted the database and imported from dump. Looked to me like an update error on Ubuntu, as /var/lib/mysql.install was created and still exists. But currently I cannot recreate the situation, thankfully. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1512178 Title: after upgrade to mysql-5.6 database stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1512178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1511524] Re: OpenVPN PAM authentication broken on 15.10 Server
** Tags added: bitesize systemd-boot ** Changed in: openvpn (Ubuntu) Status: New => Triaged ** Changed in: openvpn (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1511524 Title: OpenVPN PAM authentication broken on 15.10 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1511524/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512079] Re: package php5-common (not installed) failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 10
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: php5 (Ubuntu) Status: New => Incomplete -- 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/1512079 Title: package php5-common (not installed) failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1512079/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512112] Re: add manpage for pear
** Changed in: php5 (Ubuntu) Importance: Undecided => Low ** Tags added: neds-upstream-report ** Tags removed: neds-upstream-report ** Tags added: needs-upstream-report -- 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/1512112 Title: add manpage for pear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1512112/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1511524] [NEW] OpenVPN PAM authentication broken on 15.10 Server
You have been subscribed to a public bug by Robie Basak (racb): With OpenVPN 2.3.7 in server mode (config option 'mode server') on Ubuntu Server 15.10, using the PAM authentication plugin for client connections (config option 'plugin /usr/lib/openvpn/openvpn-plugin-auth- pam.so login') and launching the OpenVPN process via the systemd openvpn@ unit file (e.g. 'systemctl start openvpn@server', with a /etc/openvpn/server.conf config file) OpenVPN will return a failure on user authentication, even if the remote user authenticates with valid credentials. Launching the OpenVPN server manually (e.g. 'openvpn --config /etc/openvpn/server.conf') does not result in the same problem, and the user is able to authenticate. On user authentication, OpenVPN will log the following: AUTH-PAM: BACKGROUND: user 'vpnuser' failed to authenticate: System error and in /var/log/auth.log, the following will be logged: PAM audit_log_acct_message() failed: Operation not permitted CAUSE: The openvpn@.service unit file is too restrictive. The CapabilityBoundingSet parameter in /lib/systemd/system/openvpn@.service does not provide sufficient capabilities for the OpenVPN process to authenticate using PAM. SOLUTION: Adding the option CAP_AUDIT_WRITE to the CapabilityBoundingSet parameter in the openvpn@.service unit file resolves the problem and allows OpenVPN to authenticate properly using PAM. PROPOSED: Change the shipped openvpn@.service unit file to include CAP_AUDIT_WRITE in the CapabilityBoundingSet. DETAILS: Description:Ubuntu 15.10 Release:15.10 openvpn: Installed: 2.3.7-1ubuntu1 Candidate: 2.3.7-1ubuntu1 Version table: *** 2.3.7-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: bitesize openvpn pam systemd-boot -- OpenVPN PAM authentication broken on 15.10 Server https://bugs.launchpad.net/bugs/1511524 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512178] Re: after upgrade to mysql-5.6 database stopped working
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: mysql-5.6 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1512178 Title: after upgrade to mysql-5.6 database stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1512178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512168] Re: package ntp 1:4.2.6.p5+dfsg-3ubuntu8.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: ntp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1512168 Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu8.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512168/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512178] Re: after upgrade to mysql-5.6 database stopped working
>From log: 2015-11-01 23:54:51 2917 [ERROR] InnoDB: ./ibdata1 can't be opened in read-write mode 2015-11-01 23:54:51 2917 [ERROR] InnoDB: The system tablespace must be writable! 2015-11-01 23:54:51 2917 [ERROR] Plugin 'InnoDB' init function returned error. 2015-11-01 23:54:51 2917 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2015-11-01 23:54:51 2917 [ERROR] Unknown/unsupported storage engine: InnoDB 2015-11-01 23:54:51 2917 [ERROR] Aborting -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1512178 Title: after upgrade to mysql-5.6 database stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1512178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512131] [NEW] Apparmor complains about multiple /run/dovecot file access
You have been subscribed to a public bug by Robie Basak (racb): Hi, since I upgraded from XUbuntu 15.04 to 15.10 I started to get a lot of apparmor complains about dovecot. The complains were more or less like this: operation="connect" profile="/usr/lib/dovecot/auth" name="/run/dovecot/anvil-auth-penalty" comm="auth" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 operation="connect" profile="/usr/lib/dovecot/auth" name="/run/dovecot/auth-worker" comm="auth" requested_mask="wr" denied_mask="wr" fsuid=117 ouid=117 operation="file_perm" profile="/usr/lib/dovecot/anvil" name="/run/dovecot/anvil-auth-penalty" comm="anvil" requested_mask="r" denied_mask="r" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/anvil" name="/run/dovecot/anvil" comm="anvil" requested_mask="r" denied_mask="r" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/anvil" name="/run/dovecot/anvil" comm="anvil" requested_mask="w" denied_mask="w" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/anvil-auth-penalty" comm="auth" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/auth-master" comm="auth" requested_mask="w" denied_mask="w" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/auth-worker" comm="auth" requested_mask="r" denied_mask="r" fsuid=0 ouid=117 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/auth-worker" comm="auth" requested_mask="w" denied_mask="w" fsuid=117 ouid=117 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/login/login" comm="auth" requested_mask="r" denied_mask="r" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/login/login" comm="auth" requested_mask="w" denied_mask="w" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/imap" name="/run/dovecot/login/imap" comm="imap" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/imap" name="/run/dovecot/login/imap" comm="imap" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/ssl-params" name="/run/dovecot/login/ssl-params" comm="ssl-params" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 operation="file_receive" profile="/usr/lib/dovecot/imap" comm="imap" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/imap-login" operation="file_receive" profile="/usr/lib/dovecot/imap-login" comm="imap" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/imap" operation="signal" profile="/usr/sbin/dovecot" comm="dovecot" requested_mask="send" denied_mask="send" signal=int peer="/usr/lib/dovecot/auth" To avoid them, I added some stuff to the /etc/apparmor.d/local directory, patch attached. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dovecot-core 1:2.2.18-2ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 1 19:42:56 2015 InstallationDate: Installed on 2012-11-11 (1085 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: dovecot UpgradeStatus: Upgraded to wily on 2015-11-01 (0 days ago) ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug patch wily -- Apparmor complains about multiple /run/dovecot file access https://bugs.launchpad.net/bugs/1512131 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1423226] Re: package open-vm-tools 2:9.4.0-1280544-5ubuntu6.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
>From the comments it sounds like this issue is caused either by user error or by VMWare WorkStation and so is not a bug in Ubuntu? In this case I'm marking this bug Invalid, but if someone disagrees and thinks there is a bug in Ubuntu here then please explain and set the status back to New. ** Changed in: open-vm-tools (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1423226 Title: package open-vm-tools 2:9.4.0-1280544-5ubuntu6.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1423226/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512603] Re: nut-monitor systemd service is absent in nut-client package since Ubuntu vivid
The init.d script was a broken symlink to nut-client, so I just copied the systemd unit from an earlier package, and it works fine now. -- 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/1512603 Title: nut-monitor systemd service is absent in nut-client package since Ubuntu vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1512603/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512497] Re: package nagios3-common 3.5.1-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: nagios3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1512497 Title: package nagios3-common 3.5.1-1ubuntu4 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/nagios3/+bug/1512497/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512497] Re: package nagios3-common 3.5.1-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
>From log: Nov 02 15:39:18 hostname systemd[1]: Job dev-disk-by\x2duuid-728009cc\x2dfcdc\x2d4b6a\x2da504\x2d689cfbc0fb0d.device/start timed out. Nov 02 15:39:18 hostname systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-728009cc\x2dfcdc\x2d4b6a\x2da504\x2d689cfbc0fb0d.device. Nov 02 15:39:18 hostname systemd[1]: Dependency failed for /dev/disk/by-uuid/728009cc-fcdc-4b6a-a504-689cfbc0fb0d. Nov 02 15:40:49 hostname systemd[1]: Job dev-disk-by\x2duuid-728009cc\x2dfcdc\x2d4b6a\x2da504\x2d689cfbc0fb0d.device/start timed out. Nov 02 15:40:49 hostname systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-728009cc\x2dfcdc\x2d4b6a\x2da504\x2d689cfbc0fb0d.device. Nov 02 15:40:49 hostname systemd[1]: Dependency failed for /dev/disk/by-uuid/728009cc-fcdc-4b6a-a504-689cfbc0fb0d. Nov 02 15:41:01 hostname systemd[1]: Failed to start LSB: nagios host/service/network monitoring and management system. Nov 02 15:41:01 hostname systemd[1]: nagios3.service failed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1512497 Title: package nagios3-common 3.5.1-1ubuntu4 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/nagios3/+bug/1512497/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512688] Re: service haproxy stop does not work
Thank you for taking the time to report this bug and helping to make Ubuntu better. Does this issue affect the backport only, or does it also affect haproxy on Trusty or the release the backport was from? Since you've reported this as affecting the backport I'll reassign to the backports project, but if it also affects an Ubuntu release without backports then we need a bug task for that and should fix it there too. ** Package changed: haproxy (Ubuntu) => trusty-backports -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1512688 Title: service haproxy stop does not work To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1512688/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512600] Re: package mysql-server-5.6 5.6.27-0ubuntu0.14.04.1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/innochecksum.1.gz', which is also in package mysql-server-core-5.
*** This bug is a duplicate of bug 1510885 *** https://bugs.launchpad.net/bugs/1510885 ** This bug has been marked a duplicate of bug 1510885 package mysql-server-5.6 5.6.25-3+deb.sury.org~trusty+1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/innochecksum.1.gz', which is also in package mysql-server-core-5.6 5.6.25-3+deb.sury.org~trusty+1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1512600 Title: package mysql-server-5.6 5.6.27-0ubuntu0.14.04.1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/innochecksum.1.gz', which is also in package mysql-server-core-5.6 5.6.25-3+deb.sury.org~trusty+1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1512600/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512603] Re: nut-monitor systemd service is absent in nut-client package since Ubuntu vivid
** Tags added: systemd-boot -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1512603 Title: nut-monitor systemd service is absent in nut-client package since Ubuntu vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1512603/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1460712] Re: Powernap systemd setup is broken
** Tags added: systemd-boot -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to powernap in Ubuntu. https://bugs.launchpad.net/bugs/1460712 Title: Powernap systemd setup is broken To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1460712/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512603] [NEW] nut-monitor systemd service is absent in nut-client package since Ubuntu vivid
You have been subscribed to a public bug by Robie Basak (racb): The systemd unit for the upsmon has disapperared from nut-client package since Ubuntu trusty: http://packages.ubuntu.com/trusty/amd64/nut-client/filelist (2.7.1-1ubuntu1) vs http://packages.ubuntu.com/vivid/amd64/nut-client/filelist (2.7.1-1ubuntu4) ** Affects: nut (Ubuntu) Importance: Undecided Status: New ** Tags: systemd-boot vivid wily xenial -- nut-monitor systemd service is absent in nut-client package since Ubuntu vivid https://bugs.launchpad.net/bugs/1512603 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512961] Re: package mysql-server-5.6 5.6.27-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: mysql-5.6 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1512961 Title: package mysql-server-5.6 5.6.27-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1512961/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1512972] Re: package mysql-server-5.6 5.6.27-0ubuntu0.15.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: mysql-5.6 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1512972 Title: package mysql-server-5.6 5.6.27-0ubuntu0.15.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1512972/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513235] Re: package mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade: il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 1
Sorry, moving from MariaDB 10.0 to MySQL 5.6 automatically is not a supported path at the moment. You need to migrate your database manually. ** Changed in: mysql-5.6 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1513235 Title: package mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade: il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1513235/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513268] Re: upgrade unixodbc package to 2.3.4
** Changed in: unixodbc (Ubuntu) Status: New => Triaged ** Changed in: unixodbc (Ubuntu) Importance: Undecided => Medium -- 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/1513268 Title: upgrade unixodbc package to 2.3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unixodbc/+bug/1513268/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513268] [NEW] upgrade unixodbc package to 2.3.4
You have been subscribed to a public bug by Robie Basak (racb): Please package version 2.3.4 of unixODBC which was released August 2015. It has many fixes since the currently available version 2.3.1, which was released nearly 4 years ago: - ASCII-UNICODE conversion updates - mutex deadlock fixes - buffer overruns - addition of ODBC 3.8 features The complete changelog is at http://www.unixodbc.org/ ** Affects: unixodbc (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- upgrade unixodbc package to 2.3.4 https://bugs.launchpad.net/bugs/1513268 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1511875] Re: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container
I'm seeing this in Vivid -> Wily too, but in a Xen VM, not an LXC container. None of the above suggestions worked, it logs the same errors as Serge. -- 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/1511875 Title: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1511875/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513367] [NEW] qemu-system-x86_64/kvm-spice failed to boot a vm with appmor enabled
Public bug reported: This bug is seperate from bug https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532 to focus on the error. I have been trying to redeploy the environment, for this time, the error is not about kvm-spice, it is qemu-system-x86_64 got the same problem. Due to /usr/bin/qemu-system-x86_64 is a bin file, I am not able to put the strace there. And I don't know why suddenly /usr/bin/kvm-spice has been replaced by /usr/bin/qemu-systerm-x86_64. 2015-11-05 15:36:15.491 DEBUG nova.compute.utils [req-b292f304-014b-479f-af5d-38b96309f78f admin admin] [instance: 3dceb341-643d-492a-8a47-8154da341c02] internal error: Process exited prior to exec: libvirt: error : unable to set AppArmor profile 'libvirt-3dceb341-643d-492a-8a47-8154da341c02' for '/usr/bin/qemu-system-x86_64': No such file or directory from (pid=12236) notify_about_instance_usage /opt/stack/nova/nova/compute/utils.py:284 2015-11-05 15:36:15.492 DEBUG nova.compute.manager [req-b292f304-014b-479f-af5d-38b96309f78f admin admin] [instance: 3dceb341-643d-492a-8a47-8154da341c02] Build of instance 3dceb341-643d-492a-8a47-8154da341c02 was re-scheduled: internal error: Process exited prior to exec: libvirt: error : unable to set AppArmor profile 'libvirt-3dceb341-643d-492a-8a47-8154da341c02' for '/usr/bin/qemu-system-x86_64': No such file or directory Let me know what's the next step for further analysis. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1513367 Title: qemu-system-x86_64/kvm-spice failed to boot a vm with appmor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1513367/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs