Undercloud install fails in post_config phase when creating mistral config environment

Bug #1645633 reported by Sai Sindhur Malleni
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
Medium
Unassigned

Bug Description

On running openstack undercloud install, the command almost runs to completion but fails during post_config phase with the following error regarding mistral environment config https://gist.githubusercontent.com/smalleni/eeba1bf421b4a3c8a9790cad0d3373e8/raw/7c1807b614dfb3fc5c54037e788d5240eb75102d/gistfile1.txt

stackrc is generated and all commands such as ironic node-list, openstack baremetal import work fine but when trying to deploy overcloud, the deploy fails in less than 20s without the heat stack even being created with the following error "Environment not found [name=tripleo.undercloud-conf]" .

This is using the passed phase 1 ocata repos.

Tags: workflows
tags: added: workflows
Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → ocata-2
Changed in tripleo:
assignee: nobody → Sai Sindhur Malleni (smalleni)
Changed in tripleo:
assignee: Sai Sindhur Malleni (smalleni) → nobody
Revision history for this message
Sai Sindhur Malleni (smalleni) wrote :

Fwiw, rerunning openstack undercloud install on the same failed node, we didn't see this issue. The issue seems to be not checking if osprofiler_web was initialized, so having a 'if osprofiler_web:' should solve this. However, https://github.com/openstack/python-mistralclient/commit/d655e010b87c60cb62475324edfe3893c34ef711 already addresses this but doesn't seem to be included in the latest package.

Changed in tripleo:
milestone: ocata-2 → ocata-3
Changed in tripleo:
milestone: ocata-3 → pike-1
Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Revision history for this message
Dougal Matthews (d0ugal) wrote :

This seems to be already fixed.

Changed in tripleo:
status: Triaged → 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.