Project

General

Profile

Actions

Bug #23112

closed

Erratum page reports "There are no Content Views in this Environment" but there are

Added by Quirin Pamp about 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Errata Management
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

In the Interface, navigate to: Content > Errata > click on any Errata ID > Repositories tab
In the filter bar Area (under "Repositories containing <erratum_id>") it says "There are no Content Views in this Environment" and the drop down filter for Content Views is greyed out.
This is true for every erratum I looked at and irrespective of the Lifecycle Environment that is selected.
When I check under Content Views, various versions of the views containing the relevant repositories are promoted to various Lifecycle Environments.

I have seen this affect both SUSE errata and CentOS errata on different Foreman/Katello installations. (Katello versions 3.4.5 and 3.5.1.1).

Actions #1

Updated by John Mitsch about 6 years ago

  • Assignee set to Christine Fouant
Actions #2

Updated by Justin Sherrill about 6 years ago

  • translation missing: en.field_release set to 352
Actions #3

Updated by Christine Fouant about 6 years ago

  • Bugzilla link set to 1566186
Actions #4

Updated by Christine Fouant about 6 years ago

This is also reproducible in OSTree branch repositories tab.

Actions #5

Updated by The Foreman Bot about 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/7310 added
Actions #6

Updated by Christine Fouant about 6 years ago

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

Also available in: Atom PDF