[Bug 1839375] [NEW] Clean Ubuntu Bionic 18.04.2 UEFI Install fail on Samsung SSD 256GB with unknown firmware version on drive.

Public bug reported: Upon installing Bionic clean, Grub failed to install on the SSD. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion:

[Bug 1825425] Re: Upgrade Failure, Ubuntu 18.10 to 19.04

*** This bug is a duplicate of bug 1823004 *** https://bugs.launchpad.net/bugs/1823004 I had it this morning. NetPlan broke my virsh network bridges, so I attempted to upgrade past it. Couldnt catch much of the error, and was running remote SSH, but its the same install-info item. Tried

Re: [Bug 1590799] Re: nfs-kernel-server does not start because of dependency failure

I only hit this when running in a LXD server container. What he is seeing is new. On Oct 27, 2017 6:35 PM, "Rafael David Tinoco" wrote: > Kuba, > > There is some on going discussions regarding how systemd generator uses > existing sysv init scripts and creates

Re: [Bug 1590799] Change of SRU verification policy

Thanks! On Tue, Jun 27, 2017 at 11:24 AM, Łukasz Zemczak <1590...@bugs.launchpad.net > wrote: > As part of a recent change in the Stable Release Update verification > policy we would like to inform that for a bug to be considered verified > for a given release a verification-done-$RELEASE tag

[Bug 1607971] Re: [juju 2.0 ] cannot remove or destroy machine in pending state

I have the same issue on: 2.2-beta1-xenial-amd64 juju remove-machine juju remove-unit Machines are in various states (some are even deleted on LXC) and the commands succeed, but the units/machines are still listed. root@ayana-angel:~# juju status ModelController Cloud/Region

[Bug 1389811] Re: tgtadm: out of memory crash

Now that I am on the dev branch, the TGT service works great. Unfortunately now that I am on the dev branch, it is unable to determine the correct IP address for the controller during node discovery, and if you set up a new machine entry in MaaS for it using its MAC address, it ignores the ACTUAL

[Bug 1389811] Re: tgtadm: out of memory crash

I rolled both devices to the dev branch and this issue seems to be resolved. RPi 3B region: MAAS Version 2.2.0 (beta2+bzr5717) NUC rack: MAAS Version 2.2.0 (beta2+bzr5717) While I am ecstatic that this is also working now, I am deeply concerned that none of the Ubuntu "stable" stack is

[Bug 1389811] Re: tgtadm: out of memory crash

Same problem when running maas-rack controller on a second machine: Intel NUC 5i5MYHE RACK CONTROLLER: /var/lib/maas/maas.log Feb 15 19:58:13 rack2-maas-rack0 maas.import-images: [info] Updating boot image iSCSI targets. Feb 15 19:58:13 rack2-maas-rack0 maas.boot_image_download_service: [error]

[Bug 1389811] Re: tgtadm: out of memory crash

Same issue, but on RPi3B Not sure if it should even be able to run or if this qualifies as a bug since memory is so scarce on these: tgtadm: out of memory root@juju-rack2:/var/log/maas# cat /etc/issue Ubuntu 16.04.1 LTS \n \l root@juju-rack2:/var/log/maas# uname -a Linux

[Bug 1559088] Re: [Xenial 2.0] tgt fails to start with tgtadm out of memory error

It looks like Python Twisted is actually taking up most of the resources. Wondering if there is a resource cap that I can force Python to stay under to keep from killing off other services. I suspected Postgres at first but it's definitely Python. ** Attachment removed: "cloud-in-a-box.mp4"

[Bug 1559088] Re: [Xenial 2.0] tgt fails to start with tgtadm out of memory error

Raspberry Pi 3B MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) spyderdyne@juju-rack2:~$ uname -r 4.4.43-v7+ spyderdyne@juju-rack2:~$ cat /etc/issue Ubuntu 16.04.1 LTS \n \l spyderdyne@juju-rack2:~$ dpkg -l tgt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF

[Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

spyderdyne@juju-rack2:~$ service tgt status ‚óè tgt.service - (i)SCSI target daemon Loaded: loaded (/lib/systemd/system/tgt.service; enabled; vendor preset: enabled) Active: deactivating (stop-sigterm) (Result: exit-code) Docs: man:tgtd(8) Process: 5557 ExecStartPost=/usr/sbin/tgt

[Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Image source: maas.io Sync: completed ** Attachment added: "Maas GUI Capture" https://bugs.launchpad.net/maas/+bug/1639202/+attachment/4815666/+files/Screen%20Shot%202017-02-08%20at%209.57.08%20PM.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

This is happening to me on an Intel NUC 5i5MYHE blade on PXE. The error is an iSCSI destination error apparently. Same scenario... Maas version: MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) On node PXE boot console output (sorry, but some of this is cut off on this screen, typing what I can

Re: [Bug 1590799] Re: nfs-kernel-server does not start because of dependency failure

I had this issue when running under an LXD/LXC container. If you need I can deploy it out and test. Just let me know. On Mon, Feb 6, 2017 at 1:00 PM, Rafael David Tinoco < rafael.tin...@canonical.com> wrote: > ** Patch added: "yakkety_nfs-utils_1.2.8-9.2ubuntu2.debdiff" >

[Bug 1560971] Re: after default installation of maas the rack and region controller are not connected

Apparently there was something in my process that caused it to break. After wiping to a clean state, purging everything (sudo dpkg --remove --force-remove-reinstreq maas), and installing again there were no issues. Disregard my comments, nothing to see here. -- You received this bug

[Bug 1560971] Re: after default installation of maas the rack and region controller are not connected

RPC connection failed: info = yield self._fetch_rpc_info(info_url) twisted.web.error.Error: 500 INTERNAL SERVER ERROR 2017-01-19 12:15:59 -: [info] Received SIGTERM, shutting down. 2017-01-19 12:17:20 -: [info] twistd 16.0.0 (/usr/bin/python3 3.5.2) starting up. 2017-01-19 12:17:20 -: [info]

[Bug 1560971] Re: after default installation of maas the rack and region controller are not connected

Same issue on Ubuntu Mate 16.04 ARMHF (Raspberry Pi 3B): VERSIONS root@juju-rack2:~# cat /etc/issue Ubuntu 16.04.1 LTS \n \l root@juju-rack2:~# uname -a Linux juju-rack2.home.spyderdyne.net 4.4.43-v7+ #948 SMP Sun Jan 15 22:20:07 GMT 2017 armv7l armv7l armv7l GNU/Linux MAAS Version

[Bug 1499807] [NEW] vdr-plugin-vnsiserver metapackage from VDR cannot be installed 15.04

Public bug reported: Installed VDR on 15.04 Vivid but am unable to install the vnsiserver metapackage now. The metapackage says it is supplied by VDR or i wouldnt post this here. Apparently vdr-abi2.0.6-debian is not available anywhere. vdr: Installed: 2.2.0-6yavdr0~vivid Candidate:

[Bug 1311939] Re: alsa-driver no HDMI audio on Ubuntu 14.04

Update. So in the Volume Manager settings pane under output devices it shows the device as (Unplugged) and there is no sound. I clicked on the configuration tab, selected Digital Surround 5.1 Output (HDMI) Output and i magically had sound again. My issue was apparently just a failure to

[Bug 1311939] Re: alsa-driver no HDMI audio on Ubuntu 14.04

Same issue. It is only an issue with 14.04 Studio though. Ubuntu 14.04 Trusy was working fine with requgalr Ubuntu desktop but GParted wouldnt work with my RAID setup. Reinstalled with 14.04 server and now the disks are back in order thanks to partman. After server was installed I then