Bug 1729076 - Issue observed with java openjdk package during upgrade process of ipa server to latest version
Summary: Issue observed with java openjdk package during upgrade process of ipa server...
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: java-1.8.0-openjdk
Version: 8.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: jiri vanek
QA Contact: OpenJDK QA
Depends On:
TreeView+ depends on / blocked
Reported: 2019-07-11 11:06 UTC by Nikhil Dehadrai
Modified: 2021-02-01 07:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-02-01 07:42:05 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

Description Nikhil Dehadrai 2019-07-11 11:06:01 UTC
Description of problem:
Issue observed with java openjdk package while upgrading ipa server to latest version

Version-Release number of selected component (if applicable):

How reproducible:

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:               300/769 
warning: /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk- created as /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-
warning: /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk- created as /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-
restored /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk- to /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-
restored /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk- to /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-
mv: cannot stat '/etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-': No such file or directory
FAILED to restore /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk- to /etc/java/java-1.8.0-openjdk/java-1.8.0-openjdk-

Expected results:
No failed message should be observed during upgrade process

Comment 2 jiri vanek 2019-07-11 11:14:14 UTC
This should be harmeless. I would advice you to fix your test, that it do not screeam for any FAILED string.

Comment 5 RHEL Program Management 2021-02-01 07:42:05 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.