Mailinglist Archive: opensuse-buildservice (88 mails)

< Previous Next >
Re: [opensuse-buildservice] How to ensure consistency for the "deleted" project? ("rails fix_project project=deleted" fails)
Hello Adrian,

On Wed, 2020-02-19 at 09:10 +0100, Adrian Schröter wrote:

yes, right way ...


Danke!


When I run check_project, I get:

$ run_in_api rails check_project project=deleted
Project deleted lost on backend

that should not have happened ...


I thought so too.

You need to recover it on the backend, you can do so from your api server via

curl -X POST $src_server:$port/source/deleted?cmd=undelete


$ curl -s -X POST http://build:5352/source/deleted?cmd=undelete
<status code="404">
<summary>project 'deleted' is not deleted</summary>
<details>404 project 'deleted' is not deleted</details>
</status>

Do I have to create this project? Also, /srv/obs/projects/_deleted/deleted.pkg
does not exist on the backend.

You should be fine afterwards. But have a look who deleted that project
(and that without to do so in api).


I can't figure this part out. API returns the project details:

$ osc api /source/deleted
<directory count='0'>
</directory>

$ osc meta prj deleted
<project name="deleted">
<title/>
<description/>
<repository name="standard"/>
<repository name="deleted"/>
</project>

But trying to check the history of the project returns an error:

$ osc log -M deleted
Server returned an error: HTTP Error 404: project 'deleted' does not exist
project 'deleted' does not exist

$ osc log -M -D deleted
Server returned an error: HTTP Error 404: Not Found
deleted

Output does not change if I remove the "-M" option.

Am I in more trouble than I had initially imagined?

Regards,
Srinidhi.N�����r��y隊Z)z{.����Wlz��qﮞ˛���m�)z{.��+�:�{Zr�az�'z��j)h����Ǜ�)]����Ǿ�
ޮ�^�ˬz��
< Previous Next >