Bug #21670: Allow non-RH hosts to NOT have content views - Katello - Foreman

Bug #21670

Allow non-RH hosts to NOT have content views

Added by Daniel Lobato Garcia about 4 years ago. Updated over 3 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Daniel Lobato Garcia

Category:

Hosts

Target version:

Katello 3.5.1

Difficulty:

Triaged:

Bugzilla link:

Pull request:

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

Fixed in Releases:

Found in Releases:

Description

Currently the Content View and Lifecycle Environment are fields of a Content Facet. These fields have a NOT-NULL constraint, so they are validated on every host. This means that if I'm trying to create a CentOS, or Debian host, it will ask for a Content View and Lifecycle - which I may not want for hosts that don't use subscription-manager.

In fact for the CentOS case, it's harmful: having a Content View for a CentOS host changes the @mediapath variable (the parameter sent to --url in the kickstart) to point to Pulp, which means you're pointing to Red Hat and installing Red Hat instead of CentOS (unless you've synced CentOS).

Associated revisions

Revision 405a1bc7 (diff)
Added by Daniel Lobato Garcia about 4 years ago

Fixes #21670 - Allow non RH hosts to NOT have content views

Currently the Content View and Lifecycle Environment are fields of a
Content Facet. These fields have a NOT-NULL constraint, so they are
validated on every host. This means that if I'm trying to create a
CentOS, or Debian host, it will ask for a Content View and Lifecycle -
which I may not want for hosts that don't use subscription-manager.

In fact for the CentOS case, it's harmful: having a Content View for a
CentOS host changes the @mediapath variable (the parameter sent to --url
in the kickstart) to point to Pulp, which means you're pointing to
Red Hat and installing Red Hat instead of CentOS (unless you've synced
CentOS).