Skip to content

fix(ipmctl): use neutral Ansible runtime paths - #3

Merged
climateamante merged 1 commit into
mainfrom
feature/ipmctl
Aug 2, 2026
Merged

climateamante merged 1 commit into
mainfrom
feature/ipmctl

Conversation

@climateamante

Copy link
Copy Markdown
Contributor

Summary

This is the focused completion follow-up to #1. The pinned Debian 13 ipmctl
installer has already been merged, published, and successfully built on the
intended Intel Ice Lake PMem 200 server. This PR removes the repository name
from ipmctl-owned host state before the feature branch is retired and the work
is treated as the primary 0.0.5 release candidate.

The installed CLI, source tuple, compatibility patches, safety boundary, and
public interface do not change.

Why this follow-up exists

The accepted target build retained source and build evidence under
$HOME/.cache/devs-guide/ipmctl and recorded its receipt and install manifest
under /var/lib/devs-guide/ipmctl. Those paths identify the repository rather
than the system responsible for staging and applying the feature. Neutral
Ansible paths make the owner of the generated state clear to operators without
requiring a separate naming explanation.

PR #1 was already merged at 59964bd before this naming requirement was
raised, so rewriting that completed history would be misleading. This branch
was fast-forwarded to the merge commit and carries one follow-up implementation
commit.

Changes

  • Retained workspaces move to $HOME/.cache/ansible/ipmctl/runs.
  • Receipt and install-manifest state move to
    /var/lib/ansible/debian/ipmctl.
  • Ephemeral ipmctl staging uses /tmp/ansible-ipmctl.*.
  • The shared runner accepts an optional, allow-listed runtime namespace;
    existing callers retain devs-guide by default and only ipmctl selects
    ansible.
  • Existing ipmctl cache, receipt, and manifest data are migrated without
    rebuilding when the neutral destinations are absent.
  • If both namespaces contain state, or a receipt/manifest pair is incomplete,
    migration fails closed for human review. It does not merge ambiguous data or
    recursively remove unknown content.
  • The managed-install check now requires the receipt, manifest, binary
    checksum, exact version, and complete linkage before skipping a rebuild.
  • Public and shared-runner documentation plus static contracts describe and
    enforce the new paths.

Preserved feature contract

  • Debian 13 amd64 only.
  • ipmctl v03.00.00.0538 / a71f2fb1c90dd07f9862b71c789881132193e8f9.
  • EDK2 edk2-stable202511 / 46548b1adac82211d8d11da12dd914f41e7aa775.
  • The same three checksum-pinned compatibility patches.
  • /usr/local/bin/ipmctl and the existing install / read-only verify
    modes.
  • No goal creation/deletion, firmware updates, security changes, namespace
    lifecycle, formatting, or reboot automation.
  • GitHub Actions performs static validation and Pages assembly; archived Intel
    source is compiled only on the real target server.

Acceptance evidence and remaining gate

The published installer from #1 successfully completed an exact-pinned source
build and installation on Debian 13 amd64 Intel Ice Lake with four PMem 200
modules. Version 03.00.00.0538, linkage, DIMM discovery, topology, memory
resources, and the current/pending goal query passed. The host was in Memory
Mode with no App Direct allocation or pending goal. Hardware identifiers are
not included in this PR.

Local review for this follow-up was intentionally static: shell syntax,
whitespace, YAML parsing, and diff inspection. No local source compilation or
Ansible virtual environment was used.

Before merge, exact commit 86f7065 must be run twice on the accepted server
using a commit-pinned raw PAGES_BASE_URL. Both runs must skip compilation,
the first must migrate legacy state, and the second must prove idempotence from
the neutral locations. After merge and main-only Pages deployment, the public
installer must skip rebuilding and its read-only verification must pass. The
feature branch can then be deleted.

@climateamante

Copy link
Copy Markdown
Contributor Author

Hosted checkpoint and exact remote gate

Candidate: 86f7065a29a9955a701d1eb11fe75089b3b1c74b

Run the following from the accepted Debian 13 PMem server as the normal
sudo-capable build user. This stages the runner and every dependency from the
same immutable candidate commit and does not require a Git clone.

candidate_sha=86f7065a29a9955a701d1eb11fe75089b3b1c74b
candidate_base="https://raw.githubusercontent.com/devs-guide/debian/${candidate_sha}"

wget -qO /tmp/ansible-ipmctl.sh \
  "${candidate_base}/setup/cli/ipmctl.sh"
bash -n /tmp/ansible-ipmctl.sh

/usr/local/bin/ipmctl version
ldd /usr/local/bin/ipmctl
sudo test -f /var/lib/devs-guide/ipmctl/receipt.json
sudo test -f /var/lib/devs-guide/ipmctl/install_manifest.txt
test -d "${HOME}/.cache/devs-guide/ipmctl/runs"
test ! -e "${HOME}/.cache/ansible/ipmctl"
sudo test ! -e /var/lib/ansible/debian/ipmctl

set -o pipefail
PAGES_BASE_URL="${candidate_base}" \
  bash /tmp/ansible-ipmctl.sh install 2>&1 | tee ipmctl-migrate-install-1.log
install_1_rc=${PIPESTATUS[0]}
printf 'candidate install 1 exit code: %s\n' "${install_1_rc}"

test "${install_1_rc}" -eq 0
grep -F 'Matching receipt, binary checksum, version, and linkage found;' \
  ipmctl-migrate-install-1.log
grep -F 'source fetch, compilation, and installation are skipped.' \
  ipmctl-migrate-install-1.log
test -d "${HOME}/.cache/ansible/ipmctl/runs"
test ! -e "${HOME}/.cache/devs-guide/ipmctl"
sudo test -f /var/lib/ansible/debian/ipmctl/receipt.json
sudo test -f /var/lib/ansible/debian/ipmctl/install_manifest.txt
sudo test ! -e /var/lib/devs-guide/ipmctl

PAGES_BASE_URL="${candidate_base}" \
  bash /tmp/ansible-ipmctl.sh install 2>&1 | tee ipmctl-neutral-install-2.log
install_2_rc=${PIPESTATUS[0]}
printf 'candidate install 2 exit code: %s\n' "${install_2_rc}"

test "${install_2_rc}" -eq 0
grep -F 'Matching receipt, binary checksum, version, and linkage found;' \
  ipmctl-neutral-install-2.log
grep -F 'source fetch, compilation, and installation are skipped.' \
  ipmctl-neutral-install-2.log

PAGES_BASE_URL="${candidate_base}" \
  bash /tmp/ansible-ipmctl.sh verify 2>&1 | tee ipmctl-neutral-verify.log
verify_rc=${PIPESTATUS[0]}
printf 'candidate verify exit code: %s\n' "${verify_rc}"
test "${verify_rc}" -eq 0

Human review must confirm both installs skipped rebuilding, the retained run
workspace moved to the neutral cache, legacy state is absent, version and
linkage still pass, and all four read-only PMem probes remain acceptable. Do
not merge or delete the branch until this evidence is returned.

@climateamante

Copy link
Copy Markdown
Contributor Author

Human approval received to merge and retire the feature branch. The commit-pinned remote migration/idempotence procedure remains documented as post-merge acceptance; it is no longer a pre-merge blocker.

@climateamante
climateamante merged commit 1bf5778 into main Aug 2, 2026
3 checks passed
@climateamante
climateamante deleted the feature/ipmctl branch August 2, 2026 17:22
@climateamante

Copy link
Copy Markdown
Contributor Author

Merged as 1bf577876d16588e418ecdaaaaec42deda1e27fe. Main workflow https://github.com/devs-guide/debian/actions/runs/30758726510 passed validate-runtime, build-www, and deploy-www. The local and remote feature/ipmctl branches are deleted. Published target-host migration/idempotence remains the final 0.0.5 release-candidate acceptance check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant