Feature #21679: Alter foreman-maintain for use with Foreman upgrades - Foreman Maintain - Foreman

Actions

Copy link

Feature #21679

closed

Alter foreman-maintain for use with Foreman upgrades

Added by Brad Buckingham over 6 years ago. Updated 2 months ago.

Status:

Rejected

Priority:

Normal

Assignee:

Category:

Target version:

Difficulty:

medium

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

The following tooling has been introduced:
https://github.com/theforeman/foreman_maintain

It seems like it would be worthwhile to move toward using it as part of the katello upgrade process. In doing so, we can/should remove anything that is redundant. E.g:
https://github.com/Katello/katello/blob/master/lib/katello/tasks/upgrade_check.rake

Actions

Copy link

Updated by Justin Sherrill over 6 years ago

to update:

Docs
forklift: upgrade scenarios
remove code from katello that is no longer needed

Actions

Copy link

Updated by Justin Sherrill over 6 years ago

Category set to Documentation
translation missing: en.field_release set to 284
Difficulty set to easy

Actions

Copy link

Updated by John Mitsch about 6 years ago

translation missing: en.field_release changed from 284 to 352

Actions

Copy link

Updated by Andrew Kofink almost 6 years ago

foreman-maintain 0.0.3 is packaged with Foreman 1.16. It seems like we need to update the 1.16 repo before we can use foreman-maintain for upgrade to 1.17. It doesn't even do the upgrade check properly on 1.16, and the `upgrade run` subcommand doesn't exist.

Actions

Copy link

Updated by Andrew Kofink almost 6 years ago

Tracker changed from Bug to Feature
Subject changed from Utilize foreman-maintain for upgrades to Alter foreman-maintain for use with Foreman upgrades
Category changed from Documentation to Upgrades
translation missing: en.field_release deleted (~~352~~)
Difficulty changed from easy to medium

foreman-maintain is a tool for upgrading Satellite (downstream Foreman+Plugins). It's currently published in the Foreman repositories, even though it's not useful with Foreman. There are a few things to consider:

1. Should we (a) remove Satellite stuff from foreman-maintain and (b) create a separate satellite-maintain (b is outside the scope of this upstream issue)?
2. We need to alter foreman-maintain to work with Foreman + (optional) Plugins

This seems like an application-wide scope rather than plugin-specific, so I'm also moving this to the Foreman project.

Actions

Copy link