[BUG] VirtualNode Xname Type Not Valid

[PowellTravis]

Describe the bug
The VirtualNode XName type does not validate against SMD

To Reproduce
Steps to reproduce the behavior:
payload.json

{
    "Components":[
      {
        "ID": "x1000c1s7b56n0v2",
	"NID": 56
      }
    ]
  }

{"type":"about:blank","title":"Bad Request","detail":"couldn't validate components: xname ID 'x1000c1s7b56n0v2' is invalid","status":400}

https://github.com/Cray-HPE/hms-xname/blob/main/xnametypes/hmstypes.go#L75 HMS-XNAME types list as a valid xname

Expected behavior
The VurtualNode xname type should be accepted as a valid XNAME to SMD

Desktop (please complete the following information):

• OS: [e.g. iOS] Rocky 9.5

[alexlovelltroy]

@shunr-hpe Does this indicate that we're not properly using hms-xname for validation here?

[shunr-hpe]

This works for me now using the latest SMD.

Back in July when this issue was created, SMD in OpenCHAMI didn't have the latest changes from SMD in CSM.

I tested using the docker compose (quick start) environment.
Here are the commands that were run from a container on the internal network.

export ACCESS_TOKEN=$(curl -s -X GET http://opaal:3333/token | jq -r .access_token)

curl -s -X POST -H "Authorization: Bearer $ACCESS_TOKEN" -d '{"Components":[{ "ID": "x1000c1s7b56n0v2", "NID": 56, "State":"Off" } ] }' http://smd:27779/hsm/v2/State/Components

curl -s http://smd:27779/hsm/v2/State/Components | jq -c .Components[] | grep x1000c1s7b56n0v2

{"ID":"x1000c1s7b56n0v2","Type":"VirtualNode","State":"Off","Flag":"OK","Enabled":true,"Role":"Compute","NID":56}

[alexlovelltroy]

@PowellTravis Can we close this?