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.

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

updated server.hostname validator for resolve rhel 8.10 formatting issue #15298

Conversation

omkarkhatavkar
Copy link

Problem Statement

Currently the settings.server.hostname validator updates the settings.server.version.rhel_version from string value of 8.10 to 8.1

Solution

Removed the validator settigns.server.hostname

Related Issues

@omkarkhatavkar omkarkhatavkar requested a review from a team as a code owner June 4, 2024 12:01
@omkarkhatavkar omkarkhatavkar force-pushed the fix_the_version_formatting branch from 3d2977b to fc8cdbf Compare June 4, 2024 12:55
@omkarkhatavkar omkarkhatavkar force-pushed the fix_the_version_formatting branch from fc8cdbf to 40b7a75 Compare June 4, 2024 13:06
@omkarkhatavkar omkarkhatavkar changed the title removed server.hostname validator for resolve rhel 8.10 formatting issue updated server.hostname validator for resolve rhel 8.10 formatting issue Jun 4, 2024
@@ -10,7 +10,7 @@
),
],
server=[
Validator('server.hostname', default=''),
Validator('server.hostname', must_exist=True),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't have any field for settings.server.hostname in server.yml, we set it when assigning a xdist worker from settings.server.hostnames, so we can remove must_exist=True from this validator, right?
https://github.com/SatelliteQE/robottelo/blob/master/pytest_fixtures/core/xdist.py#L45

@Gauravtalreja1 Gauravtalreja1 added the No-CherryPick PR doesnt need CherryPick to previous branches label Jun 4, 2024
Copy link
Member

@JacobCallahan JacobCallahan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This field shouldn't be set by a user, it is set by the xdist alignment fixture as @Gauravtalreja1 pointed out

@omkarkhatavkar
Copy link
Author

I dont think this is required as the solution was on the exporting env variables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
No-CherryPick PR doesnt need CherryPick to previous branches
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants