Seeing the same for new versions of taskomatic and spacewalk-java

# yum update
Resolving Dependencies
--> Running transaction check
---> Package cglib.noarch 0:2.1.3-4.jpp5 will be updated
--> Processing Dependency: cglib < 2.2 for package: spacewalk-taskomatic-2.3.117-1.el7.noarch
--> Processing Dependency: cglib < 2.2 for package: spacewalk-java-2.3.117-1.el7.noarch
---> Package cglib.noarch 0:2.2-18.el7 will be an update
--> Finished Dependency Resolution
Error: Package: spacewalk-java-2.3.117-1.el7.noarch (@spacewalk-nightly)
           Requires: cglib < 2.2
           Removing: cglib-2.1.3-4.jpp5.noarch (@jpackage-generic)
               cglib = 2.1.3-4.jpp5
           Updated By: cglib-2.2-18.el7.noarch (base)
               cglib = 2.2-18.el7
Error: Package: spacewalk-taskomatic-2.3.117-1.el7.noarch (@spacewalk-nightly)
           Requires: cglib < 2.2
           Removing: cglib-2.1.3-4.jpp5.noarch (@jpackage-generic)
               cglib = 2.1.3-4.jpp5
           Updated By: cglib-2.2-18.el7.noarch (base)
               cglib = 2.2-18.el7
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

We need rhel7-optional because that's where we get things like apache-commons-beanutils, apache-commons-digester, and apache-commons-validator. The issue is that cglib-2.2 is *also* in rhel7-optional, and Spacewalk code is only tested with the cglib-2.1 that is found in the JPackage repository.

The only real fix for this, is to build SW and test against cglib-2.2, and see what breaks, so we can address those and (possibly) relax the <2.2 restriction.

In the meantime, a workaround is to force cglib to stay at 2.1:

 yum install yum-versionlock; yum versionlock cglib

Any changes?

I have tested on the lastest v spacewalk-java and spacewalk-taskomatic and the problem is still here.

> yum upgrade
....
Error: Package: spacewalk-java-2.3.179-1.el7.noarch (@spacewalk)
           Requires: cglib < 2.2
           Removing: cglib-2.1.3-4.jpp5.noarch (@jpackage-generic)
               cglib = 2.1.3-4.jpp5
           Updated By: cglib-2.2-18.el7.noarch (rhel-7-server-optional-rpms)
               cglib = 2.2-18.el7
Error: Package: spacewalk-taskomatic-2.3.179-1.el7.noarch (@spacewalk)
           Requires: cglib < 2.2
           Removing: cglib-2.1.3-4.jpp5.noarch (@jpackage-generic)
               cglib = 2.1.3-4.jpp5
           Updated By: cglib-2.2-18.el7.noarch (rhel-7-server-optional-rpms)
               cglib = 2.2-18.el7
...

No change - workaround is still "versionlock cglib", fixing will require a lot of testing to make sure cglib-2.2 doesn't break anything.

Version locking cglib is no longer a viable work around. This lock is currently holding back 10 fixes to our spacewalk server. These include a critical Tomcat update, which allows remote execution.

We need to move to a later version of cglib.

Priority should be set to urgent.

Still present, bumping version.

I too am having this issue with Spacewalk release 2.4.

# yum upgrade
...
Error: Package: spacewalk-taskomatic-2.4.79-1.el7.noarch (@spacewalk)
           Requires: cglib < 2.2
           Removing: cglib-2.1.3-4.jpp5.noarch (@jpackage-generic)
               cglib = 2.1.3-4.jpp5
           Updated By: cglib-2.2-18.el7.noarch (base)
               cglib = 2.2-18.el7
Error: Package: spacewalk-java-2.4.79-1.el7.noarch (@spacewalk)
           Requires: cglib < 2.2
           Removing: cglib-2.1.3-4.jpp5.noarch (@jpackage-generic)
               cglib = 2.1.3-4.jpp5
           Updated By: cglib-2.2-18.el7.noarch (base)
               cglib = 2.2-18.el7
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


Thanks

Also having the same issue. 
Error: Package: spacewalk-taskomatic-2.4.79-1.el7.noarch (@spacewalk)
           Requires: cglib < 2.2

Hey Jan, is there any progress on this as this seems to be an issue for some time. I'm running Centos 7 Spacewalk 2.4.

Would like to know the progress of this bug as I am encountering it as well.

I reverted back to a snapshot as it seems like no work is being done on this bug. Please update. Running CENTOS 7

I can confirm that this is happening on Centos 7 Spacewalk 2.5, please can we have an update?

Same Here, Centos 7.2.1511 spacewalk 2.5, I'd like to see an update too.

*** Bug 1375051 has been marked as a duplicate of this bug. ***

Same issue, in CentOS Linux release 7.3.1611. Thanks.

Same issue, SW 2.6 on CentOS Linux release 7.3.1611. Thanks.

We're experiencing the same issue, just as w.westra (what an email, hilarious) mentioned.  CentOS v 7.3 aka 1611 and spacewalk 2.6 with latest everthing as of the last 2 weeks.

Same issue in spacewalk 2.6 on CentOS Linux release 7.3.1611 (Core). Hoping for an update soon! Thank you.

AS of 2017-05-30 issue is still present. CentOS Linux release 7.3.1611 (Core). Hoping for a resolution or and update soon!!!

This bug is no longer reproducible with Spacewalk nightly. We did some changes and substituted jpackage repo with a new Copr repository (https://copr.fedorainfracloud.org/coprs/g/spacewalkproject/java-packages/) with packages needed for Spacewalk runtime.

Check instructions at HowToInstallNightly wiki page: https://github.com/spacewalkproject/spacewalk/wiki/HowToInstallNightly#java-packages-red-hat-enterprise-linux-centos-scientific-linux

If you can reproduce this bug against Spacewalk nightly, feel free to open this bug.

Additional info:
# rpm -q spacewalk-taskomatic spacewalk-java cglib
spacewalk-taskomatic-2.7.86-1.el7.noarch
spacewalk-java-2.7.86-1.el7.noarch
cglib-2.2-18.el7.noarch


I will attach "yum history info <transaction_number>" output.

Created attachment 1292404 [details]
yum history info <yum_upgrade-transaction_id>

This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.

*** Bug 1437921 has been marked as a duplicate of this bug. ***