Bug #17779
openWhen doing a bulk action moving many (100+) content hosts to new content view, some clients stay on old content view
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1384139
Description of problem:
When doing a bulk action moving many (100+) content hosts to new content view, some clients stay on old content view until you enter the individual content host, reselect the content view and then save. Then running subscription-manager refresh generates a "1 local certificate deleted" (or similar) message - then a 'yum repoinfo' reloads repo data from the Satellite app with the correct content view selected.
How reproducible:
Always, in customer environment.
Steps to Reproduce:
1. Select 100+ content hosts
2. Attempt to move them all to a new content view via Bulk Action
Actual results:
Some content hosts will not be changed to the new content view after the action completes.
Expected results:
All content hosts should be moved to the new view upon action completion.
Updated by Justin Sherrill over 8 years ago
- Subject changed from When doing a bulk action moving many (100+) content hosts to new content view, some clients stay on old content view to When doing a bulk action moving many (100+) content hosts to new content view, some clients stay on old content view
- Translation missing: en.field_release set to 114