Hide Forgot
Description of problem: ----------------------- After a server role is selected/deselected, the corresponding worker thread refuses to start/stop. Version-Release number of selected component (if applicable): ------------------------ 5.6 How reproducible: ----------------- Always Steps to Reproduce: ------------------ 1.Select a server role and save the configuration setting.Observe that the worker role refuses to start. 2.Alternatively, deselect a server role and observe that the corresponding worker refuses to stop. Actual results: --------------- After a server role is selected/deselected, the corresponding worker thread refuses to start/stop. Expected results: ----------------- After a server role is selected/deselected, the corresponding worker thread should start/stop. Additional info: ----------------
This issue exists in Beta 2 as well.I'm unable to start the C&U worker threads because of this issue.This issue is blocking C&U testing.
https://github.com/ManageIQ/manageiq/pull/8060
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/29695c7bbbb0a1930052ec2a25b0dcc498b0bc77 commit 29695c7bbbb0a1930052ec2a25b0dcc498b0bc77 Author: Joe Rafaniello <jrafanie> AuthorDate: Mon Apr 18 14:19:19 2016 -0400 Commit: Joe Rafaniello <jrafanie> CommitDate: Mon Apr 18 17:08:19 2016 -0400 Clear the my_server cache so we can detect role changes faster. With a cached MiqServer, sync_needed? fails to detect changes to active roles within a reasonable amount of time. The default cache_with_timeout value is 5 minutes. With this change, we'll refetch the my_server with each iteration of the monitor loop. https://bugzilla.redhat.com/show_bug.cgi?id=1325738 app/models/miq_server/worker_management/monitor.rb | 3 +++ 1 file changed, 3 insertions(+)
Verified in 5.6.0.4-beta2.3
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/RHBA-2016:1348