-
Notifications
You must be signed in to change notification settings - Fork 192
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
QE: Add smoke tests for Grafana in BV #6170
QE: Add smoke tests for Grafana in BV #6170
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some nitpickings
testsuite/features/build_validation/smoke_tests/smoke_tests.template
Outdated
Show resolved
Hide resolved
testsuite/features/build_validation/smoke_tests/smoke_tests.template
Outdated
Show resolved
Hide resolved
I think that's not the correct approach sorry. I think we need to have as infrastructure:
We first prepare a SUSE minion that will act as our Monitoring server, applying the prometheus and grafana formulas. Then we test every , by applying the Prometheus exporter formula and checking that the entry of this minion is available in the dashboard from the monitoring server. In addition, but a different scenario, we should also check in all our suse minions, if the Prometheus and Grafana salt formulas can work on them, |
@srbarrios that's all fine by me but how do we put that into effect? I'm afraid I'm new to the BV infra and would probably need help setting up our additional monitoring server |
afc7f2d
to
bb125b4
Compare
This comment was marked as outdated.
This comment was marked as outdated.
bb125b4
to
99fac05
Compare
testsuite/features/build_validation/smoke_tests/smoke_tests.template
Outdated
Show resolved
Hide resolved
testsuite/features/build_validation/smoke_tests/smoke_tests.template
Outdated
Show resolved
Hide resolved
testsuite/features/build_validation/init_clients/monitoring_server.feature
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see requested nitpicks, otherwise lgtm
testsuite/features/build_validation/init_clients/monitoring_server.feature
Outdated
Show resolved
Hide resolved
testsuite/features/build_validation/init_clients/monitoring_server.feature
Outdated
Show resolved
Hide resolved
testsuite/features/build_validation/init_clients/monitoring_server.feature
Outdated
Show resolved
Hide resolved
f61b0fe
to
44fc86f
Compare
292c7a4
to
6036888
Compare
db9205a
to
471dab8
Compare
@@ -72,6 +72,7 @@ def twopence_init(target) | |||
$opensuse154arm_ssh_minion = twopence_init("ssh:#{ENV['OPENSUSE154ARM_SSHMINION']}") if ENV['OPENSUSE154ARM_SSHMINION'] | |||
$sle12sp5_buildhost = twopence_init("ssh:#{ENV['SLE12SP5_BUILDHOST']}") if ENV['SLE12SP5_BUILDHOST'] | |||
$sle15sp4_buildhost = twopence_init("ssh:#{ENV['SLE15SP4_BUILDHOST']}") if ENV['SLE15SP4_BUILDHOST'] | |||
$monitoring_server = twopence_init("ssh:#{ENV['MONITORING_SERVER']}") if ENV['MONITORING_SERVER'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you already adjust the .bashrc
on the controller in sumaform and added those environment variable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright. All good then 😉
What does this PR change?
Adds tests in the BV testsuite for the Grafana formula
monitoring_server
as monitoring server (for Prometheus and Grafana)GUI diff
No difference.
Documentation
No documentation needed: only internal and user invisible changes
DONE
Test coverage
Cucumber tests were added for BV teststuite
DONE
Links
Closes https://github.com/SUSE/spacewalk/issues/17627
Ports:
Changelogs
Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository
If you don't need a changelog check, please mark this checkbox:
If you uncheck the checkbox after the PR is created, you will need to re-run
changelog_test
(see below)Re-run a test
If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run: