Bug 246480
| Summary: | sync last_modified dates correctly for ks trees instead of defaulting to current date | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Pradeep Kilambi <pkilambi> |
| Component: | Satellite Synchronization | Assignee: | Jan Pazdziora <jpazdziora> |
| Status: | CLOSED ERRATA | QA Contact: | Šimon Lukašík <slukasik> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | cperry, jpazdziora, kbaxley, mzazrivec, tao, vgaikwad |
| Target Milestone: | --- | Keywords: | Reopened, Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | sat510 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-03-22 12:04:31 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: | 328271 | ||
| Bug Blocks: | 531600 | ||
|
Description
Pradeep Kilambi
2007-07-02 16:20:25 UTC
not a very high priority/blocker IMO, this bug fits well with the Enhancements we're planning for rhn-sat-exporter tool for 520. Investigating further, looks like we don't export last_modified from hosted. So for us to include the right KickstartTree last_modified date field into sat's rhnKickstartTree table, we need this date to be first exported by hosted satellite exporter. I opened a bug(bz#328271) for hosted to add this to the exporter. Once thats done, we can grab the last_modified from the xml stream and populate db with correct values. https://bugzilla.redhat.com/show_bug.cgi?id=328271#c1 Comment #1 From James Bowes (jbowes) on 2007-10-17 19:55 EST [reply] Private Data is sent, but as last-modified rather than last_modified Looks like even though the data is sent as a different key, looks like the satsync was never written to handle last_modified dates for kickstart-trees and hence there seems to be no validation for the last-modified dates verses the the timestamps. So we pretty much need to rewrite rhnKickstartTreeCollection and Container classes. I would say we could scope this for next release if we're short on time. After discussing with cliff, moving to sat-5.2 .. Moving to sat-channel-dumps tracker. Agree we should look to address this as part of the feature code changes needed to redo channel dump creation process. Cliff Fixed in Spacewalk master 460aad3e019c6fd064732aed14127d822d62217b. satellite.git: 9ee57b70a63c7fbdb3e46e8b4352cfbbd2681fb0 spacewalk-backend-0.5.28-40.1 Taking QA contact for the bug verification. spacewalk-backend-0.5.28-48 Verified against: (on rhel-i386-server-5-u4) spacewalk-backend-0.5.28-49.el5sat.noarch An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0160.html Although the errata fixing this particular issue is out, I'd like to point out two important things: 1) The updated packages won't update last_modified values that already exist in the database. This means, if the previous satellite-sync set these values incorrectly, new sync won't update these values. It will only be able to insert new correct values for newly synchronized kickstartable trees. 2) Due to bug #576222, even correctly set last_modified values will be overwritten when taskomatic executes CobblerSyncTask, which modifies existing rows in rhnKickstartableTree for use with cobbler (disabling this task may help, as long as cobbler functionality is not required). |