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 2106022

Summary: Uncaught TypeError: window.update_interface_table is not a function
Product: Red Hat Satellite Reporter: Lukáš Hellebrandt <lhellebr>
Component: Compute Resources - VMWareAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: chrobert, lstejska, mhulan, rlavi
Target Milestone: UnspecifiedKeywords: EasyFix, MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 12:23:38 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:

Description Lukáš Hellebrandt 2022-07-11 14:35:47 UTC 
Description of problem:
When editing Compute profile field for a VMWare CR, I get the following error in the browser console:
```
Uncaught TypeError: window.update_interface_table is not a function
    success vmware.js:79
    jQuery 6
    onClusterChange vmware.js:68
    onClusterChange vmware.js:22
    onchange new:1
    jQuery 5
    triggerChange select2.js:1168
    onSelect select2.js:2465
    selectHighlighted select2.js:1870
    init select2.js:807
    bind select2.js:681
    jQuery 8
    init select2.js:804
    select2 select2.js:3391
    jQuery 2
    select2 select2.js:3378
    activate_select2 application-9111693c38a60f2b64407f369c1c059a54bee46206e49709bda0db678359fe9c.js:1
    onContentLoad application-9111693c38a60f2b64407f369c1c059a54bee46206e49709bda0db678359fe9c.js:1
    jQuery 5
    <anonymous> application-9111693c38a60f2b64407f369c1c059a54bee46206e49709bda0db678359fe9c.js:3
    jQuery 7
    Webpack 7
vmware.js:79:13


```
Also, this causes issues in automation and is perhaps related:
```
jQuery.active
1 
```

Version-Release number of selected component (if applicable):
Reproduced on Sat 6.11.0 and 6.10.7 with VMWare 6 and 7

How reproducible:
Deterministic

Steps to Reproduce:
1. Have a Satellite with some CR of type VMWare
2. Infrastructure -> Compute Profiles -> select any -> select the VMWare CR
3. Open console (ctrl+shift+k in Firefox)
4. Click the Cluster dropdown, select some cluster

Actual results:
Above mentioned error

Expected results:
Not sure what it's supposed to do but definitely no error
Comment 1 Ron Lavi 2023-03-15 13:24:25 UTC 
Created redmine issue https://projects.theforeman.org/issues/36201 from this bug
Comment 2 Brad Buckingham 2023-09-01 21:10:52 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 4 Brad Buckingham 2023-10-04 20:57:17 UTC 
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.
Comment 7 Eric Helms 2024-06-06 12:23:38 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.