It's all about the answers!

Ask a question

Cannot deliver a baseline for a component


Duncan Lilly (66104) | asked Apr 04 '10, 6:19 a.m.
Our nightly build (command line driven use of RTC; not using the RTC build system) has started bombing out with an error:

Problem
An error occurred during "Deliver".

Can not update an item that has already been deleted from the configuration. config id = ; item id = ; item name = 'null'


Nothing has changed at our end and it was working fine on Friday morning; but has failed the last two nights.

Some investigation has narrowed it down to a single component. If I use the RTC client I can deliver the changeset from within the baseline - but if I try to deliver a baseline (even a new one created in the client) I get the error message.

Any suggestions?

3 answers



permanent link
Geoffrey Clemm (30.1k33035) | answered Apr 04 '10, 9:22 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
One initial comment: something like this is pretty clearly a bug (at a
minimum, the error message needs to be improved, if this really is a
user error), so you'd want to file a bug report when you first encounter
it, either with IBM support or directly as a work item on jazz.net. I
did a quick search on jazz.net, and didn't find a work item for this
(but it was a very quick search, so I may have missed it).

Submitting a bug to the forum like this is also then reasonable, both as
a head's up to other users, as well as a way of getting a work around
from other folks that may have encountered it (although ideally, those
other folks would have filed a bug report, so the problem and any
workarounds would already be documented and available on jazz.net).

Cheers,
Geoff

DuncanL wrote:
Our nightly build (command line driven use of RTC; not using the RTC
build system) has started bombing out with an error:

Problem
An error occurred during "Deliver".

Can not update an item that has already been deleted from the
configuration. config id = ; item id =
; item name = 'null'; item id = ; item name = 'null'


Nothing has changed at our end and it was working fine on Friday
morning; but has failed the last two nights.

Some investigation has narrowed it down to a single component. If I
use the RTC client and suspend the changeset, I can deliver it - but
If I create a baseline and try to deliver that I get the error
message.

Any suggestions?

permanent link
Duncan Lilly (66104) | answered Apr 06 '10, 4:32 a.m.
One initial comment: something like this is pretty clearly a bug (at a
minimum, the error message needs to be improved, if this really is a
user error), so you'd want to file a bug report when you first encounter
it, either with IBM support or directly as a work item on jazz.net. I
did a quick search on jazz.net, and didn't find a work item for this
(but it was a very quick search, so I may have missed it).

Submitting a bug to the forum like this is also then reasonable, both as
a head's up to other users, as well as a way of getting a work around
from other folks that may have encountered it (although ideally, those
other folks would have filed a bug report, so the problem and any
workarounds would already be documented and available on jazz.net).

Thanks - it was the Bank Holiday weekend so I didn't want to spend too much of my holiday working on it - just get it out for the users and developers in other parts of the world (who weren't on holiday! :) ) to see; but I have now filed a bug. Hopefully someone can give us a quick solution.

permanent link
Duncan Lilly (66104) | answered Apr 07 '10, 4:24 a.m.
For future reference of anyone finding this topic via a search:

The problem was caused by a user locking a file that was not stored in RTC from the Pending Changes view. This created "<unknown>" locks that were not visible from anywhere except the Locks search view. The original creator could unlock the non-existent files and then the baseline could be delivered.

This is a known bug and will apparently be fixed in RTC 3.

Your answer


Register or 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.