Strange issues using Launchpad OpenID

[Paul Sokolovsky]

From mail:

[] it seems that we face an
epidemic of broken Launchpad OpenID access on devel systems. I first saw
that on http://staging.patches.linaro.org/ . I asked Milo about it, and
he said that maybe patches.l.o required special treatment from
Launchpad, which hence doesn't work on staging.*. Well, we didn't pay
too much attention, because purpose of staging.patches.linaro.org is to
test Crowd migration (it now runs off Crowd, so Launchpad issue is not
reproducible).

But today I started testing my Ansible android-build deploy, and faced
the issues that OpenID fails with "OpenID failed/Unknown user". I of
course thought that maybe it's some issue with new setup, fired all
shell-based sandbox setup, known to work, and got the same issue at the
end.

[Paul Sokolovsky (pfalcon)]

Why this "important" (in a sense "has some importance level"): 1) even though we mostly switched to Crowd, LP OpenID is still default config for few systems, which is useful for development, as it requires zero config (unlike Crowd which requires credentials); 2) there's ongoing talk that LAVA is not happy to be switched to Crowd, because Crowd is "Linaro only" and LP OpenID is "open". If there're any access restrictions regarding LP OpenID, we should know that for planning (note: I don't that's it, likely a technical issues, but risk management).

[Milo Casagrande (milo)]

Due to the age of this issue, we are acknowledging that this issue will likely not be fixed, is no longer applicable, or was already fixed by an indirect change. If this issue is still important, please add details and reopen the issue using http://bugs.linaro.org.