-
Notifications
You must be signed in to change notification settings - Fork 5
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
Automated install tests #226
base: master
Are you sure you want to change the base?
Conversation
scripts/install_xcpng.py
Outdated
@@ -237,7 +198,7 @@ def main(): | |||
hdd = 'nvme0n1' if vm.is_uefi else 'sda' | |||
generate_answerfile(tmp_local_path, installer, args.host, args.target_hostname, args.action, hdd, | |||
netinstall_gpg_check) | |||
generate_boot_conf(tmp_local_path, installer, args.action) | |||
pxe.generate_boot_conf(tmp_local_path, installer) |
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 don't understand this change. This option was used to have 3 actions: install, upgrade or restore.
I don't see how is it managed in the pxe file. It doesn't seems to exist anymore.
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.
generate_boot_conf
only uses the action to set rt=1
as a workaround in the restore
case, I want to have a look at that to see if we can do better (e.g. an answerfile solution). Note it's all still very draft...
@@ -26,6 +26,15 @@ PXE_CONFIG_SERVER = 'pxe' | |||
# Default VM images location | |||
DEF_VM_URL = 'http://pxe/images/' | |||
|
|||
# Default shared ISO SR |
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 using another ISO SR when we already have DEFAULT_NFS_ISO_DEVICE_CONFIG
in the data.py?
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.
Ah, I had missed that one
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.
In fact those are different, DEFAULT_NFS_ISO_DEVICE_CONFIG
is used in tests that create a new ISO SR from an existing NFS server, while what I'm doing is using an existing ISO SR.
Using an existing shared ISO SR is in fact not perfect because of the possibility of interference with other users (filename clashes), but turning an existing NFS share into an ISO SR does not help this, and does not seem really suitable when working with hosts that already have an ISO SR configured.
OTOH the test could provide its own ISO SR to workaround the filename clashes - or, more comfortably, make a clever use of mkstemp
through ssh
.
Current status: install + firstboot work in a single test
|
13282cc
to
64d0e9c
Compare
Current status: 2 separate tests for install and firstboot work without any manual intervention
|
143c991
to
56abc4e
Compare
Current status:
Next steps:
|
1fda4a1
to
2dd8ec0
Compare
Current status:
Next steps:
|
b75d3ed
to
ebe6700
Compare
358055b
to
18e0ef8
Compare
3383b51
to
795c185
Compare
Signed-off-by: Samuel Verschelde <stormi-xcp@ylix.fr>
When using --hosts=cache://... it is much too early for such a check, so we have to give the info manually, and the script would not allow this. And honor it not just for "collect".
9a91ea3
to
f167fac
Compare
Signed-off-by: Yann Dirson <yann.dirson@vates.tech>
Now based on top of preliminary PRs to separate generally-useful stuff:
Requires at least python 3.8 and pytest 8.2.