On Montag, 25. Januar 2016, 02:33:40 CET wrote Neal Gompa:

On Mon, Jan 25, 2016 at 2:17 AM, Adrian Schröter wrote:

...

On Samstag, 23. Januar 2016, 14:53:41 CET wrote Neal Gompa:

...

Hello,

On Thursday, I set up a new instance of OBS, expecting for it to be as functional as all the previous ones I had before. However, I wound up being unable to build anything with it, because all the build targets don't work. The error it reports is "The repository setup is broken, build not possible".

After quite a bit of digging, I found out that api.opensuse.org/public is returning HTTP 404 errors, which I believe is preventing my OBS

You may have not used httpS ? /public should given you a 302 redirection.

Better try something like

https://api.opensuse.org/public/about

...

instances from configuring and building packages.

I'm running OBS Unstable, but I've also verified the problem with OBS 2.6.7 as well.

The openSUSE.org linker project is configured as such:

<project name="openSUSE.org"> <title>Standard OBS instance at build.opensuse.org</title> <description>This instance delivers the default build targets for OBS.</description> <remoteurl>https://api.opensuse.org/public</remoteurl> </project>

It is using https, and this is the default configuration that OBS sets up with. https://api.opensuse.org/public/about also returns a 404 error.

k, I see that this route got broken latelty. However, it is not an important one. Is https://api.opensuse.org/public/source/openSUSE:Tools/ working?

-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Montag, 25. Januar 2016, 02:51:22 CET wrote Neal Gompa:

On Mon, Jan 25, 2016 at 2:48 AM, Adrian Schröter wrote:

...

On Montag, 25. Januar 2016, 02:33:40 CET wrote Neal Gompa:

...

On Mon, Jan 25, 2016 at 2:17 AM, Adrian Schröter wrote:

...

On Samstag, 23. Januar 2016, 14:53:41 CET wrote Neal Gompa:

...

Hello,

On Thursday, I set up a new instance of OBS, expecting for it to be as functional as all the previous ones I had before. However, I wound up being unable to build anything with it, because all the build targets don't work. The error it reports is "The repository setup is broken, build not possible".

After quite a bit of digging, I found out that api.opensuse.org/public is returning HTTP 404 errors, which I believe is preventing my OBS

You may have not used httpS ? /public should given you a 302 redirection.

Better try something like

https://api.opensuse.org/public/about

...

instances from configuring and building packages.

I'm running OBS Unstable, but I've also verified the problem with OBS 2.6.7 as well.

The openSUSE.org linker project is configured as such:

<project name="openSUSE.org"> <title>Standard OBS instance at build.opensuse.org</title> <description>This instance delivers the default build targets for OBS.</description> <remoteurl>https://api.opensuse.org/public</remoteurl> </project>

It is using https, and this is the default configuration that OBS sets up with. https://api.opensuse.org/public/about also returns a 404 error.

k, I see that this route got broken latelty. However, it is not an important one. Is

https://api.opensuse.org/public/source/openSUSE:Tools/

working?

No, that's broken too. HTTP 404.

Can you please check with curl -v https://api.opensuse.org/public/source/openSUSE:Tools/ who is giving the 404 to you? It just works for me from different IPs .. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Patrick Shanahan writes:

* Adrian Schröter [01-25-16 03:35]: [...]

...

Can you please check with

curl -v https://api.opensuse.org/public/source/openSUSE:Tools/

who is giving the 404 to you?

It just works for me from different IPs ..

This works for me, but 6 different browsers give me 404's

That's ok, try https://api.opensuse.org/public/source/openSUSE:Tools/?format=xml instead. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

I had to remove my remote link to opensuse.org because of this issue. Any project which included it in search paths hung forever on my private 2.4 instance. (Yes, I know I need to upgrade. It's on the list. :) ) It was definitely working fine up until a few days ago. -Matt On Mon, 2016-01-25 at 14:41 +0100, Adrian Schröter wrote:

On Montag, 25. Januar 2016, 08:27:31 CET wrote Patrick Shanahan:

...

* Adrian Schröter [01-25-16 03:35]: [...]

...

Can you please check with

curl -v https://api.opensuse.org/public/source/openSUSE:Tools/

who is giving the 404 to you?

It just works for me from different IPs ..

This works for me, but 6 different browsers give me 404's

ah, do not use a web browser. The rails code is switching then to webui mode and that one can not handle /public at all...

--

Adrian Schroeter email: adrian@suse.de

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

Maxfeldstraße 5 90409 Nürnberg Germany

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

On Montag, 25. Januar 2016, 11:25:53 CET wrote Neal Gompa:

On Mon, Jan 25, 2016 at 8:45 AM, Matthew Drobnak wrote:

...

I had to remove my remote link to opensuse.org because of this issue. Any project which included it in search paths hung forever on my private 2.4 instance. (Yes, I know I need to upgrade. It's on the list. :) )

It was definitely working fine up until a few days ago.

It was really bad timing for me, as I was preparing to show off the system internally for wider adoption.

We enforce the authentification for all routes beside /public some days ago. But that should have no effect on your interconnect, _if_ you are using /public. You need to tell me which requests may hung. Check in src and scheduler logs in /srv/obs/log/ . -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Mon, Jan 25, 2016 at 12:23 PM, Matthew Drobnak wrote:

I was definitely using /public, and it definitely broke.

This was the Meta:

<project name="openSUSE.org"> <title>Standard OBS instance at build.opensuse.org</title> <description>This instance delivers the default build targets for OBS.</description> <remoteurl>https://api.opensuse.org/public</remoteurl> <person userid="Admin" role="bugowner"/> <person userid="Admin" role="maintainer"/> </project>

The logs have already rotated away, sorry. I was referring to local builds hanging, as they had opensuse.org at the end of the repository search path.

-Matt

I managed to fix it by editing the meta in each project. I deleted the repository targets, saved, and then re-added them and saved again. It forced OBS to regenerate everything and suddenly stuff starts working again... -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org