Project

General

Profile

Actions

Bug #12673

closed

content-view inconsistency when creating errata exclude filter by date

Added by Partha Aji over 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Web UI
Target version:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1264729
Description of problem:
There is difference in content, when we are creating content view on day D with exclude filter F and another version published after the (D+n days) with exact same filter F. Ideally the content for both the version should be the same. As this is how customer maintain their environment like TEST/DEV/PROD baseline.

All of below mentioned Erratas are having change in 'Last updated on', which means 'Issued on' date is not same as 'Last updated on' date. So consider below scenario,

RHBA-2015-0005 :
Issued on: 2015-01-05
Last updated on: 2015-07-22

We created content view on or before '2015-01-05'(Issued on) with Errata exclude filter. The exclude filter excludes Erratas which are released after '2015-01-05'. This means I am including above Errata to content view. Without changing anything in filter I publish content view again on or after '2015-07-22'. As we have added new packages in same Errata now I have new versions of below packages in content view,

gdbm 1.8.0 37.el6
gdbm 1.8.0 38.el6

When maintaining package base lines these packages are not tested and even system updates to latest version because those are now available in content view. If I check spacewalk-clone-by-date utility of Satellite 5.x then it does provide option to consider 'Last updated on' instead of 'Issued on' date when creating clone channel, which may help in this case. On Satellite 6 how we can workaround this situation where we are updating Erratas itself with new packages and we don't want those new packages in content view ?

Version-Release number of selected component (if applicable):
6.1.0

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results: Additional package are present is new version.

Content

Expected results: Ideally the content for both the version should be the same which have created with same filter date.

Additional info:

Actions #1

Updated by Partha Aji over 8 years ago

Other comments:

We need to let the user choose between "Updated On" vs "Issued Date" when filtering errata

We should add the option, likely at the filter level. I think defaulting to 'updated on' makes the most sense, but we likely want to set all existing filters to 'issued at' to not break existing configured content views.

Actions #2

Updated by Partha Aji over 8 years ago

  • Assignee set to Partha Aji
Actions #3

Updated by The Foreman Bot over 8 years ago

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

Updated by The Foreman Bot over 8 years ago

  • Pull request https://github.com/Katello/hammer-cli-katello/pull/335 added
Actions #5

Updated by Eric Helms over 8 years ago

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

Updated by Partha Aji over 8 years ago

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

Also available in: Atom PDF