Red Hat Bugzilla – Bug 982658
Application records in mongo seem to have gotten broken.
Last modified: 2015-05-14 20:18:45 EDT
Description of problem:
On Wednesday 07/03 I created application mydiy-sosiouxme specifying a cartridge to download:
rhc app create mydiy "http://cartreflect-claytondev.rhcloud.com/reflect?github=sosiouxme/diy-extra-port-cartridge&commit=ssl-hack" --no-git --no-dns
It was created and I proceeded to add an IRC proxy to it and use it as such since then by forwarding the port. I have been doing this daily and didn't make any other changes since then.
This morning I tried rhc port-forward on it and received an error. Even doing "rhc apps" gets me an error.
No idea, this is the only instance seen so far AFAIK, and it took nearly a week to manifest.
Adding --debug tells me the port forward is failing like so:
DEBUG: Request GET https://openshift.redhat.com/broker/rest/domains/sosiouxme/applications/mydiy
DEBUG: code 500 45 ms
DEBUG: Response did not include a message from server: invalid character at "<!DOCTYPE "
The server did not respond correctly. [...]
On "rhc apps" I get a similar result for:
DEBUG: Request GET https://openshift.redhat.com/broker/rest/domains/sosiouxme/applications?include=cartridges
BTW, I can continue to ssh into the gear and port-forward manually. It is still there and working. I just can't access it via the broker and given that "rhc apps" is broken it's kind of a nuisance for other apps I own too, which is why I thought it's high severity in case anyone else runs into this.
Broker access should work exactly like it did each day before now :)
This is not an important app. I authorize whatever looking around or adjustment is needed for debugging, up to and including deleting it. I'm thinking there is at least a 50% chance that me deleting it would work and fix my issue, but that wouldn't be a good solution for most.
Can you please verify if your application is now fixed?
*** This bug has been marked as a duplicate of bug 982436 ***
Looks good, thanks :)