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

Fix vCloud and Tanzu inheriting vSphere's filtered events #936

Conversation

agrare
Copy link
Member

@agrare agrare commented Jan 28, 2025

The BaseManager.default_blacklisted_event_names method uses the provider name (aka Vmware) rather than the ems_type so all
ManageIQ::Providers::Vmware::*Managers were getting the vSphere blacklisted events

The BaseManager.default_blacklisted_event_names method uses the provider
name (aka Vmware) rather than the ems_type so all
ManageIQ::Providers::Vmware::*Managers were getting the vSphere
blacklisted events
@agrare agrare added the bug label Jan 28, 2025
@agrare agrare requested a review from Fryguy as a code owner January 28, 2025 21:37
@agrare
Copy link
Member Author

agrare commented Jan 28, 2025

@miq-bot cross-repo-tests ManageIQ/manageiq@master

miq-bot pushed a commit to ManageIQ/manageiq-cross_repo-tests that referenced this pull request Jan 28, 2025
@Fryguy Fryguy self-assigned this Jan 28, 2025
@@ -337,6 +337,10 @@ def self.provision_class(via)
end
end

def self.default_blacklisted_event_names
Settings.ems.ems_vmware.blacklisted_event_names
Copy link
Member Author

Choose a reason for hiding this comment

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

NOTE this one can't use ems_type because for the infra_manager ems_type is vmwarews not vmware

@Fryguy Fryguy merged commit dc6103d into ManageIQ:master Jan 28, 2025
3 of 4 checks passed
@agrare agrare deleted the fix_vmware_default_blacklisted_event_names_other_providers branch January 28, 2025 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants