-
Bug
-
Resolution: Unresolved
-
Major
-
6.18.0
-
3
-
False
-
Moderate
-
Satellite Endeavour Sprint 11
-
sat-endeavour
-
None
-
None
-
None
-
None
Description of problem:
When trying to abort the running job by clicking the 3 dots besides the Pending Status shows two messages:
~~~
Trying to abort the task for the host
Danger alert:Could not abort the task
~~~
- Observed below message in /var/log/foreman/production.log
# cat /var/log/foreman/production.log| grep -i 363766b2 2025-08-25T23:11:59 [I|app|363766b2] Started POST "/foreman_tasks/tasks/e9b84c74-c4e3-461d-9115-67768b3adcd5/abort" for 10.74.64.10 at 2025-08-25 23:11:59 +0530 2025-08-25T23:11:59 [I|app|363766b2] Processing by ForemanTasks::TasksController#abort as JSON 2025-08-25T23:11:59 [I|app|363766b2] Parameters: \{"id"=>"e9b84c74-c4e3-461d-9115-67768b3adcd5", "task"=>{}} 2025-08-25T23:11:59 [W|app|363766b2] private method `abort' called for nil:NilClass 2025-08-25T23:11:59 [I|app|363766b2] Backtrace for 'private method `abort' called for nil:NilClass' error (NoMethodError): private method `abort' called for nil:NilClass
How reproducible:
Always
Steps to Reproduce:
1. Navigate to Hosts --> Content Hosts --> Click on any Hosts --> Click on Schedule a Job --> Go to Job Page --> Click on 3 dots besides the Pending Status for the associated Host --> Click on Abort Job
2. After aborting, the job shows a message "Could not abort the task" and the job gets completed successfully
Actual behavior:
After clicking Abort Task, the concerned pop-up message Could not abort the task.
Expected behavior:
- After clicking the Abort Task option, the job should cancel immediately.
Business Impact / Additional info:
- is duplicated by
-
SAT-37352 When attempting to abort the running job by clicking 3 dots for associated host shows message "Could not abort the task"
-
- Closed
-