MAAS

ipmi-config command not found in snap

Bug #1891331 reported by Nick Niehoff
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Adam Collard
MAAS 2.9.0b1
2.8
Fix Released
Undecided
Adam Collard
MAAS 2.8.3
freeipmi (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When using the MAAS snap (version 2.8.1-8567-g.c4825ca06 rev 7808), the following warning appears in the logs numerous times:

maas.drivers.power.ipmi: [warn] Failed to change the boot order to PXE X.X.X.X: /snap/maas/7808/usr/sbin/ipmi-chassis-config: 15: exec: /usr/sbin/ipmi-config: not found

Investigating the script we find:

exec /usr/sbin/ipmi-config $options

However when in the snap environment (snap run --shell maas) /usr/sbin is not accessible. the ipmi-config is located next to the script at /snap/maas/7808/usr/sbin/ipmi-chassis. The wrapper script should either rely on $PATH and simply use the relative path or should understand it is in a snap and use the full path.

Related branches

~adam-collard/maas:2.8-ipmi-chassis-config-path
MAAS Lander: Approve
Adam Collard (community): Approve
Diff: 13 lines (+2/-0)
1 file modified
snap/snapcraft.yaml (+2/-0)
~adam-collard/maas:ipmi-chassis-config-path
MAAS Lander: Needs Fixing
Lee Trager (community): Approve
Diff: 13 lines (+2/-0)
1 file modified
snap/snapcraft.yaml (+2/-0)
Adam Collard (adam-collard)
Changed in maas:
status: New → In Progress
assignee: nobody → Adam Collard (adam-collard)
milestone: none → 2.9.0b1
importance: Undecided → High
MAAS Lander (maas-lander)
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
Behroz Sikander (behroz89) wrote :

What is the impact of this bug?

My node stays in comissioning status until timeout. Is my problem related to this bug?
Will this fix be backported to 2.8 and available through snap?

Revision history for this message
Paride Legovini (paride) wrote :

Hi,

I don't think there anything to be fixed on the freeipmi package side. I'm marking the task Invalid, so it will stop showing up in our triage routine. If I'm mistaken just revert my change and we'll look at it again.

Changed in freeipmi (Ubuntu):
status: New → Invalid
Revision history for this message
Behroz Sikander (behroz89) wrote :

I am new to MaaS but i think that this script is executed through MaaS somehow. MaaS throws these warning multiple times and my node stays in commissioning side. It must be somehow MaaS related, since I found this exception in MaaS logs.

Revision history for this message
anmc (anmc) wrote :

We're also running into this. While there's a log line for each of our servers, there's one server that just will not commission and times out. The rest did commission and are deployed at the moment.

Our snap version is:
snap list
maas 2.8.1-8567-g.c4825ca06 7808 2.8/stable canonical✓ -

Servers are a mix of Dell PowerEdge R710 and R640

Revision history for this message
Behroz Sikander (behroz89) wrote :

I have the exact version of maas and we are using Dell C6100.

I see similar behavior. No matter what I do, i cannot commission this server. Once, I was able to atleast get power information but that also vanished and doesn't work. I have tried everything. Not sure what to do next.

Lee Trager (ltrager)
Changed in maas:
status: Fix Committed → Fix Released
Revision history for this message
Chris Zembower (czembower) wrote :

Sorry if I'm missing something, but isn't this an extremely fundamental flaw with core functionality of the platform?

Is there a workaround recommendation for those of us on 2.8.2 snap?

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.