Red Hat Bugzilla – Bug 1463694
BUG: unable to persistently delete the pcmoore / module-testmodule-master-20170509201446 project
Last modified: 2017-10-02 11:00:29 EDT
Description of problem:
Despite deleting the pcmoore / module-testmodule-master-20170509201446 project multiple times, it keeps reappearing when I login to COPR.
Every ten minutes, there is an attempt to create the project:
18.104.22.168 - - [18/Jun/2017:11:45:48 +0000] "POST /api/coprs/pcmoore/module-testmodule-master-20170509201446/module/make/
Usually this ends up in 500 fatal error because a project with the same name already exists but if you delete it, then it is recreated again.
Any chance you have setup a cron script to auto-create the project? The script is running somewhere but the question is where.
Actually, you are not the only one who has got this problem. That probably means there is something quite off with project creation logic for "modules".
My apologies, for some reason I never received notification emails for your above comments.
To answer your question from comment #1, no there is no cron job or any similar process which is set to (re)create the project; although it looks like you may have found a possible root cause in comment #2. Any updates?
(In reply to Paul Moore from comment #3)
> My apologies, for some reason I never received notification emails for your
> above comments.
> To answer your question from comment #1, no there is no cron job or any
> similar process which is set to (re)create the project; although it looks
> like you may have found a possible root cause in comment #2. Any updates?
This is a bug in COPR<->MBS integration. That's all I can tell. I will try to reassign it to somebody who might know more.
Hi Jakub, any ideas as to what the problem might be?
I tried deleting the COPR repository again, the problem still persists. Help?
So I've marked the module as failed. It shouldn't create the project anymore. Paul, can you please try to delete it once more?
@clime, just for the record, I did this on MBS database
>> select id, state from module_builds where name='testmodule' and stream='master' and version=20170509201446;
The id was 19 and state was 2, which means that build is in progress. It shouldn't have since one of it's components failed.
>> update module_builds set state=4, state_reason='Manually killed' where id=19;
I just deleted the project, let's see if it sticks this time ...
It's been a couple of weeks and the project hasn't been recreated so I think we can consider this fixed. Thanks for your help!