Bug 1320493

Summary: Javascript errors when selecting cv in hostgroup
Product: Red Hat Satellite Reporter: Kedar Bidarkar <kbidarka>
Component: WebUIAssignee: Partha Aji <paji>
WebUI sub component: Katello QA Contact: Kedar Bidarkar <kbidarka>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: bbuckingham, oshtaier
Version: 6.2.0Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:14:27 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:

Description Kedar Bidarkar 2016-03-23 10:49:40 UTC
Description of problem:

Javascript errors when selecting cv in hostgroup

TypeError: t is null
	

...=KT.hosts.getPuppetEnvironmentSelect();e.val(t.id),e.trigger("change")})},KT.hos...

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

How reproducible:


Steps to Reproduce:
1. create a hostgroup and assign CV 
2. I think this happens when the CV has no puppet-module associated to it.
3.

Actual results:
javascript errors seen as below

TypeError: t is null
...=KT.hosts.getPuppetEnvironmentSelect();e.val(t.id),e.trigger("change")})},KT.hos...

Expected results:


No javascript related errors should be seen


Additional info:

Comment 2 Oleksandr Shtaier 2016-03-23 12:15:14 UTC
Same error for Host entity

Comment 3 Partha Aji 2016-04-22 21:35:06 UTC
The fix for https://bugzilla.redhat.com/show_bug.cgi?id=1318743 should fix this also moving to on_qa

Comment 4 Kedar Bidarkar 2016-05-26 12:45:21 UTC
No javascript errors seen now when selecting cv in hostgroup


VERIFIED with sat62-snap(GA)-13.1

Comment 5 Bryan Kearney 2016-07-27 11:14:27 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