Add read-only HMC LIC firmware inventory diagnostics
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
Research direction
Start with the HMC driver after blockers #1817, #1822, and #1824 land, then read the capability limits in docs/design/m4-byo-host.md:168-174 and resource enumeration in src/kdive/domain/catalog/resources.py:17-22. Implement the fixed read-only LIC selectors with bounded output, structured parsing, and redaction; test selector restrictions, level differences, unknown and error cases, truncation, and redaction. Done means reporting installed, activated, and accepted levels with provenance while keeping unsupported or unavailable data explicit and performing no firmware mutation.
Written by the indexing model from the issue text.
Description
Problem
The PowerVM diagnostic path lacks read-only LIC firmware inventory metadata needed to describe the environment when comparing failures. OpenPower-only firmware selectors must not be treated as universal PowerVM support.
Part of #1814. Follow-up to the capability survey in #1816, explicitly approved for filing and campaign enqueueing. Hardware operations remain held.
Blocked by #1817
Blocked by #1822
Blocked by #1824
Evidence
-
docs/design/m4-byo-host.md:168-174limits OOB widening to surveyed capabilities with a named caller. The BYO doctor report (#1824) is the caller for this contribution. -
src/kdive/domain/catalog/resources.py:17-22currently enumerates local, fault-injection, and remote-libvirt resources; the BYO skeleton and HMC driver are prerequisites, rather than an existing implemented HMC capability. -
IBM documents
lslic -t sys,io, andsriov, including installed, activated, and accepted levels; BMC/PNOR selectors have platform restrictions: https://www.ibm.com/docs/en/power11/9824-22A?topic=commands-lslic . This is documented command support, not a hardware proof.
Expected
The BYO doctor contribution reports available installed, activated, and accepted firmware levels with selector/platform/version provenance. Unsupported and unavailable data remain explicit. The path performs no firmware update or activation.
Proposed approach
Extend the existing HMC driver after its prerequisite lands with fixed read-only LIC inventory selectors, bounded duration/output, structured parsing, deterministic redaction, and diagnostic artifact references. Test supported selector construction, platform restrictions, differing levels, unknown fields, empty/error/truncation paths, and redaction. Document reporting limits. Keep this one inventory contribution in one PR; no firmware mutation, automatic compatibility or allocation veto, arbitrary command runner, new public MCP tool, or hardware operation is authorized by this tracking issue.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 9h 13m
- Merged PRs (30d)
- 197
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from randomparity/kdive
-
area:core-platform effort:S priority:P3 risk:night-safe status:ready type:test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
randomparity/kdive#3620 ·
Maintainers usually reply within 1 day
-
area:providers effort:S priority:P3 risk:night-watch status:ready type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
randomparity/kdive#3618 ·
Maintainers usually reply within 1 day
-
area:core-platform effort:S priority:P3 risk:night-safe status:ready type:test
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
randomparity/kdive#3603 ·
Maintainers usually reply within 1 day
-
area:providers effort:S priority:P3 risk:night-safe status:ready type:docs
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
randomparity/kdive#3593 ·
Maintainers usually reply within 1 day
-
area:providers effort:S priority:P3 risk:night-safe status:ready type:refactor
Difficulty 1/5 Under an hour Newbie friendliness 84/100
randomparity/kdive#3592 ·
Maintainers usually reply within 1 day
All issues in randomparity/kdive
Similar issues
-
fleet size/m
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sipyourdrink-ltd/bernstein#7548 ·
Maintainers usually reply within 1 day
-
good first issue help wanted level 1 wocs
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
GianlucaBave/murmury#73 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
G-nn-r/lg_heatpump#52 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
agno-agi/agno#11657 · 1 comment ·
Maintainers usually reply within 1 day
-
category:codebase:gpi category:codebase:handle type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day