Bug 2036716 - Unable to create heat stack in Horizon. Danger there was an error submitting the form [NEEDINFO]
Summary: Unable to create heat stack in Horizon. Danger there was an error submitting ...
Keywords:
Status: POST
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat-ui
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ga
: ---
Assignee: OSP Team
QA Contact: Ronnie Rasouli
URL:
Whiteboard:
: 2070859 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-03 16:27 UTC by nalmond
Modified: 2023-08-16 13:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
alisci: needinfo? (rhos-maint)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 828579 0 None NEW Decode object before sending it to json decoder 2022-02-09 15:56:06 UTC
Red Hat Issue Tracker OSP-11987 0 None None None 2022-01-03 16:30:26 UTC

Description nalmond 2022-01-03 16:27:11 UTC
Description of problem:
When attempting to create a heat stack in Horizon it immediately fails with "Danger there was an error submitting the form". It seems to fail before the request reaches the heat api. The same templates work in RHOSP 13 and also via the cli in this 16.2 environment.

Version-Release number of selected component (if applicable):


How reproducible:
Consistently in this 16.2 environment

Steps to Reproduce:
1. Log in to horizon
2. Attempt to create a heat stack
3. 

Actual results:
Danger there was an error submitting the form

Expected results:
Successful stack creation

Additional info:

If this parameter (the actual url in the template is valid) is removed we're able to get past the form submission failure:

      config_file_content: {get_file: 'http://example.com/path/to/file.txt'}

Comment 10 Radomir Dopieralski 2022-04-07 14:40:42 UTC
*** Bug 2070859 has been marked as a duplicate of this bug. ***


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