Bug 786495 - resync of updated repo does not show updated packages (size, cnt)
Summary: resync of updated repo does not show updated packages (size, cnt)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-01 15:25 UTC by Garik Khachikyan
Modified: 2019-09-26 13:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:24:12 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Garik Khachikyan 2012-02-01 15:25:59 UTC
Description of problem:
In the katello/sync_management/index there is not getting updated the info about resynced repo/product.

Version-Release number of selected component (if applicable):
katello-0.1.209-1.git.0.6ff9c30.el6.noarch
katello-cli-0.1.49-1.git.0.6962a71.el6.noarch
pulp-0.0.263-1.el6.noarch
candlepin-0.5.8-1.el6.noarch


How reproducible:
Always doing resync of updated repo

Steps to Reproduce:
1. prepare a repo (let say locally created repo (via createrepo)). url is: "file:///tmp/katello-local" let's say
2. sync that repo (fix the size, count information) through UI
3. apply some new rpms to that /tmp/katello-local  (copy them to that folder just)
4. run: `createrepo /tmp/katello-local`
5. go to UI and resync the repo again
6. logout/login and go to the sync page again. Info about size/cound does not changes.
  
Actual results:
size and count of packages remains unchanged 

Expected results:
Should be updated properly. CLI works better: `katello repo status` provides correct number of packages 

Additional info:

Comment 3 Mike McCune 2012-03-07 23:43:02 UTC
mass move ON_QA after brewing

Comment 4 Corey Welton 2012-03-15 18:37:09 UTC
QA Verified.

Comment 6 Mike McCune 2013-08-16 17:50:49 UTC
getting rid of 6.0.0 version since that doesn't exist


Note You need to log in before you can comment on or make changes to this bug.