package ca-certificates-java 20170930 failed to install/upgrade: installed ca-certificates-java package post-installation script subprocess returned error exit status 127

[Ivo Carapinha]

Package ca-certificates-java 20170930 failed to install while doing a clean install of openjdk-10-jdk 10~32-0ubuntu1.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates-java 20170930
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
Date: Sun Feb 11 17:23:20 2018
DuplicateSignature:
 package:ca-certificates-java:20170930
 Setting up ca-certificates-java (20170930) ...
 /var/lib/dpkg/info/ca-certificates-java.postinst: line 56: java: command not found
 dpkg: error processing package ca-certificates-java (--configure):
  installed ca-certificates-java package post-installation script subprocess returned error exit status 127
ErrorMessage: installed ca-certificates-java package post-installation script subprocess returned error exit status 127
InstallationDate: Installed on 2017-10-09 (125 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt 1.6~alpha7ubuntu1
SourcePackage: ca-certificates-java
Title: package ca-certificates-java 20170930 failed to install/upgrade: installed ca-certificates-java package post-installation script subprocess returned error exit status 127
UpgradeStatus: Upgraded to bionic on 2017-11-17 (85 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Brian Murray (brian-murray)]

This seems to have been an issue with openjdk-10 which is no longer in the archive and I was unable to reproduce this with openjdk-11 packages.