kolla

Kolla reconfigure failure after mariadb connection limit reset

Bug #1563643 reported by Manjeet Singh Bhatia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Critical
Jeffrey Zhang
kolla newton-1 "n1"
Mitaka
Fix Released
Critical
Jeffrey Zhang
kolla mitaka-rc3 "mitaka-rc3"

Bug Description

I tried increasing database connection limit and got issues while reconfigure
logs http://paste.openstack.org/show/492386/

Steven Dake (sdake)
Changed in kolla:
milestone: none → newton-1
status: New → Confirmed
importance: Undecided → Critical
Jeffrey Zhang (jeffrey4l)
Changed in kolla:
assignee: nobody → Jeffrey Zhang (jeffrey4l)
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

Checking the fix condition first in the when clause rather than the
    dynamic condition. Otherwise it will raise issue, especially in
    multinode env.

    For example use

      when:
        - nova_console == 'novnc'
        - inventory_hostname in groups['nova-novncproxy']

    rather than

      when:
        - inventory_hostname in groups['nova-novncproxy']
        - nova_console == 'novnc'

    Because the nova-novncproxy groups may do not exist.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/299219

Changed in kolla:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/299219
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=792e2c1f26de6782879eefdccfcce242c35dff80
Submitter: Jenkins
Branch: master

commit 792e2c1f26de6782879eefdccfcce242c35dff80
Author: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
Date: Wed Mar 30 16:57:42 2016 +0800

    Fix the nova reconfigure in the multinode env

    Checking the fix condition first in the when clause rather than the
    dynamic condition. Otherwise it will raise issue, especially in
    multinode env.

    For example use

      when:
        - nova_console == 'novnc'
        - inventory_hostname in groups['nova-novncproxy']

    rather than

      when:
        - inventory_hostname in groups['nova-novncproxy']
        - nova_console == 'novnc'

    Because the nova-novncproxy groups may do not exist.

    Change-Id: I1e76ee239908a17a4c2ffd9a18c570fbc485172e
    Closes-Bug: #1563643

Changed in kolla:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/mitaka)

Reviewed: https://review.openstack.org/300657
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=d6b083afb69eb7e2ee40069771b690bc7a6d40a4
Submitter: Jenkins
Branch: stable/mitaka

commit d6b083afb69eb7e2ee40069771b690bc7a6d40a4
Author: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
Date: Wed Mar 30 16:57:42 2016 +0800

    Fix the nova reconfigure in the multinode env

    Checking the fix condition first in the when clause rather than the
    dynamic condition. Otherwise it will raise issue, especially in
    multinode env.

    For example use

      when:
        - nova_console == 'novnc'
        - inventory_hostname in groups['nova-novncproxy']

    rather than

      when:
        - inventory_hostname in groups['nova-novncproxy']
        - nova_console == 'novnc'

    Because the nova-novncproxy groups may do not exist.

    Change-Id: I1e76ee239908a17a4c2ffd9a18c570fbc485172e
    Closes-Bug: #1563643
    (cherry picked from commit 792e2c1f26de6782879eefdccfcce242c35dff80)

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/kolla 2.0.0

This issue was fixed in the openstack/kolla 2.0.0 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/kolla 1.1.0

This issue was fixed in the openstack/kolla 1.1.0 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/kolla 3.0.0.0b1

This issue was fixed in the openstack/kolla 3.0.0.0b1 development milestone.

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.