Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 214819

Summary: Satellite-sync NEEDS versioned caching!!!!!
Product: [Retired] Red Hat Network Reporter: John Wregglesworth <wregglej>
Component: RHN/BackendAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED NOTABUG QA Contact: Brandon Perkins <bperkins>
Severity: medium Docs Contact:
Priority: medium    
Version: rhn500CC: brian, rhn-bugs
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-20 20:07:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 471260    

Description John Wregglesworth 2006-11-09 16:59:29 UTC 
Description of problem: satellite-sync's caching isn't versioned. This causes an
issue where we have to manually remove the cache when the cache format changes.
What really needs to happen is that satellite-sync will detect when the version
of the cache changes and will automatically replace the cache as needed. This
will enable us to simplify the upgrade process a little bit.


Version-Release number of selected component (if applicable): All of them.


How reproducible: Always


Steps to Reproduce:
1. Upgrade rhns-server on a satellite.
2. ls -l /var/cache/rhn/
  
Actual results: /var/cache/rhn/ is wiped out.


Expected results: We should only wipe out /var/cache/rhn/ when the format of the
cache changes.


Additional info: I used capslock and multiple exclamation points just like I
said I would in IRC. :)
Comment 1 Mike McCune 2007-04-04 17:50:20 UTC 
moving to 510
Comment 2 Red Hat Bugzilla 2007-04-12 01:41:08 UTC 
User bnackash's account has been closed
Comment 5 Bill Nottingham 2009-02-27 16:23:15 UTC 
*** Bug 487604 has been marked as a duplicate of this bug. ***