Red Hat Bugzilla – Bug 1191855
firebug raises "TypeError: t is undefined" on selecting subnet from "Hostgroup --> New Hostgroup --> Network"
Last modified: 2016-07-27 04:47:51 EDT
Created attachment 990751 [details] Firebug raises "TypeError: t is undefined" on selecting subnet from dropdown. Description of problem: firebug raises "TypeError: t is undefined" on selecting subnet from "Hostgroup --> New Hostgroup --> Network TypeError: t is undefined ...bnet_id"),t=e.val(),n=e.data("subnets");return t==""?!0:n[t].ipam}$(document).on... Version-Release number of selected component (if applicable): Satellite-6.1.0-RHEL-6-20150210.0 Sat6.1.0 beta snap2 How reproducible: always Steps to Reproduce: 1. Go to "configure" --> Host Group --> New Host Group --> Network 2. select subnet from dropdown Actual results: Firebug raises "TypeError: t is undefined" on selecting subnet from dropdown. Expected results: no error should be raised on selecting subnet dropdown Additional info:
Created redmine issue http://projects.theforeman.org/issues/9443 from this bug
Dominic says in the upstream bug that this is actually fixed by http://projects.theforeman.org/issues/7456 which will be delivered in 1.8. Since this is a medium priority, I am moving this to ON_QA for 6.2 to be verified there.
Upstream bug assigned to ohadlevy@redhat.com
Failed QA attaching screenshot of error Uncaught TypeError: Cannot read property 'undefined' of undefined selectedSubnetHasIPAM @ host_edit-f28aad5e3f4a480dcd142fd790e49243.js:1subnet_ selected @ host_edit-f28aad5e3f4a480dcd142fd790e49243.js:1onchange @ new:1
Created attachment 1028363 [details] Chrome console error
Please test when 6.2 is available as suggested in previous comments. Moving back to ON_QA.
Verified in upstream. No errors found during selection. HOSTNAME: rhsm-qe-1.rhq.lab.eng.bos.redhat.com OS: redhat RELEASE: Red Hat Enterprise Linux Server release 7.1 (Maipo) FOREMAN: 1.11.0-develop RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux] PUPPET: 3.8.3
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:1500