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
mgr/selftest: fix disabled module selection #24517
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.
change looks good, but that typo will probably show up in QA runs
src/pybind/mgr/selftest/module.py
Outdated
all_modules = [m['name'] for m in mgr_map['available_modules']] | ||
disabled_modules = set(all_modules) - set(mgr_map['modules']) | ||
disabled_module = list(disabled_modules)[0] | ||
assert disabled_moduled not in mgr_map['modules'] |
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.
disabled_module
d typo?
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: presumably the the assert is testing that the module isn't enabled and it isn't always on. might want to test that its not in the union of map['modules'] and map['always_on_modules']
This was broken by always on modules -- it was also unnecessary complication, let's just pick some hardcoded module to use. Signed-off-by: John Spray <john.spray@redhat.com>
Good catch, updated |
Merged on strength of a vstart_runner pass, as this was already generating failures in teuthology |
This was broken intermittently by always on modules -- it was also
unnecessary complication, let's just pick some
hardcoded module to use.
Signed-off-by: John Spray john.spray@redhat.com