Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

BF Cannot Purge Jobs with Owner "System"

I have a number of jobs for which the Owner is now "System". I have no idea how the owner got to be "System" but those particular jobs cannot be purged. They sit in the State of "Waiting to Purge". And the server logs show an "API: Permission Denied: PurgeBuild" error for that particular build id. This also blocks other jobs from being purged.

If I cancel the purge and look at the job step logs I can see that the BF_USER that ran the job originally is no longer a valid user. Perhaps this is why the Owner has been moved to "System".

So how do I purge jobs owned by "System"?

--Jeff

0 votes



2 answers

Permanent link
Hello,

This is a known defect that has been resolved under Build Forge 7.1.2.2.

NULL bf_builds.bf_user_id builds are not purgable
https://jazz.net/jazz08/web/projects/Rational%20Build%20Forge#action=com.ibm.team.workitem.viewWorkItem&id=19619

The issue is caused under builds that have been set to "System" are attempting to purge the build as the user "System", which is an invalid user.

To workaround the issue, you can update the build entries via the database directly to re-assign the builds to a valid user such as root.

**Before modifying the database directly, it is recommend to perform a backup of the database and shutting the Build Forge console down.**

The following query can be used to update the offending build entries to be owned by the Build Forge root user.
Afterwards, the builds should purge normally.

UPDATE bf_builds SET bf_user_id='1' WHERE bf_user_id IS NULL;

0 votes


Permanent link
Thanks for the feedback. We have taken this approach and it is working for us. I think we are upgrading to 7.1.3 1Q 2012.

--Jeff

Hello,

This is a known defect that has been resolved under Build Forge 7.1.2.2.

NULL bf_builds.bf_user_id builds are not purgable
https://jazz.net/jazz08/web/projects/Rational%20Build%20Forge#action=com.ibm.team.workitem.viewWorkItem&id=19619

The issue is caused under builds that have been set to "System" are attempting to purge the build as the user "System", which is an invalid user.

To workaround the issue, you can update the build entries via the database directly to re-assign the builds to a valid user such as root.

**Before modifying the database directly, it is recommend to perform a backup of the database and shutting the Build Forge console down.**

The following query can be used to update the offending build entries to be owned by the Build Forge root user.
Afterwards, the builds should purge normally.

UPDATE bf_builds SET bf_user_id='1' WHERE bf_user_id IS NULL;

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Oct 21 '11, 12:58 p.m.

Question was seen: 8,393 times

Last updated: Oct 21 '11, 12:58 p.m.

Confirmation Cancel Confirm