failed to deploy with Xenial image

Bug #1598364 reported by Mian
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
Critical
Unassigned

Bug Description

MAAS Server:

Ubuntu: 14.04.4 LTS
Mass: 1.7.6+bzr3376-0ubuntu3~14.04.1
Boot images: 16.04 LTS / 14.04 LTS

Use Juju to create a machine with xenial series:
juju --debug deploy --constraints tags=test cs:xenial/ubuntu test

When deploying to a VM with the fast installer, the installer runs normally, succeeds and reboots, as expected. Then the OS starts to boot and gets stuck with what you see in the attached screen shot fast_install_vm.png.
When deploying to a physical server with the fast installer, the installer runs normally, succeeds and reboots, as expected. Then the OS starts to boot and gets stuck with what you see in the attached screen shot fast_install_hw.png, some sort of error about invalid opcodes.

Using the debian installer when deploying to the VM works fine, with the exception that it stop during installation prompting for the device where the boot loader should be installed on (as attached vm_deb_install_boot_loader.png ). The installer continues normally after providing the device, the VM reboots and boots normally and the deployment end successfully.
Similarly for a physical server. The debian installer works fine, except for the boot device prompt as attached hw_deb_install_boot_loader.png, reboots and boots normally, except MAAS says that deployment failed as attached hw_failed_deployment.png and in Juju it states that it's "Waiting for agent initialization to finish". Yet the server is up and running.

Other information:
ii maas 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS server all-in-one metapackage
ii maas-cli 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS command line API tool
ii maas-cluster-controller 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS server cluster controller
ii maas-common 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS server common files
ii maas-dhcp 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS DHCP server
ii maas-dns 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS DNS server
ii maas-proxy 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS Caching Proxy
ii maas-region-controller 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS server complete region controller
ii maas-region-controller-min 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS Server minimum region controller
ii python-django-maas 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS server Django web framework
ii python-maas-client 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS python API client
ii python-maas-provisioningserver 1.7.6+bzr3376-0ubuntu3~14.04.1 all MAAS server provisioning libraries

Revision history for this message
Lee Trager (ltrager) wrote :

I've confirmed Xenail has issues deploying. When using the daily stream to deploy Xenial it deploys but gets stuck at "Booting local disk" on reboot.

Changed in maas:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Andres Rodriguez (andreserl) wrote : Re: [Bug 1598364] [NEW] failed to deploy with Xenial image

Can you please attach a installation log? This should be made available
from the web UI.

On Friday, July 8, 2016, Lee Trager <email address hidden> wrote:

> I've confirmed Xenail has issues deploying. When using the daily stream
> to deploy Xenial it deploys but gets stuck at "Booting local disk" on
> reboot.
>
> ** Changed in: maas
> Status: New => Triaged
>
> ** Changed in: maas
> Importance: Undecided => Critical
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1598364
>
> Title:
> failed to deploy with Xenial image
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1598364/+subscriptions
>

--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

Changed in maas:
status: Triaged → Incomplete
Revision history for this message
Lee Trager (ltrager) wrote :

Looks like MAAS 1.7 is unable to install grub-pc when deploying Xenial.

Lee Trager (ltrager)
Changed in maas:
status: Incomplete → Triaged
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Dear user,

This is an automated message.

We believe this bug report is no longer an issue in the latest version of MAAS. For such reason, we are making this issue as Won't Fix. If you believe this issue is still present in the latest version of MAAS, please re-open this bug report.

Changed in maas:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.