#7711 API access to fedorainfracloud.org tenant `copr` vs `coprdev`
Closed: Will Not/Can Not fix 5 months ago by kevin. Opened a year ago by praiskup.

Hey, I have two rc files which only differ in:

--- rc-fic-dev-copr.sh  2019-04-15 09:03:54.517481145 +0200
+++ rc-fic-prod-copr.sh 2019-04-15 09:12:10.191225671 +0200
-export OS_TENANT_ID=coprdev
-export OS_TENANT_NAME=..snip..
+export OS_TENANT_ID=copr
+export OS_TENANT_NAME=..snip..

And I'm fine to hit nova list with the coprdev tenatnt, but not
with the copr tenant:

$ . rc-fic-dev-copr.sh && nova list
... works
$ . rc-fic-prod-copr.sh && nova list
... looong waiting ... and:
ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-b1d0cf5e-b3ff-4c4a-b24f-...)

Well, our cloud is ancient and I don't think we really have any desire to try and troubleshoot this.

it's likely a timeout...somewhere in the stack.

Does it work from copr-be?

Does it work from copr-be?

It is not :-( @msuchy suspected there's some permission misconfiguration for copr and praiskup users in the OS.

Both files are available in /home/copr/praiskup-test on production backend:

drwx------.  2 copr copr 4.0K Apr 18 09:40 .
drwx------. 11 copr copr 4.0K Apr 18 09:40 ..
-rw-------.  1 copr copr  256 Apr 18 09:36 rc-fic-dev-copr.sh
-rw-------.  1 copr copr  253 Apr 18 09:36 rc-fic-prod-copr.sh

After try with --debug -v, the copr vs copr-dev request started to differ on
REQ: curl -g -i -X GET https://fedorainfracloud.org:8774/v2/<tenant_id>/servers/detail

where with copr-dev tenant, HTTP code 200 is returned - but with copr tenant HTTP code 500 is returned.

@puiterwijk might have some idea here... but it may be we just can't easily fix this. ;(

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

a year ago

So... since we no longer have an openstack cloud, going to close this. ;)

Metadata Update from @kevin:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

5 months ago

Login to comment on this ticket.