Bug 1445419 - Deployment with neutron-ml2-cisco-nexus-ucsm fails, resources.AllNodesExtraConfig: "" is not a map
Summary: Deployment with neutron-ml2-cisco-nexus-ucsm fails, resources.AllNodesExtraCo...
Keywords:
Status: CLOSED DUPLICATE of bug 1415103
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 10.0 (Newton)
Assignee: Angus Thomas
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-25 15:57 UTC by Sid Ahmed Sadouni
Modified: 2021-03-11 15:10 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-21 14:37:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
overcloud.j2.yaml (25.30 KB, text/plain)
2017-04-26 15:16 UTC, Sid Ahmed Sadouni
no flags Details

Description Sid Ahmed Sadouni 2017-04-25 15:57:56 UTC
Description of problem:


Using Director OSP10, we deploy for now 3 CTRL, 1 CMPT

The deployment fails within the first minute with the error :
Failed to validate: resources.AllNodesExtraConfig: "" is not a map

our neutron-ml2-cisco-nexus-ucsm.yaml is the following

https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/extraconfig/all_nodes/neutron-ml2-cisco-nexus-ucsm.yaml#L300..L302

The heat-engine trace is the following :
http://pastebin.test.redhat.com/478408


Deploy using the command :

[atos_adm@vel1-nfv01-director01 templates_SFR]$ cat deploy_lab.sh

#!/bin/bash

time openstack overcloud deploy \

--templates /home/atos_adm/templates_SFR \

--ntp-server pool.ntp.org \

--timeout 60 \

--control-flavor control --control-scale 3 \

--compute-flavor compute --compute-scale 1 \

--neutron-tunnel-types vxlan \

--neutron-network-type vxlan \

-e /home/atos_adm/templates_SFR/net-env.yaml \

-e /home/atos_adm/templates_SFR/environments/network-isolation.yaml \

-e /home/atos_adm/templates_SFR/HostnameMap.yaml \

-e /home/atos_adm/templates_SFR/ips-from-pool-all.yaml \

-e environments/storage-environment.yaml \

-e environments/cinder-netapp-config.yaml \

-e environments/neutron-ml2-cisco-nexus-ucsm.yaml

 

packages :

puppet-tripleo-5.5.0-4.el7ost.noarch

openstack-tripleo-heat-templates-5.2.0-3.el7ost.noarch

openstack-tripleo-common-5.4.1-1.el7ost.noarch

openstack-tripleo-0.0.8-0.2.4de13b3git.el7ost.noarch

openstack-tripleo-image-elements-5.2.0-1.el7ost.noarch

python-tripleoclient-5.4.1-1.el7ost.noarch

openstack-tripleo-puppet-elements-5.2.0-2.el7ost.noarch

openstack-tripleo-ui-1.1.0-1.el7ost.noarch

openstack-tripleo-validations-5.1.1-1.el7ost.noarch

[atos_adm@vel1-nfv01-director01 templates_SFR]$


Test :

I tested to disabled all the lines linked to the role we don't deploy.
ie :
https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/extraconfig/all_nodes/neutron-ml2-cisco-nexus-ucsm.yaml#L225..L227
https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/extraconfig/all_nodes/neutron-ml2-cisco-nexus-ucsm.yaml#L238..L240
https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/extraconfig/all_nodes/neutron-ml2-cisco-nexus-ucsm.yaml#L300..L302

but without better success, same error.

Comment 1 Steven Hardy 2017-04-26 10:11:08 UTC
After some discussion & debugging on IRC, it seems this may be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1415103

I think the error is because of this mistake in overcloud.j2.yaml:

https://review.openstack.org/#/c/424079/3/overcloud.j2.yaml

If re-testing with that fix manually applied solves the problem, I think this can be closed as a duplicate

Comment 2 Sid Ahmed Sadouni 2017-04-26 11:39:21 UTC
Hi

I applied this modification overcloud.j2.yaml :
https://review.openstack.org/#/c/424079/3/overcloud.j2.yaml

And we don't have the same error, but another one : Unknown Property ObjectStorage

log form heat-engine :

2017-04-26 13:11:51.479 2706 DEBUG heat.engine.stack [req-404bfa60-7a28-4f62-a25b-fa1a9703e2ca 32bbdec68b754dce80665f3f63a5d9b5 246f2a00a92649b0bb059f1e6fd65122 - - -] Property error: resources.AllNodesExtraConfig.properties: Unknown Property ObjectStorage validate /usr/lib/python2.7/site-packages/heat/engine/stack.py:831

We have a deployment without other roles than controller and compute node FYI.

Comment 3 Steven Hardy 2017-04-26 12:44:10 UTC
> Unknown Property ObjectStorage 

I suspect this may be an issue with the manual application of the patch, please can you paste or attach the full modified overcloud.j2.yaml, thanks!

Comment 4 Sid Ahmed Sadouni 2017-04-26 15:16:28 UTC
Created attachment 1274270 [details]
overcloud.j2.yaml

Comment 5 Steven Hardy 2017-04-26 16:35:17 UTC
The patch I referenced has not been correctly applied:

    properties:
{% for role in roles %}
      {{role.name}}: {get_attr: [{{role.name}}, attributes, nova_server_resource]}
{% endfor %}

Should be

    properties:
      servers:
{% for role in roles %}
      {{role.name}}: {get_attr: [{{role.name}}, attributes, nova_server_resource]}
{% endfor %}

Note "servers" is the property expected by the ExtraConfig template you are trying to use, which is why this is still failing.

Please can you re-test with https://review.openstack.org/#/c/424079/3/overcloud.j2.yaml correctly applied, thanks!

Comment 6 Steven Hardy 2017-04-26 16:37:58 UTC
Sorry should be:

    properties:
      servers:
{% for role in roles %}
        {{role.name}}: {get_attr: [{{role.name}}, attributes, nova_server_resource]}
{% endfor %}

(corrected indentation)

Or alternatively copy/paste the AllNodesExtraConfig resource definition from here:

https://github.com/openstack/tripleo-heat-templates/blob/master/overcloud.j2.yaml#L661

Or, test the package verified as fixing https://bugzilla.redhat.com/show_bug.cgi?id=1415103

Thanks!

Comment 7 Sid Ahmed Sadouni 2017-04-27 08:31:29 UTC
I applied the patch without being really focused. Sorry for that. 

It's now starting the deployment without complaining about the original error in subject.

So I think that we can say that https://review.openstack.org/#/c/424079/3/overcloud.j2.yaml is OK for our case.

Thanks

Comment 8 Sandhya Dasu 2017-06-02 20:38:54 UTC
If this issue is taken care of, should this bugzilla be closed?


Note You need to log in before you can comment on or make changes to this bug.