mysqld wasn't started during HA cluster deployment

Bug #1390719 reported by Dennis Dmitriev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Critical
Fuel Library (Deprecated)

Bug Description

Jenkins job http://jenkins-product.srt.mirantis.net:8080/job/6.0.staging.centos.bvt_1/58/

Cluster configuration:
 - CentOS , HA
 - neutron/vlan
 - 3 controller nodes
 - 2 compute nodes

Deployment failed on node-2 (controller #2) while node-1 and node-4 became 'ready'.

Pacemaker on the node-2 didn't start 'mysql' resource at all. This caused additional errors in the puppet during deployment.

api: '1.0'
astute_sha: 3c374c9f7bfbdbcd7ce2f716cd704e3044e6fb41
auth_required: true
build_id: 2014-11-07_23-03-15
build_number: '64'
feature_groups:
- mirantis
fuellib_sha: c7b71bd1ee939b5a634715ac7b13c2936ad93a5e
fuelmain_sha: f536d11fb40fed78c26f4d7326c45b0c48f157d8
nailgun_sha: 8330f6221e190db87fc5baa735fa719c85a2e02d
ostf_sha: 9c6fadca272427bb933bc459e14bb1bad7f614aa
production: docker
release: '6.0'
release_versions:
  2014.2-6.0:
    VERSION:
      api: '1.0'
      astute_sha: 3c374c9f7bfbdbcd7ce2f716cd704e3044e6fb41
      build_id: 2014-11-07_23-03-15
      build_number: '64'
      feature_groups:
      - mirantis
      fuellib_sha: c7b71bd1ee939b5a634715ac7b13c2936ad93a5e
      fuelmain_sha: f536d11fb40fed78c26f4d7326c45b0c48f157d8
      nailgun_sha: 8330f6221e190db87fc5baa735fa719c85a2e02d
      ostf_sha: 9c6fadca272427bb933bc459e14bb1bad7f614aa
      production: docker
      release: '6.0'

Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :
Changed in fuel:
importance: Undecided → Critical
status: New → Confirmed
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

The issue is related to public vip ping start failure:
2014-11-08T02:14:54.549439+00:00 err: (/Stage[corosync_setup]/Osnailyfacter::Cluster_ha::Virtual_ips/Cluster::Virtual_ips[public]/Cluster::Virtual_ip[public]/Service[ping_vip__public]/ensure) change from stopped to running failed: Execution timeout after 600 seconds!

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.