If the Boot Script Service (BSS) metadata server does contain the proper Spire metadata, then the
computes will fail to boot. This is due to dracut pulling server data from the
metadata during startup. To fix this issue, the spire-update-bss job needs
to be rerun.
[ 557.513984] Apr 22 18:02:02 nid000004 dracut-initqueue[4177]: time="2022-04-22T18:02:02Z" level=info msg="SVID is not found. Starting node attestation" subsystem_name=attestor trust_domain_id="spiffe://null"
[ 557.514000] Apr 22 18:02:07 nid000004 dracut-initqueue[4194]: Agent is unavailable.
[ 557.514017] Apr 22 18:02:07 nid000004 dracut-initqueue[4174]: Warning: Spire-agent healthcheck failed, return code 1
(ncn-m#) Run the goss-spire-bss-metadata-exist test.
goss -g /opt/cray/tests/install/ncn/tests/goss-spire-bss-metadata-exist.yaml v
Example output:
Failures/Skipped:
Title: Kubernetes Query BSS Cloud-init for spire meta data
Meta:
desc: Kubernetes Query BSS Cloud-init for spire meta data
sev: 0
Command: spire_in_bss_cloudinit: exit-status:
Expected
<int>: 1
to equal
<int>: 0
Total Duration: 0.387s
Count: 1, Failed: 1, Skipped: 0
Run the following command on a master node to restart the job that populates the metadata server with the correct Spire information.
(ncn-m#) Re-run the spire-update-bss job.
JOB=$(kubectl get jobs -n spire -l app.kubernetes.io/name=spire-update-bss --no-headers -oname |sort -u | tail -n1); kubectl get -n spire $JOB -o json | jq 'del(.spec.selector,.spec.template.metadata.labels)' | kubectl replace --force -f -