OOPS-1679X514 No usable OpenID services found

I don't know what you are doing wrong; I haven't seen this or heard of it.

Do you have openid.launchpad.dev, ubuntu-openid.launchpad.dev and testopenid.dev all in your /etc/hosts (on the machine or VM that has the browser you are using) pointing to the LP virtual machine (locally, typically)?

The oops number doesn't really help us. You could look at it by looking in /var/tmp/lperr/[DATE]/[OOPS ID SUFFIX] on your VM. For instance, if the OOPS id were OOPS-1679X514 and it happened on Aug 6, you would look for

/var/tmp/lperr/2010-07-30/[NUMBER].X514 where [NUMBER] is unimportant in this context.

I suspect that's not going to be much help either, TBH, but it's worth a try.

Those 3 URLs are in both my VM's /etc/hosts file and my Windows hosts file. openid.lp.dev and ubuntu-openid.lp.dev return a page not found error if you try to go to them directly.

Also that file you said look up didn't provide any more relevent info that what I've posted. The same OPPS code, the fact that it was DiscoveryFailure, nothing new here.

Perhaps I should add that I was using a Maverick build to run all this.

Ah, Maverick, OK. We will be working to support Maverick soon, but we're not there yet. If you can dupe now on Lucid, please reply. Otherwise, maybe we'll encounter this when we start developing LP on Maverick--we'll need that working in September.

Ok..after spending most of the day building a new Lucid VM to test LP, I still get the same error. "No usable OpenID services at testopenid.dev"

I'm sorry.

Do you get the same error if you use a browser within Ubuntu, rather than in Windows?

Well, the VMs I've been working in have all been command line only Ubuntu. No X or GNOME is installed. Using Lynx, on the VM I get the same error, only this time with a link to disable redirection. And outside the VM on my physical Ubuntu install, I get the error again minus the aforementioned link.

Can you paste the content of the OOPS file in https://paste.ubuntu.com. It might have other information (like a traceback) that will help us debug this.

Also, can you see what the following command gives on your VM?

$ curl -k --header "accept: application/xrds+xml" https://testopenid.dev

It should return something like this:
<?xml version="1.0"?>
<xrds:XRDS xmlns="xri://$xrd*($v*2.0)"
           xmlns:xrds="xri://$xrds">
  <XRD>
    <Service priority="0">
      <Type>http://specs.openid.net/auth/2.0/server</Type>
      <URI>https://testopenid.dev/+openid</URI>
    </Service>
  </XRD>
</xrds:XRDS>

But in your case it will probably redirect to launchpad.dev, just like what happens when you point your browser to testopenid.dev.

You might also want to add a breakpoint at the top of XRDSContentNegotiationMixin.render() in lib/lp/services/openid/browser/openiddiscovery.py and stepping through the code to see where it's redirecting you to launchpad.dev.

If this doesn't allow us to figure out exactly what's going on, it should at least help us finding out where to look next.

http://pastebin.ubuntu.com/479470/ << Theres the OOPS.

Could this possibly be an Apache config issue? I mean, if I go to https://testopenid.dev/+openid directly I get a 503 error.

I'll be honest, I don't know much about Python so setting breakpoints on a Python file is bit beyond me. I'm more of a offline app developer than anything.

A simple explanation of how to set a python breakpoint or what tool I'd use to do such is all I'd need.

Oh and applogies for the 2nd comment here..but running the curl command you provided above also redirects as expected.

You just need to add a 'import pdb; pdb.set_trace()' where you want, kill the process and start again (make run).
(If you prefer you can apply this patch instead of doing the change manually: http://paste.ubuntu.com/479586/ and restart as above)

Now when you hit the login button, the terminal where you ran 'make run' will drop at the pdb (python debugger) prompt, where you can step through the statements (http://docs.python.org/library/pdb.html).

If that doesn't help us find out what's going on, I suggest you join #launchpad-dev on irc.freenode.net and look for myself (salgado), although somebody should be able to help you there if I'm not around. The next thing I'd suggest is to add a breakpoint at LaunchpadBrowserResponse.render() in lib/canonical/launchpad/webapp/servers.py because that's what will actually perform the redirect. From there you'd have to go u(p) to see what called it, so it will certainly be easier to do that on IRC.

Ok, at the advice of someone on IRC, I reset my apache config back to the normal, after changing it to allow remote access, and lo and behold it works.