Opened 12 years ago
Closed 12 years ago
#95 closed (fixed)
Aggregate details for ExoGENI/InstaGENI test data gives Internal Server error in the UI
| Reported by: | sedwards@bbn.com | Owned by: | pbohan@bbn.com |
|---|---|---|---|
| Priority: | major | Milestone: | gmoc.py data submission debugging |
| Component: | WebUI | Version: | |
| Keywords: | Cc: | ||
| Dependencies: |
Description
This link gives me an Internal Server error: https://gmoc-db2.grnoc.iu.edu/protected-openid/index.pl?method=aggregate_details;aggregate=http%3A%2F%2Fwww.example.com%2FexogeniTest
Change History (9)
comment:1 Changed 12 years ago by
| Milestone: | 2012-09-04 client release → gmoc.py data submission debugging |
|---|
comment:2 Changed 12 years ago by
comment:3 Changed 12 years ago by
Following up: for reverse-compatibility, it'd be nice to accept <fqdn> in addition to <fqdn>:<port>, but i don't feel strongly.
comment:4 Changed 12 years ago by
We also see the same Invalid Server error with instageni aggregate which is reporting Aggregate and Resource.
comment:5 Changed 12 years ago by
| Summary: | Aggregate details for ExoGENI test data gives Internal Server error in the UI → Aggregate details for ExoGENI/InstaGENI test data gives Internal Server error in the UI |
|---|
comment:6 Changed 12 years ago by
| Owner: | changed from somebody to pbohan@bbn.com |
|---|
comment:7 Changed 12 years ago by
In the morning let's discuss the id for Aggregates again and make sure we're doing this right.
comment:8 Changed 12 years ago by
For the record, my reference here is 67, which is where i think we decided to do <fqdn>:<port>.
comment:9 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I think this is fixed as long as the AM ID isn't a URL (which we no longer allow). We'll reopen if we see it again.
Incidentally:
http://www.example.com/exogeniTestisn't a valid name for an aggregate. It should be<fqdn>:<port>, per our agreement in 67. Maybe this should actually be being rejected, not displayed?