Open tpatzig opened 7 years ago
The reason for using the v2.0 API is 74203e8692cdcbd1271beb9a54e0e9f3afdde284 -- in short, glance-scrubber didn't work with v3. I just checked again, it's still the case here.
So I'm slightly confused as to why you would get the issue with v2.0, tbh. Do you have more than this line of log? Do you see anything in the keystone logs?
The v2 api seems to work, at least i get a valid response when i curl https://cluster.xxx:5000/v2.0/ But with the added /tokens (i guess this is added by glance-scrubber code) path i get a 404.
@tpatzig did you do a GET or a POST? TBH, a better test is simply to run any openstack CLI with the v2.0 API.
@tpatzig will check if this issue still is in place
need to look at /var/log/glance/scrubber.log
why this doesn't work. If glance-scrubber is not working, we are not wiping glance images.
glance-scrubber is not working and errors:
2017-02-03 14:45:02.222 13113 ERROR glance.scrubber [req-fcb3ffbd-accc-4739-981b-8838496740ed glance service - - -] Can not get scrub jobs from queue: Connect error/bad request to Auth service at URL https://cluster.xxx:5000/v2.0/tokens
Looks like just the wrong auth_url is configured.