Gate bundles allocate too little memory for the octavia unit

Bug #1895319 reported by Frode Nordahl
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Octavia Charm
Fix Released
High
Frode Nordahl

Bug Description

As detailed by the build artifacts of the gate failures in https://review.opendev.org/#/c/744402/ the octavia units go OOM while running in the gate.

What happens is that the policyd functional test add/remove policy file resources, and juju's behavior for handling that is to run a upgrade-charm hook.

The Octavia charm is using the reactive framework, and a upgrade-charm event for a reactive charm means rebuilding the charms wheelhouse.

Rebuilding a charms wheelhouse some times means compiling binary code, and is this instance there just is not enough memory to do it because of all the services running etc.

Frode Nordahl (fnordahl)
tags: added: unstable-test
Revision history for this message
Frode Nordahl (fnordahl) wrote :
Changed in charm-octavia:
importance: Undecided → High
assignee: nobody → Frode Nordahl (fnordahl)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-octavia (master)

Reviewed: https://review.opendev.org/751663
Committed: https://git.openstack.org/cgit/openstack/charm-octavia/commit/?id=6e5f83571ca6b63af734990c978a2284fb70e8a4
Submitter: Zuul
Branch: master

commit 6e5f83571ca6b63af734990c978a2284fb70e8a4
Author: Frode Nordahl <email address hidden>
Date: Mon Sep 14 10:25:19 2020 +0200

    Increase available cores and memory for octavia unit

    The charm Octavia gate job has started to OOM for the Octavia
    units as detailed on the bug.

    This change addresses both that issue and attempts to increase the
    velocity of the test by adding CPU cores which might help for the
    time it takes to compile binary dependencies on initial deploy
    and during the policyd tests.

    Note that instead of explicitly mentioning amount of memory we
    assume a flavor with more cores to also have more memory.

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/418
    Change-Id: I0f332c5f6d97ed99f59c9985ff4a033920708bf2
    Closes-Bug: #1895319

Changed in charm-octavia:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-octavia (stable/20.08)

Fix proposed to branch: stable/20.08
Review: https://review.opendev.org/758134

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-octavia (stable/20.08)

Reviewed: https://review.opendev.org/758134
Committed: https://git.openstack.org/cgit/openstack/charm-octavia/commit/?id=30543ac39be973d32407acfa2153aae924873629
Submitter: Zuul
Branch: stable/20.08

commit 30543ac39be973d32407acfa2153aae924873629
Author: Frode Nordahl <email address hidden>
Date: Mon Sep 14 10:25:19 2020 +0200

    Increase available cores and memory for octavia unit

    The charm Octavia gate job has started to OOM for the Octavia
    units as detailed on the bug.

    This change addresses both that issue and attempts to increase the
    velocity of the test by adding CPU cores which might help for the
    time it takes to compile binary dependencies on initial deploy
    and during the policyd tests.

    Note that instead of explicitly mentioning amount of memory we
    assume a flavor with more cores to also have more memory.

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/418
    Change-Id: I0f332c5f6d97ed99f59c9985ff4a033920708bf2
    Closes-Bug: #1895319
    (cherry picked from commit 6e5f83571ca6b63af734990c978a2284fb70e8a4)

Changed in charm-octavia:
milestone: none → 20.10
Changed in charm-octavia:
status: Fix Committed → Fix Released
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.