kubeadm: fix unit test panic for TestNewResetData

[SataQiu]

What type of PR is this?

/kind bug

What this PR does / why we need it:

When multiple CRI endpoints on the host:

go test -timeout 30s -run ^TestNewResetData$ k8s.io/kubernetes/cmd/kubeadm/app/cmd

--- FAIL: TestNewResetData (0.00s)
    --- FAIL: TestNewResetData/pre-flights_errors_from_CLI_args (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x101886dcd]

goroutine 51 [running]:
testing.tRunner.func1.2({0x101ae3ae0, 0x1031c3ac0})
        /Users/machine/workspace/soft/go/src/testing/testing.go:1526 +0x24e
testing.tRunner.func1()
        /Users/machine/workspace/soft/go/src/testing/testing.go:1529 +0x39f
panic({0x101ae3ae0, 0x1031c3ac0})
        /Users/machine/workspace/soft/go/src/runtime/panic.go:884 +0x213
k8s.io/kubernetes/cmd/kubeadm/app/cmd.expectedResetIgnorePreflightErrors.func1(0xc0004d46e0?, 0xc0003807e0?)
        /Users/machine/workspace/gopath/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/reset_test.go:110 +0x2d
k8s.io/kubernetes/cmd/kubeadm/app/cmd.TestNewResetData.func1(0xc0004d3ba0)
        /Users/machine/workspace/gopath/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/reset_test.go:102 +0x5e3
testing.tRunner(0xc0004d3ba0, 0xc00039cda0)
        /Users/machine/workspace/soft/go/src/testing/testing.go:1576 +0x10b
created by testing.(*T).Run
        /Users/machine/workspace/soft/go/src/testing/testing.go:1629 +0x3ea
FAIL    k8s.io/kubernetes/cmd/kubeadm/app/cmd   0.642s
FAIL

we need to pass a predefined CRI endpoint in CLI flag for unit tests.

Which issue(s) this PR fixes:

Ref kubernetes/kubeadm#2863

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[SataQiu]

/assign @chendave

[SataQiu]

/retest

[pacoxu]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 15d4a4bfebbd800d4006e00c21d1c4513c2a1dde

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pacoxu, SataQiu

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:

• cmd/kubeadm/OWNERS [SataQiu]

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