b64f9adbc6
Tenks/libvirt was not reusing the MAC address assigned when invoked repeatedly, which was leading to errors and confusion when extending an existing Tenks deployment. Check Ansible facts for a pre-existing interface and reuse the assigned MAC if one is found. Any existing MAC is added to the data structure returned by set_libvirt_interfaces. Change-Id: If45516d06d41992e7142ca8071ddcb84160a13e5 |
||
---|---|---|
.. | ||
add-support-for-libvirt-connection-uri-10fd40407fb1cc53.yaml | ||
ansible-2.7-2.8-63f01fbf5ab9ba08.yaml | ||
default-properties-a59636e41be05d66.yaml | ||
default-uefi-126f76735950188c.yaml | ||
do-not-install-openvswitch-651218091900ba27.yaml | ||
drop-py-2-7-d311573543d0e3ba.yaml | ||
fix-issue-mac-addresses-being-regenerated-36a90e18666a2dc0.yaml | ||
fix-reconfigure-1d1b11a57f4d1827.yaml | ||
fix-schedule-templating-05e4dcee8a1771b7.yaml | ||
fix-veth-uniqueness-05bf5ebfcd5d4929.yaml | ||
jinja-context-54bce72cab955ca0.yaml | ||
macvtap-passthrough-adfecbce7dcd8474.yaml | ||
node-vol-name-prefix-55fb7752014cfb86.yaml | ||
standalone-ironic-33281da1623e912d.yaml | ||
uefi-7a19ff8a549a3e9e.yaml | ||
virtualbmc-cryptography-03d62a3d1e965197.yaml | ||
virtualbmc-module-f9d40eb9198ca8c0.yaml | ||
virtualbmc-selinux-86a667ba27d9a05e.yaml |