Bug 1491684

Summary: Upgrade from Spacewalk 2.6 to 2.7 fails
Product: [Community] Spacewalk Reporter: Andreas Schmechtig <Andreas.Schmechtig>
Component: InstallationAssignee: Jan Dobes <jdobes>
Status: CLOSED NOTABUG QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.7CC: mario.mikocevic
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-23 15:07:07 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: 1564160    
Attachments:
Description Flags
Output of failed yum update command
none
List of installed RPMS including spacewalk 2.6 none

Description Andreas Schmechtig 2017-09-14 12:04:09 UTC
Created attachment 1325947 [details]
Output of failed yum update command

Description of problem:
We want to do a upgrade installation from Spacewalk 2.6 to 2.7.
The upgrade fails with problems during dependency resoultion.

Version-Release number of selected component (if applicable):
Installed version: Spacewalk 2.6.6-1
Update Version: Spacewalk 2.7.6-1

How reproducible:
Do a yum update operation

Steps to Reproduce:
1. Enable Spacewalk 2.7 repo (baseurl=http://spacewalk.redhat.com/yum/2.7/RHEL/6/$basearch/)
2. yum update

Actual results:
yum update fails

Expected results:
yum update does an update to Spacewalk 2.7


Additional info:
OS: Red Hat Enterprise Linux Server release 6.9 (Santiago) x86_64
See attached list of installed RPMS.
See the yum output in the attached file.

with kind regards
Andreas Schmechtig

Comment 1 Andreas Schmechtig 2017-09-14 12:04:49 UTC
Created attachment 1325948 [details]
List of installed RPMS including spacewalk 2.6

Comment 2 Jan Dobes 2017-10-27 16:35:04 UTC
Do you have jpackage repo disabled and conflicting packages removed according to instructions?

https://github.com/spacewalkproject/spacewalk/wiki/HowToUpgrade#assumptions
https://github.com/spacewalkproject/spacewalk/wiki/HowToUpgrade#remove-conflicting-packages

Comment 3 Andreas Schmechtig 2017-11-23 15:07:07 UTC
Hello Jan,

meanwhile I have successfully upgraded from 2.6 to 2.7.

The more detailed instructions at

https://github.com/spacewalkproject/spacewalk/wiki/HowToUpgrade

helped.

I think when I tried to upgrade the last time, these specific instructions with hints (new repos, deinstall of jpackage rpms with nodeps) were not available.

So from my point of view this bug can be closed.

Comment 4 Mario Mikocevic 2018-04-23 08:42:43 UTC
The more detailed instruction are still *NOT* enough, it still fails.
The main problem is ->

Transaction Check Error:
  file /usr/share/java/slf4j/api.jar from install of slf4j-0:1.5.8-8.el6.noarch conflicts with file from package spacewalk-slf4j-1.6.1-6.el6.noarch
  file /usr/share/java/slf4j/jcl.jar from install of slf4j-0:1.5.8-8.el6.noarch conflicts with file from package spacewalk-slf4j-1.6.1-6.el6.noarch

or in another words package
spacewalk-java-2.7.116-1.el6.noarch
is *NOT* obsoleting correctly other old packages.