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.
1. Proposed title of this feature request
[RFE] set release version of a content host via bulk action
2. In non-public update...
3. What is the nature and description of the request?
When doing a bulk action on content hosts, the "Content Host Content" tab allows you to set the Lifecycle Environment and Content View, but not the Release Version. This is possible when changing the host one-by-one.
4. Why does the customer need this? (List the business requirements here)
Moving hundreds of servers from one Release to another without changing it one-by-one.
5. How would the customer like to achieve this? (List the functional requirements here)
Add "release version" field to the bulk action dialog for content.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Have a content host in Satellite, select it, click bulk action, click content, set the release version.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Not that I would be aware of
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
No, but 6.2.z would be nice.
9. Is the sales team involved in this request and do they have any additional input?
No
10. List any affected packages or components.
katello
11. Would the customer be able to assist in testing this functionality if implemented?
Yes
Tested with sat6.3 GA snap27
Nothing happens on UI on selecting the "Set Release version" from bulk actions, and see following error in "developer tools"
---
bastion-fdb3a220e59a…935485bc360516.js:2 Error: [$injector:unpr] Unknown provider: NotificationProvider <- Notification <- ContentHostsBulkReleaseVersionModalController
http://errors.angularjs.org/1.5.5/$injector/unpr?p0=NotificationProvider%20%3C-%20Notification%20%3C-%20ContentHostsBulkReleaseVersionModalController
at bastion-fdb3a220e59a…935485bc360516.js:1
at bastion-fdb3a220e59a…935485bc360516.js:1
at Object.r [as get] (bastion-fdb3a220e59a…935485bc360516.js:1)
at bastion-fdb3a220e59a…935485bc360516.js:1
at r (bastion-fdb3a220e59a…935485bc360516.js:1)
at a (bastion-fdb3a220e59a…935485bc360516.js:1)
at Object.o [as invoke] (bastion-fdb3a220e59a…935485bc360516.js:1)
at c.instance (bastion-fdb3a220e59a…935485bc360516.js:2)
at bastion-fdb3a220e59a…35485bc360516.js:72
at o (bastion-fdb3a220e59a…935485bc360516.js:3)
--
Verified with satellite 6.3 snap29.
I can set release version on multiple content hosts through bulk action and task was completed successfully. Please see the attached screenshot.
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/RHSA-2018:0336