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.

Description of problem:
 Javascript errors seen when publishing a CV

Error: e.versions is undefined
m/<@https://abc.redhat.com.redhat.com/assets/bastion_katello/bastion_katello-19591ce9a122bede4cc22880922ca9ee086af20a4b51cb39d503d1311f11e576.js:3:14228
Sn/l/o.promise.then/u@https://abc.redhat.com.redhat.com/assets/bastion/bastion-996d46a5a76c6cd2252d536902fd48294b66334eba9d258e35372afc98f845d3.js:2:29876
Sn/s/<.then/<@https://abc.redhat.com.redhat.com/assets/bastion/bastion-996d46a5a76c6cd2252d536902fd48294b66334eba9d258e35372afc98f845d3.js:2:30562
kn/this.$get</c.prototype.$eval@https://abc.redhat.com.redhat.com/assets/bastion/bastion-996d46a5a76c6cd2252d536902fd48294b66334eba9d258e35372afc98f845d3.js:3:1954
kn/this.$get</c.prototype.$digest@https://abc.redhat.com.redhat.com/assets/bastion/bastion-996d46a5a76c6cd2252d536902fd48294b66334eba9d258e35372afc98f845d3.js:3:654
kn/this.$get</c.prototype.$apply@https://abc.redhat.com.redhat.com/assets/bastion/bastion-996d46a5a76c6cd2252d536902fd48294b66334eba9d258e35372afc98f845d3.js:3:2275
i@https://abc.redhat.com.redhat.com/assets/bastion/bastion-996d46a5a76c6cd2252d536902fd48294b66334eba9d258e35372afc98f845d3.js:2:16279
v@https://abc.redhat.com.redhat.com/assets/bastion/bastion-996d46a5a76c6cd2252d536902fd48294b66334eba9d258e35372afc98f845d3.js:2:18105
Kt/</x.onreadystatechange@https://abc.redhat.com.redhat.com/assets/bastion/bastion-996d46a5a76c6cd2252d536902fd48294b66334eba9d258e35372afc98f845d3.js:2:18644
	

...,headers:Ht(r),config:t})}function s(){var e=P(p.pendingRequests,t);-1!==e&&p.pe...




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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Javascript errors seen as shown in the description of the bug.

Expected results:
No Javascript related errors

Additional info:

I see a different error when publishing a CV:

TypeError: Cannot set property '0' of undefined
    at bastion_katello-c05d092….js:3
    at u (bastion-c4cbce0….js:2)
    at bastion-c4cbce0….js:2
    at c.$eval (bastion-c4cbce0….js:3)
    at c.$digest (bastion-c4cbce0….js:3)
    at c.$apply (bastion-c4cbce0….js:3)
    at i (bastion-c4cbce0….js:2)
    at v (bastion-c4cbce0….js:2)
    at XMLHttpRequest.x.onreadystatechange (bastion-c4cbce0….js:2)

which was fixed with bug #1240795 so I am marking this as a duplicate.  Once bug #1240795 is ON_QA please have a look at this bug as well.

*** This bug has been marked as a duplicate of bug 1240795 ***