-
Notifications
You must be signed in to change notification settings - Fork 896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate Methods hang after rails 5 upgrade #6814
Comments
I noticed this problem yesterday as well. It seems that it reaches the point where a subprocess is spawned that never wakes up from sleep for whatever reason, causing everything else to hang. |
This seems to happen because of MiqAePassword being undefined when executing this line of code https://github.com/ManageIQ/manageiq/blob/master/lib/miq_automation_engine/engine/miq_ae_service/miq_ae_service_object_common.rb#L5 if the MiqAePassword is required in lib/miq_automation_engine/engine/miq_ae_service.rb then we don't see this issue. |
Is it a difference with autoloading of files in test vs. dev/prod from rails 4 to 5? Did we change the autoload paths? |
@jrafanie Stepping thru the code we locate the correct file to be loaded but hang on this line Dependencies.load_interlock https://github.com/rails/rails/blob/v5.0.0.beta2/activesupport/lib/active_support/dependencies/interlock.rb#L11 |
It's a good thing we have the right person for the job @matthewd. 🙇 |
Ohhhhh, I see. The thing that invokes the drb needs to wrap the invocation in https://github.com/rails/rails/blob/master/activesupport/lib/active_support/dependencies/interlock.rb#L46 -- thereby promising it's not going to run any code that might hit an autoloadable constant inside the block / while it's waiting. |
Fixes ManageIQ#6814 The Automate methods were hanging when loading constants, which trigger require processing.
Fixes ManageIQ#6814 The Automate methods were hanging when loading constants, which trigger require processing.
After upgrading to rails 5 automate methods hang in dev and prod environment but works in test env.
The text was updated successfully, but these errors were encountered: