Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 857078 - `yum update katello` fails: unpacking of archive failed on file /usr/share/katello/public/fonts: cpio: rename
`yum update katello` fails: unpacking of archive failed on file /usr/share/ka...
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Infrastructure (Show other bugs)
6.0.0
Unspecified Unspecified
unspecified Severity urgent (vote)
: Unspecified
: Unused
Assigned To: Martin Bacovsky
Garik Khachikyan
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-13 10:16 EDT by Garik Khachikyan
Modified: 2015-01-04 16:59 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
A change from directory to symbolic link for public/fonts breaks the yum update. This fix provides an update from a version without converge-ui. This resolves the yum update error.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-12-04 14:52:47 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
rpm -qV katello katello-common (46.36 KB, application/octet-stream)
2012-09-13 10:31 EDT, Garik Khachikyan
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-04 19:39:57 EST

  None (edit)
Description Garik Khachikyan 2012-09-13 10:16:30 EDT
Description of problem:
Scenario is upgrading 1.0 -> 1.1 (katello-0.1.311-1.el6_2.noarch -> katello-1.1.12-4.el6cf.noarch)

Doing yum update katello fails recently with an error:
---
=================================================================================================================================
 Package                    Arch                      Version                             Repository                        Size
=================================================================================================================================
Updating:
 katello                    noarch                    1.1.12-4.el6cf                      system-engine                    4.1 M

Transaction Summary
=================================================================================================================================
Upgrade       1 Package(s)

Total download size: 4.1 M
Downloading Packages:
katello-1.1.12-4.el6cf.noarch.rpm                                                                         | 4.1 MB     00:00     
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Updating   : katello-1.1.12-4.el6cf.noarch                                                                                 1/2 
Error unpacking rpm package katello-1.1.12-4.el6cf.noarch
error: unpacking of archive failed on file /usr/share/katello/public/fonts: cpio: rename
Installed products updated.
  Verifying  : katello-1.1.12-4.el6cf.noarch                                                                                 1/2 
katello-0.1.311-1.el6_2.noarch was supposed to be removed but is not!
  Verifying  : katello-0.1.311-1.el6_2.noarch                                                                                2/2 

Failed:
  katello.noarch 0:0.1.311-1.el6_2                                katello.noarch 0:1.1.12-4.el6cf                               

Complete!
---

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

How reproducible:
always performing 1.0 -> 1.1 upgrade scenario

Steps to Reproduce:
1.have installed CFSE 1.0
2.prepare 1.1 yum repo
3.yum update katello
  
Actual results:
failure

Expected results:
no errors.

Additional info:
Comment 1 Garik Khachikyan 2012-09-13 10:17:58 EDT
critical issue for 1.0 -> 1.1 upgrade. needs to be handled in 1.1
Comment 2 Garik Khachikyan 2012-09-13 10:31:29 EDT
Created attachment 612469 [details]
rpm -qV katello katello-common
Comment 3 Lukas Zapletal 2012-09-13 10:47:48 EDT
Addning one more issue to this one - autostop does not work. Maybe you want to fix them both:

# katello-upgrade -y -a -s
Service 'katello' can not be running while katello-upgrade is in progress
Service 'katello-jobs' can not be running while katello-upgrade is in progress
Service 'tomcat6' can not be running while katello-upgrade is in progress
Service 'pulp-server' can not be running while katello-upgrade is in progress
Service 'httpd' can not be running while katello-upgrade is in progress
Service 'elasticsearch' can not be running while katello-upgrade is in progress
================================================================================
We will stop all katello services using katello-service stop.
PROCEED? (y/n): y
katello-service: unrecognized service
There was an issue stopping your services. Please resolve this manually
and try again

Katello nightly on RHEL 6.3
Comment 4 Garik Khachikyan 2012-09-14 03:26:38 EDT
rpm -qV katello katello-common
..5....T.    /usr/share/katello/db/seeds.rb
SM5..UGT.  c /etc/httpd/conf.d/katello.conf
S.5..UGT.  c /etc/katello/katello.yml
S.5....T.  c /etc/katello/thin.yml
S.5....T.  c /etc/sysconfig/katello
.M.......    /var/log/katello
Comment 5 Ivan Necas 2012-09-17 09:09:02 EDT
Pulled in https://github.com/Katello/katello/pull/663 commit

8ca8cce2e2087c8da5b98accb3fcbe1b0cc8275e
Comment 6 Ivan Necas 2012-09-17 09:10:41 EDT
Previous comment related to the rpm stuff, the update script issues still there
Comment 7 Lukas Zapletal 2012-09-17 09:19:41 EDT
Okay, flipping to ON_DEV and moving the comment 3 as a new bugzilla:

https://bugzilla.redhat.com/show_bug.cgi?id=857913
Comment 10 Garik Khachikyan 2012-10-04 08:32:46 EDT
# VERIFIED

now it is fine. yum update katello works without an issue there.

checked on updating 1.0.1 -> 1.1:
---
katello-1.1.12-12.el6cf.noarch
Comment 12 errata-xmlrpc 2012-12-04 14:52:47 EST
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.

http://rhn.redhat.com/errata/RHSA-2012-1543.html

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