Heat post check failed : "Process 'heat-engine' is not running!"

Bug #1449155 reported by Tatyanka
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Critical
Daniil Trishkin

Bug Description

504 Gateway Time-out

\n', "The server didn't respond in time.\n", '\n', '\n'], stdout is ['Run options: \n', '\n', '# Running tests:\n', '\n', '....F.......F...\n', '\n', 'Finished tests in 60.330054s, 0.2652 tests/s, 0.2984 assertions/s.\n', '\n', ' 1) Failure:\n', 'test_heat_stack_list_run(HeatPostTest) [/etc/puppet/modules/osnailyfacter/modular/heat/heat_post.rb:54]:\n', 'Could not run heat-stack list!\n', '\n', ' 2) Failure:\n', 'test_process_heat-engine_running(HeatPostTest) [/etc/puppet/modules/osnailyfacter/modular/heat/heat_post.rb:32]:\n', "Process 'heat-engine' is not running!\n", '\n', '16 tests, 18 assertions, 2 failures, 0 errors, 0 skips\n'] on remote

in heat-engine.log
http://paste.openstack.org/show/208608/

in heat-api

http://paste.openstack.org/show/208619/

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  openstack_version: "2014.2.2-6.1"
  api: "1.0"
  build_number: "354"
  build_id: "2015-04-27_09-17-29"
  nailgun_sha: "2efc207e7156e362c2506b66e63b8bfa745d1153"
  python-fuelclient_sha: "2b311b3b82a1e2df1dc3484a0f37e282273cd988"
  astute_sha: "c1793f982fda7e3fc7b937ccaa613c649be6a144"
  fuel-library_sha: "6bdf783e2bffdce80ecffcca2915e6d32a8ccdd7"
  fuel-ostf_sha: "b38602c841deaa03ddffc95c02f319360462cbe3"
  fuelmain_sha: "01288380950bc89d572cf5902141c9a393ada950"

Steps:
Deploy ubuntu neutron gre:
1 controller
2 computes with cinder

After depolyment ssh on controller and run ruby /etc/puppet/modules/osnailyfacter/modular/heat/heat_post.rb

in my case it fails with :AssertionError: Check ruby /etc/puppet/modules/osnailyfacter/modular/heat/heat_post.rb finishes with non zero exit code, stderr is ['ERROR: <html><body><h1>504 Gateway Time-out</h1>\n', "The server didn't respond in time.\n", '</body></html>\n', '\n'], stdout is ['Run options: \n', '\n', '# Running tests:\n', '\n', '....F.......F...\n', '\n', 'Finished tests in 60.330054s, 0.2652 tests/s, 0.2984 assertions/s.\n', '\n', ' 1) Failure:\n', 'test_heat_stack_list_run(HeatPostTest) [/etc/puppet/modules/osnailyfacter/modular/heat/heat_post.rb:54]:\n', 'Could not run heat-stack list!\n', '\n', ' 2) Failure:\n', 'test_process_heat-engine_running(HeatPostTest) [/etc/puppet/modules/osnailyfacter/modular/heat/heat_post.rb:32]:\n', "Process 'heat-engine' is not running!\n", '\n', '16 tests, 18 assertions, 2 failures, 0 errors, 0 skips\n'] on remote

Then look at the heat-engine. log on controller

Tags: heat murano
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :
Mike Scherbakov (mihgen)
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → MOS Heat (mos-heat)
Revision history for this message
Sergey Kraynev (skraynev) wrote :

According to the logs Heat-engine didi not start due to conflict in requirements of oslo.utils. need update package and re-check

Changed in fuel:
assignee: MOS Heat (mos-heat) → Daniil Trishkin (dtrishkin)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Victor Ryzhenkin (vryzhenkin) wrote :

Reproduced on ISO:
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  openstack_version: "2014.2.2-6.1"
  api: "1.0"
  build_number: "355"
  build_id: "2015-04-27_17-04-35"
  nailgun_sha: "070ae962a3fd1231069887f185ff3865ca5c8f22"
  python-fuelclient_sha: "8cd6cf575d3c101dee1032abb6877dfa8487e077"
  astute_sha: "c1793f982fda7e3fc7b937ccaa613c649be6a144"
  fuel-library_sha: "0640124dadcdc0c9a1aa55d6f3d61acbda0edd2d"
  fuel-ostf_sha: "b38602c841deaa03ddffc95c02f319360462cbe3"
  fuelmain_sha: "01288380950bc89d572cf5902141c9a393ada950"

Ubuntu, neutron-gre, Murano, All Ceph, HA (3 KVM controllers, 1 Hardware compute)

This bug also blocks Murano functionality on Ubuntu-based environments due to Murano using Heat for deployment.

tags: added: heat murano
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.