Bug 1162283
| Summary: | Cannot register ovirt-node image to ovirt-engine | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Raul Laansoo <raul.laansoo> | ||||||
| Component: | vdsm | Assignee: | Nir Soffer <nsoffer> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Gil Klein <gklein> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.5 | CC: | amureini, bazulay, bugs, danken, dfediuck, ecohen, fdeutsch, gklein, iheim, lsurette, mgoldboi, raul.laansoo, rbalakri, yeylon | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.5.1 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | storage | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-11-18 06:03:18 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 1161021 | ||||||||
| Bug Blocks: | 1193195 | ||||||||
| Attachments: |
|
||||||||
|
Description
Raul Laansoo
2014-11-10 18:07:58 UTC
This could be related to iptables settings being changed when you add the host / register it. Can you verify if there were any configuration changes in iptables before and after? It could be related to bug 1149655. That bug is about registering 3.4 host with 3.5 engine, but maybe that is because the Node used here is very old, and might not have the relevant jsonrpc patches. The fact that the host looses all connectivity makes me think that you are experiencing bug 1144639, and not the one suggested by Fabian. Your attached log state that you are running vdsm 4.16.4-0.el6, which is prior to ovirt-3.5.0 release and the resolution of the said bug. Could you retry installation using a post-3.5.0 release (vdsm >= 4.16.7)? I have attached logs from latest install on CentOS 6.6, vdsm-4.16.7-1.gitdb83943.el6.src.rpm Created attachment 956884 [details]
node logs
The symptoms are exactly the same, when I issue echo "1" > /sys/class/fc_host/host/issue_lip on node host. Does vdsm rescan storage interconnects when starting? Raul, supervdsm.log confirms your suggestion:
MainProcess|storageRefresh::DEBUG::2014-11-13 00:20:37,752::supervdsmServer::101::SuperVdsm.ServerCallback::(wrapper) call hbaRescan with () {}
MainProcess|storageRefresh::INFO::2014-11-13 00:20:37,752::hba::54::Storage.HBA::(rescan) Rescanning HBAs
MainProcess|storageRefresh::DEBUG::2014-11-13 00:20:37,753::hba::56::Storage.HBA::(rescan) Issuing lip /sys/class/fc_host/host0/issue_lip
MainProcess|storageRefresh::DEBUG::2014-11-13 00:20:38,061::hba::56::Storage.HBA::(rescan) Issuing lip /sys/class/fc_host/host1/issue_lip
MainProcess|storageRefresh::DEBUG::2014-11-13 00:20:38,408::supervdsmServer::108::SuperVdsm.ServerCallback::(wrapper) return hbaRescan with None
The LIP has been disabled by default in http://gerrit.ovirt.org/#/c/34215/ which would be part of ovirt-3.5.1. I'd appreciate if you verify that this is indeed your issue by taking the patch.
I can verify that this patch solves the issue I reported. *** This bug has been marked as a duplicate of bug 1152587 *** |