Description of problem: Even if button is showed as disabled it is clickable and working normally as enabled. Applies to almost every disabled button in UI. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: For example 1. Go to Monitor -> Jobs 2. Select job, that already run. 3. Buttons 'Cancel Job' and 'Abort Job' are disabled 4. Click on any disabled button Actual results: Button works even if, it is disabled. Page is refreshed and warning 'The job cannot be cancelled at the moment.' is shown Expected results: Clicking on disabled button does nothing Additional info: Found similar behavior in hosts. In Satellite 6.5 clicking on disabled button does nothing.
I noticed change of component. Just noting that same behavior is in 'Host details' as I mentioned above, not only in Remote Execution.
Thanks Peter, I missed that. Reverting to general WebUI then.
Created redmine issue https://projects.theforeman.org/issues/27813 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27831 has been resolved.
ON_QA Failed: @Satellite 6.6.0 snap 20.1 Steps: 1. Go to Monitor -> Jobs 2. Select job, that already run. 3. Buttons 'Rerun Failed' , 'Cancel Job' and 'Abort Job' are disabled 4. Click on any disabled button Actual results: 1. Button works even if, it is disabled. Page is refreshed and warning 'The job cannot be cancelled at the moment.' is shown 2. 'Rerun Failed' clickable 3. 'Abort Job' clickable
I couldn't reproduce the first two - for me they were always disabled, as for the third, it seem that on the first click it is disabled, and after that it will be enabled. added a small fix: - https://projects.theforeman.org/issues/27881 - https://github.com/theforeman/foreman/pull/7063
> I couldn't reproduce the first two - for me they were always disabled, Could you try to run a fresh job and see ?
Thanks Vijay, I saw it now only when creating, but after those few seconds they are always disabled.
Opened a PR to fix the first two issues in foreman_remote_execution: - https://projects.theforeman.org/issues/27930 - https://github.com/theforeman/foreman_remote_execution/pull/435 The PR that fixes the 3rd issue is already merged in Foreman: https://projects.theforeman.org/issues/27881
ON_QA Verified: @Satellite 6.6.0 snap 22.0 Steps: 1. Go to Monitor -> Jobs 2. Select job, that already run. or run a new job Actual results: a. 'Cancel Job' => if the job is running, it can be cancelled and after finish it can't b. 'Abort Job' => if the job is running, it can be Aborted and after finish it can't
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-2019:3172