Hide Forgot
Description of problem: Issue observed with java openjdk package while upgrading ipa server to latest version Version-Release number of selected component (if applicable): ipa-server-4.7.90.pre1-3.module+el8.1.0+3389+a3c612fa.x86_64 How reproducible: Always Steps to Reproduce: 1. Setup IPA Master at RHEL 80 (in my case ipa-server-4.7.1-11.module+el8+2842+7481110c.x86_64) 2. Setup repo for RHEL 81beta to IPA-Master 3. Upgrade the IPA-Master using command # yum -y update or # dnf -y update Actual results: During update process followin FAILED message is observed: Running scriptlet: java-1.8.0-openjdk-headless-1:1.8.0.212.b04-3.el8.x86_64 300/769 warning: /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/calendars.properties created as /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/calendars.properties.rpmnew warning: /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/security/java.security created as /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/security/java.security.rpmnew restored /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/security/java.security.rpmnew to /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/security/java.security restored /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/calendars.properties.rpmnew to /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/calendars.properties mv: cannot stat '/etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/security/java.security.rpmnew': No such file or directory FAILED to restore /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/security/java.security.rpmnew to /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-1.8.0.212.b04-3.el8.x86_64/lib/security/java.security Expected results: No failed message should be observed during upgrade process
This should be harmeless. I would advice you to fix your test, that it do not screeam for any FAILED string.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.