Skip to content
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

MiqSmartProxyWorker not running in Podified #20497

Merged

Conversation

agrare
Copy link
Member

@agrare agrare commented Aug 28, 2020

SmartState jobs aren't getting started on podified, no MiqSmartProxyWorker is running so the start signal never gets run.

require_nested :Runner

self.required_roles = ["smartproxy"]
self.default_queue_name = "smartproxy"

def self.supports_container?
true
end
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if this was an oversight or there was a reason for the smart proxy worker not running on pods

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than this worker, only the cockpit worker doesn't support containers:

>> MiqWorker.leaf_subclasses.reject(&:supports_container?).map(&:name)
=> ["MiqCockpitWsWorker"]

Maybe better to change the default in the base class to true and just say not supported in the cockpit worker?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. Maybe we didn't enable the smart proxy because we didn't know if we could scan things in pods?

ManageIQ/manageiq-pods#595
ManageIQ/manageiq-pods#596

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want to support it by default in all workers other than cockpit and possibly this one, yeah, I agree, we should default to support in the base class and have them disable it in those one or two classes.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah if that's the reason then that's only RHV fleecing the rest are fine (this happened to be Azure SSA)

Copy link
Member Author

@agrare agrare Aug 29, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any discussion on #15884 about which workers to enable and why unfortunately

@miq-bot
Copy link
Member

miq-bot commented Aug 28, 2020

Checked commit agrare@3acd8ac with ruby 2.6.3, rubocop 0.69.0, haml-lint 0.28.0, and yamllint
1 file checked, 0 offenses detected
Everything looks fine. 🍰

@Fryguy Fryguy self-assigned this Aug 31, 2020
@Fryguy Fryguy merged commit ff7f15b into ManageIQ:master Aug 31, 2020
@agrare agrare deleted the smart_proxy_worker_not_running_in_podified branch August 31, 2020 13:35
simaishi pushed a commit that referenced this pull request Aug 31, 2020
…in_podified

MiqSmartProxyWorker not running in Podified

(cherry picked from commit ff7f15b)
@simaishi
Copy link
Contributor

Jansa backport details:

$ git log -1
commit ff39526599465a2f815d95f582ff0f245b9cc0bd
Author: Jason Frey <fryguy9@gmail.com>
Date:   Mon Aug 31 09:34:51 2020 -0400

    Merge pull request #20497 from agrare/smart_proxy_worker_not_running_in_podified

    MiqSmartProxyWorker not running in Podified

    (cherry picked from commit ff7f15bccf2c2c08843bc206bc2a63b5de06b96d)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants