Bug 1387146
| Summary: | Proxy set when running hosted-engine may prevent completion | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Jon Archer <jonathan.archer> |
| Component: | General | Assignee: | Simone Tiraboschi <stirabos> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikolai Sednev <nsednev> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0.3.1 | CC: | bugs, stirabos, ylavi |
| Target Milestone: | ovirt-4.0.6 | Keywords: | Reopened, Triaged |
| Target Release: | 2.0.4 | Flags: | rule-engine:
ovirt-4.0.z+
ylavi: planning_ack+ sbonazzo: devel_ack+ mavital: testing_ack+ |
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
Adding from https://gerrit.ovirt.org/#/c/65955/
network:
Add a warning if a proxy is in use, since a not properly configured proxy could prevent the host to reach the engine VM.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-18 07:27:13 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1396051 | ||
|
Description
Jon Archer
2016-10-20 09:11:07 UTC
(In reply to Jon Archer from comment #0) > Description of problem: > When running the deployment of the hosted engine, if you have a proxy set as > an environment variable there is a chance that the check (hosted-engine > --check-liveliness) which is done towards the end will fail. > > May be worth mentioning that if a proxy is to be used to gain access to > repositories that it should be configured within yum.conf rather than as an > exported environment variable. > > Side effect of the check not responding as required prevents the installer > from completing the final stages i.e. copying answer file to shared storage, > setting up HA. I guess it will be safer to drop all environment variables that may cause check-liveliness to use a proxy. Thanks for the report! You have just to use the no_proxy env var to filter out local machines. On my opinion we should honor the system configuration, it's up to the user to correctly configure it. Something like: http_proxy="http://myproxysrv:8080/" no_proxy=".mydomain.local,host1,host2,192.168.1.18" Agreed, what I was suggesting is that we mention it in the documentation. It's caught me out a couple of times - through nobodies fault but my own - and its annoying that you get almost to the end of the installer and find that you are stuck in a loop of the check-liveliness not responding correctly and the only option is to quit out, clean up and start again. I'm sure there would be ways to prevent this i.e. have a detection for proxy and set a no_proxy for the HE fqdn during the deploy process. But for now highlighting it may be useful. OK, maybe overblown, but could be worth to check and add an early warning since the user will notify the issue only at the end of the deployment process. Forth to my last chat with Simone, this bug only adds a proper warning for customer in case of host was configured by customer to work over web-proxy server. prior to hosted-engine deployment.
In order to verify the bug, I've pre-configured my host to work with not-existing web-proxy server and initiated hosted-engine deployment, right at the beginning I've received proper warning, just as appears bellow:
[ INFO ] Hardware supports virtualization
Configuration files: []
Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20161130171457-83gshm.log
Version: otopi-1.5.2 (otopi-1.5.2-1.el7ev)
[WARNING] It seems that this host is configured to use a proxy, please ensure that this host will be able to reach the engine VM trough that proxy or add a specific exception.
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Generating libvirt-spice certificates
Moving this bug to verified as it works for me on these components on host:
rhevm-appliance-20161116.0-1.el7ev.noarch
ovirt-imageio-daemon-0.4.0-0.el7ev.noarch
vdsm-4.18.17-1.el7ev.x86_64
rhev-release-4.0.6-3-001.noarch
sanlock-3.4.0-1.el7.x86_64
ovirt-host-deploy-1.5.3-1.el7ev.noarch
ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch
ovirt-imageio-common-0.3.0-0.el7ev.noarch
libvirt-client-2.0.0-10.el7.x86_64
ovirt-vmconsole-host-1.0.4-1.el7ev.noarch
qemu-kvm-rhev-2.6.0-27.el7.x86_64
ovirt-hosted-engine-ha-2.0.5-1.el7ev.noarch
rhevm-appliance-20161116.0-1.el7ev.noarch
ovirt-setup-lib-1.0.2-1.el7ev.noarch
ovirt-vmconsole-1.0.4-1.el7ev.noarch
mom-0.5.8-1.el7ev.noarch
ovirt-hosted-engine-setup-2.0.4-2.el7ev.noarch
Linux version 3.10.0-514.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Wed Oct 19 11:24:13 EDT 2016
Linux 3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.3 (Maipo)
|