Bug 1336727 - Javascript error is raised for create docker compute resource process
Summary: Javascript error is raised for create docker compute resource process
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.2.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-17 10:27 UTC by Oleksandr Shtaier
Modified: 2019-09-26 14:00 UTC (History)
1 user (show)

Fixed In Version: rubygem-foreman_docker-2.0.1.10-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:23:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Log with JS stack traces (2.03 KB, text/plain)
2016-05-17 10:37 UTC, Oleksandr Shtaier 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15135 0 None None None 2016-05-23 11:07:30 UTC

Description Oleksandr Shtaier 2016-05-17 10:27:03 UTC 
Description of problem:
When I try to create new compute resource I am getting JS error in console

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

How reproducible:
Always

Steps to Reproduce:
1. Go to Infrastructure->Compute Resource
2. Push 'New Compute Resource' button
3. Enter any value into 'Name' field
4. Choose 'Docker' provider
5. Put correct value into 'URL' field (e.g. 'unix:///var/run/docker.sock')
6. Push 'Submit' button
'TypeError' exception is raised

Actual results:
Create process raises JS error

Expected results:
Create process doesn't raise JS error

Additional info:
Issue existed in BETA too
Comment 1 Oleksandr Shtaier 2016-05-17 10:37:13 UTC 
Created attachment 1158242 [details]
Log with JS stack traces
Comment 2 Oleksandr Shtaier 2016-05-17 10:37:31 UTC 
Test automation blocker
Comment 5 Daniel Lobato Garcia 2016-05-23 10:58:42 UTC 
Created redmine issue http://projects.theforeman.org/issues/15135 from this bug
Comment 6 Bryan Kearney 2016-05-23 12:16:35 UTC 
Upstream bug component is Container Management
Comment 7 Daniel Lobato Garcia 2016-05-24 08:14:48 UTC 
PR waiting for review at https://github.com/theforeman/foreman-docker/pull/164
Comment 8 Bryan Kearney 2016-05-30 10:17:08 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/15135 has been closed
Comment 9 Oleksandr Shtaier 2016-06-02 12:52:48 UTC 
Functionality works as intended on 6.2 SNAP14. Test automation cases passed for problematic area successfully
Comment 10 Bryan Kearney 2016-07-27 11:23:26 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.