[Bug 1679873] [NEW] Backport Cavium LiquidIO driver into Yakkety for lio_23xx support
Public bug reported: The Current Yakkety driver does not have support for the new generation of Cavium LiquidIO adapter. This bug is for backporting the driver. A firmware file also needs to be included in initramfs for the driver to initialize correctly. git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git cd linux-firmware/liquidio Use the lio_23xx_nic.bin file ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: oil -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679873 Title: Backport Cavium LiquidIO driver into Yakkety for lio_23xx support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor
Hi Christian, here's the requested data below. This is with Xenial and Ocata. It has worked with Xenial and Mitaka. ubuntu@phanpy:~$ virsh capabilities 12ded42d-2831-44a4-b0ba-cc3af3481077 aarch64 tcp rdma 131989624 32997406 0 apparmor 0 dac 0 +64055:+117 +64055:+117 hvm 32 /usr/bin/qemu-system-arm integratorcp nuri verdex ast2500-evb smdkc210 collie imx25-pdk spitz realview-pbx-a9 realview-eb versatilepb realview-pb-a8 musicpal z2 akita virt-2.7 kzm virt-2.8 virt realview-eb-mpcore sx1 sx1-v1 virt-2.6 cubieboard highbank raspi2 netduino2 terrier n810 mainstone palmetto-bmc sabrelite midway cheetah tosa borzoi versatileab lm3s6965evb n800 connex xilinx-zynq-a9 vexpress-a9 vexpress-a15 canon-a1100 lm3s811evb /usr/bin/qemu-system-aarch64 integratorcp nuri verdex ast2500-evb smdkc210 collie imx25-pdk spitz realview-pbx-a9 realview-eb versatilepb realview-pb-a8 musicpal z2 akita virt-2.7 kzm virt-2.8 virt realview-eb-mpcore sx1 sx1-v1 virt-2.6 cubieboard highbank raspi2 netduino2 terrier n810 mainstone palmetto-bmc sabrelite midway cheetah tosa borzoi versatileab lm3s6965evb n800 connex xilinx-zynq-a9 xlnx-ep108 vexpress-a9 vexpress-a15 xlnx-zcu102 canon-a1100 lm3s811evb hvm 64 /usr/bin/qemu-system-aarch64 integratorcp nuri verdex ast2500-evb smdkc210 collie imx25-pdk spitz realview-pbx-a9 realview-eb versatilepb realview-pb-a8 musicpal z2 akita virt-2.7 kzm virt-2.8 virt realview-eb-mpcore sx1 sx1-v1 virt-2.6 cubieboard highbank raspi2 netduino2 terrier n810 mainstone palmetto-bmc sabrelite midway cheetah tosa borzoi versatileab lm3s6965evb n800 connex xilinx-zynq-a9 xlnx-ep108 vexpress-a9 vexpress-a15 xlnx-zcu102 canon-a1100 lm3s811evb /usr/bin/kvm integratorcp nuri verdex ast2500-evb smdkc210 collie imx25-pdk spitz realview-pbx-a9 realview-eb versatilepb realview-pb-a8 musicpal z2 akita virt-2.7 kzm virt-2.8 virt realview-eb-mpcore sx1 sx1-v1 virt-2.6 cubieboard highbank raspi2 netduino2 terrier n810 mainstone palmetto-bmc sabrelite midway cheetah tosa borzoi versatileab lm3s6965evb n800 connex xilinx-zynq-a9 xlnx-ep108 vexpress-a9 vexpress-a15 xlnx-zcu102 canon-a1100 lm3s811evb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673467 Title: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1673467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com
[Bug 1673467] [NEW] [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor
Public bug reported: We hit this error in Ocata while trying to launch an arm64 instance: 2017-03-16 08:01:42.329 144245 ERROR nova.virt.libvirt.guest [req-2ad2d5d9-696d-4baa-a071-756e460ca3de 8f431f83f7e44ef1a084e7e27b40a685 a904dd389c5d4817a4d95b8f3268cf4d - - -] Error launching a defined domain with XML: instance-0001 220bec1b-8907-4da9-9862-9cc2354abf39 http://openstack.org/xmlns/libvirt/nova/1.0";> guestOS-test-arm64-kvm-xenial-ci_oil_slave14_0 2017-03-16 08:01:38 2048 20 0 0 1 admin admin 2097152 2097152 1 1024 hvm /usr/share/AAVMF/AAVMF_CODE.fd /var/lib/libvirt/qemu/nvram/instance-0001_VARS.fd destroy restart destroy /usr/bin/kvm 2017-03-16 08:01:42.333 144245 ERROR nova.virt.libvirt.driver [req-2ad2d5d9-696d-4baa-a071-756e460ca3de 8f431f83f7e44ef1a084e7e27b40a685 a904dd389c5d4817a4d95b8f3268cf4d - - -] [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] Failed to start libvirt guest 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1930, in _build_and_run_instance 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] block_device_info=block_device_info) 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2688, in spawn 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] destroy_disks_on_failure=True) 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5099, in _create_domain_and_network 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] destroy_disks_on_failure) 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] self.force_reraise() 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] six.reraise(self.type_, self.value, self.tb) 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5071, in _create_domain_and_network 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] post_xml_callback=post_xml_callback) 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 4989, in _create_domain 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] guest.launch(pause=pause) 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] self._encoded_xml, errors='ignore') 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] self.force_reraise() 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] six.reraise(self.type_, self.value, self.tb) 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/guest.py", line 140, in launch 2017-03-16 08:01:43.522 144245 ERROR nova.compute.manager [instance: 220bec1b-8907-4da9-9862-9cc2354abf39] return self._domain.createWithFlags(fla
[Bug 1637230] Re: [2.0] Error calling 'lxd forkstart
I have tried to recreate however I am now seeing the agent not coming up on the unit and can't ssh it it (connection refused): jenkins@juju-a6a70b-integration-juju2-1:~$ juju status 5 --format=yaml model: name: ci-oil-slave14 controller: maas cloud: maas version: 2.1-rc2 machines: "5": juju-status: current: pending since: 23 Feb 2017 00:32:24Z dns-name: 10.244.242.181 ip-addresses: - 10.244.242.181 instance-id: 4y4fm8 machine-status: current: running message: Deployed since: 23 Feb 2017 01:07:34Z series: trusty containers: 5/lxd/0: juju-status: current: pending since: 23 Feb 2017 00:33:13Z instance-id: pending machine-status: current: pending since: 23 Feb 2017 00:33:13Z series: trusty constraints: tags=integrationnedge1 hardware: arch=amd64 cores=4 mem=8192M tags=whitelist-nedge,integrationnedge1,hw-integration-xenial availability-zone=default "6": juju-status: current: started since: 23 Feb 2017 00:39:37Z version: 2.1-rc2 dns-name: 10.244.242.231 ip-addresses: - 10.244.242.231 instance-id: 4y4crh machine-status: current: running message: Deployed since: 23 Feb 2017 00:39:05Z series: trusty containers: 6/lxd/0: juju-status: current: started since: 23 Feb 2017 00:48:04Z version: 2.1-rc2 dns-name: 10.244.242.105 ip-addresses: - 10.244.242.105 instance-id: juju-0ce83c-6-lxd-0 machine-status: current: running message: Container started since: 23 Feb 2017 00:47:22Z series: trusty constraints: tags=hayward-43 hardware: arch=amd64 cores=8 mem=16384M tags=hardware-sm15k,hayward-43,hw-integration-xenial availability-zone=default applications: keystone: charm: cs:keystone-262 series: trusty os: ubuntu charm-origin: jujucharms charm-name: keystone charm-rev: 262 exposed: false application-status: current: active message: Unit is ready since: 23 Feb 2017 15:26:39Z relations: cluster: - keystone identity-service: - cinder - glance - neutron-api - nexentaedge-swift-gw - nova-cloud-controller - openstack-dashboard shared-db: - mysql units: keystone/0: workload-status: current: active message: Unit is ready since: 23 Feb 2017 15:26:39Z juju-status: current: idle since: 23 Feb 2017 15:26:44Z version: 2.1-rc2 leader: true machine: 6/lxd/0 open-ports: - 5000/tcp public-address: 10.244.242.105 version: 9.2.0 nexentaedge-mgmt: charm: cs:trusty/nexentaedge-mgmt-5 series: trusty os: ubuntu charm-origin: jujucharms charm-name: nexentaedge-mgmt charm-rev: 5 exposed: false application-status: current: waiting message: waiting for machine since: 23 Feb 2017 00:32:58Z relations: cinder-gw: - nexentaedge-iscsi-gw nedge: - nexentaedge-data swift-gw: - nexentaedge-swift-gw units: nexentaedge-mgmt/0: workload-status: current: waiting message: waiting for machine since: 23 Feb 2017 00:32:58Z juju-status: current: allocating since: 23 Feb 2017 00:32:58Z machine: "5" public-address: 10.244.242.181 openstack-dashboard: charm: cs:openstack-dashboard-243 series: trusty os: ubuntu charm-origin: jujucharms charm-name: openstack-dashboard charm-rev: 243 exposed: false application-status: current: waiting message: waiting for machine since: 23 Feb 2017 00:33:23Z relations: cluster: - openstack-dashboard identity-service: - keystone units: openstack-dashboard/0: workload-status: current: waiting message: waiting for machine since: 23 Feb 2017 00:33:23Z juju-status: current: allocating since: 23 Feb 2017 00:33:23Z machine: 5/lxd/0 So, I have to get passed that first. This could be a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637230 Title: [2.0] Error calling 'lxd forkstart To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1637230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606102] Re: ppc64le - GU_PAGE_SIZE(4096) does not maptch real system page size(65536)
I tried to test but percona-galera-3 is what actually gets installed in our deployment. We'd need this package built as well in order to be able to verify the fix. Will it be possible to have that built as well please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606102 Title: ppc64le - GU_PAGE_SIZE(4096) does not maptch real system page size(65536) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/galera-3/+bug/1606102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657305] Re: percona cluster getting wrong private ip
I was able to get the percona-cluster to fetch the correct private- address by using access-network option to specify the correct network where I expected this private-address to be on. Note that I also was using the access binding to specify space associated with that subnet so not sure if both binding and access- network are needed. However, the access binding by itself did not work. For example: With space oil set mapped to 192.0.5.0/24 percona-cluster: charm: cs:trusty/percona-cluster num_units: 1 options: sst-password: root root-password: root max-connections: 1500 access-network: 192.0.5.0/24 source: cloud:trusty-mitaka bindings: access: oil to: - lxc:3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657305 Title: percona cluster getting wrong private ip To manage notifications about this bug go to: https://bugs.launchpad.net/opnfv/+bug/1657305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657305] Re: percona cluster getting wrong private ip
** Tags added: oil oil-2.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657305 Title: percona cluster getting wrong private ip To manage notifications about this bug go to: https://bugs.launchpad.net/opnfv/+bug/1657305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649476] [NEW] 16.04: Unity unexpectedly moves windows to different workspace windows when using extended display
Public bug reported: I have been using a monitor to extend the display on my laptop since Trusty. It is connected through HDMI cable to my laptop, then I extend the display instead of mirroring. Strange things started happening after I switched to Xenial. After my screen gets locked automatically and I unlock it, I will find my windows moved around workspace windows. If I disable workspaces, then I will have windows disappear. I then have to re-enable workspaces in order to find that they were moved to a virtual workspace window. This is exacerbated when I try to access a window by clicking on an application in the side bar and I am taken to workspace windows that I am not familiar with. Trying to get back to previous windows then becomes a search activity. I want to disable workspaces but I can't since I have to use the extended display. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Summary changed: - 16.04: Unity moves windows to different workspaces when using multiple monitors + 16.04: Unity unexpectedly moves windows to different workspace windows when using extended display -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649476 Title: 16.04: Unity unexpectedly moves windows to different workspace windows when using extended display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1649476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574610] Re: [DVSPlugin]Missing table nsxv_subnet_ext_attributes
** Tags added: oil -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574610 Title: [DVSPlugin]Missing table nsxv_subnet_ext_attributes To manage notifications about this bug go to: https://bugs.launchpad.net/vmware-nsx/+bug/1574610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628535] [NEW] AH00493: SIGUSR1 received. Doing graceful restart - Apache2 crashes - Can't access maas server URL
Public bug reported: We stopped being able to access maas through its web address and this caused a crash: File "/usr/lib/python2.7/dist-packages/oil_ci/common/maas.py", line 137, in get_tagged_nodes all_nodes_list = self.nodes_list(user) File "/usr/lib/python2.7/dist-packages/oil_ci/common/maas.py", line 378, in nodes_list return json.loads(self.cmd(command)) File "/usr/lib/python2.7/dist-packages/oil_ci/common/maas.py", line 281, in cmd content = self.client.get(command).read() File "/usr/lib/python2.7/dist-packages/apiclient/maas_client.py", line 237, in get url, method="GET", headers=headers) File "/usr/lib/python2.7/dist-packages/apiclient/maas_client.py", line 116, in dispatch_query res = urllib2.urlopen(req) File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen return _opener.open(url, data, timeout) File "/usr/lib/python2.7/urllib2.py", line 404, in open response = self._open(req, data) File "/usr/lib/python2.7/urllib2.py", line 422, in _open '_open', req) File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 1214, in http_open return self.do_open(httplib.HTTPConnection, req) File "/usr/lib/python2.7/urllib2.py", line 1184, in do_open raise URLError(err) URLError: On the apache2 error log, I saw: ue Sep 27 06:25:12.159028 2016] [mpm_event:notice] [pid 1895:tid 140037883340672] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations [Tue Sep 27 06:25:12.159257 2016] [core:notice] [pid 1895:tid 140037883340672] AH00094: Command line: '/usr/sbin/apache2' [Wed Sep 28 06:25:09.318844 2016] [mpm_event:notice] [pid 1895:tid 140037883340672] AH00493: SIGUSR1 received. Doing graceful restart AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message [Wed Sep 28 06:25:12.038905 2016] [mpm_event:notice] [pid 1895:tid 140037883340672] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations [Wed Sep 28 06:25:12.038944 2016] [core:notice] [pid 1895:tid 140037883340672] AH00094: Command line: '/usr/sbin/apache2' [Wed Sep 28 06:25:14.040425 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 06:25:15.041505 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 06:25:16.042554 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 06:25:17.043605 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 06:25:18.045062 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 06:25:19.046130 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 06:25:20.047475 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 06:25:21.048295 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers ... ull, not at MaxRequestWorkers [Wed Sep 28 12:53:25.662213 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 12:53:26.663278 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 12:53:27.664325 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 12:53:28.665413 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers [Wed Sep 28 12:53:29.666492 2016] [mpm_event:error] [pid 1895:tid 140037883340672] AH00485: scoreboard is full, not at MaxRequestWorkers The errors stopped when I restarted the apache2 service with sudo service apache2 restart. I couldn't tell where to find the core. There was only this file from a week ago: $ ls -l _usr_sbin_apache2.0.crash -rw-r- 1 root root 2526598 Sep 21 22:33 _usr_sbin_apache2.0.crash I tried to rerun it again and timestamp changed but core info did not appear to change. I have collected access and error logs of the past couple of days as well as other logs including maas logs. Tarball is attached to this bug and it contains the 2 crash files: $ ls -l _usr_sbin_apache2.0.crash.* -rw-r- 1 ubuntu ubuntu 2698755 Sep 28 13:42 _usr_sbin_apache2.0.crash.new -rw-r- 1 ubuntu ubuntu 2526598 Sep 21 22:33 _usr_sbin_apache2.0.crash.old These are the package versions: ii maas 2.0.0+bzr5189-0 all "Metal as a Service" is a physical cloud and I ii apache2
[Bug 1614271] [NEW] virtual nic with vmxnet3 driver has 1Gbit/s capacity instead of 10Gbit/s in trusty
Public bug reported: In trusty, properties for virtual vmxnet3 NIC from an ESXi 6.0 virtual machine are showing 1Gbit/s capacity. In Xenial, it's showing speed 10Gbit/s. $ lsb_release -rd Description:Ubuntu 14.04.5 LTS Release:14.04 This is for trusty: *-pci:2 description: PCI bridge product: PCI Express Root Port vendor: VMware physical id: 15 bus info: pci@:00:15.0 version: 01 width: 32 bits clock: 33MHz capabilities: pci pm pciexpress msi normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:40 ioport:4000(size=4096) memory:fd40-fd4f ioport:c000(size=3145728) *-network description: Ethernet interface product: VMXNET3 Ethernet Controller vendor: VMware physical id: 0 bus info: pci@:03:00.0 logical name: eth0 version: 01 serial: 00:50:56:87:40:8a capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list rom ethernet physical logical tp 1000bt-fd configuration: autonegotiation=off broadcast=yes driver=vmxnet3 driverversion=1.2.0.0-k-NAPI duplex=full ip=10.244.241.14 latency=0 link=yes multicast=yes port=twisted pair resources: irq:18 memory:fd4fc000-fd4fcfff memory:fd4fd000-fd4fdfff memory:fd4fe000-fd4f ioport:4000(size=16) memory:c000-c000 For Xenial: *-pci:2 description: PCI bridge product: PCI Express Root Port vendor: VMware physical id: 15 bus info: pci@:00:15.0 version: 01 width: 32 bits clock: 33MHz capabilities: pci pm pciexpress msi normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:24 ioport:4000(size=4096) memory:fd40-fd4f ioport:c000(size=2097152) *-network description: Ethernet interface product: VMXNET3 Ethernet Controller vendor: VMware physical id: 0 bus info: pci@:03:00.0 logical name: eth0 version: 01 serial: 00:50:56:87:40:8a size: 10Gbit/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list rom ethernet physical logical tp 1000bt-fd configuration: autonegotiation=off broadcast=yes driver=vmxnet3 driverversion=1.4.5.0-k-NAPI duplex=full ip=10.244.241.12 latency=0 link=yes multicast=yes port=twisted pair speed=10Gbit/s resources: irq:18 memory:fd4fc000-fd4fcfff memory:fd4fd000-fd4fdfff memory:fd4fe000-fd4f ioport:4000(size=16) memory:fd40-fd40 lshw output and versions are attached. ** Affects: lshw (Ubuntu) Importance: Undecided Status: New ** Tags: oil ** Attachment added: "lshw.tar.gz" https://bugs.launchpad.net/bugs/1614271/+attachment/4723005/+files/lshw.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614271 Title: virtual nic with vmxnet3 driver has 1Gbit/s capacity instead of 10Gbit/s in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1614271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1389811] Re: tgtadm: out of memory crash
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389811 Title: tgtadm: out of memory crash To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1389811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582364] Re: Failure to reset devices.list on LXC privileged containers on Xenial
Serge, thanks for looking. Here's the *release info. The lxc package info is in description. ubuntu@psyduck-maas20:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS" NAME="Ubuntu" VERSION="16.04 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; UBUNTU_CODENAME=xenial Right, the issue is not the container not being able to start, but whether there is an impact to services within the container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582364 Title: Failure to reset devices.list on LXC privileged containers on Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1582364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582364] [NEW] Failure to reset devices.list on LXC privileged containers on Xenial
Public bug reported: I created a privilege container on Xenial using command "sudo lxc-create -n test-privilege -t ubuntu", and container hits failed to reset devices.list errors for every boot: root@psyduck-maas20:/var/lib/lxc# sudo lxc-start -n test-privilege -F systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) Detected virtualization lxc. Detected architecture x86-64. Welcome to Ubuntu 16.04 LTS! Set hostname to . Failed to install release agent, ignoring: No such file or directory [ OK ] Reached target Swap. [ OK ] Listening on Syslog Socket. Failed to reset devices.list on /system.slice: Operation not permitted [ OK ] Created slice System Slice. Failed to reset devices.list on /system.slice/system-getty.slice: Operation not permitted [ OK ] Created slice system-getty.slice. [ OK ] Reached target Encrypted Volumes. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on Journal Socket. Failed to reset devices.list on /system.slice/dev-hugepages.mount: Operation not permitted Mounting Huge Pages File System... Failed to reset devices.list on /system.slice/systemd-journald.service: Operation not permitted Starting Journal Service... Failed to reset devices.list on /system.slice/resolvconf.service: Operation not permitted Starting Nameserver information manager... Failed to reset devices.list on /system.slice/systemd-remount-fs.service: Operation not permitted Starting Remount Root and Kernel File Systems... [ OK ] Started Dispatch Password Requests to Console Directory Watch. Failed to reset devices.list on /system.slice/system-container\x2dgetty.slice: Operation not permitted [ OK ] Created slice system-container\x2dgetty.slice. [ OK ] Reached target Slices. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Reached target Sockets. Failed to reset devices.list on /system.slice/dev-lxc-tty4.mount: Operation not permitted Failed to reset devices.list on /system.slice/sys-kernel-debug.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-lxc-tty2.mount: Operation not permitted Failed to reset devices.list on /system.slice/-.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-lxc-tty1.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-mqueue.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-lxc-tty3.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-diskstats.mount: Operation not permitted Failed to reset devices.list on /system.slice/sys-fs-fuse-connections.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-meminfo.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-uptime.mount: Operation not permitted Failed to reset devices.list on /system.slice/sys-devices-virtual-net.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-lxc-console.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-sys-net.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-swaps.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-sysrq\x2dtrigger.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-stat.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-cpuinfo.mount: Operation not permitted Failed to reset devices.list on /init.scope: Operation not permitted [ OK ] Mounted Huge Pages File System. [ OK ] Started Remount Root and Kernel File Systems. Failed to reset devices.list on /system.slice/systemd-random-seed.service: Operation not permitted Starting Load/Save Random Seed... [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Failed to reset devices.list on /system.slice/systemd-remount-fs.service: Operation not permitted [ OK ] Started Journal Service. Starting Flush Journal to Persistent Storage... [ OK ] Started Nameserver information manager. Starting Raise network interfaces... [ OK ] Started Load/Save Random Seed. [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Started Create Volatile Files and Directories. Starting Update UTMP about System Boot/Shutdown... [ OK ] Reached target System Time Synchronized. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Reached target System Initialization. [ OK ] Started Trigger resolv
[Bug 1524339] [NEW] virsh failure to start lxc container - internal error: Unable to find 'cpuacct' cgroups controller mount
Public bug reported: Seeing libvirt error while trying to deploy instances in OpenStack deployment: "error: internal error: Unable to find 'cpuacct' cgroups controller mount". This is recreatable for kilo and liberty. The cloud version for kilo is root@lambert:~# dpkg -l|grep virt ii libvirt-bin 1.2.12-0ubuntu14.2~cloud0 amd64programs f or the libvirt library ii libvirt01.2.12-0ubuntu14.2~cloud0 amd64library fo r interfacing with different virtualization systems And I was also able to recreate with liberty version: root@lambert:/etc/apt/sources.list.d# apt-cache policy libvirt-bin libvirt-bin: Installed: 1.2.16-2ubuntu11~cloud0 Candidate: 1.2.16-2ubuntu11~cloud0 Version table: *** 1.2.16-2ubuntu11~cloud0 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu13.1.14 0 500 http://archive.ubuntu.com//ubuntu/ trusty-updates/main amd64 Packages 1.2.2-0ubuntu13.1.7 0 500 http://archive.ubuntu.com//ubuntu/ trusty-security/main amd64 Packages 1.2.2-0ubuntu13 0 500 http://archive.ubuntu.com//ubuntu/ trusty/main amd64 Packages When I tried on a system with 1.2.2-0ubuntu13.1.7, there was no issue starting the container. If this is an issue with the version in the cloud archives, when was it fixed and when does the fix makes it to the kilo and liberty cloud archives? Below is the error on the nova-compute node with actual instance xml and I also recreated with a basic container: root@lambert:~# virsh -c lxc:/// dumpxml instance-0001 instance-0001 9d5ecebb-f387-4eb7-b337-c1a47589094b http://openstack.org/xmlns/libvirt/nova/1.0";> guestOS-test-lxc-precise_0 2015-12-09 11:12:13 2048 20 0 0 1 admin admin 2097152 1 1024 exe /sbin/init console=tty0 console=ttyS0 console=ttyAMA0 destroy restart destroy /usr/lib/libvirt/libvirt_lxc [583/1825] root@lambert:~# virsh -c lxc:/// start instance-0001 error: Failed to start domain instance-0001 error: internal error: Unable to find 'cpuacct' cgroups controller mount root@lambert:~# virsh -c lxc:/// dumpxml myinstance myinstance 704269a9-d9ae-49eb-ae5e-1222fd703872 102400 102400 1 exe /bin/sh destroy restart destroy /usr/lib/libvirt/libvirt_lxc root@lambert:~# virsh -c lxc:/// start myinstance error: Failed to start domain myinstance error: internal error: Unable to find 'cpuacct' cgroups controller mount ** Affects: cloud-archive Importance: Undecided Status: New ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: oil ** Also affects: cloud-archive Importance: Undecided Status: New ** Summary changed: - Failure to start lxc container - internal error: Unable to find 'cpuacct' cgroups controller mount + virsh failure to start lxc container - internal error: Unable to find 'cpuacct' cgroups controller mount -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524339 Title: virsh failure to start lxc container - internal error: Unable to find 'cpuacct' cgroups controller mount To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1524339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429739] Re: neutron-server does not start: OperationalError: (OperationalError) no such table: ml2_vlan_allocations
I was able to recreate. The errors are same on the retry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429739 Title: neutron-server does not start: OperationalError: (OperationalError) no such table: ml2_vlan_allocations To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1429739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429739] Re: neutron-server does not start: OperationalError: (OperationalError) no such table: ml2_vlan_allocations
Attaching /var/log/neutron/server.log ** Attachment added: "server.log.gz" https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1429739/+attachment/4517291/+files/server.log.gz ** Tags added: oil -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429739 Title: neutron-server does not start: OperationalError: (OperationalError) no such table: ml2_vlan_allocations To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1429739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429739] Re: neutron-server does not start: OperationalError: (OperationalError) no such table: ml2_vlan_allocations
I hit similar issue in trusty. The following error is repeated multiple
times in server.log:
2015-11-11 20:20:40.238 9354 TRACE neutron File
"/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 436, in
do_execute
2015-11-11 20:20:40.238 9354 TRACE neutron cursor.execute(statement,
parameters)
2015-11-11 20:20:40.238 9354 TRACE neutron OperationalError: (OperationalError)
no such table: ml2_vlan_allocations u'SELECT
ml2_vlan_allocations.physical_network AS ml2_vlan_allocations
_physical_network, ml2_vlan_allocations.vlan_id AS
ml2_vlan_allocations_vlan_id, ml2_vlan_allocations.allocated AS
ml2_vlan_allocations_allocated \nFROM ml2_vlan_allocations' ()
2015-11-11 20:20:40.238 9354 TRACE neutron
2015-11-11 20:20:41.166 9371 ERROR neutron.service [-] Unrecoverable error:
please check log for details.
2015-11-11 20:20:41.166 9371 TRACE neutron.service Traceback (most recent call
last):
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/neutron/service.py", line 102, in serve_wsgi
2015-11-11 20:20:41.166 9371 TRACE neutron.service service.start()
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/neutron/service.py", line 73, in start
2015-11-11 20:20:41.166 9371 TRACE neutron.service self.wsgi_app =
_run_wsgi(self.app_name)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/neutron/service.py", line 168, in _run_wsgi
2015-11-11 20:20:41.166 9371 TRACE neutron.service app =
config.load_paste_app(app_name)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/neutron/common/config.py", line 183, in
load_paste_app
2015-11-11 20:20:41.166 9371 TRACE neutron.service app =
deploy.loadapp("config:%s" % config_path, name=app_name)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 247, in
loadapp
2015-11-11 20:20:41.166 9371 TRACE neutron.service return loadobj(APP, uri,
name=name, **kw)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 272, in
loadobj
2015-11-11 20:20:41.166 9371 TRACE neutron.service return context.create()
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in create
2015-11-11 20:20:41.166 9371 TRACE neutron.service return
self.object_type.invoke(self)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 144, in invoke
2015-11-11 20:20:41.166 9371 TRACE neutron.service **context.local_conf)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in fix_call
2015-11-11 20:20:41.166 9371 TRACE neutron.service val = callable(*args,
**kw)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/urlmap.py", line 28, in urlmap_factory
2015-11-11 20:20:41.166 9371 TRACE neutron.service app =
loader.get_app(app_name, global_conf=global_conf)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 350, in
get_app
2015-11-11 20:20:41.166 9371 TRACE neutron.service name=name,
global_conf=global_conf).create()
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in create
2015-11-11 20:20:41.166 9371 TRACE neutron.service return
self.object_type.invoke(self)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 144, in invoke
2015-11-11 20:20:41.166 9371 TRACE neutron.service **context.local_conf)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in fix_call
2015-11-11 20:20:41.166 9371 TRACE neutron.service val = callable(*args,
**kw)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/neutron/auth.py", line 71, in pipeline_factory
2015-11-11 20:20:41.166 9371 TRACE neutron.service app =
loader.get_app(pipeline[-1])
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 350, in
get_app
2015-11-11 20:20:41.166 9371 TRACE neutron.service name=name,
global_conf=global_conf).create()
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in create
2015-11-11 20:20:41.166 9371 TRACE neutron.service return
self.object_type.invoke(self)
2015-11-11 20:20:41.166 9371 TRACE neutron.service File
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 146, i
[Bug 1498669] [NEW] config-changed nvp.NVPInteractionError: Unable to create transport node: Create transport node failed: Entity '' not registered
Public bug reported:
This is for OpenStack deployment with these parameters:
++ export OPENSTACK_RELEASE=icehouse
++ OPENSTACK_RELEASE=icehouse
++ export COMPUTE=nova-kvm
++ COMPUTE=nova-kvm
++ export BLOCK_STORAGE=cinder-iscsi
++ BLOCK_STORAGE=cinder-iscsi
++ export IMAGE_STORAGE=glance-swift
++ IMAGE_STORAGE=glance-swift
++ export PIPELINE_ID=ec2ea05a-0b20-4915-9399-0b25c8e80c30
++ PIPELINE_ID=ec2ea05a-0b20-4915-9399-0b25c8e80c30
++ export BACKEND_DATABASE=galera-cluster
++ BACKEND_DATABASE=galera-cluster
++ export NETWORKING=neutron-nsx
++ NETWORKING=neutron-nsx
++ export UBUNTU_RELEASE=trusty
++ UBUNTU_RELEASE=trusty
>From unit log file:
ar/lib/juju/agents/unit-nvp-transport-node-0/charm"
2015-09-22 21:02:25 INFO worker.uniter.jujuc server.go:158 running hook tool
"juju-log" ["Creating bridge br-int"]
2015-09-22 21:02:25 DEBUG worker.uniter.jujuc server.go:159 hook context id
"nvp-transport-node/0-config-changed-3917353472212443775"; dir
"/var/lib/juju/agents/unit-nvp-transport-node-0/charm"
2015-09-22 21:02:25 INFO juju-log Creating bridge br-int
2015-09-22 21:02:26 INFO worker.uniter.jujuc server.go:158 running hook tool
"unit-get" ["--format=json" "private-address"]
2015-09-22 21:02:26 DEBUG worker.uniter.jujuc server.go:159 hook context id
"nvp-transport-node/0-config-changed-3917353472212443775"; dir
"/var/lib/juju/agents/unit-nvp-transport-node-0/charm"
2015-09-22 21:02:26 INFO worker.uniter.jujuc server.go:158 running hook tool
"juju-log" ["Reading ovs certificate from /etc/openvswitch/ovsclient-cert.pem"]
2015-09-22 21:02:26 DEBUG worker.uniter.jujuc server.go:159 hook context id
"nvp-transport-node/0-config-changed-3917353472212443775"; dir
"/var/lib/juju/agents/unit-nvp-transport-node-0/charm"
2015-09-22 21:02:26 INFO juju-log Reading ovs certificate from
/etc/openvswitch/ovsclient-cert.pem
2015-09-22 21:02:26 INFO config-changed Traceback (most recent call last):
2015-09-22 21:02:26 INFO config-changed File
"/var/lib/juju/agents/unit-nvp-transport-node-0/charm/hooks/config-changed",
line 96, in
2015-09-22 21:02:26 INFO config-changed hooks.execute(sys.argv)
2015-09-22 21:02:26 INFO config-changed File
"/var/lib/juju/agents/unit-nvp-transport-node-0/charm/hooks/charmhelpers/core/hookenv.py",
line 478, in execute
2015-09-22 21:02:26 INFO config-changed self._hooks[hook_name]()
2015-09-22 21:02:26 INFO config-changed File
"/var/lib/juju/agents/unit-nvp-transport-node-0/charm/hooks/config-changed",
line 82, in config_changed
2015-09-22 21:02:26 INFO config-changed config('integration-bridge'))
2015-09-22 21:02:26 INFO config-changed File
"/var/lib/juju/agents/unit-nvp-transport-node-0/charm/hooks/nvp.py", line 73,
in create_transport_node
2015-09-22 21:02:26 INFO config-changed .format(response.text))
2015-09-22 21:02:26 INFO config-changed nvp.NVPInteractionError: Unable to
create transport node: Create transport node failed: Entity
'28a44ef7-8620-41c9-bc3e-f1df8eb1aab3' not registered.
2015-09-22 21:02:26 INFO juju.worker.uniter.context context.go:543 handling
reboot
2015-09-22 21:02:26 ERROR juju.worker.uniter.operation runhook.go:103 hook
"config-changed" failed: exit status 1
2015-09-22 21:02:26 DEBUG juju.worker.uniter modes.go:31 [AGENT-STATUS] failed:
run config-changed hook
2015-09-22 21:02:26 INFO juju.worker.uniter modes.go:543 ModeAbide exiting
2015-09-22 21:02:26 INFO juju.worker.uniter modes.go:541 ModeHookError starting
2015-09-22 21:02:26 DEBUG juju.worker.uniter.filter filter.go:597 want resolved
event
2015-09-22 21:02:26 DEBUG juju.worker.uniter.filter filter.go:591 want forced
upgrade true
2015-09-22 21:02:26 DEBUG juju.worker.uniter.filter filter.go:727 no new charm
event
2015-09-22 21:02:26 DEBUG juju.worker.uniter modes.go:31 [AGENT-STATUS] error:
hook failed: "config-changed"
I didn't see any issue with the NSX controller at first glance.
** Affects: nsx-transport-node (Ubuntu)
Importance: Undecided
Status: New
** Affects: nvp-transport-node (Juju Charms Collection)
Importance: Undecided
Status: New
** Tags: oil
** Package changed: charms => nvp-transport-node (Juju Charms
Collection)
** Also affects: nsx-transport-node (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498669
Title:
config-changed nvp.NVPInteractionError: Unable to create transport
node: Create transport node failed: Entity '' not
registered
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nsx-transport-node/+bug/1498669/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492298] Re: config-changed: nvp.NVPInteractionError: Unable to retrieve transport nodes - 503 Service Unavailable
This bug is invalid. The issue was due to an issue with the NSX control cluster which will be tracked through a separate bug. ** Changed in: charms Status: New => Invalid ** Changed in: nsx-transport-node (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492298 Title: config-changed: nvp.NVPInteractionError: Unable to retrieve transport nodes - 503 Service Unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nsx-transport-node/+bug/1492298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492298] Re: config-changed: nvp.NVPInteractionError: Unable to retrieve transport nodes - 503 Service Unavailable
bundle file ** Attachment added: "bundle.tar.gz" https://bugs.launchpad.net/charms/+bug/1492298/+attachment/4457343/+files/bundle.tar.gz ** Also affects: nsx-transport-node (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492298 Title: config-changed: nvp.NVPInteractionError: Unable to retrieve transport nodes - 503 Service Unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nsx-transport-node/+bug/1492298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel
Steve, here is the output with the -t flags: ubuntu@pullman-01:~$ sudo strace -t -o process_dump -ff /usr/sbin/grub-probe --device /dev/sda1 --target=fs sudo: unable to resolve host pullman-01 ext2 ubuntu@pullman-01:~$ sudo strace -t -o process_dump -ff /usr/sbin/grub-probe --device /dev/sda1 --target=fs_uuid sudo: unable to resolve host pullman-01 d1617fb9-47e7-4a90-a65f-a5cb5d20b72a ** Attachment added: "strace-timestamp-grub-probe.tar.gz" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+attachment/4423000/+files/strace-timestamp-grub-probe.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel
Attached is the strace output for running: root@pullman-01:~/fs# strace -o process_dump -ff /usr/sbin/grub-probe --device /dev/sda1 --target=fs ext2 root@pullman-01:~/fs_uuid# strace -o process_dump -ff /usr/sbin/grub-probe --device /dev/sda1 --target=fs_uuid 61e97f71-41bd-432d-97b7-e86826f8a81d root@pullman-01:~/fs_uuid# Both command seemed to take as long to complete (as when I monitored through ps -ef).. I timed one of these commands to take as long as 50 seconds. ** Attachment added: "strace-grub-probe.tar.gz" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+attachment/4420929/+files/strace-grub-probe.tar.gz ** Changed in: grub2 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory
Stefan, it's ubuntu@sirrush:~$ uname -a Linux sirrush 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached is output of dpkg -l ** Attachment added: "dpkg-curtin-trusty.txt" https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+attachment/4420011/+files/dpkg-curtin-trusty.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464442 Title: installing or upgrading libc6 in Trusty removes all content from /tmp directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory
Brad, one additional bit of info: it is through ssh that I am able to access the environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464442 Title: installing or upgrading libc6 in Trusty removes all content from /tmp directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory
Brad, I need some clarification on the apport-collect script. The curtin environment is a very limited installation environment and when I ran apport-collect, it was attempting to open a socket but never returned. AFAICT, it needs to open a browser to allow user to authenticate through a browser, but I don't see a way for me to do it that way since there's no browser. Is it possible for the tool to collect this data offline then use the apport-collect to post the data from another system from which I can authenticate from? If so, can you please share the steps? Seth, we haven't recreated this without MAAS but we think that this should re-creatable in any environment with an overlay root... You could try with a LiveCD for example. Once inside the environment, then you would verify content of /tmp then run "sudo apt-get update && sudo apt- get install libc6" assuming that the libc6 version in the archive is newer. If the content of /tmp is empty, then issue was successfully recreated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464442 Title: installing or upgrading libc6 in Trusty removes all content from /tmp directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel
attached lshw for the 2 systems. ** Attachment added: "lshw.tar.gz" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+attachment/4418945/+files/lshw.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel
I meant to set it to new for the previous data in comment #7 to be analyzed. The issue itself is still very reproducible. I was just noting that we failed to recreate on another system which were able to access today. However, the 2 systems are not fully identical. For the system that fails, the disks are ST300MM0006 300GB drives. For the new system which deployed Precise, the disks are WD3001BKHG-33D1 drives. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel
We tried recreated today with a similar Cisco UCS 260 server and it deployed Precise ok with hwe-t kernel; we did not observe any issue with grub. ** Changed in: grub2 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel
After perhaps 20 minutes or so, it's able to go on and the memtest completes, but some processes still remains: + fs_uuid=d729740f-7516-4530-80fc-a7d77bfe2bde + echo search --no-floppy --fs-uuid --set=root d729740f-7516-4530-80fc-a7d77bfe2bde + [ x != x ] + prepare_boot_cache= insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d729740f-7516-4530-80fc-a7d77bfe2bde + test -e /boot/memtest86+.bin + make_system_path_relative_to_its_root /boot/memtest86+.bin + /usr/bin/grub-mkrelpath /boot/memtest86+.bin + MEMTESTPATH=/boot/memtest86+.bin + echo Found memtest86+ image: /boot/memtest86+.bin Found memtest86+ image: /boot/memtest86+.bin + cat + printf %s\n insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d729740f-7516-4530-80fc-a7d77bfe2bde + cat + printf %s\n insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d729740f-7516-4530-80fc-a7d77bfe2bde + cat done Setting up linux-image-generic-lts-trusty (3.13.0.55.48) ... Setting up linux-headers-3.13.0-55 (3.13.0-55.94~precise1) ... Setting up linux-headers-3.13.0-55-generic (3.13.0-55.94~precise1) ... Setting up linux-headers-generic-lts-trusty (3.13.0.55.48) ... Setting up linux-generic-lts-trusty (3.13.0.55.48) ... Leaving 'diversion of /etc/init/ureadahead.conf to /etc/init/ureadahead.conf.disabled by cloud-init' 8192+0 records in 8192+0 records out 8589934592 bytes (8.6 GB) copied, 6.31303 s, 1.4 GB/s Before /usr/sbin/grub-probe --device /dev/sda1 --target=fs_uuid completes: root@pullman-01:/tmp/tmpO24sZq/target/etc/grub.d# ps -ef|grep grub root 12328 2588 0 19:01 ?00:00:00 /bin/sh /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg root 12703 12328 0 19:13 ?00:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 12714 12703 0 19:13 ?00:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 12715 12714 0 19:13 ?00:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 12748 12715 30 19:16 ?00:00:09 /usr/sbin/grub-probe --device /dev/sda1 --target=fs_uuid root 12759 12361 0 19:17 pts/000:00:00 grep --color=auto grub After: root@pullman-01:~# ps -ef|grep grub root 12931 2425 0 19:18 ?00:00:00 /bin/bash /curtin/helpers/install-grub /tmp/tmpO24sZq/target /dev/sda root 12938 12931 0 19:18 ?00:00:00 sh -ec ?pkg=$1; shift;?dpkg-reconfigure "$pkg"?update-grub? for d in "$@"; do grub-install "$d" || exit; done -- grub-pc /dev/sda root 12939 12938 0 19:18 ?00:00:00 /usr/bin/perl -w /usr/sbin/dpkg-reconfigure grub-pc root 12950 12939 0 19:18 ?00:00:00 /bin/bash /var/lib/dpkg/info/grub-pc.postinst configure 1.99-21ubuntu3.17 root 13312 12950 0 19:20 ?00:00:00 /bin/sh /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg root 13356 13312 27 19:23 ?00:00:13 /usr/sbin/grub-probe --device /dev/sda1 --target=fs_uuid root 13363 12361 0 19:24 pts/000:00:00 grep --color=auto grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel
This is the output and looks to be stuck for some time on the last line: update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-55-generic /boot/vmlinuz-3.13.0-55-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-55-generic /boot/vmlinuz-3.13.0-55-generic update-initramfs: Generating /boot/initrd.img-3.13.0-55-generic df: Warning: cannot read table of mounted file systems: No such file or directory run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-55-generic /boot/vmlinuz-3.13.0-55-generic run-parts: executing /etc/kernel/postinst.d/x-grub-legacy-ec2 3.13.0-55-generic /boot/vmlinuz-3.13.0-55-generic Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Ignoring non-Xen Kernel on Xen domU host: vmlinuz-3.2.0-80-generic Found kernel: /boot/vmlinuz-3.13.0-55-generic Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-55-generic /boot/vmlinuz-3.13.0-55-generic Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.13.0-55-generic Found initrd image: /boot/initrd.img-3.13.0-55-generic Found linux image: /boot/vmlinuz-3.2.0-80-generic Found initrd image: /boot/initrd.img-3.2.0-80-generic + [ -f /usr/lib/grub/grub-mkconfig_lib ] + . /usr/lib/grub/grub-mkconfig_lib + transform=s,x,x, + prefix=/usr + exec_prefix=/usr + datarootdir=/usr/share + datadir=/usr/share + bindir=/usr/bin + sbindir=/usr/sbin + echo grub + sed s,x,x, + pkgdatadir=/usr/share/grub + test x = x + echo grub-probe + sed s,x,x, + grub_probe=/usr/sbin/grub-probe + test x = x + echo grub-mkrelpath + sed s,x,x, + grub_mkrelpath=/usr/bin/grub-mkrelpath + which gettext + + gettext=gettext + LX=linux16 + prepare_grub_to_access_device /dev/sda1 + device=/dev/sda1 + loop_file= + sed -e s/^/\t/ + grep -q crypt[[:space:]]$ + dmsetup status /dev/sda1 + /usr/sbin/grub-probe --device /dev/sda1 --target=abstraction + abstraction= + /usr/sbin/grub-probe --device /dev/sda1 --target=partmap + partmap=msdos + echo insmod part_msdos + /usr/sbin/grub-probe --device /dev/sda1 --target=fs + fs=ext2 + echo insmod ext2 + /usr/sbin/grub-probe --device /dev/sda1 --target=drive + echo set root='(hd0,msdos1)' + /usr/sbin/grub-probe --device /dev/sda1 --target=fs_uuid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel
I am trying the set -x step. We don't have 15.10 images on our maas servers, but I will look to see whether we can get it on there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory
I was only able to recreate in curtin environment which has overlay root: $ mount overlayroot on / type overlayfs (rw,lowerdir=/media/root-ro/,upperdir=/media/root-rw/overlay) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) /dev/sdf on /media/root-ro type ext4 (ro) tmpfs-root on /media/root-rw type tmpfs (rw,relatime) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,relatime,name=systemd) Attached are process_dump files for strace -o process_dump -ff apt-get install libc6 ** Attachment added: "strace_process_dump_ff_files.tar.gz" https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+attachment/4413545/+files/strace_process_dump_ff_files.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464442 Title: installing or upgrading libc6 in Trusty removes all content from /tmp directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464442] [NEW] installing or upgrading libc6 in Trusty removes all content from /tmp directory
Public bug reported: We are seeing an issue with installation of dkms package during a curtin installation which ends up with /tmp directory being wiped clean. This is very bad for curtin as it saves critical installation files in /tmp. It turns out that it's the of upgrading libc6, which is triggered as a result of installing dependencies, that removes content of /tmp. For example, installation of gcc results in the same result since it ends up with libc6 being upgraded. The only way that this won't be recreated is if the latest libc6 is already installed. This problem does not exist in precise. It can also be recreated by installing the .deb file for any version in trusty including 2.17. ubuntu@host:~$ ls /tmp tmpHHbRkP ubuntu@sirrush:~$ sudo apt-get install libc6 sudo: unable to resolve host sirrush Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libc-dev-bin libc6-dev Suggested packages: glibc-doc Recommended packages: manpages-dev The following packages will be upgraded: libc-dev-bin libc6 libc6-dev 3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded. Need to get 6,714 kB of archives. After this operation, 6,144 B disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 2.19-0ubuntu6.6 [1,910 kB] Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc-dev-bin amd64 2.19-0ubuntu6.6 [68.9 kB] Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6 amd64 2.19-0ubuntu6.6 [4,735 kB] Fetched 6,714 kB in 0s (18.5 MB/s) Preconfiguring packages ... (Reading database ... 57798 files and directories currently installed.) Preparing to unpack .../libc6-dev_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc6-dev:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Preparing to unpack .../libc-dev-bin_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc-dev-bin (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Preparing to unpack .../libc6_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc6:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up libc6:amd64 (2.19-0ubuntu6.6) ... Setting up libc-dev-bin (2.19-0ubuntu6.6) ... Setting up libc6-dev:amd64 (2.19-0ubuntu6.6) ... Processing triggers for libc-bin (2.19-0ubuntu6.3) ... ubuntu@host:~$ ls /tmp ubuntu@host:~$ This is very recreatable. ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Tags: oil ** Summary changed: - installing or upgrading libc6 removes all content from /tmp directory + installing or upgrading libc6 in Trusty removes all content from /tmp directory ** Description changed: We are seeing an issue with installation of dkms package during a curtin - installation ends up removing content of /tmp directory which is very - bad for curtin as it saves file in /tmp for the installation. It turns - out that it's the of upgrading libc6, which is triggered as a result of - installing dependencies, that removes content of /tmp. For example, - installation of gcc results in the same result. The only way that this - won't be recreated is if the latest libc6 is already installed. + installation which ends up with /tmp directory being wiped clean. This + is very bad for curtin as it saves critical installation files in /tmp. + + It turns out that it's the of upgrading libc6, which is triggered as a + result of installing dependencies, that removes content of /tmp. For + example, installation of gcc results in the same result since it ends up + with libc6 being upgraded. The only way that this won't be recreated is + if the latest libc6 is already installed. This problem does not exist in precise. It can also be recreated by installing the .deb file for any version in trusty including 2.17. ubuntu@host:~$ ls /tmp tmpHHbRkP ubuntu@sirrush:~$ sudo apt-get install libc6 sudo: unable to resolve host sirrush Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following extra packages will be installed: - libc-dev-bin libc6-dev + libc-dev-bin libc6-dev Suggested packages: - glibc-doc + glibc-doc Recommended packages: - manpages-dev + manpages-dev The following packages will be upgraded: - libc-dev-bin libc6 libc6-dev + libc-dev-bin libc6 libc6-dev 3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded. Need to get 6,714 kB of archives. After this operation, 6,144 B disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 2.19-0ubuntu6.6 [1,910 kB] Get:2 http://
[Bug 1463046] Re: installation of multipath-tools-boot can break boot
** Tags added: oil -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463046 Title: installation of multipath-tools-boot can break boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1463046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub does not complete for deployment of Precise with hwe-t kernel and Cisco UCS B260 servers
Using the same cisco system, I deployed trusty. I then installed a package and installation of the package around the same location. I then found that it was hanging in grub-probe. I kill that process a couple of times and the installation proceeded and completed afterwards. The Killed message showed that it was the right grub-probe process that I killed. ubuntu@pullman-01:~$ ps -ef|grep grub root 48137 48120 0 20:09 pts/200:00:00 /bin/sh /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg root 48436 48137 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48447 48436 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48448 48447 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48455 48448 30 20:22 pts/200:00:13 /usr/sbin/grub-probe --device /dev/sda1 --target=partmap ubuntu 48742 48643 0 20:23 pts/400:00:00 grep --color=auto grub ubuntu@pullman-01:~$ sudo kill -9 48455 kill: No such process ubuntu@pullman-01:~$ ps -ef|grep grub root 48137 48120 0 20:09 pts/200:00:00 /bin/sh /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg root 48436 48137 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48447 48436 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48448 48447 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48747 48448 22 20:24 pts/200:00:04 /usr/sbin/grub-probe --device /dev/sda1 --target=drive ubuntu 48751 48643 0 20:24 pts/400:00:00 grep --color=auto grub ubuntu@pullman-01:~$ ps -ef|grep grub root 48137 48120 0 20:09 pts/200:00:00 /bin/sh /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg root 48436 48137 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48447 48436 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48448 48447 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48747 48448 29 20:24 pts/200:00:06 /usr/sbin/grub-probe --device /dev/sda1 --target=drive ubuntu 48753 48643 0 20:24 pts/400:00:00 grep --color=auto grub ubuntu@pullman-01:~$ ps -ef|grep grub root 48137 48120 0 20:09 pts/200:00:00 /bin/sh /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg root 48436 48137 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48447 48436 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48448 48447 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48747 48448 32 20:24 pts/200:00:10 /usr/sbin/grub-probe --device /dev/sda1 --target=drive ubuntu 48756 48643 0 20:24 pts/400:00:00 grep --color=auto grub ubuntu@pullman-01:~$ sudo kill -9 48747 ubuntu@pullman-01:~$ ps -ef|grep grub root 48137 48120 0 20:09 pts/200:00:00 /bin/sh /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg root 48436 48137 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48447 48436 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48448 48447 0 20:21 pts/200:00:00 /bin/sh /etc/grub.d/20_memtest86+ root 48759 48448 18 20:24 pts/200:00:00 /usr/sbin/grub-probe --device /dev/sda1 --target=fs_uuid ubuntu 48761 48643 0 20:24 pts/400:00:00 grep --color=auto grub ubuntu@pullman-01:~$ sudo kill -9 48759 On the installation window, the installation proceeds to completion: update-alternatives: using /usr/share/images/desktop-base/spacefun-wallpaper.svg to provide /usr/share/images/desktop-base/desktop-background (desktop-background) in auto mode. update-alternatives: using /usr/share/images/desktop-base/spacefun-splash.svg to provide /usr/share/images/desktop-base/desktop-splash (desktop-splash) in auto mode. update-alternatives: using /usr/share/images/desktop-base/spacefun-grub.png to provide /usr/share/images/desktop-base/desktop-grub.png (desktop-grub) in auto mode. Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.13.0-52-generic Found initrd image: /boot/initrd.img-3.13.0-52-generic Found linux image: /boot/vmlinuz-3.2.0-80-generic Found initrd image: /boot/initrd.img-3.2.0-80-generic Killed Killed Found memtest86+ image: /boot/memtest86+.bin done update-initramfs: deferring update (trigger activated) Setting up libxfce4util-common (4.8.2-1) ... Setting up libxfce4util4 (4.8.2-1) ... Setting up libexo-common (0.6.2-4) ... Setting up libexo-helpers (0.6.2-4) ... ... Setting up miscfiles (1.4.2.dfsg.1-9) ... Ignoring install-info called from maintainer script The package miscfiles should be rebuilt with new debhelper to get trigger support Ignoring install-info called from maintainer script The package miscfiles should be rebuilt with new debhelper to get trigger support
[Bug 1455268] Re: update-grub does not complete for deployment of Precise with hwe-t kernel and Cisco UCS B260 servers
correction: installation of the package around the same location --> installation of the package stalled at around the same location ** Summary changed: - update-grub does not complete for deployment of Precise with hwe-t kernel and Cisco UCS B260 servers + update-grub (grub-probe) during package installation on Cisco UCS B260 servers ** Summary changed: - update-grub (grub-probe) during package installation on Cisco UCS B260 servers + update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455268] Re: update-grub does not complete for deployment of Precise with hwe-t kernel and Cisco UCS B260 servers
** Project changed: curtin => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455268 Title: update-grub does not complete for deployment of Precise with hwe-t kernel and Cisco UCS B260 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
This was the test case: 1) Update trusty daily root-tgz image with a copy of dcap and cap properties. 2) Sync image to cache 3) Deploy a node with trusty 4) Access deployed node 5) Ensure that cap properties for the new file are preserved on deployed system. This test passed. Here are test details: == 1) Update image root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# ls -l usr/bin/dpkgcap -rwxr-xr-x 1 root root 261840 Dec 17 09:33 usr/bin/dpkgcap root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# getcap usr/bin/dpkgcap usr/bin/dpkgcap = cap_net_raw+p root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# tar --xattrs '--xattrs-include=*' -czf root.tar.gz * tar: root.tar.gz: file changed as we read it 2) Sync image root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# ls -l total 550812 drwxr-xr-x 2 root root 4096 Dec 17 02:54 bin drwxr-xr-x 3 root root 4096 Dec 8 14:34 boot drwxr-xr-x 6 root root 4096 Dec 8 14:34 dev drwxr-xr-x 96 root root 4096 Dec 17 02:56 etc drwxr-xr-x 2 root root 4096 Apr 10 2014 home lrwxrwxrwx 1 root root33 Dec 8 14:33 initrd.img -> boot/initrd.img-3.13.0-40-generic drwxr-xr-x 22 root root 4096 Dec 8 14:31 lib drwxr-xr-x 2 root root 4096 Dec 4 18:40 lib64 drwx-- 2 root root 4096 Dec 4 18:43 lost+found drwxr-xr-x 2 root root 4096 Dec 4 18:40 media drwxr-xr-x 2 root root 4096 Apr 10 2014 mnt drwxr-xr-x 2 root root 4096 Dec 4 18:40 opt drwxr-xr-x 2 root root 4096 Apr 10 2014 proc drwx-- 2 root root 4096 Dec 17 02:05 root -rw-r--r-- 1 root root 563942052 Dec 17 09:40 root.tar.gz drwxr-xr-x 4 root root 4096 Dec 8 14:33 run drwxr-xr-x 2 root root 4096 Dec 17 02:54 sbin drwxr-xr-x 2 root root 4096 Dec 4 18:40 srv drwxr-xr-x 2 root root 4096 Mar 12 2014 sys drwxrwxrwt 4 root root 4096 Dec 17 02:55 tmp drwxr-xr-x 10 root root 4096 Dec 4 18:40 usr drwxr-xr-x 12 root root 4096 Dec 4 18:43 var lrwxrwxrwx 1 root root30 Dec 8 14:33 vmlinuz -> boot/vmlinuz-3.13.0-40-generic root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# ls -l ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 -rw-r--r-- 1 root root 424884409 Dec 17 03:28 ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# cp root.tar.gz ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# ls -l ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 -rw-r--r-- 1 root root 563942052 Dec 17 09:42 ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# service tgt restart tgt stop/waiting tgt start/running, process 16692 root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# cp ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 ../../current/ubuntu/amd64/generic/trusty/daily/root-tgz root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# sync;sync root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# exit logout 3) Deploy node from maas 4) Access deployed node lmic@ubuntumaas:/var/lib/maas/boot-resources/cache/root$ ssh 192.168.224.100 @@@ @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is 5b:1b:de:c3:ff:d6:e5:64:3c:b7:be:19:55:69:b5:7e. Please contact your system administrator. Add correct host key in /home/lmic/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /home/lmic/.ssh/known_hosts:20 remove with: ssh-keygen -f "/home/lmic/.ssh/known_hosts" -R 192.168.224.100 ECDSA host key for 192.168.224.100 has changed and you have requested strict checking. Host key verification failed. lmic@ubuntumaas:/var/lib/maas/boot-resources/cache/root$ ssh-keygen -f "/home/lmic/.ssh/known_hosts" -R 192.168.224.100 # Host 192.168.224.100 found: line 20 type ECDSA /home/lmic/.ssh/known_hosts updated. Original contents retained as /home/lmic/.ssh/known_hosts.old lmic@ubuntumaas:/var/lib/maas/boot-resources/cache/root$ ssh 192.168.224.100 The authenticity of host '192.168.224.100 (192.168.224.100)' can't be established. ECDSA key fingerprint is 5b:1b:de:c3:ff:d6:e5:64:3c:b7:be:19:55:69:b5:7e. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.224.100' (ECDSA) to the list of known hosts. Permission denied (publickey). lmic@ubuntumaas:/var/lib/maas/boo
[Bug 1370249] Re: 'ascii' codec can't decode byte 0xc3 in position 19027: ordinal not in range(128) (curtin can't handle non-ascii characters in dpkg --list output)
I verified this for trusty deployment with maas 1.7.0+bzr3299-0ubuntu3~trusty1 and curtin version was 0.1.0~bzr195-0ubuntu1~14.04.1~ppa0. The steps to test this was to edit the root-tgz after uncompressing and extracting it, doing a chroot. I then did a sudo apt-get install deja- dup-backend-gvfs which also installed deja-dup and fonts-dejavu-core. The non-ascii characters were in description for deja-dup-backend-gvfs: Remote server support for Déjà Dup. After exiting, I then recreated the compressed tgz image from the modified files and copied the file to cached filename in /var/lib/maas/boot-resources/cache, and to root-tgz file in /var/lib/maas/boot- resources/current/ubuntu/amd64/generic/trusty/daily. Finally, I restarted tgt. I then deployed trusty through maas which worked. The 2nd test was to do a juju bootstrap which also passed. To make sure that I was dealing with the right image, I verified that the deja-up packages were installed on the deployed node. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370249 Title: 'ascii' codec can't decode byte 0xc3 in position 19027: ordinal not in range(128) (curtin can't handle non-ascii characters in dpkg --list output) To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1370249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370249] Re: 'ascii' codec can't decode byte 0xc3 in position 19027: ordinal not in range(128) (curtin can't handle non-ascii characters in dpkg --list output)
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370249 Title: 'ascii' codec can't decode byte 0xc3 in position 19027: ordinal not in range(128) (curtin can't handle non-ascii characters in dpkg --list output) To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1370249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391354] Re: Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more
I tested this by installing systemd from Proposed onto image then doing update-initramfs -u. I still saw the issue. ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391354 Title: Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1391354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391354] Re: Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more
Brian, will we be able to pull this fix from the daily images? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391354 Title: Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1391354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
