upload-swift-artifacts using http for secure keystone port 13000

Bug #1693034 reported by John Fulton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Medium
Unassigned

Bug Description

While trying to use upload-puppet-modules as provided by tripleo-common [1], the call to upload-swift-artifacts failed with the following:

(undercloud) [stack@undercloud ~]$ upload-puppet-modules -d puppet-modules
Creating tarball...
Tarball created.
Authorization Failure. Authorization failed: (http://192.168.24.2:13000/auth/tokens): The resource could not be found. (HTTP 404)
(undercloud) [stack@undercloud ~]$

The above indicates that it's using plain HTTP to communicate with the secure keystone port of 13000. My deployment, as set up by quickstart with release master, configured keystone with SSL only (so switching OS_AUTH_URL to plain HTTP and port 5000 failed).

(undercloud) [stack@undercloud ~]$ grep OS_AUTH_URL stackrc
OS_AUTH_URL=https://192.168.24.2:13000/
#OS_AUTH_URL=http://192.168.24.2:5000/
export OS_AUTH_URL
(undercloud) [stack@undercloud ~]$

Perhaps upload-swift-artifacts constructed the wrong URL to arrive at http://192.168.24.2:13000/auth/tokens (without the 's')?

[1] openstack-tripleo-common-7.0.1-0.20170512193241.bde811b.el7.centos.noarch

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.