Skip the failed CI test of docker-machine

[yankay]

What type of PR is this?

/kind flake

What this PR does / why we need it:

Skip the failed CI test of the docker-machine to Prevent the PR from breaking.

The CI failed because of #11049 .

It needs a lot of time to refactor. So, skip it.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Skip the failed CI test of docker-machine

[mzaian]

Thanks @yankay

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mzaian, yankay

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 [mzaian,yankay]

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

[VannTen]

I don't think we should just skip theses CI runs. Unlike #10886 which we're for optional features, this tests basic operations. If we just remove those, we risk to merge regressions (this already happens a lot).
Can we discuss this a bit more ?
/hold
(temporarily).

FYI, molecule can be used with kubevirt, apparently : https://github.com/ansible-community/molecule-kubevirt
There is also a vagrant plugin for kubevirt, which would let us indirectly use kubevirt in molecule (since AFAIK it currently use vagrant)

[yankay]

I don't think we should just skip theses CI runs. Unlike #10886 which we're for optional features, this tests basic operations. If we just remove those, we risk to merge regressions (this already happens a lot). Can we discuss this a bit more ? /hold (temporarily).

FYI, molecule can be used with kubevirt, apparently : https://github.com/ansible-community/molecule-kubevirt There is also a vagrant plugin for kubevirt, which would let us indirectly use kubevirt in molecule (since AFAIK it currently use vagrant)

Thanks @VannTen

I'm working on it #11063.
If lucky, the PR will be complete in a while. Or it may take time and help :-）

And from https://ansible.readthedocs.io/projects/team-devtools/stats/molecule-plugins/ .
"
Unmaintained drivers archived between January 5th-8th, 2023: openstack, goss, libvirt, alicloud, vmware, digitalocean, kubevirt, lxd, inspec.
"

[yankay]

The CI has been repaired by :

1. Upgrade to the docker-machine-driver-meta:
   https://github.com/equinix/docker-machine-driver-metal/releases/tag/v0.6.0

2. Change the config of Gitlab to using metro :

root@docker-machine-runner:/etc/gitlab-runner# diff config.toml config.toml-backup
45,47c45,46
< #      "metal-facility-code=pa4",
<       "metal-metro-code=am",
<       "metal-termination-time=4hours",
---
>       "metal-facility-code=am6",
>       "metal-ttl=4h",