Hide Forgot
Description of problem: When installed package jboss-on-agent from jbappplatform-6-i386-server-6-rpm RHN channel, "yum check" results to the following error: jboss-on-agent-3.1.2.GA-1.el6_5.1.noarch has installed conflicts jboss-on-agent: jboss-on-agent-3.1.2.GA-1.el6_5.1.noarch The similar happens if you install jboss-on-agent-3.2 package instead. Version-Release number of selected component (if applicable): 3.1.2, 3.2 How reproducible: always Steps to Reproduce: 1. Subscribe to jbappplatform-6-i386-server-6-rpm RHN channel 2. yum install jboss-on-agent 3. yum check all Actual results: jboss-on-agent-3.1.2.GA-1.el6_5.1.noarch has installed conflicts jboss-on-agent: jboss-on-agent-3.1.2.GA-1.el6_5.1.noarch Expected results: no conflicts Additional info: The current state of jbappplatform-6-i386-server-6-rpm RHN channel has caused by [1] errata which didn't pass TPS tests (neither Errata nor DistQA TPS phase) which are mandatory part of the standard Errata testing process. [1] https://errata.devel.redhat.com/advisory/17632
Same issue is manifested in RHUI. The following commands were run in a instance with already installed jboss-on-agent and jboss-on-agent-init-ec2 packages, which were upgraded after performing "yum update" command. # yum check all Loaded plugins: amazon-id, rhui-lb, security jboss-on-agent-3.1.2.GA-1.el6_5.1.noarch has installed conflicts jboss-on-agent: jboss-on-agent-3.1.2.GA-1.el6_5.1.noarch jboss-on-agent-init-ec2-3.1.2.GA-1.el6_5.1.noarch has installed conflicts jboss-on-agent-init-ec2: jboss-on-agent-init-ec2-3.1.2.GA-1.el6_5.1.noarch # rpm --verify --all | perl -ne 'print if (! /\S{9}\s{1,2}c\s/)'" Unsatisfied dependencies for jboss-on-agent-init-ec2-3.1.2.GA-1.el6_5.1.noarch: jboss-on-agent-init-ec2 conflicts with jboss-on-agent-init-ec2-3.1.2.GA-1.el6_5.1.noarch jboss-on-agent-init-ec2 conflicts with jboss-on-agent-init-ec2-3.1.2.GA-1.el6_5.1.noarch Unsatisfied dependencies for jboss-on-agent-3.1.2.GA-1.el6_5.1.noarch: jboss-on-agent conflicts with jboss-on-agent-3.1.2.GA-1.el6_5.1.noarch jboss-on-agent conflicts with jboss-on-agent-3.1.2.GA-1.el6_5.1.noarch
The TPS report from comment #1 is completely missing. Could you please re-run to see the exact error? Also, could you please provide more context for the error? Also, the conflicts and provides tags for the RPM were deliberately set to the current values to prevent automatic update between non-patch versions of the RPM. Please read bug 1118752 comment 2 for the exact details and testing done for the RPM. Is this TPS error preventing any channel releases?
This error doesn't prevent channel releases from our (EAP) side. We will rerun the tests in next week EAP 6.3.1 testing and will let you know.
Katerina, any news about the EAP 6.3.1 channel test runs?
Stefan, sorry for the delay. In the EAP 6.3.1 the results are still the same as described in the first comment.
Moving into CR01 target milestone as missed ER01 cutoff.
Moving into CR01 as missed ER01 cutoff.
Available for test with 3.3.3 ER01 build: https://brewweb.devel.redhat.com/buildinfo?buildID=446732 *Note: jon-server-patch-3.3.0.GA.zip maps to ER01 build of jon-server-3.3.0.GA-update-03.zip.
Created attachment 1054308 [details] conflict.log
@Stefan, @Katerina, could you please double-check the log file attached? The conflict log is updated with JON version ( the same log repeated 3 times ). The conflict log is still visible, but does not break the repo - you can still install the new JON version or any other RPM from channel. Not sure if this should be considered as fixed or not, since the conflict still exists but without any harm to system.
Available for test with following build: https://brewweb.devel.redhat.com/buildinfo?buildID=448923 *Note: jon-server-patch-3.3.0.GA.zip maps to CR01 build of jon-server-3.3.0.GA-update-03.zip.
Created attachment 1055746 [details] conflict.log.July24
verified with latest RPM build from errata. See log file attached for both RHEL6 and RHEL7.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1525.html