4 Commits

Author	SHA1	Message	Date
Trevor Cooper	152b347f75	replace fedoraproject.org with rockylinux.org ... - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes	2023-03-17 10:04:54 -07:00
Trevor Cooper	61d57d4591	enforce standard coding on all Perl files	2023-02-12 14:59:37 -08:00
Adam Williamson	940848b628	Use 'test.openqa.fedoraproject.org' not 'domain.local' ... Using .local is apparently Bad Form because it's reserved for mDNS. However there doesn't appear to be any particularly Good Form for what to call a test domain you never want to exist outside of a closed system, apparently. Sigh. Let's try this. Includes a bump to disk_ks version because the kickstarts on that image also need to have this change applied. Signed-off-by: Adam Williamson <awilliam@redhat.com>	2020-12-15 14:40:30 -08:00
Adam Williamson	aa41fe4e4e	Automate QA:Testcase_Zezere_Ignition ... This is a bit complex to automate, because we cannot really use the production Zezere server (provision.fedoraproject.org) as the test case shows, as we'd have to solve authentication and we also don't really want to constantly keep registering new hosts to it that are going to disappear and never be seen again. So, instead we'll do it by setting up our *own* Zezere, and provisioning our IoT system in that. We run two tests. The 'ignition' test is the actual IoT 'device'; all it really does is boot up, sit around, and wait to be provisioned. The 'server' test first sets up a Zezere server, then logs into it, adds an ssh key, claims the IoT device, provisions it, and connects to it to create a special file which tells the 'ignition' test everything worked and it can close out. Signed-off-by: Adam Williamson <awilliam@redhat.com>	2020-07-23 18:01:06 -07:00