On Wed, Dec 04, 2013 at 07:36:36AM -0500, Eoghan Glynn wrote: > > How old is your heat client? > > I think your issue may have been addressed by this commit from yesterday: > > https://github.com/openstack/python-heatclient/commit/e259163d
Yeah, this sounds like the issue, apologies for the regression - if you pull latest python-heatclient which includes that commit all should be OK. The problem is Heat requires the username/password headers when configured to store (encrypted) credentials for deferred operations like autoscaling adjustments. I was working on making python-heatclient work better when you provide an existing keystone token, and forgot that you have to pass the username/password *and* X-Auth-Token if heat is configured with deferred_auth_method=password. The alternative is to use deferred_auth_method=trusts, which means we create a trust instead and store that, but this is not yet the default becuse it's less well tested, and there are some remaining issues (e.g bug #1235290, which would affect autoscaling) Hope that solves your problem, and apologies again for being the cause of it! :) Steve _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
