Bug 1454620
| Summary: | Spacewalk start fails after fresh install with java-errors | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | Thomas Schweikle <tschweikle> | ||||
| Component: | Server | Assignee: | Tomáš Kašpárek <tkasparek> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Satellite QA List <satqe-list> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 2.6 | CC: | linuxraja, mmraka | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | spacewalk-java-2.7.53-1 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-09-27 07:04:11 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1484117 | ||||||
| Attachments: |
|
||||||
|
Description
Thomas Schweikle
2017-05-23 08:06:29 UTC
Missing dependency?? This is caused by the updated c3p0 package (c3p0-0.9.2.1-5) from EPEL repository. The lower version c3p0-0.9.1.2-2 will fix this issue. [root@spacewalk01 rhn]# rpm -qa | grep c3p0* c3p0-0.9.2.1-5.jpp5.noarch After spacewalk setup downgrade the c3p0 package yum downgrade c3p0 [root@spacewalk01 rhn]# rpm -qa | grep c3p0* c3p0-0.9.1.2-2.jpp5.noarch Now start the spacewalk service Test the service startup now systemctl status taskomatic.service systemctl start taskomatic.service systemctl status taskomatic.service Then restart Spacewalk service /usr/sbin/spacewalk-service restart This is caused by the updated c3p0 package (c3p0-0.9.2.1-5) from EPEL repository. The lower version c3p0-0.9.1.2-2 will fix this issue. [root@spacewalk01 rhn]# rpm -qa | grep c3p0* c3p0-0.9.2.1-5.jpp5.noarch After spacewalk setup downgrade the c3p0 package yum downgrade c3p0 [root@spacewalk01 rhn]# rpm -qa | grep c3p0* c3p0-0.9.1.2-2.jpp5.noarch Test the service startup now systemctl status taskomatic.service systemctl start taskomatic.service systemctl status taskomatic.service Then restart Spacewalk service /usr/sbin/spacewalk-service restart Already fixed in spacewalk master, most likely by
commit da7ff4efedf2f243aefd34921a405eff72eedc52
no more special jar handling is needed
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug. |