-
Notifications
You must be signed in to change notification settings - Fork 197
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
SSM and systems groups #9787
base: master
Are you sure you want to change the base?
SSM and systems groups #9787
Conversation
👋 Hello! Thanks for contributing to our project. You can see the progress at the end of this page and at https://github.com/uyuni-project/uyuni/pull/9787/checks If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code. Reference tests: KNOWN ISSUES Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience. For more tips on troubleshooting, see the troubleshooting guide. Happy hacking! |
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 comments
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.
Thanks Pablo
I left some nitpicks/suggestion which are about naming scenarios and form.
The actual logic and steps LGTM
PS: add an empty new line at the end of the file ;)
cf0c08a
to
0af3e26
Compare
0af3e26
to
4230831
Compare
4230831
to
b6cb4aa
Compare
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.
Small question about removing RHlike minion from the group, why do we do that? Otherwise seems good
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.
LGTM
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.
Thanks for the changes, LGTM
b6cb4aa
to
b6e966d
Compare
f25e3de
b6e966d
to
f25e3de
Compare
1fd96a9
to
a4b8370
Compare
@@ -1,47 +1,125 @@ | |||
# Copyright (c) 2017-2024 SUSE LLC | |||
# Copyright (c) 2017-2025 SUSE LLC | |||
# Licensed under the terms of the MIT license. | |||
|
|||
@scope_visualization |
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.
What about include the tag @sle_minion
?
This feature depends on having a SLE minion deployed, so it make sense to skip it if the minion is not present.
@@ -1,47 +1,125 @@ | |||
# Copyright (c) 2017-2024 SUSE LLC | |||
# Copyright (c) 2017-2025 SUSE LLC | |||
# Licensed under the terms of the MIT license. | |||
|
|||
@scope_visualization |
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.
Also, as we are enhancing this feature, maybe we can also consider to create a new Cucumber profile.
If you go to testsuite/config/cucumber.yml
you will see that we have a list of Cucumber profiles, that runs when the Cucumber feature have some specified tags.
What about creating a new one for the SSM feature?
ssm: --tags @scope_ssm
And then we add the new tag on top of this feature like:
@scope_visualization
@scope_ssm
@sle_minion
Feature: Manage a group of systems
...
Some info about Cucumber profiles integration explained on these slides: https://oubiti.com/smart-integration-tests/
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.
Just some suggestions, but LGTM
7bc87fc
to
0eb16e9
Compare
319dc14
to
cbb10dc
Compare
…on of packages and patches can be done in a system groups and in a SSM
2afc433
to
28306d5
Compare
28306d5
to
b535f37
Compare
f012079
to
c49467d
Compare
dbaa3a0
to
412b8b9
Compare
Because this test was worng were missing sle_mions with rhlike minions |
412b8b9
to
f7e4bf7
Compare
What does this PR change?
This PR adds some smoke test to SSM and systems groups test features and fixes:https://github.com/SUSE/spacewalk/issues/15437
GUI diff
No difference.
Documentation
No documentation needed
DONE
Test coverage
Cucumber tests were added
DONE
Links
Issue(s): https://github.com/SUSE/spacewalk/issues/15437
Port(s):
Manager 5.0:
Manager 4.3:
DONE
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:
Before you merge
Check How to branch and merge properly!