Bug 1330570 - Raise helpful message while allocating Memory w/o unit to Docker Container
Summary: Raise helpful message while allocating Memory w/o unit to Docker Container
Keywords:
Status: CLOSED DUPLICATE of bug 1243140
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-26 13:39 UTC by Jitendra Yejare
Modified: 2019-04-01 20:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-26 18:49:04 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jitendra Yejare 2016-04-26 13:39:07 UTC
Description of problem:
While creating a docker container from satellite and allocating memory to the container w/o unit(i.e m for mb,g for gb) satellite UI throws error:
"Oops, we're sorry but something went wrong undefined method `full_messages' for #<Array:0x007f5175822990>"
Some helpfull message should be raised to mention unit or by default memory size should be considered in mb.

Version-Release number of selected component (if applicable):
Sat 6.2 Snap 9.2

How reproducible:


Steps to Reproduce:
1. From UI, Attempt to create a docker container with custom Memory size without unit.
2. Attempt to submit the Container.

Actual results:
satellite UI throws error:
"Oops, we're sorry but something went wrong undefined method `full_messages' for #<Array:0x007f5175822990>"

Expected results:
Some helpfull message should be raised to mention unit or by default memory size should be considered in mb.

Comment 2 Brad Buckingham 2016-04-26 18:49:04 UTC

*** This bug has been marked as a duplicate of bug 1243140 ***


Note You need to log in before you can comment on or make changes to this bug.