Bug 1562546
Summary: | FFU: updating stack outputs fails on environments using OS::TripleO::NodeExtraConfig customizations with resources.NodeExtraConfig: Property error: resources.PreDeployDeployment.properties: Property name not assigned | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> |
Component: | openstack-tripleo-heat-templates | Assignee: | Jose Luis Franco <jfrancoa> |
Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 13.0 (Queens) | CC: | dbecker, dmacpher, jfrancoa, lbezdick, mandreou, mbracho, mburns, morazi, rhel-osp-director-maint, sathlang, shardy |
Target Milestone: | beta | Keywords: | Reopened, Triaged |
Target Release: | 13.0 (Queens) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-8.0.2-10.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-27 13:49:35 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: | |
Embargoed: |
Description
Marius Cornea
2018-03-31 21:47:22 UTC
PreDeployDeployment: type: OS::Heat::SoftwareDeployment properties: < here you are missing name: "whatever" > server: {get_param: server} config: {get_resource: PreDeployConfig} @Marius, have you tried adding the name property as Lukas mentioned? I will close it as this seems a misconfiguration, if it's still occurring after feel free to re-open it. (In reply to Jose Luis Franco from comment #4) > @Marius, have you tried adding the name property as Lukas mentioned? I will > close it as this seems a misconfiguration, if it's still occurring after > feel free to re-open it. I don't think we can consider this a misconfiguration. Deployment passed fine without the name property and also it is how we advertise to apply these kind of customization in the product docs: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/advanced_overcloud_customization/chap-configuration_hooks#sect-Customizing_Overcloud_PreConfiguration_All This means that environments out there in production are already deployed without the name property in the template. If there is no possible way to cover this issue automatically in code and we go to the documentation route then I think we need to answer these questions: 1. How does the operator know before starting the upgrade that it will fail because of the resource missing the name property. Provide a way to identify all the environments files which require this change. 2. At which point in the upgrade workflow does the operator need to adjust the templates and add the name property? Ideally I think we should fix this automatically in code to avoid the user doing yet another manual step during the upgrade procedure. We need to update docs for this to make sure you always have the name property set in your templates. If this OSP13 only? Also, is there any relevance to the name i.e. do users have to make it something specific? I suspect this is because FFU enables the config-download overrides to the *Deployment heat resources e.g: https://github.com/openstack/tripleo-heat-templates/blob/master/config-download-software.yaml#L5 https://github.com/openstack/tripleo-heat-templates/blob/master/config-download-structured.yaml the "name" parameter in both of these is mandatory, which I suspect is a bug, if we add a default to each of those files is the problem resolved? Thank you @Steve, that makes total sense and its a better solution than modifying the documentation, as there are no real changes in the SoftwareDeployment resource properties for queens: https://docs.openstack.org/heat/queens/template_guide/openstack.html#OS::Heat::SoftwareDeployment 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. https://access.redhat.com/errata/RHEA-2018:2086 |