MAAS fails to PXE boot IBM LPAR machine as VM host

Bug #1923516 reported by Bill Wear
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned

Bug Description

>> this is a sample bug to demonstrate how to submit a valid MAAS bug report. marked invalid, please ignore. <<

I'm using snap version/build 3.0.0~beta2-9796-g.2182ab55f.

I tried to create a VM host using a previously discovered IBM LPAR machine, using the MAAS UI.

I was able to select the machine under "Add KVM," define its parameters, and select a project. I was also able to push "Authenticate," and the expected commissioning process began. After the machine powered on, though, the commissioning process timed out trying to PXE boot the machine. Looking at the machine, it had indeed been powered on, but nothing happened after that.

>>Steps to reproduce:
1. Confirm that at least one IBM LPAR 700 model is discovered and in the Ready state (see screenshot-1).

2. Select the KVM tab (see screenshot-2).

3. Press the "Add KVM" button.

4. Select the KVM host type according to your network (I selected "<selection>").

5. Enter a name for the KVM host (I entered "<entered-name>").

6. Enter a bridge address to reach the KVM host (I entered "<power-address>").

7. Enter the appropriate password.

8. Press the "Authenticate" button.

9. On the project screen which pops up, select the "default" project.

10. Press the "Add KVM" button.

11. Return to the machine list and find the machine you just added as a KVM. It should show "Powering on."

12. Watch until the machine enters the "Performing PXE boot" stage.

13. Wait for the machine to time out without reaching "Loading ephemeral" stage, as normal.

14. Examine the logfiles (see attached logfiles).

Revision history for this message
Bill Wear (billwear) wrote :
Changed in maas:
status: New → Invalid
description: updated
Revision history for this message
Bill Wear (billwear) wrote :
Revision history for this message
Bill Wear (billwear) wrote :
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.