juju bootstrap fails due to wrong Date header (openstack_s3)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
After "juju bootstrap", machine 0 fails to start correctly. /var/log/
usage: juju-admin [-h] [--verbose] [--version] [--log-file LOG_FILE] ...
juju cloud orchestration internal tools
positional arguments:
initialize Initialize Zookeeper hierarchy
optional arguments:
-h, --help show this help message and exit
--verbose, -v Enable verbose logging
--version show program's version number and exit
--log-file LOG_FILE, -l LOG_FILE
juju-admin: error: unrecognized arguments: version="1.0" encoding=
This is because the curl command failed.
The AccessDenied error comes from /usr/share/
date = email.utils.
However, printing out req.headers['Date'] shows that it is an integer (which time.ctime() shows is exactly 10 years in the future).
I don't know what the correct fix is, but I changed it to ignore unparsable dates and that allowed Juju to work.
I have done two OpenStack installs on two different machines, one starting with Essex and upgrading to Folsom and another starting with Folsom, and I hit this issue both times.
Changed in juju: | |
importance: | Undecided → Low |
status: | New → Triaged |
does it work with native openstack provider ie not openstack_s3