-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Flatcar 4081 CI test #11868
base: master
Are you sure you want to change the base?
Add Flatcar 4081 CI test #11868
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tico88612 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
855702c
to
990d3fd
Compare
@yankay @VannTen, could you help me to check the infrastructure (I'm not approver to do this) why can't we connect Flatcar's VM? thanks!
|
3db44ef
to
914f859
Compare
HI @tico88612 From the Log, the ansible cannot connect the ssh correctly. Based on previous experience, it could be due to issues with cloud-init, as referenced here. However, I lack knowledge about the Flatcar operating system and am unsure if this is the root cause. |
Signed-off-by: ChengHao Yang <[email protected]>
Signed-off-by: ChengHao Yang <[email protected]>
Signed-off-by: ChengHao Yang <[email protected]>
914f859
to
85b7fb3
Compare
Signed-off-by: ChengHao Yang <[email protected]>
85b7fb3
to
1a7dab1
Compare
@yankay I've tried replacing Cloud-init with several possibilities, but it still doesn't work. Another possibility is that Flatcar should choose QEMU instead of Kubevirt (or the OpenStack version). I want to know if the KubeVirt VM was created successfully or was due to something else (other than cloud-init). |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Test for Flatcar stable version
Which issue(s) this PR fixes:
Fixes #11804
Does this PR introduce a user-facing change?: