-
Notifications
You must be signed in to change notification settings - Fork 115
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
Update target os name due to RHELC-1737 #17208
base: master
Are you sure you want to change the base?
Conversation
1bf68ea
to
e24e014
Compare
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
PRT Result
|
assert ( | ||
"CentOS" | ||
if is_open('RHELC-1737') | ||
else target_os_name in convert2rhel_facts['conversions.target_os.name'] | ||
) |
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.
It isn't good practice to modify assertion as per open issue, but when checking locally this assertion is always true, so I'd suggest to handle it in the variable instead of assertion, and I think it's best to check 'CentOS Linux'
instead of just CentOS for target_os.name
assert ( | |
"CentOS" | |
if is_open('RHELC-1737') | |
else target_os_name in convert2rhel_facts['conversions.target_os.name'] | |
) | |
target_os_name = 'CentOS Linux' if is_open('RHELC-1737') else 'Red Hat' | |
assert target_os_name in convert2rhel_facts['conversions.target_os.name'] |
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.
This is altered because of the open bug and I added a check for it. But you are right, we should not do incorrect assertions. I have skipped the assertion until bug is fixed.
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.
no, I don't mean to skip entire assertion until bug is fixed, instead we can check if we're getting same target OS as source OS until its fixed as suggested in the target_os_name
variable and not in assertion
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.
Why should we assert the incorrect target_os_version? I think it is better to skip it. We do not expect os_version to be CentOS or Oracle post conversion. Wdyt?
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.
we've been validating this fact for a while for conversion tests, so I don't think it's good idea to skip it now, instead I'd suggest and think asserting both source_os and target_os is good addition to our conversion tests, and anyway It'll verify at least we're getting this facts after conversion
e24e014
to
8afb779
Compare
trigger: test-robottelo |
PRT Result
|
PRT Result
|
Problem Statement
Bug#RHELC-1737: Incorrect target os name post conversion to RHEL
Solution
Updated assertion
Related Issues