Bug 1434520
Summary: | Neutron database sync times out during deployment | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Dan Macpherson <dmacpher> |
Component: | openstack-tripleo-heat-templates | Assignee: | Or Idgar <oidgar> |
Status: | CLOSED ERRATA | QA Contact: | Toni Freger <tfreger> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 11.0 (Ocata) | CC: | amuller, dmacpher, eglynn, ekultails, jjoyce, jschluet, mburns, nlevinki, oidgar, rhel-osp-director-maint, rhos-maint, slinaber, tvignaud |
Target Milestone: | ga | Keywords: | Triaged |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-7.0.0-0.20170628002128.el7ost.noarch | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1434279 | Environment: | |
Last Closed: | 2017-12-13 21:18:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1433535, 1434279 | ||
Bug Blocks: |
Description
Dan Macpherson
2017-03-21 16:08:54 UTC
Assigned to Or Idgar, who doesn't have a Bugzilla account yet. I suggest that we bump the default timeout significantly. To which value should I update the timeout - 600 or 900? I think 900 would cover all future db sync scenarios significantly and would cover a variety of hardware types, including low spec test environments. Hi Dan, People in upstream argue that this change is not reasonable and that 300 seconds should be more than enough. I'm not that familiar with the low spec environments which encountered that issue and reached timeout. 1. Could you provide the specs that exhibit this issue, particular the storage specs? 2. Where can I find more information about tripleo db sync actions? I have a similar issue with the Neutron database sync failing due to a timeout when trying to use tripleo-quickstart to deploy OpenStack using nested KVM virtual machines. https://bugs.launchpad.net/tripleo/+bug/1712901 The storage on the hypervisor VM is a QCOW2 image with preallocated metadata, no drive cache, and VirtIO drivers. This nested hypervisor VM has 20 cores and 30GB of RAM. All of the timeouts seem to be defined in the puppet-<OPENSTACK_SERVICE> GitHub repositories for the upstream TripleO. For example, Neutron's default $db_sync_timeout is defined here: https://github.com/openstack/puppet-neutron/blob/master/manifests/db/sync.pp Hi Toni, All you need to do is to take low spec environment (with emphasis on storage low performance) and run overcloud deployment with director. for the command you will need to add an environment file as a parameter. for example: "openstack overcloud deploy -e /usr/share/openstack-tripleo-heat-templates/environments/low-memory-usage.yaml" without this environment file, on low spec environment the deployment should fail. Let me know if you need additional help Or thanks for the details. Since low spec environment without this yaml will fail, is it documented to run it with the low-memory-usage.yaml? There isn't any documentation about it. we use it mainly in non production environments (devenvs, CI, etc.). Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462 |