-
Notifications
You must be signed in to change notification settings - Fork 63
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
Skip hostname validation for monitoring manager #220
Conversation
c9fb7b1
to
d0c4d4e
Compare
@zeari Cannot apply the following label because they are not recognized: gapridashvili/yes |
@miq-bot add_label gaprindashvili/yes |
Checked commit zeari@d0c4d4e with ruby 2.3.3, rubocop 0.52.0, haml-lint 0.20.0, and yamllint 1.10.0 |
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.
Perfect!
I'm still on the lookout for a cleaner interface to both UI and API then endpoints-with-side-effects. And I still hate the child delegates :endpoints, :to => :parent_manager
lie.
But for now, this is great 👍
cc @masayag you might want similar fix for kubevirt child manager. |
Is it worth to add tests for this to manageiq-api? |
@zeari could we have caught the breakage in the main repo by having a model spec doing If so, do you think it is worth doing? |
Verified locally: Without PR
With PR:
PS: (had to rebase the PR or I would get |
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.
LGTM 👍
Skip hostname validation for monitoring manager (cherry picked from commit d64480e) https://bugzilla.redhat.com/show_bug.cgi?id=1537137
Gaprindashvili backport details:
|
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1535941
The problem is that the monitoring manager looks for a default endpoint which it does not have.
The parent provider has that endpoint and validates it anyway so no need for the monitoring manager to validate it.
Another solution could be to delegate the default endpoint from the monitoring_manager to the parent provider or just regard the alert endpoint as the default endpoint for monitoring.
Monitoring manager has some prep work for the latter: https://github.com/manageiq/manageiq-providers-kubernetes/blob/master/app/models/manageiq/providers/kubernetes/monitoring_manager_mixin.rb#L59
but ext_management_system doesnt take it into account:
https://github.com/manageiq/manageiq/blob/master/app/models/ext_management_system.rb#L295
@cben @moolitayer Please review
@miq-bot add_label bug, gapridashvili/yes