| Summary: | heat_cfn and heat_cloudwatch services should be enabled/disabled per boolean params | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ryan O'Hara <rohara> | ||||
| Component: | openstack-foreman-installer | Assignee: | Ryan O'Hara <rohara> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Ami Jeain <ajeain> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.0 | CC: | breeler, ddomingo, hateya, jguiditt, morazi, rhos-maint, yeylon | ||||
| Target Milestone: | rc | Keywords: | OtherQA | ||||
| Target Release: | 4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-foreman-installer-0.0.25-1.el6ost | Doc Type: | Bug Fix | ||||
| Doc Text: |
The Orchestration engine's controller used incorrectly constructed boolean parameters for the following services:
* openstack-heat-api-cfn
* openstack-heat-api-cloudwatch
The boolean parameters were instructed in such a way that when either service was enabled, attempting to disable it in the host group failed.
This release corrects the affected boolean parameters, ensuring that enabling and disabling these services work as expected.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-12-20 00:43:34 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Ryan O'Hara
2013-12-09 17:31:18 UTC
Created attachment 834442 [details]
Fix enable/disable of heat_cfg and heat_cloudwatch
This patch modifies the heat_controller.pp manifest such that the
heat_cfn and heat_cloudwatch services are enabled/disabled per the
heat_cfn and heat_cloudwatch boolean parameters. Previously, once
either boolean had been set to true the services would be running on
the controller, but reverting either parameter to false would not
stop/disable the service.
This patch also fixes the call to the heat::keystone::auth class such
that the heat_cfn endpoints are always created with the correct IP
addresses.
With heat_cfn and heat_cloudwatch parameters initially set to false in a controller hostgroup, the services should be stopped and disabled: # chkconfig --list openstack-heat-api-cfn openstack-heat-api-cfn 0:off 1:off 2:off 3:off 4:off 5:off 6:off # chkconfig --list openstack-heat-api-cloudwatch openstack-heat-api-cloudwatch 0:off 1:off 2:off 3:off 4:off 5:off 6:off # service openstack-heat-api-cfn status heat-api-cfn is stopped # service openstack-heat-api-cloudwatch status heat-api-cloudwatch is stopped Also check that a single endpoint exists for the cloudformation service and the URLs have the correct IP addresses: # keystone endpoint-get --service cloudformation --endpoint-type publicURL +--------------------------+-----------------------------+ | Property | Value | +--------------------------+-----------------------------+ | cloudformation.publicURL | http://10.15.85.144:8000/v1 | +--------------------------+-----------------------------+ # keystone endpoint-get --service cloudformation --endpoint-type internalURL +----------------------------+--------------------------------+ | Property | Value | +----------------------------+--------------------------------+ | cloudformation.internalURL | http://192.168.101.144:8000/v1 | +----------------------------+--------------------------------+ # keystone endpoint-get --service cloudformation --endpoint-type adminURL +-------------------------+--------------------------------+ | Property | Value | +-------------------------+--------------------------------+ | cloudformation.adminURL | http://192.168.101.144:8000/v1 | +-------------------------+--------------------------------+ Set both heat_cfn and heat_cloudwatch parameters to true and reapply. Both services should now be running and enabled: # chkconfig --list openstack-heat-api-cfn openstack-heat-api-cfn 0:off 1:off 2:on 3:on 4:on 5:on 6:off # chkconfig --list openstack-heat-api-cloudwatch openstack-heat-api-cloudwatch 0:off 1:off 2:on 3:on 4:on 5:on 6:off # service openstack-heat-api-cfn status heat-api-cfn (pid 10579) is running... # service openstack-heat-api-cloudwatch status heat-api-cloudwatch (pid 10692) is running... Also check that changing heat_cfn from false to true did not result in additional keystone enpoint: # keystone endpoint-get --service cloudformation +--------------------------+-----------------------------+ | Property | Value | +--------------------------+-----------------------------+ | cloudformation.publicURL | http://10.15.85.144:8000/v1 | +--------------------------+-----------------------------+ Set both heat_cfn and heat_cloudwatch parameters back to false and reapply. Both services should not be stopped and disabled: # chkconfig --list openstack-heat-api-cfn openstack-heat-api-cfn 0:off 1:off 2:off 3:off 4:off 5:off 6:off # chkconfig --list openstack-heat-api-cloudwatch openstack-heat-api-cloudwatch 0:off 1:off 2:off 3:off 4:off 5:off 6:off # service openstack-heat-api-cfn status heat-api-cfn is stopped # service openstack-heat-api-cloudwatch status heat-api-cloudwatch is stopped Upstream pull request: https://github.com/redhat-openstack/astapor/pull/79 Merged, this should get into the next build Test results are in comment #3. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html |