On Wed, May 1, 2019 at 4:28 PM Neil Jerram neil@tigera.io wrote:
On Wed, May 1, 2019 at 4:21 PM Colleen Murphy colleen@gazlene.net wrote:
On Tue, Apr 30, 2019, at 10:41, Neil Jerram wrote:
Does anyone know what causes this problem at [1]:
2019-04-30 16:34:03.137 | +++ functions-common:oscwrap:2346 : command openstack role add admin --user neutron --project service --user-domain Default --project-domain Default 2019-04-30 16:34:03.139 | +++ functions-common:oscwrap:2346 : openstack role add admin --user neutron --project service --user-domain Default --project-domain Default 2019-04-30 16:34:04.331 | Failed to discover available identity versions when contacting http://104.239.175.234/identity. Attempting
to
parse version from URL. 2019-04-30 16:34:04.331 | Could not find versioned identity endpoints when attempting to authenticate. Please check that your auth_url is correct. Not Found (HTTP 404)
[1]
http://logs.openstack.org/79/638479/3/check/networking-calico-tempest-dsvm/5...
I think there are loads of uses of that URL, before where the networking-calico plugin uses it, so I can't see why the plugin's use hits that error.
Thanks, Neil
That error usually means that keystone couldn't be reached at all. Looking through the devstack log, it looks like keystone is not even enabled:
http://logs.openstack.org/79/638479/3/gate/networking-calico-tempest-dsvm/58...
Many thanks Colleen, I'll explicitly enable keystone and see if that helps.
Do you know if that's a recent change, that keystone used to be enabled by default, and now requires explicit enabling?
I'm sorry, I've spotted what the real problem is now, and it doesn't implicate any change to the enablement of keystone. But many thanks again for your input, which was the hint I needed to see the problem!
(networking-calico's devstack plugin supports running on multiple nodes, and has a heuristic to differentiate between when it's the first node being set up - with both control and compute functions - and when it's a subsequent node - with compute only. That heuristic had gone wrong, so CI was installing a compute-only node.)
Best wishes, Neil