Ubuntu
openjdk-17 package

  1. Bug #2055280
  2. Comment #10

Comment 10 for bug 2055280

Revision history for this message
Sebastian (slovdahl) wrote :

Not in Jenkins, but we saw the same error in another application when unattended upgrades upgraded from 17.0.9 to 17.0.10 back in February. Now with the 17.0.10 to 17.0.11 upgrade we are seeing the same problem again. Was there another change in the protocol or what's going on here? I found https://bugs.openjdk.org/browse/JDK-8307990 that could possibly be related at least.