Heat-api.conf not overriden by Puppet variables

Bug #1227037 reported by Sylvain Bauza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-heat
Invalid
Undecided
Unassigned

Bug Description

The following values in heat-api.conf are left unchanged while Puppet should write them :

admin_tenant_name = service
admin_user = heat
admin_password = verybadpass

These values should match the Heat Puppet vars, or Puppet should remove these entries.

Revision history for this message
Mathieu Gagné (mgagne) wrote :

Heat moved from multiple configuration files to single configuration file:
- https://review.openstack.org/#/c/36476/
- https://review.openstack.org/#/c/43697/

We updated the puppet-heat module accordingly:
- https://review.openstack.org/#/c/39980/
- https://review.openstack.org/#/c/43406/

Which OS/packages are you using?

If people packaging Heat still use multiple configuration files, we might want to revert our changes or see what can be done.

Revision history for this message
Sylvain Bauza (sylvain-bauza) wrote :

I was hitting heat havana-b2 on the UCA 'proposed' repo, from where there was stil an heat-api.conf and heat-engine.conf.

Now as per http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/havana_versions.html, 'proposed' repo provides Heat-b3, which should not package these files.

We can leave this bug as 'Invalid' but at the moment UCA havana/updates is still stuck to Havana-b2 which ships the heat-[api,engine].conf

Revision history for this message
Mathieu Gagné (mgagne) wrote :

This has been fixed since Havana-3.

Changed in puppet-heat:
status: New → Invalid
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.