Skip to content
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

LAVA Runtimes selection in Kubernetes deployment recipes for Production instance is out of sync #925

Open
pawiecz opened this issue Dec 3, 2024 · 1 comment · Fixed by #937

Comments

@pawiecz
Copy link
Contributor

pawiecz commented Dec 3, 2024

Several LAVA Runtimes added to the Pipeline configuration were not added to the Kubernetes deployment recipes:

  • 'lava-collabora-staging'
  • 'lava-qualcomm'
  • 'lava-cip'
pawiecz added a commit to pawiecz/kernelci-pipeline that referenced this issue Dec 5, 2024
Scheduler is able to filter out Runtimes it will submit Jobs to with
a "--runtimes" option. The filter currently in use for Kubernetes
deployment got out-of-sync with the LAVA Runtimes enabled in the
Pipeline config.

This patch drops this option to fall back to the default behaviour which
is submitting Jobs to all the Runtimes available in the Pipeline config.

Fixes: kernelci#925

Signed-off-by: Paweł Wieczorek <[email protected]>
github-merge-queue bot pushed a commit that referenced this issue Dec 9, 2024
Scheduler is able to filter out Runtimes it will submit Jobs to with
a "--runtimes" option. The filter currently in use for Kubernetes
deployment got out-of-sync with the LAVA Runtimes enabled in the
Pipeline config.

This patch drops this option to fall back to the default behaviour which
is submitting Jobs to all the Runtimes available in the Pipeline config.

Fixes: #925

Signed-off-by: Paweł Wieczorek <[email protected]>
@pawiecz pawiecz reopened this Dec 16, 2024
@pawiecz
Copy link
Contributor Author

pawiecz commented Dec 16, 2024

#937 had to be reverted due to the lack of lab_type filter set for the LAVA Runtime Scheduler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant