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

Reduce the default oVirt open timeout to 1 minute #15099

Merged
merged 1 commit into from
May 17, 2017
Merged

Reduce the default oVirt open timeout to 1 minute #15099

merged 1 commit into from
May 17, 2017

Conversation

jhernand
Copy link
Contributor

Currently the timeout used when opening connections to oVirt isn't
explicitly set. That means that when trying to connect to an oVirt
system that doesn't exist, or that doesn't respond, it may take as long
as the TCP timeout till the error is detected. In a typical setup on top
of Linux this timeout is approx 2 minutes and 8 seconds. But in
production environments the web server that is in front of the ManageIQ
user interface has a request timeout explicitly set to 2 minutes. This
means that validation of credentials for oVirt systems that don't exist,
or don't respond are ignored by the ManageIQ user interface, because it
gives up before the error is detected by the ManageIQ server. To avoid
that issue this patch changes the default connection timeout used by the
oVirt provider to 1 minute.

https://bugzilla.redhat.com/1448065

Currently the timeout used when opening connections to oVirt isn't
explicitly set. That means that when trying to connect to an oVirt
system that doesn't exist, or that doesn't respond, it may take as long
as the TCP timeout till the error is detected. In a typical setup on top
of Linux this timeout is approx 2 minutes and 8 seconds. But in
production environments the web server that is in front of the ManageIQ
user interface has a request timeout explicitly set to 2 minutes. This
means that validation of credentials for oVirt systems that don't exist,
or don't respond are ignored by the ManageIQ user interface, because it
gives up before the error is detected by the ManageIQ server. To avoid
that issue this patch changes the default connection timeout used by the
oVirt provider to 1 minute.

https://bugzilla.redhat.com/1448065
@jhernand
Copy link
Contributor Author

@masayag @borod108 please review.

@miq-bot
Copy link
Member

miq-bot commented May 16, 2017

Checked commit https://github.com/jhernand/manageiq/commit/ec8664221bd59a129e63ea12092f44a8f41f9106 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
0 files checked, 0 offenses detected
Everything looks fine. 👍

Copy link

@borod108 borod108 left a comment

Choose a reason for hiding this comment

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

Great fix.

@chessbyte
Copy link
Member

@jhernand Maybe you should move the whole ems_redhat section of settings to https://github.com/ManageIQ/manageiq-providers-ovirt/blob/master/config/settings.yml

@jhernand
Copy link
Contributor Author

@chessbyte yes, that makes sense. How are upgrades managed in that case? I mean, what will happen for users that already did changes to their global settings file? Will the settings in the provider specific file override the settings in the global file or the other way around?

@bdunne bdunne merged commit 7e05340 into ManageIQ:master May 17, 2017
@bdunne
Copy link
Member

bdunne commented May 17, 2017

@jhernand Users shouldn't be changing anything in settings.yaml. Any settings changes should be done through the UI which are then saved in the database.

For extra credit, it would be nice if the key was also changed to ems_ovirt to match the provider plugin name. For this, you'll need a migration to update any settings records in the database.

@bdunne bdunne added this to the Sprint 61 Ending May 22, 2017 milestone May 17, 2017
@bdunne bdunne added fine/no and removed fine/no labels May 17, 2017
@bdunne
Copy link
Member

bdunne commented May 17, 2017

@jhernand Please add a Fine label

@jhernand
Copy link
Contributor Author

@miq-bot add_label fine/yes

simaishi pushed a commit that referenced this pull request Jun 15, 2017
…eout

Reduce the default oVirt open timeout to 1 minute
(cherry picked from commit 7e05340)

https://bugzilla.redhat.com/show_bug.cgi?id=1461860
@simaishi
Copy link
Contributor

Fine backport details:

$ git log -1
commit 10effaeaf66ad8697dba892339ac93c57ba2ff6f
Author: Brandon Dunne <brandondunne@hotmail.com>
Date:   Wed May 17 07:47:42 2017 -0400

    Merge pull request #15099 from jhernand/reduce_default_ovirt_open_timeout
    
    Reduce the default oVirt open timeout to 1 minute
    (cherry picked from commit 7e05340118a44de6614de1ebbfdff272daf2b45a)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1461860

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.

9 participants