Skip to content

CI: fix vagrant jobs#12787

Open
VannTen wants to merge 3 commits intokubernetes-sigs:masterfrom
VannTen:ci/cleanup_vagrant
Open

CI: fix vagrant jobs#12787
VannTen wants to merge 3 commits intokubernetes-sigs:masterfrom
VannTen:ci/cleanup_vagrant

Conversation

@VannTen
Copy link
Copy Markdown
Contributor

@VannTen VannTen commented Dec 11, 2025

What type of PR is this?
/kind bug

What this PR does / why we need it:

Since b9e251a (CI: cleanup terraform + deduplicate and simplify, 2025-03-14), the vagrant CI does not actually work, because Ansible does not see the hosts created !
This restore the behaviour or copying the vagrant inventory to make it available to the playbook.

Also some simplifying of dependencies to have the vagrant jobs not wait on pre-commit (which can take some time with ansible-lint)

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

@VannTen
CI: relax jobs dependencies
aeb7180 
The vagrant test jobs don't actually need to wait for pre-commit, and
the kubevirt jobs don't need to wait for vagrant-validate.
@VannTen
Fix vagrant CI + delete unused Makefile
8559084
@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/bug Categorizes issue or PR as related to a bug. labels Dec 11, 2025
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Dec 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: VannTen

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Dec 11, 2025
@VannTen
Copy link
Copy Markdown
Contributor Author

VannTen commented Dec 11, 2025

/label ci-full

@k8s-ci-robot k8s-ci-robot added the ci-full Run every available tests label Dec 11, 2025
@VannTen
Copy link
Copy Markdown
Contributor Author

VannTen commented Dec 11, 2025

/retest

@VannTen
Copy link
Copy Markdown
Contributor Author

VannTen commented Dec 12, 2025

/retest-failed

1 similar comment
@VannTen
Copy link
Copy Markdown
Contributor Author

VannTen commented Dec 12, 2025

/retest-failed

@k8s-triage-robot
Copy link
Copy Markdown

k8s-triage-robot commented Mar 12, 2026

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Mar 12, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Mar 12, 2026

PR needs rebase.

Details

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-sigs/prow repository.

@k8s-triage-robot
Copy link
Copy Markdown

k8s-triage-robot commented Apr 11, 2026

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle rotten
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cyclinder cyclinder Awaiting requested review from cyclinder

@tico88612 tico88612 Awaiting requested review from tico88612

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. ci-full Run every available tests cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@VannTen @k8s-ci-robot @k8s-triage-robot