Fuel for OpenStack

HA deployment failed with (/Stage[main]/Osnailyfacter::Cluster_ha/Nova_floating_range[10.108.11.128-10.108.11.254]) Could not evaluate: Oops - not sure what happened: 757: unexpected token at '<html><body><h1>504 Gateway Time-out</h1>

Bug #1346192 reported by Andrey Sledzinskiy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Triaged
High
Fuel Library (Deprecated)
Fuel for OpenStack 5.1
5.0.x
Confirmed
Critical
Unassigned
Fuel for OpenStack 5.0.1

Bug Description

http://jenkins-product.srt.mirantis.net:8080/view/5.0_swarm/job/5.0_fuelmain.system_test.centos.thread_5/46/testReport/junit/%28root%29/deploy_ha/deploy_ha/

{

    "build_id": "2014-07-20_00-31-14",
    "mirantis": "yes",
    "build_number": "141",
    "ostf_sha": "09b6bccf7d476771ac859bb3c76c9ebec9da9e1f",
    "nailgun_sha": "17444180b7e8c0c454488e63a05693881168f76a",
    "production": "docker",
    "api": "1.0",
    "fuelmain_sha": "312121d05c780e44dbf6db138847547b45bc3848",
    "astute_sha": "9a74b788be9a7c5682f1c52a892df36e4766ce3f",
    "release": "5.0.1",
    "fuellib_sha": "1a39cf33b217535cdbb6374da855085a8b420605"

}

Steps:
1. Create next cluster - CentOS, HA, Flat Nova-network, Cinder for volumes, 3 controllers, 2 compute nodes
2. Deploy cluster

Actual - deployment failed with errors in puppet on first controller (node-1):
(/Stage[main]/Osnailyfacter::Cluster_ha/Nova_floating_range[10.108.11.128-10.108.11.254]) Could not evaluate: Oops - not sure what happened: 757: unexpected token at '<html><body><h1>504 Gateway Time-out</h1>

Logs are attached

Tags: heartbeat
Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

According to logs, the issue likely caused by 1.3.0 heartbeat patch
2014-07-20T01:12:26.671589 node-1 ./node-1.test.domain.local/rabbitmq.log:2014-07-20T01:12:26.671589+00:00 err: =ERROR REPORT==== 20-
Jul-2014::01:12:24 ===
2014-07-20T01:12:26.671589 node-1 ./node-1.test.domain.local/rabbitmq.log:2014-07-20T01:12:26.671589+00:00 err: {heartbeat_timeout,ru
nning}
2014-07-20T01:15:08.479341 node-1 ./node-1.test.domain.local/rabbitmq.log:2014-07-20T01:15:08.479341+00:00 err: connection_closed_abr
uptly
2014-07-20T01:15:08.479341 node-1 ./node-1.test.domain.local/rabbitmq.log:2014-07-20T01:15:08.479341+00:00 err: =WARNING REPORT==== 2
0-Jul-2014::01:15:08 ===
2014-07-20T01:17:13.352629 node-1 ./node-1.test.domain.local/puppet-apply.log:2014-07-20T01:17:13.352629+00:00 err: (/Stage[main]/Osn
ailyfacter::Cluster_ha/Nova_floating_range[10.108.11.128-10.108.11.254]) Could not evaluate: Oops - not sure what happened: 757: unexp
ected token at '<html><body><h1>504 Gateway Time-out</h1>
2014-07-20T01:17:13.352749 node-1 ./node-1.test.domain.local/puppet-apply.log:2014-07-20T01:17:13.352749+00:00 err: (/Stage[main]/Osn
ailyfacter::Cluster_ha/Nova_floating_range[10.108.11.128-10.108.11.254]) The server didn't respond in time.

Changed in fuel:
status: New → Confirmed
tags: added: heartbeat
Changed in fuel:
status: Confirmed → Triaged
Revision history for this message
Andrew Woodward (xarses) wrote :

This Nova_floating_range only involves the API, why would 504 likely nova-api not working behind the vip be a duplicate of the hearbeat? although it is seperately a case of hearbeat issues

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.