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.
Description of problem:
It should be easier to delete content hosts where registration failed (e.g. when registering in scale). Issue which caused registration to fail is not subject of this bugzilla.
Version-Release number of selected component (if applicable):
satellite-6.2.0-8.2.beta.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. Have few content hosts, where registration failed, e.g. with some of
the error messages bellow:
Task <uuid>: RestClient::InternalServerError: 500 Internal Server Error
There was an issue with the backend service pulp: Pulp message bus connection issue.
There was an issue with the backend service pulp: 500 Internal Server Error
2. Attempt to delete these content hosts:
Hosts -> Content Hosts -> tick few of them -> Bulk Actions -> Remove Hosts
Actual results:
Now deleting task fails because some of its sub-tasks fails. To make it pass, you have to:
1. Go to failed parent task's sub tasks
2. Find these with State: stopped/Result: error
3. Open the link in the Error message which says:
> Required lock is already taken by other running tasks.
> Please inspect their state, fix their errors and resume them.
>
> Required lock: read
> Conflicts with tasks:
> - https://<fqdn>/foreman_tasks/tasks/b1654849-ec92-4e9e-bd68-78d925a2a8d4
4. Click [Dynflow Console] (make sure this works - because page is autoreloading, sometimes you have to click multiple times to make it work)
5. Click "Skip" at red row
6. Click resume and see the task to change from paused / warning to stopped / warning
7. Go back to Hosts -> Content Hosts
8. Select system(s) which had the problem again and delete it using bulk actions
Expected results:
There should be some workflow where this all would be possible via simmilar number of clicks as single ... -> Bulk Actions -> Remove Hosts
Additional info:
Imagine use case as I was solving: I was registering via subscription-manager in bunches 10 of 100 clients in parallel (1000 clients in total) and in different of these bunches few hosts failed. I have ended with 23 invalid profiles. When I have attempted to delete these, it meant 115+ clicks on Satellite webUI. There seems not to be a way to script this via Hammer (looks like there is simply no required API).
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Description of problem: It should be easier to delete content hosts where registration failed (e.g. when registering in scale). Issue which caused registration to fail is not subject of this bugzilla. Version-Release number of selected component (if applicable): satellite-6.2.0-8.2.beta.el7sat.noarch How reproducible: always Steps to Reproduce: 1. Have few content hosts, where registration failed, e.g. with some of the error messages bellow: Task <uuid>: RestClient::InternalServerError: 500 Internal Server Error There was an issue with the backend service pulp: Pulp message bus connection issue. There was an issue with the backend service pulp: 500 Internal Server Error 2. Attempt to delete these content hosts: Hosts -> Content Hosts -> tick few of them -> Bulk Actions -> Remove Hosts Actual results: Now deleting task fails because some of its sub-tasks fails. To make it pass, you have to: 1. Go to failed parent task's sub tasks 2. Find these with State: stopped/Result: error 3. Open the link in the Error message which says: > Required lock is already taken by other running tasks. > Please inspect their state, fix their errors and resume them. > > Required lock: read > Conflicts with tasks: > - https://<fqdn>/foreman_tasks/tasks/b1654849-ec92-4e9e-bd68-78d925a2a8d4 4. Click [Dynflow Console] (make sure this works - because page is autoreloading, sometimes you have to click multiple times to make it work) 5. Click "Skip" at red row 6. Click resume and see the task to change from paused / warning to stopped / warning 7. Go back to Hosts -> Content Hosts 8. Select system(s) which had the problem again and delete it using bulk actions Expected results: There should be some workflow where this all would be possible via simmilar number of clicks as single ... -> Bulk Actions -> Remove Hosts Additional info: Imagine use case as I was solving: I was registering via subscription-manager in bunches 10 of 100 clients in parallel (1000 clients in total) and in different of these bunches few hosts failed. I have ended with 23 invalid profiles. When I have attempted to delete these, it meant 115+ clicks on Satellite webUI. There seems not to be a way to script this via Hammer (looks like there is simply no required API).