Bug 1010449 - sometimes sat-sync does not import kickstart trees to the database
Summary: sometimes sat-sync does not import kickstart trees to the database
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 560
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat560-triage
TreeView+ depends on / blocked
 
Reported: 2013-09-20 19:31 UTC by Stephen Herr
Modified: 2013-10-09 20:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-09 20:23:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Stephen Herr 2013-09-20 19:31:05 UTC
Description of problem:
Sometimes when you do a satellite-sync to pull in new base channels the kickstart trees are synced to disk but not imported to the database (or maybe the webui results are being cached). I don't know what causes the trees to import sometimes and what causes them to not. If you restart satellite they are visible.

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

How reproducible:
sometimes

Steps to Reproduce:
1. satellite-sync a base channel
2. systems -> kickstarts -> profiles -> create new kickstart profile

Actual results:
no trees are listed as available in your base channel

Expected results:
trees are available

Additional info:
A very similar thing was reported before and fixed as bug 240137.

Comment 4 Stephen Herr 2013-10-09 20:23:02 UTC
After a bunch of code inspection and various attempts at reproducing, I have concluded that the problem must have been that Taskomatic was not running. The UI actually gets the list of available kickstart trees from cobbler, so if the cobbler-sync Taskomatic task has not run since your satellite-sync has finished you will not see the kickstart trees.

As such, I will close this as not a bug.


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