[BUG] SMD and OPAAL dependency

[travisbcotton]

Describe the bug
The SMD quadlet should depend on OPAAL.
If the SMD quadlet starts before OPAAL it will fail to get a token and then will be essentially unusable.

You'll see it fail in the logs

main.go:950: failed to initialize auth token: failed to fetch "http://opaal:3333/keys": Get "http://opaal:3333/keys": dial tcp: lookup opaal on 10.89.3.1:53: no such host

To Reproduce

systemctl start openchami.target

Observe logs in SMD and see the above.

Expected behavior
SMD should get a token correctly

[synackd]

In my SMD logs:

smd[3266131]: 2025/08/29 17:58:25.024113 main.go:950: failed to initialize auth token: failed to fetch "http://opaal:3333/keys": Get "http://opaal:3333/keys": dial tcp 10.89.2.121:3333: connect: connection refused                                                                                                                                                                        
smd[3266131]: 2025/08/29 17:58:30.027755 main.go:954: Initialized the auth token successfully.

In SMD, there is a retry loop here that attempts 5 times to get its token. Are these exhausted during your testing?

[travisbcotton]

Yes it tries 5 times and still fails but then continues to run