Bug 491379 - scheduler keeps rescheduling the same package even after a successful build
Summary: scheduler keeps rescheduling the same package even after a successful build
Status: NEW
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: BuildService (show other bugs)
Version: unspecified
Hardware: x86-64 SLES 10
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: craig gardner
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-02 05:59 UTC by Srinidhi B S
Modified: 2014-03-28 21:47 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Srinidhi B S 2009-04-02 05:59:06 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7

In our local OBS instance, even after a package has been built successfully, the same package gets scheduled once again for rebuild. This happens usually when one of the dependencies have updated in the full tree

Reproducible: Always

Steps to Reproduce:
1. Update a package in full-tree
2. One of the packages get scheduled to build
3. Build succeeds
4. Look up the status of the package - scheduled
Comment 2 Dominique Leuenberger 2009-04-02 08:55:21 UTC 
I've seen this behavior on my own OBS too.
Mainly I see it against the only Repo I have linked in using remoteURL: Factory (the others are DoD). I've already let it run for 2 days and it would not resolve it. Restarting the scheduler then gave me the entire project, built against Factory in scheduled mode. So it might be linked to the fact when big changes in the project to build against happen.
Comment 3 Michael Schröder 2009-04-06 09:57:49 UTC 
Those re-schedules also happen if the metadata of a project doesn't match the rpm data for some reason. I'm afraid I can't help you much without access to the build service. Sending "rescan" events (bs_admin --rescan-repository) for the repositories in question (i.e. the ones containing "CASA") might help.
Comment 6 Adrian Schröter 2009-04-27 06:44:18 UTC 
Please give us the output of the "_reason" files in build dir.
There are most likely md5sum changes listed inside. Please check to which packages do these md5sums match.
Comment 7 Michael Schröder 2009-04-27 08:55:49 UTC 
Adrian, do not reassign...
Comment 10 Adrian Schröter 2010-06-23 06:49:09 UTC 
I am a bit puzzeled here. I thought you run OBS 1.6, but you have the reason file already ?

What version do you run on ?

Would be nice, if you can upgrade to 2.0.x and verify your problem. The binary data handling is about to get rewritten for 2.2 release, so we can maybe solve your problem better then.
Comment 11 craig gardner 2010-09-24 16:11:13 UTC 
Srinidhi, will you please give Adrian the info he requested in comment #10?

Maybe this problem doesn't exist anymore with the latest code.
Comment 13 Srinidhi B S 2010-10-11 14:45:01 UTC 
Sorry about the delay in responding!

After updating BBS to 2.0.5, I haven't seen this issue so very often. But I do have a small problem. Whenever I trigger a rebuild of a package, the entire dependency tree gets scheduled for rebuild - thus blocking the package that I wanted to rebuild!

This has been an observation. I tried looking at the <reason> tag in 'osc buildinfo' and I have always seen "meta change" - but it does not list the packages for which the metadata changed.