[8.0][Tempest] Heat cannot create stack from template: Found a [<type 'unicode'>] instead

Bug #1704731 reported by Vladimir Jigulin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
High
MOS Maintenance

Bug Description

Catched on tempest test: test_exceed_max_template_size_fails
Steps to reproduce:
1. Deploy cluster with heat
2. Create template file heat.tmpl with content:
HeatTemplateFormatVersion: '2012-12-12'
Description: 'Description'
Outputs:
  Foo: bar
3. Try to create new stack: heat stack-create -f stack.tmpl test1
heatclient.exc.HTTPBadRequest: ERROR: Output validation error: : Outputs: : Outputs must contain Output. Found a [<type 'unicode'>] instead

Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/heat/common/context.py", line 308, in wrapped
    return func(self, ctx, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/heat/engine/service.py", line 747, in create_stack
    parent_resource_name)
  File "/usr/lib/python2.7/dist-packages/heat/engine/service.py", line 658, in _parse_template_and_validate_stack
    stack.validate()
  File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 105, in wrapper
    return f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/heat/engine/stack.py", line 709, in validate
    message=message)
StackValidationFailed: Output validation error: Outputs: Outputs must contain Output. Found a [<type 'unicode'>] instead

Reproducibility: 100%
First fail: 07/14/17
Last pass: 04/26/17

Changed in mos:
milestone: none → 8.0-updates
importance: Undecided → High
status: New → Confirmed
summary: - [8.0][Tempest] Heat cannot create stack: Found a [<type 'unicode'>]
- instead
+ [8.0][Tempest] Heat cannot create stack from template: Found a [<type
+ 'unicode'>] instead
Changed in mos:
assignee: nobody → MOS Maintenance (mos-maintenance)
description: updated
description: updated
Revision history for this message
Vladimir Jigulin (vjigulin) wrote :

The cause of the failures was the incorrect configuration of tempest. Close as invalid until there is no updates.

Changed in mos:
status: Confirmed → 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.