Created attachment 1012169 [details] engine.log Description of problem: Firstly, add rhevh7.1 with vlan tagged to rhevm3.5.1. Then add nfs storage ad Date domain. It will report an error as follows. ================================================================================ Error while executing action Add Storage Connection: Problem while trying to mount target ================================================================================ Version-Release number of selected component (if applicable): rhev-hypervisor7-7.1-20150402.0.el7ev ovirt-node-3.2.2-3.el7.noarch ovirt-node-plugin-vdsm-0.2.0-20.el7ev.noarch vdsm-4.16.13-1.el7ev.x86_64 Red Hat Enterprise Virtualization Manager Version: 3.5.1-0.3.el6ev How reproducible: 100% Steps to Reproduce: 1. Install rhev-hypervisor7-7.1-20150402.0.el7ev. 2. Configure network with vlan tagged 3. Add rhevh7.1 to rhevm3.5.1 4. Attach nfs as data domain. Actual results: 1. After step3, it reports an error as follows. ================================================================================ Error while executing action Add Storage Connection: Problem while trying to mount target ================================================================================ Expected results: 1. It should attach nfs as data domain succeed. Additional info:
We need the VDSM log too please.
I have tested this issue for several times more and find the follow issues. 1. I can attach the nfs storage in vlan env now. So I can not reproduce this issue anymore. 2. But this issue indeed exists during my last testing process. I have tried 4 times to reproduced this issue. And the same nfs storage can be attached to rhevh6.6. 3. Since we can not reproduce this issue now. I suggested that we can adjust this bug priority and severity to low now. It's hard to say whether this issue is caused by our hardware environment or not. Or maybe it's caused by rhevm environment problem. Thanks.
Agreed. I've pushed it out to 3.6.0 in the meanwhile. If you have a reproducer and/or logs from a failing attempt, feel free to re-escalate this issue.
I was also unable to reproduce the bug; storage attached successfully to rhevh with networking on a tagged vlan.
As comment#8 said, we have tested the same nfs storage with rhevh6.7. And it's ok for that. And we also manual test mount of the storage in rhevh7.1, and it's also ok. The firewall is off in the server. But there is one thing so wried that I can not reporduce this issue today. As the comment#4 said, we encounter this issue again! 1. I can attach the nfs storage in vlan env now. So I can not reproduce this issue anymore. 2. But this issue indeed exists during my last testing process. I have tried 4 times to reproduced this issue. And the same nfs storage can be attached to rhevh6.6. 3. Since we can not reproduce this issue now. I suggested that we can adjust this bug priority and severity to low now. It's hard to say whether this issue is caused by our hardware environment or not. Or maybe it's caused by rhevm environment problem. Thanks! Hui Wang
(In reply to wanghui from comment #13) > But there is one thing so wried that I can not reporduce this issue today. > As the comment#4 said, we encounter this issue again! Thanks Hui! Yes, this bug is quite elusive. If anyone reproduces it again, please capture the vdsm logs from the rhevm; a manual mount attempt on the same host that failed would also help diagnose the issue.
(In reply to Greg Padgett from comment #14) > (In reply to wanghui from comment #13) > > But there is one thing so wried that I can not reporduce this issue today. > > As the comment#4 said, we encounter this issue again! > > Thanks Hui! Yes, this bug is quite elusive. If anyone reproduces it again, > please capture the vdsm logs from the rhevm; a manual mount attempt on the > same host that failed would also help diagnose the issue. There's no way to proceed here. I'm closing this bug in the meanwhile so it doesn't clutter up bugzilla. If it reproduces please feel free to reopen.