Bug #8353: Can't upgrade Katello from 2.0 -> 2.1 when Katello is registered to itself due to package dependencies - Packaging - Foreman

Actions

Copy link

Bug #8353

closed

Can't upgrade Katello from 2.0 -> 2.1 when Katello is registered to itself due to package dependencies

Added by Stephen Benjamin about 10 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Difficulty:

medium

Triaged:

Bugzilla link:

Pull request:

https://github.com/Katello/katello/pull/4925

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

In order to upgrade 2.0 to 2.1, there's a few packages that need to be installed by katello-installer instead of being grabbed via dependencies:

[ERROR 2014-11-11 22:38:57 main]  Execution of '/usr/bin/yum -d 0 -e 0 -y install python-crane' returned 1: This system is not registered with RHN Classic or RHN Satellite.
[ERROR 2014-11-11 22:38:57 main]  /Stage[main]/Crane::Install/Package[python-crane]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install python-crane' returned 1: This system is not registered with RHN Classic or RHN Satellite.
[ERROR 2014-11-11 22:38:57 main]  Execution of '/usr/bin/yum -d 0 -e 0 -y install qpid-cpp-client-devel' returned 1: This system is not registered with RHN Classic or RHN Satellite.
[ERROR 2014-11-11 22:38:57 main]  /Stage[main]/Qpid::Client::Install/Package[qpid-cpp-client-devel]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install qpid-cpp-client-devel' returned 1: This system is not registered with RHN Classic or RHN Satellite.

If these packages were proper depdencies of the products, such an upgrade would work -- yum upgrade would capture the new packages, and the katello-installer would be able to run while katello itself is not started.

Related issues 1 (0 open — 1 closed)