yahoo-eng-team team mailing list archive

[OpenStack Infra <1661396@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/428435
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=3f7e74ab24bb43f9ad7e24e0efd4206ac6a3dd4e
Submitter: Jenkins
Branch:    master

commit 3f7e74ab24bb43f9ad7e24e0efd4206ac6a3dd4e
Author: Alex Schultz <aschultz@xxxxxxxxxx>
Date:   Thu Feb 2 21:29:32 2017 +0000

    Revert "set innodb_file_per_table to ON for MySQL / Galera"
    
    This reverts commit 621ea892a299d2029348db2b56fea1338bd41c48.
    
    We're getting performance problems on SATA disks.
    
    Change-Id: I30312fd5ca3405694d57e6a4ff98b490de388b92
    Closes-Bug: #1661396
    Related-Bug: #1660722


** Changed in: tripleo
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1661396

Title:
  undercloud install fails (nova-db-sync timeout) on VM on an SATA disk
  hypervisor

Status in OpenStack Compute (nova):
  New
Status in tripleo:
  Fix Released

Bug description:
  2017-02-01 15:24:49,084 INFO: Error: Command exceeded timeout
  2017-02-01 15:24:49,084 INFO: Error: /Stage[main]/Nova::Db::Sync/Exec[nova-db-sync]/returns: change from notrun to 0 failed: Command exceeded timeout

  The nova-db-sync command is exceeding 300 seconds when installing the
  undercloud on a VM that is using SATA based storage. This seems to be
  related to the switch to innodb_file_per_table to ON which has doubled
  the amount of time the db sync takes on this class of hardware.  To
  unblock folks doing Ocata testing, we need to skip doing this in Ocata
  and will need to revisit enabling it in Pike.

  See Bug 1660722 for details as to why we enabled this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1661396/+subscriptions