Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1661198

Summary: Windows Installer MSI does not register OpenJDK for uninstallation (entry in Add/Remove programs)
Product: Red Hat Enterprise Linux 7 Reporter: Jonathan Dowland <jdowland>
Component: java-11-openjdkAssignee: OpenJDK QA <java-qa>
Status: CLOSED CURRENTRELEASE QA Contact: OpenJDK QA <java-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.7-AltCC: akashche, ashipile, dbhole, jvanek, rcap
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-08 13:21:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Dowland 2018-12-20 11:37:40 UTC
Description of problem:

The following issue was reported to the Red Hat Developer team here:
https://issues.jboss.org/browse/RHDFEED-756

"The MSI fails to add an entry into the Add/Remove Programs or the Programs and Features if installed with the system account. We are using an Enterprise tool to deploy the software to customers if they don't have admin permissions to install software."

Comment 2 Alex Kashchenko 2018-12-31 21:09:05 UTC
Reproduced this with:

psexec /i /s cmd.exe
msiexec /q /i jdk11.msi

This way MSI is installed and registered successfully, but not added to "Programs and Features" list.

Uninstall still works under both LocalSystem and Administrator:

msiexec /q /x jdk11.msi

Currently not sure if this is correct handling of LocalSystem installation, will look more into this.

Comment 3 Alex Kashchenko 2019-02-05 14:04:08 UTC
(In reply to Alex Kashchenko from comment #2) 
> Uninstall still works under both LocalSystem and Administrator:

This part was incorrect, after install under LocalSystem, it cannot be uninstalled by Administrator.

Problem was caused by the fact, that "InstallScope" attribute was not set inside the Package element in MSI descriptor [1]. It defaulted to "perUser", that didn't cause problems in most cases, as installer requires elevated permissions for registry access and cannot be installed "perUser" for non-admin users. But installation under LocalSystem exposes this problem.

Added support to "perUser/perMachine" flag to the tool used to produce installer descriptor [2] with "perMachine" as default.

This fix is NOT included with 8u201 and 11.0.2 installers, it is going to be included with the next release in April.


[1] http://wixtoolset.org/documentation/manual/v3/xsd/wix/package.html
[2] https://github.com/akashche/wixgen/commit/bba38ec75205cdf81143fda4187aca65f80652c0

Comment 5 Alex Kashchenko 2019-02-11 16:09:06 UTC
Note, that because of this change it won't be possible to update existing 8u201 installation to 8u211. 8u201 should be uninstalled before installing 8u211. The following updates (8u211 to 8u221 and so on) should work fine.