memory-limit is not passed to docker API correctly

Bug #1567834 reported by Eli Qiao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
High
Eli Qiao

Bug Description

Commit I34e5e49ae650219f986a2b0032df65672c319ec6 tried to fix mem_limit
not passed to docker when create container for docker API vesion >=1.19
in a wrong way.

we need to convert mem_limit unit to Memory Byte

Eli Qiao (taget-9)
Changed in magnum:
assignee: nobody → Eli Qiao (taget-9)
status: New → Confirmed
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

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

Changed in magnum:
status: Confirmed → In Progress
Changed in magnum:
assignee: Eli Qiao (taget-9) → Spyros Trigazis (strigazi)
Changed in magnum:
assignee: Spyros Trigazis (strigazi) → Eli Qiao (taget-9)
Changed in magnum:
assignee: Eli Qiao (taget-9) → Yolanda Robla (yolanda.robla)
Changed in magnum:
assignee: Yolanda Robla (yolanda.robla) → Eli Qiao (taget-9)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/303299
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=2b667eba052e785fef90d93b94c4ef9b13059787
Submitter: Jenkins
Branch: master

commit 2b667eba052e785fef90d93b94c4ef9b13059787
Author: Eli Qiao <email address hidden>
Date: Fri Apr 8 14:52:51 2016 +0800

    Fix container-create memory not passed

    Commit I34e5e49ae650219f986a2b0032df65672c319ec6 tried to fix mem_limit
    not passed to docker when create container for docker API vesion >=1.19
    in a wrong way, this patch fixes it by passing Memory unit to host_config

    Closes-Bug: #1567834
    Change-Id: Id8da5e40cf165317a9a5453036490cc028bd2e0d
    Co-Authored-By: Spyros Trigazis <email address hidden>

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 3.0.0

This issue was fixed in the openstack/magnum 3.0.0 release.

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.