-
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
Extend VMware provisioning tests for OS version check #14094
Extend VMware provisioning tests for OS version check #14094
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.
I think you don't need to sat.execute and from there ssh to the host. You should be able to execute on the host directly, shouldn't you?
Otherwise LGTM.
9593bb3
to
bc1ca38
Compare
trigger: test-robottelo |
trigger: test-robottelo |
PRT Result
|
62ef2d8
to
5e1ef99
Compare
trigger: test-robottelo |
PRT Result
|
5e1ef99
to
89a9d09
Compare
trigger: test-robottelo |
PRT Result
|
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.
co-reviewed with @rmynar
What is the status of this PR? Do you need any help with this one?
From what we see, [E 240410 13:32:18 exceptions:17] AuthenticationError: Key-based authentication failed.
pops up when the test tries to connect to the host using broker.
Did you try to investigate the server logs? Enabling debug logging on SSHD where you are trying to connect is usually helpful in debugging these sorts of issues.
Also since the workaround is not present in the patch, I would recommend changing the PR title.
Signed-off-by: Gaurav Talreja <[email protected]>
89a9d09
to
c180aa1
Compare
trigger: test-robottelo |
PRT Result
|
PRT Result
|
else: | ||
wait_for( | ||
self.connect, | ||
fail_condition=lambda res: res is not None, | ||
handle_exception=True, | ||
raise_original=True, | ||
timeout=timeout, | ||
delay=1, | ||
) |
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.
is this actually necessary?
isn't
lambda: self.connect(key_filename=self.key_filename),
universal for both cases?
you could still pass key_filename=None
if it is not specified and it should work, shouldn't it?
https://github.com/SatelliteQE/broker/blob/master/broker/hosts.py#L117
@pytest.mark.parametrize('vmware', ['vmware8'], indirect=True) | ||
@pytest.mark.parametrize('pxe_loader', ['uefi'], indirect=True) | ||
@pytest.mark.parametrize('provision_method', ['build']) | ||
@pytest.mark.rhel_ver_match('[8, 9]') |
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.
i noticed you have a hardcoded rhel8
here:
https://github.com/SatelliteQE/robottelo/pull/14094/files#diff-f5876fe03942ff6e50c18a8f2c95255cdca6f84b9956721a587abf7322fb73abR130
mind changing that, so it reflects the current rhel_ver parameter?
provisioning_host = ContentHost( | ||
host_info['network-interfaces'][0]['ipv4-address'], auth=module_ssh_key_file | ||
) | ||
expected_rhel_version = host_info['operating-system']['operating-system'][-3:] |
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.
You are setting yourself for a failure with this kind of version parsing
In [1]: '8.10'[-3:]
Out[1]: '.10'
also, that field might contain os name + version + some suffix, like beta
or possibly eus
.
I'd suggest to use nailgun to get the host info, which should resolve the os entity where you can directly access major
and minor
versions.
This pull request has not been updated in the past 45 days. |
@Gauravtalreja1 I'm converting pr to draft for now, please mark it ready for review once you're done with changes/addressing the comments. |
Problem Statement
Bootdisk provisioning passes for VMware 8, but installed status isn't updated, we've BZ:2255264 reported for it,
Solution
Handling BZ:2255264 in automation while this is open, and extending the test to check OS version when provisioning is completed for all methods including bootdisk