CheckExclusiveArch should use local JSON too

[baude]

When performing CheckExclusiveArch, we should get a list of VMs that exist on disk (JSON). We should then iterate those and checking if they are running in HyperV.

[NO NEW TESTS NEEDED]

Does this PR introduce a user-facing change?

None

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: baude

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [baude]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Luap99]

LGTM

[Luap99]

properly ok to not log this here. I think for something like machine ls it should be logged as error but if I start one machine I don't think there is a point in erroring about another machine config problem.

[mheon]

/lgtm

[baude]

/cherry-pick v4.8

[openshift-cherrypick-robot]

@baude: #21009 failed to apply on top of branch "v4.8":

Applying: CheckExclusiveArch should use local JSON too
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	pkg/machine/hyperv/config.go
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
Auto-merging pkg/machine/hyperv/config.go
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 CheckExclusiveArch should use local JSON too
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick v4.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.