Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Bug 1323446

Summary:

UI: Unable to create Container NoMethodError: undefined method `full_messages' for []:Array

Product:

Red Hat Satellite

Reporter:

Tazim Kolhar <tkolhar>

Component:

Container Management

Assignee:

Daniel Lobato Garcia <dlobatog>

Status:

CLOSED WONTFIX

QA Contact:

Katello QA List <katello-qa-list>

Severity:

high

Docs Contact:

Priority:

unspecified

Version:

6.2.0

CC:

cwelton, tomckay

Target Milestone:

Unspecified

Keywords:

Triaged

Target Release:

Unused

Hardware:

Unspecified

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2018-08-02 20:59:08 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Bug Depends On:

Bug Blocks:

1247313

Attachments:

Description	Flags
Production.log for container create failure in UI	none

Description Tazim Kolhar 2016-04-03 06:10:52 UTC

Created attachment 1142919 [details]
Production.log for container create failure in UI

Description of problem:
Create Container in UI
NoMethodError: undefined method `full_messages' for []:Array

Version-Release number of selected component (if applicable):
# rpm -q foreman
foreman-1.11.0.9-1.el7sat.noarch


How reproducible:
everytime

Steps to Reproduce:
1.# hammer -u admin -p changeme compute-resource info --id 2
Resource compute_resource not found by id '2'
[root@hp-dl360g7-01 foreman]# hammer -u admin -p changeme compute-resource info --id 1
Id:            1
Name:          compute_docker_r
Provider:      Docker
Url:           unix:///var/run/docker.sock
Description:   
User:          
Organizations: 
    Default Organization
Created at:    2016/04/03 04:16:41
Updated at:    2016/04/03 04:16:41

2.# hammer -u admin -p changeme content-view info --name con_view --organization-id 1
ID:                     6
Name:                   con_view
Label:                  con_view
Composite:              false
Description:            
Content Host Count:     0
Organization:           Default Organization
Yum Repositories:       

Docker Repositories:    
 1) ID:    2
    Name:  test_prod_docker
    Label: test_prod_docker
OSTree Repositories:    

Puppet Modules:         

Lifecycle Environments: 
 1) ID:   1
    Name: Library
Versions:               
 1) ID:        5
    Version:   1.0
    Published: 2016/04/03 04:20:46
Components:             

Activation Keys:

3.In UI, Try to create a Container
2016-04-03 06:28:11 [app] [W] Action failed
 | NoMethodError: undefined method `full_messages' for []:Array

Actual results:
Container Creation failed

Expected results:
Container Create worked

Additional info:
attaching production.log

Comment 1 Brad Buckingham 2016-04-05 15:22:15 UTC

Hi Tazim,

Can you confirm that a 'Test Connection' via the UI works on the docker compute resource?

Also, can you provide details on the values of the parameters you provided (either text or screenshots) when going through the 'New Container' UI/widget?

I have seen the 'full_messages' error in other places when the Satellite is unable to interface with docker (e.g. bug 1318641) or if a value is invalid in the widget (e.g. container name invalid).

Comment 3 Tazim Kolhar 2016-04-11 09:22:18 UTC

Hi,

 
  Test Connection works properly:
  Test Connection was successful

  The list of values passed to the parameter:
   1. Deploy on : Docker
   2. Image tab :
       Lifecycle Environment : Library
       Content View: Default Organization view
       Repository : docker repo          
       Tag:"glibc"
       Capsule:default capsule
   3. Configuration tab: 
        Name: test_docker
        Command : bash
        Entry point : /bin/sh
        CPU sets: 1
        CPU shares : 1
        Memory : 512
   4. Environment tab:
        Attach STDIN : yes
        Attach STDOUT : yes
        Attach STDERR : yes        
       
  
Thanks and Regards,
Tazim

Comment 5 Bryan Kearney 2016-07-26 15:25:24 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 6 Bryan Kearney 2016-07-26 15:31:25 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 8 Bryan Kearney 2018-08-02 20:59:08 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.