Commit Graph

8 Commits

Author SHA1 Message Date
Adam Williamson 0998bc7c76 Drop match level on a couple of Zezere needles
These things are always trouble...

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2021-10-12 14:40:58 -07:00
Adam Williamson 4c8a58be22 Add yet another variant of an IoT zezere needle
There's some issue with font kerning or something on this page
which means we constantly get slightly different rendering of
this text. Rather annoying.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2021-09-28 15:48:41 -07:00
Adam Williamson 6f221809b1 Drop the match level on zezere claim button needle
This often seems to get a 90-95% match for some reason. Let's
just drop the threshold. I think it may be a kerning difference
based on the width of the MAC address?

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2021-08-24 16:08:56 -07:00
Adam Williamson 492fcf62e4 Great Needle Cleanup 2021
Remove a whole chunk of needles that haven't matched for more
than 3 months. Also move a few needles to appropriate locations,
simplify some code chunks that relied on removed needles (if
we're not matching the needles, we don't need those chunks any
more), and drop some other no-longer-needed conditionals for
older releases.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2021-08-10 11:57:48 -07:00
Adam Williamson df8d08db6f Update zezere needles for upstream/os-autoinst changes
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2021-07-19 15:59:07 -07:00
Adam Williamson d87d61df4d Update Zezere submit provision request needle
Dunno what changed.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-08-24 12:50:40 -07: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
Lukáš Růžička ce584750b4 Create test for IoT Greenboot.
Finish test and add necessary needles.

Create IOT needle directory and move needles in it.

Delete needle as required by the review.

Add to templates.
2020-05-29 16:25:46 +00:00