Project

General

Profile

Actions

Bug #9670

closed

[RFE] Content hosts -> Errata tab: Add helptext to inform Applicable errata cannot be applied

Added by Walden Raines about 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Web UI
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1194773
Description of problem:
Content hosts -> Errata tab: Add helptext to inform Applicable errata cannot be applied

Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150217.0

How reproducible:
Always

Steps to Reproduce:
1. Upload a manifest, sync a repo (with errata)
2. Create multiple environments say Library -> QE
3. Create content view (cv3) and make sure Library has more errata than QE environment
4. Register a content host to QE environment

Actual results:
Go to Content host > Errata tab
1. Select Current Environment (QE/cv3) - shows 'Installable errata'.
- 2. Select Previous Environment (Library/cv3) - shows 'Applicable errata'
- 3. Select Library Synced Content - shows 'Applicable errata'

For scenarios 2 and 3 above, I am not able to actually install errata as part of Incremental updates. I learnt later that Incremental Updates can be applied only from Content -> 'Errata'

Expected results:
For scenarios 2 and 3 above, make it obvious to the user that these are not installed by
- Adding clear help text that this is view only and install of these errata can be done only from Content > Errata page.
greying out errata selection options
and anything else which is necessary

Additional info:

Actions #1

Updated by The Foreman Bot about 9 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 67
  • Pull request https://github.com/Katello/katello/pull/5085 added
  • Pull request deleted ()
Actions #2

Updated by Eric Helms about 9 years ago

  • translation missing: en.field_release set to 31
  • Triaged changed from No to Yes
Actions #3

Updated by Walden Raines about 9 years ago

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

Also available in: Atom PDF