Unable to deploy Bionic on bare-metals with MaaS 2.3.0

Bug #1748875 reported by Po-Hsu Lin
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Unassigned
cloud-images
Invalid
Undecided
Unassigned
maas-images
Fix Released
Undecided
Unassigned

Bug Description

MAAS version: 2.3.0 (6434-gd354690-0ubuntu1~16.04.1)

We cannot deploy Bionic on those bare-metals in the kernel SRU test pool.
(Bionic image imported on the MaaS server)

It looks like virtual machines are working well.

Tried to monitor the output with ipmitool, this is the last thing I could see:
Loading ubuntu/i386/ga-18.04/bionic/daily/boot-kernel... ok
Loading ubuntu/i386/ga-18.04/bionic/daily/boot-initrd...ok

And it timed out in the end.

Related bugs:
 * bug 1750851: re-add cloud-initramfs-dyn-netconf to ubuntu-server

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: maas 2.3.0-6434-gd354690-0ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Mon Feb 12 11:21:49 2018
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in maas (Ubuntu):
status: New → Confirmed
Revision history for this message
Dan Watkins (oddbloke) wrote :

Hi Po-Hsu,

Could you confirm the serial of the image that you are seeing this in? Are you able to test older serials to determine when we started seeing the failure?

Thanks,

Dan

Revision history for this message
Andres Rodriguez (andreserl) wrote :

The image is: 20180210

Changed in maas (Ubuntu):
status: Confirmed → Invalid
information type: Public → Private
information type: Private → Public
Changed in cloud-images:
status: New → Invalid
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

So I think the bug status should be Fix Committed now?

Revision history for this message
Dan Watkins (oddbloke) wrote : Re: [Bug 1748875] Re: Unable to deploy Bionic on bare-metals with MaaS 2.3.0

On Wed, Feb 14, 2018 at 08:13:11AM -0000, Po-Hsu Lin wrote:
> So I think the bug status should be Fix Committed now?

I think this is actually fixed now; can you confirm?

Changed in maas (Ubuntu):
status: Invalid → Fix Committed
status: Fix Committed → Incomplete
no longer affects: maas (Ubuntu)
Changed in maas:
status: New → Fix Committed
milestone: none → 2.4.0alpha1
assignee: nobody → Andres Rodriguez (andreserl)
importance: Undecided → High
no longer affects: maas/2.3
Changed in maas:
status: Fix Committed → Invalid
Changed in maas-images:
status: New → Fix Committed
Changed in maas:
milestone: 2.4.0alpha1 → none
assignee: Andres Rodriguez (andreserl) → nobody
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Hello,
Yes I can deploy Bionic with our MaaS server now!
Thanks!

Dan Watkins (oddbloke)
Changed in maas-images:
status: Fix Committed → Fix Released
Scott Moser (smoser)
description: updated
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.