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
Drop the vnc_port start, end and range from the codebase #2954
Conversation
Not quite sure, but looks like this is used in
def reserve_next_available_vnc_port
port_start = ext_management_system.try(:host_default_vnc_port_start).try(:to_i) || 5900
port_end = ext_management_system.try(:host_default_vnc_port_end).try(:to_i) || 5999
... called from The reason I'm not as sure is that that method is called by |
Checked commit skateman@c2cb0b1 with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@himdel the |
Sounds like we should add the fields on adding as well :). Maybe it may make sense to prefill them with the defualt values? (Well, or if nobody is ever using it, drop the whole thing, even from the db, but.. do we know? :)) |
This is where @agrare or someone from the providers team could help us decide 😉 |
Hey @skateman what specifically do you need help deciding on? |
@agrare The choice is:
Basically, the question is: do customers ever set it to non-default values? |
I have to assume that yes, at some point, someone has set non-default values because security :) |
Closing this PR then, will create a new one where we display the fields on a new vmware provider form too. |
This seems like dead code to me, so ✂️ 🗑️ ✂️ 🔥 ✂️ 🚽
@martinpovolny and @agrare can you confirm?
https://bugzilla.redhat.com/show_bug.cgi?id=1514594