ledmon incorrectly sets the status LED

Bug #1831733 reported by Roman Sobanski
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OEM Priority Project
Fix Released
High
Woodrow Shen
ledmon (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Description:

After creating the RAID volume, deleting it and creating second RAID volume (with same disks as with first volume but with less disks' count), LED statuses on disks left in container are ‘failure’.

Steps to reproduce:
1. Turn on ledmon:
# ledmon --all

2. Create RAID container:
# mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=3 /dev/nvme5n1 /dev/nvme4n1 /dev/nvme2n1 --run –force

3. Create first RAID volume:
# mdadm --create /dev/md/Volume --level=5 --chunk 64 --raid-devices=3 /dev/nvme5n1 /dev/nvme4n1 /dev/nvme2n1 --run –force

4. Stop first RAID volume:
# mdadm --stop /dev/md/Volume

5. Delete first RAID volume:
# mdadm --kill-subarray=0 /dev/md127

6. Create second RAID volume in the same container (with less disks' count than first RAID, using the sane disks as in the first volume):
# mdadm --create /dev/md/Volume --level=1 --raid-devices=2 /dev/nvme5n1 /dev/nvme4n1 --run

7. Verify status LED on container member disks which are not part of second RAID volume.

Expected results:
Disks from container which are not in the second volume should have ‘normal’ status LED.

Actual results:
Disks from container which are not in the second volume have ‘failure’ status LED.

Tags: patch
Revision history for this message
Roman Sobanski (rsobans) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ledmon (Ubuntu):
status: New → Confirmed
Rex Tsai (chihchun)
affects: ledmon (Ubuntu) → oem-priority
Changed in ledmon (Ubuntu):
status: New → Confirmed
Changed in oem-priority:
importance: Undecided → High
Rex Tsai (chihchun)
Changed in oem-priority:
assignee: nobody → Woodrow Shen (woodrow-shen)
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

tags: added: patch
Revision history for this message
Woodrow Shen (woodrow-shen) wrote :

a debdiff for new release of ledmon_0.92-0.1

Revision history for this message
Woodrow Shen (woodrow-shen) wrote :

debdiff v1

Mathew Hodson (mhodson)
Changed in ledmon (Ubuntu):
importance: Undecided → Low
Revision history for this message
Woodrow Shen (woodrow-shen) wrote :

The upstream version 0.93 is landed in focal now:

ledmon (0.93-3) unstable; urgency=medium

  * Fix 32bit compilation error to prevent shift-count-overflow.

Mathew Hodson (mhodson)
Changed in ledmon (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Pawel Baldysiak (pbaldysi) wrote :

Hi,
Are there any plans to fix it in bionic for which this issue was originally reported?

Thanks
Pawel

Rex Tsai (chihchun)
Changed in oem-priority:
status: Confirmed → Fix Released
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.