MAAS

[2.5.0a2] Missing link for lpxelinux.0 means commissioning fails

Bug #1788884 reported by Mark Shuttleworth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Lee Trager
MAAS 2.5.0beta1

Bug Description

I'm unable to commissioning machines with 2.5.0a2 unless I manually add a symlink to lpxelinux.0 such as this:

rwxrwxrwx 1 maas maas 31 Aug 24 15:18 lpxelinux.0 -> bootloader/pxe/i386/lpxelinux.0

With that link added, commissioning proceeds normally.

Tags: track

Related branches

~ltrager/maas:lp1788884
Blake Rouse (community): Approve
MAAS Lander: Approve
Andres Rodriguez (community): Needs Fixing
Diff: 336 lines (+90/-39)
3 files modified
src/provisioningserver/tests/test_plugin.py (+0/-1)
src/provisioningserver/tests/test_upgrade_cluster.py (+56/-20)
src/provisioningserver/upgrade_cluster.py (+34/-18)
Andres Rodriguez (andreserl)
Changed in maas:
milestone: none → 2.5.0beta1
tags: added: track
Changed in maas:
assignee: nobody → Blake Rouse (blake-rouse)
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Mark,

Any chance you can check rackd.log on that machines to see if it fail to update images ? The image update process should automatically create that symlink.

Maybe the other option could be that the update was in progress at the time of the boot?

Revision history for this message
Mark Shuttleworth (sabdfl) wrote : Re: [Bug 1788884] Re: [2.5.0a2] Missing link for lpxelinux.0 means commissioning fails

I think the image sync process had run at least once when I created the
links manually. Are you saying that, if I remove the link, it should be
recreated by syncing images?

Andres Rodriguez (andreserl)
Changed in maas:
assignee: Blake Rouse (blake-rouse) → Lee Trager (ltrager)
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Mark,

Yes, the image syncing process should really be regenerating the symlinks once new images are installed.

That said, I think we have pinned what the issue may be, and it could be that the upgrade doesn't ask the rack controller to ensure that all symlinks are created correctly. However, if MAAS were to update the images, symlinks should be recreated.

Changed in maas:
status: New → Triaged
importance: Undecided → High
Lee Trager (ltrager)
Changed in maas:
status: Triaged → In Progress
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.5.0beta1 → 2.5.0beta2
milestone: 2.5.0beta2 → 2.5.0beta1
MAAS Lander (maas-lander)
Changed in maas:
status: In Progress → Fix Committed
Andres Rodriguez (andreserl)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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