-
Notifications
You must be signed in to change notification settings - Fork 897
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
Increase Timeouts and Worker Memory for Azure SSA #16016
Increase Timeouts and Worker Memory for Azure SSA #16016
Conversation
@miq-bot add_label fine/yes |
In support of high priority BZ https://bugzilla.redhat.com/show_bug.cgi?id=1488967 we need to increase various timeouts to allow the Azure SSA job to succeed. 1) Increase the Job timeout specific to Azure SSA similar to how it has been done for SCVMM previously. 2) Increase the SmartProxyWorker MiqQueue msg_timeout value similar to how it has been done for both SCVMM and OpenStack previously. 3) Increase the memory_threshold and restart_interval for all SmartProxyWorker jobs. The memory_threshold issue has been seen running SSA on other providers as well as Azure so the overall default change here is appropriate.
191b2a9
to
3b5b283
Compare
Checked commit jerryk55@3b5b283 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
@@ -82,6 +82,9 @@ def queue_call(ost) | |||
if target.kind_of?(ManageIQ::Providers::Openstack::CloudManager::Vm) || | |||
target.kind_of?(ManageIQ::Providers::Openstack::CloudManager::Template) | |||
timeout_adj = 4 | |||
elsif target.kind_of?(ManageIQ::Providers::Azure::CloudManager::Vm) || | |||
target.kind_of?(ManageIQ::Providers::Azure::CloudManager::Template) | |||
timeout_adj = 4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the future, we should probably have these classes implement a timeout function so we can just ask the target what it's timeout should be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup I said something to that effect in the description of the PR.
@@ -178,6 +178,9 @@ def timeout_adjustment | |||
if target.kind_of?(ManageIQ::Providers::Microsoft::InfraManager::Vm) || | |||
target.kind_of?(ManageIQ::Providers::Microsoft::InfraManager::Template) | |||
timeout_adjustment = 4 | |||
elsif target.kind_of?(ManageIQ::Providers::Azure::CloudManager::Vm) || | |||
target.kind_of?(ManageIQ::Providers::Azure::CloudManager::Template) | |||
timeout_adjustment = 4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as below.
@miq-bot add_label smart state |
@miq-bot add_label fine/yes |
@miq-bot Y U NO WORK |
😵 |
@jrafanie that is cheating... no logging into the bot account... |
@jrafanie unrecognized command 'Y', ignoring... Accepted commands are: add_label, assign, close_issue, move_issue, remove_label, rm_label, set_milestone |
I'm fine with the code change. There's no test even though the @roliveri please review/merge. |
…e_ssa Increase Timeouts and Worker Memory for Azure SSA (cherry picked from commit a3c9213) https://bugzilla.redhat.com/show_bug.cgi?id=1488967
Fine backport details:
|
…for_azure_ssa Increase Timeouts and Worker Memory for Azure SSA (cherry picked from commit a3c9213) https://bugzilla.redhat.com/show_bug.cgi?id=1488967
In support of high priority BZ https://bugzilla.redhat.com/show_bug.cgi?id=1488967
we need to increase various timeouts to allow the Azure SSA job to succeed.
done for SCVMM previously.
been done for both SCVMM and OpenStack previously.
The memory_threshold issue has been seen running SSA on other providers as well as
Azure so the overall default change here is appropriate.
Other PRs are related to the BZ as well but this PR may be merged in any order as there
are no prerequisites for it.
This PR should be back ported to FINE.
Please note that we should probably refactor the timeout code in items 1 and 2 above to distribute it to the Providers in question rather than have it live in the ManageIQ repo but that is an item for another day.
Links
Steps for Testing/QA [Optional]
Run SSA on various providers including Azure - especially with Managed Disks. along with other required PRs referenced in the BZ above the scan should complete.
@roliveri @jrafanie please review and merge as soon as possible to allow us to get this BZ addressed.