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.

Sign up for GitHub

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

Jump to bottom

Test Case for Klipper #278

Open
timothystewart6 opened this issue Apr 16, 2023 · 0 comments
Open

Test Case for Klipper #278

timothystewart6 opened this issue Apr 16, 2023 · 0 comments
Labels
CI Related to continuous integration and testing

Comments

@timothystewart6
Copy link
Contributor

Since we are disabling klipper during the default install with --disable servicelb , we should also test this with molecule to be sure that the klipperpods do not exist.

Done when:

  • CI Test that checks for klipper and confirms it is not installed
  • Optionally could detect the presence of --disable servicelb flag and do it in process too (during the playbook execution) and check
@timothystewart6 timothystewart6 added the CI Related to continuous integration and testing label Apr 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CI Related to continuous integration and testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@timothystewart6