Bug 1672941
| Summary: | setup-engine requires pingable gateway | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Veaceslav Mindru <mindruv> |
| Component: | Network | Assignee: | Ido Rosenzwig <irosenzw> |
| Status: | CLOSED DUPLICATE | QA Contact: | Lukas Svaty <lsvaty> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.2.24 | CC: | bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-02-13 08:36:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
[root@server ansible]# hosted-engine --deploy
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
During customization use CTRL-D to abort.
Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine.
The locally running engine will be used to configure a new storage domain and create a VM there.
At the end the disk of the local VM will be moved to the shared storage.
Are you sure you want to continue? (Yes, No)[Yes]:
Configuration files: []
Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20190206045507-mcac3u.log
Version: otopi-1.7.8 (otopi-1.7.8-1.el7)
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization
--== STORAGE CONFIGURATION ==--
--== HOST NETWORK CONFIGURATION ==--
[ INFO ] Bridge ovirtmgmt already created
Please indicate a pingable gateway IP address [172.22.4.249]: [ ERROR ] Specified gateway is not pingable
Please indicate a pingable gateway IP address [172.22.4.249]:
[ ERROR ] Specified gateway is not pingable
Please indicate a pingable gateway IP address [172.22.4.249]:
[ ERROR ] Specified gateway is not pingable
Please indicate a pingable gateway IP address [172.22.4.249]:
Closing this bug as duplicate of bug #1659052 we are discussing there alternatives to pingable address. *** This bug has been marked as a duplicate of bug 1659052 *** |
Description of problem: Currently, engine-setup enforces a requirement for default pingable gateway, this is ignoring the fact that network routers can route traffic while ignoring ICMP requests. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.2.33-1.el7.noarch How reproducible: drop ( filter out ) ICMP requests on the server where engine-setup is being deployed or drop ( filter out) ICMP requests on the gateway. Steps to Reproduce: 1. iptables -A OUTPUT -p icmp --icmp-type echo-request -j DROP # DISABLE ICMP 2. setup-egine --deploy 3. engine will fail at an early stage assuming that GATEWAY is nonfunctional when nonpingable. Actual results: setup-engien --deploy cannot continue installation without smthing pingable ... Expected results: Do a proper check under ```129 valid = ohostedutil.check_is_pingable( 130 self, 131 self.environment[ 132 ohostedcons.NetworkEnv.GATEWAY 133 ] 134 ) ``` in plugins/gr-he-common/network/gateway.py Additional info: current workaround when you know your GATEWAY is functioning but it's not pingable for whatever reason. change ```129 valid = ohostedutil.check_is_pingable( 130 self, 131 self.environment[ 132 ohostedcons.NetworkEnv.GATEWAY 133 ] 134 ) ``` to ```129 valid = ohostedutil.check_is_pingable( 130 self, 131 self.environment[ 132 ohostedcons.NetworkEnv.GATEWAY 133 ] 134 ) valud = True ``` A proper fix would be to 1) proper do a better check on the gateway 2) give the use the possibility to continue to install.