Project

General

Profile

Actions

Bug #21670

closed

Allow non-RH hosts to NOT have content views

Added by Daniel Lobato Garcia about 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Hosts
Target version:
Difficulty:
Triaged:
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).

Actions #1

Updated by The Foreman Bot about 7 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Daniel Lobato Garcia
  • Pull request https://github.com/Katello/katello/pull/7064 added
Actions #2

Updated by Justin Sherrill about 7 years ago

  • Translation missing: en.field_release set to 329
Actions #3

Updated by Anonymous about 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #4

Updated by Andrew Kofink over 6 years ago

  • Has duplicate Bug #23457: Running bootstrap fails: Content view can't be blank added
Actions #5

Updated by Andrew Kofink over 6 years ago

  • Has duplicate deleted (Bug #23457: Running bootstrap fails: Content view can't be blank)
Actions

Also available in: Atom PDF