Are you trying to deploy the hosted engine to a Storage Domain which is in a separate
network with a VLAN?
If this is the issue you must inform VDSM the network so it finds the path. This must be
informed during the playbook phase where it asks for the shared storage settings.
For example:
storage-network.json:
{"networks": {"storage": {"bonding": "bond0",
"bridged": false, "vlan": 192, "ipaddr":
"192.168.10.1", "netmask": "255.255.255.248",
"defaultRoute": false}}, "bondings": {}, "options":
{"connectivityCheck": false}}
vdsm-client -f storage-network.json Host setupNetworks
Sent from my iPhone
On 4 Feb 2020, at 19:15, "clam2718(a)gmail.com"
<clam2718(a)gmail.com> wrote:
Hello,
I am having this same issue and have inserted the three new lines from
https://github.com/ansible/ansible/issues/66858
into
"/lib/python2.7/site-packages/ansible/modules/cloud/ovirt/ovirt_network.py" yet
the issue still occurs when attempting deployement. I have rebooted the oVirt Node hosts
since patching to no avail. Do I need to insert the fix elsewhere or take other action to
properly apply this fix?
Thank you very much for your assistance.
Respectfully,
Charles
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UKWVUWZBISU...