Repository navigation
fix(ipmctl): use neutral Ansible runtime paths - #3
Conversation
Hosted checkpoint and exact remote gateCandidate:
Run the following from the accepted Debian 13 PMem server as the normal 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 0Human review must confirm both installs skipped rebuilding, the retained run |
|
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. |
|
Merged as |
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/ipmctland recorded its receipt and install manifestunder
/var/lib/devs-guide/ipmctl. Those paths identify the repository ratherthan 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
59964bdbefore this naming requirement wasraised, 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
$HOME/.cache/ansible/ipmctl/runs./var/lib/ansible/debian/ipmctl./tmp/ansible-ipmctl.*.existing callers retain
devs-guideby default and only ipmctl selectsansible.rebuilding when the neutral destinations are absent.
migration fails closed for human review. It does not merge ambiguous data or
recursively remove unknown content.
checksum, exact version, and complete linkage before skipping a rebuild.
enforce the new paths.
Preserved feature contract
v03.00.00.0538/a71f2fb1c90dd07f9862b71c789881132193e8f9.edk2-stable202511/46548b1adac82211d8d11da12dd914f41e7aa775./usr/local/bin/ipmctland the existinginstall/ read-onlyverifymodes.
lifecycle, formatting, or reboot automation.
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, memoryresources, 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
86f7065must be run twice on the accepted serverusing 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.