Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Assigning values for Memory, CPU Share etc while creating a Docker container does not seem to be working, as the information displayed (UI and using docker inspect command) does not show that the parameters passed were used.

Version-Release number of selected component (if applicable):

* Satellite-6.1.0-RHEL-7-20150320.1

How reproducible:


Steps to Reproduce:
1. Create a new Docker container using the web ui
2. Type 512m for Memory and 2 for CPU Share and finish the wizard
3.

Actual results:

The container created does not have the amount of memory and cpu share passed during the wizard

Expected results:


Additional info:

Created redmine issue http://projects.theforeman.org/issues/10191 from this bug

Moving to POST since upstream bug http://projects.theforeman.org/issues/10191 has been closed
-------------
Adam Ruzicka
Applied in changeset commit:foreman-docker|e88059db3a33445f654b199d803e4364662b7eaf.

Currently, in upstream we are not able to create new container even after 
creating compute resource ..
thanks

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/RHBA-2016:1501