Openjdk-infrastructure: UB18 x86 ansible failures

[jdekonin]

• azul repo errors
  -- workaround...delete repo additions as well as zulu-9 package installation
• apt install errors with libmpfr4, libmpfr4-dbg, openjdk-7-jdk
  -- workaround...delete from list
• docker role needs rework
  -- workaround... run with --skip-tags docker

Note that I am using this machine for performing adoptopenjdk testing, and not compilation of openjdk or openj9-openjdk. So there very well might be other issues when it comes to creating an SDK binary.

[karianna]

• Azul Repo errors maybe an http vs https issue.
• What's the failure on apt install errors with libmpfr4, libmpfr4-dbg, openjdk-7-jdk?
• What sort of rework does the docker role need?

[jdekonin]

Azul error

The error was: apt.cache.FetchFailedException:
W:GPG error: http://repos.azulsystems.com/ubuntu stable
Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B1998361219BD9C9,
E:The repository 'http://repos.azulsystems.com/ubuntu stable Release' is not signed.

If I fetch the public key then rerun, the docker tag runs to completion and apparently successful.
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys B1998361219BD9C9

For apt errors the packages don't exist in the default ub18 repos. Although I think libmpfr4 and libmpfr4-dbg were required for gcc 4.8.5 source compiles, I don't recall exactly though.

Docker error

The error was: apt.cache.FetchFailedException: 
W:GPG error: https://download.docker.com/linux/ubuntu bionic 
InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7EA0A9C3F273FCD8, 
E:The repository 'https://download.docker.com/linux/ubuntu bionic InRelease' is not signed.

If I fetch the public key then rerun, the docker tag runs to completion and apparently successful.

I'm not familiar with the addition of keys, I need input on whether this would be the correct addition/solution for adding public keys.

[sxa]

To be honest, Unless there's a reason to continue using the azul stuff I'd prefer to install ours now that we're close to having all the version coverage.

[karianna]

We don't have a solution for OpenJDK 7. I think adding keys is a good idea

[sxa]

@jdekonin Here's an example of adding a key: https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/master/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Docker/tasks/main.yml#L56 although I'm surprised that what's in there doesn't cover you for docker.

[sxa]

Note that I am using this machine for performing adoptopenjdk testing, and not compilation of openjdk or openj9-openjdk. So there very well might be other issues when it comes to creating an SDK binary.

We could do with having a way to run a subset of the installs for build / test / JCK purposes. The additional JCK playbook is entirely independent at the moment that those requirements would be best included in the main playbooks. It's on the todo list to merge them ;-)

[sxa]

We don't have a solution for OpenJDK 7

Unless we bootstrap 8 with 8

[karianna]

We could do for later 8 builds as no spec changes are likely to come in.

[jdekonin]

Was azul added just for bootjdk for compiling JDK10? If so, then I agree those entries could just be removed.

openjdk7 not being on the machine is only of importance if someone were to try compiling a JDK8 binary. The build system compiles on centos6.9.

[karianna]

Azul was added to provide an OpenJDK 7 to bootstrap 8 builds. I think we then stuck with Azul builds for subsequent versions

[sxa]

With the move to exclusively RHEL/CentOS for all of the main builds (https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/256) the presence of a JDK7 on Ubuntu now serves no purpose so that could just be removed entirely there unless needed for some other purposes or if we need to specifically build anything on Ubuntu)

[jdekonin]

Not even have for test machine installations? Are you saying that we should delete anything ubuntu?

[sxa]

No I'm saying we don't need boot JDKs on Ubuntu so could remove the section that installs the JDK7 boot JDKs

[jdekonin]

Ah, yes of course. That makes sense.

[sxa]

In addition to Docker, there are the following issues when running on Ubuntu 18.04

• GPG key Solution: Remove zulu from Common/*/Ubuntu (Looks like it's only installing 9 now anyway, and we can pull an adopt one for that)
• libmpfr4 packages don't exist in Ubuntu 18 repos
• openjdk-7-jdk packages don't exist in Ubuntu 18 repos (openjdk-8-jdk does though)
• libgstreamer version (OpenJFX prereq) needs to be changed from 0.10 to 1.0

[sxa]

As far as I know this is ok now - it fundamentally works (aarch64 may have some other problems) but in the main this is now done and we can deal with subsequent issues as they arise, so I'm closing this issue