#220 Run workstation and workstation_encrypted upgrade tests on aarch64
Closed: Fixed 2 years ago by adamwill. Opened 3 years ago by adamwill.

We have matrix spots for these, so we should really automate them so @pwhalen doesn't have to sit there running them for hours.

The only potential stumbling block is disk space, in fact - I think we don't carry all the necessary base disk images for aarch64 at present, and we're kind of tight on disk space for aarch64 assets at this point. The size limit we have configured means they get garbage collected very fast, and I don't know if the prod server actually has enough disk space to bump the limit. I'll have to check how many more images we'd need to carry, and if we have room to bump the limit a bit.


So I set this up on staging to test it. issues so far:

  1. it does start to stretch resources - we only have one aarch64 worker host for staging, and these are long-running tests. Prod has two worker hosts so it wouldn't be so bad there. Might be nice if we could get another for staging, though.
  2. Encrypted tests fail because we don't see the encryption prompt; I forgot that for the encrypted install test we have to do a workaround in postinstall to avoid https://bugzilla.redhat.com/show_bug.cgi?id=1661288 , and the createhdds-built base image for the encrypted upgrade test doesn't have that. I'll have to see if we can add it there somehow.

So I fixed 2 in createhdds, and deployed this to production. It's working now, we have passes for all four tests from coconut for today's compose.

Metadata Update from @adamwill:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

So I fixed 2 in createhdds, and deployed this to production. It's working now, we have passes for all four tests from coconut for today's compose.

Thanks, Adam!

Login to comment on this ticket.

Metadata