-
Notifications
You must be signed in to change notification settings - Fork 898
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
Cloud VM should be marked as connected by default #18213
Cloud VM should be marked as connected by default #18213
Conversation
With this commit we set default value of connection stats for cloud instances, which is supposed to be 'connected' for all of them. That's because cloud instances can not reach disconnected state. Until now `connection_stats = nil` was the default which is interpreted as 'disconnected' by MIQ -> which is imposssible for cloud instances per se. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1649403 Fixes ManageIQ/manageiq-ui-classic#4909 Signed-off-by: Miha Pleško <miha.plesko@xlab.si>
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
Thanks @miha-plesko This wasn't your initial solution. I appreciate you hearing me out and putting this PR together. @agrare can decide which one works best for the providers as a whole |
Sorry guys for opening the 3rd PR on this topic today - I'm struggling between fixing it for vCloud only or fixing it in general and risk breaking other providers :) I kind of like the solution @kbrock suggested. Nice thing is also that rspecs will explode in all cloud providers (where we assert |
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.
Checked commit miha-plesko@dd0ff97 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@miha-plesko this will work for newly created VMs but we would need a migration to fix existing VMs as those will still show disconnected. For a lower risk change I'd recommend overriding FTR I think a data migration to update all null connection_states to "connected" and changing the parsers to set it always is a good idea so we don't have unset values in the db. |
Cool, let me open a separate PR on vcd as you suggest so we needn't backport this one. @miq-bot remove_label hammer/yes |
Closing in favor of #18216 accompanied with provider inventory updates where we'll explicitly set connection_state to |
With this commit we set default value of connection stats for cloud instances, which is supposed to be 'connected' for all of them. That's because cloud instances can not reach disconnected state. Until now
connection_stats = nil
was the default which is interpreted as 'disconnected' by MIQ -> which is imposssible for cloud instances per se.Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1649403
Fixes ManageIQ/manageiq-ui-classic#4909
@miq-bot assign @agrare
@miq-bot add_label enhancement,hammer/yes
/cc @kbrock @Fryguy @skateman