[Update] Update cluster from 9.1 to 9.2 failed on nova-db task

Bug #1641947 reported by Ilya Bumarskov
This bug report is a duplicate of:  Bug #1644152: Pacemaker hang during upgrade to 9.2. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
In Progress
Critical
Anton Chevychalov

Bug Description

Fuel 9.1

Detailed bug description:
Update cluster from 9.1 to 9.2 (snapshot id#515) failed on nova-db task.

Steps to reproduce:
   - Deploy 9.1 env with following nodes:
         * Controller
         * Compute, cinder
         * Compute, cinder
   - Add proposed repo for env (http://mirror.fuel-infra.org/mos-repos/ubuntu/snapshots/9.0-2016-11-14-194322)
   - Download mos-mu tool on master (git clone https://github.com/aepifanov/mos_mu.git)
   - Make a perform a preparation playbook (ansible-playbook playbooks/mos9_prepare.yml -e '{"env_id":<env_id>, "mos9_centos_repo":"http://mirror.fuel-infra.org/mos-repos/centos/mos9.0-centos7/snapshots/proposed-2016-11-14-194322/x86_64"}, "mos9_GPG_KEY":"http://mirror.fuel-infra.org/mos-repos/centos/mos9.0-centos7/snapshots/proposed-2016-11-14-194322/RPM-GPG-KEY-mos9.0"')
   - Update fuel node (ansible-playbook playbooks/update_fuel.yml)
   - Update env (fuel2 update --env <ENV_ID> install)

Observed behavior:
Deployment has failed. All nodes are finished. Failed tasks: Task[nova-db/2] Stopping the deployment process!
Task [nova-db/2] is failed because MySQL doesn't reachable (via vip__management ip):
(/Stage[main]/Nova::Db::Mysql_api/Openstacklib::Db::Mysql[nova_api]/Mysql_database[nova_api]/ensure) change from absent to present failed: Execution of '/usr/bin/mysql --defaults-extra-file=/root/.my.cnf -NBe create database if not exists `nova_api` character set `utf8` collate `utf8_general_ci`' returned 1: ERROR 2003 (HY000): Can't connect to MySQL server on '10.109.1.6' (113)

Changed in fuel:
importance: Undecided → Critical
milestone: none → 9.2
tags: added: blocker-for-qa
Revision history for this message
Ilya Bumarskov (ibumarskov) wrote :

vip_managment ip becomes available through several minutes (1-2 minutes) after stopped deployment.

Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Ilya, please provide diagnostic snapshot.

Changed in fuel:
status: New → Incomplete
Revision history for this message
Ilya Bumarskov (ibumarskov) wrote :
Changed in fuel:
status: Incomplete → New
description: updated
Changed in fuel:
status: New → Confirmed
assignee: Fuel Sustaining (fuel-sustaining-team) → Anton Chevychalov (achevychalov)
Revision history for this message
Anton Chevychalov (achevychalov) wrote :

I see a lot of br-mgmt flapping in logs:

cat fuel-snapshot-2016-11-15_14-11-11/node-2-10.109.0.3/var/log/messages | grep br-mgmt | grep 'Nov 15 12:' | wc -l
176

I can't reproduce it on my lab. Can you confirm problem on another lab instance?

Changed in fuel:
status: Confirmed → Incomplete
Changed in fuel:
status: Incomplete → In Progress
Revision history for this message
Anton Chevychalov (achevychalov) wrote :

That bug related to pacemaker hang. See https://bugs.launchpad.net/fuel/+bug/1644152.

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.