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.
If you have a controller with a section_id of "X" then no row in the tupane can have the accessor which returns "X". If you do then both both body and the tupane row have id="X" which causes issues with the ajax refresh.
There are a series of commits that address this the final and latest being:
commit 9448eb84988a00728dab3660dbd2d1a9ad25ae6e
This issue was addressed by adding a new convention for representing model resources as DOM IDs. They are now prefixed with their resource or controller type followed by an underscore and then the id. For example, instead of id="ACME_Corporation", it would now be id="organization_ACME_Corporation" or "system_1" instead of simply "1".