Hello,
I was able to address the problem. The solution that Daniel provided worked on
our Kilo, HCG, and Liberty labs. It did not work on our Mitaka lab. The issue
seems to be the way that Ubuntu 16.04, system, and cloud-init interact with our
Mitaka lab. We had to add the following line to the yaml file for the Ubuntu
16.04 vms:
# Disable cloud-init for networking on reboot
echo 'network: {config: disabled}' >>
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
That disable the networking part of cloud-init after the reboot. That seemed to
solve the problem.
I've attached my updated yaml file in anyone is interested.
Thanks and take care,
Chris
[cid:image001.png at 01D1F3C0.B46A49B0]
Chris Reece
Technologist
www.AwardSolutions.com<http://www.awardsolutions.com/>
(W) 972-664-0727 x242
[cid:image003.png at
01D1F3D6.75565C80]<https://devops2.awardsolutions.com/portal/>[cid:image005.png
at
01D1F3D6.75565C80]<https://www.linkedin.com/company/award-solutions>[cid:image007.png
at 01D1F3D6.75565C80]<https://twitter.com/awardsolutions>
2100 Lakeside Blvd, Suite 300
Richardson, TX 75082 USA
Recognized 8x in Best Companies to Work for in Texas |
More<http://www2.awardsolutions.com/BestCompaniesTX_AwardSolutions.pdf>
Official Technology Training Partner of CTIA |
More<http://www.ctiasupermobility2016.com/events/eventdetails.cfm/2849>
NOTICE: The unauthorized use, copying, and/or distribution of the information
contained in this e-mail message and its attachments is strictly prohibited;
said information is confidential, may also contain proprietary matter, and is
intended solely for disclosure to and use by the intended recipient. If you
are not the intended recipient, please notify me immediately by e-mail, do not
use, copy or disseminate the information and please immediately delete this
email from your system. The sender is not aware of the presence of any virus in
this email or its attachments. The sender makes no warranty as to viruses and
accepts no liability for any damage or loss caused by any virus transmitted via
this email or its attachments and you are encouraged to check the email and its
attachments for viruses.
From: ROSE, DANIEL V [mailto:[email protected]]
Sent: Thursday, April 13, 2017 9:33 AM
To: Chris Reece <creece at awardsolutions.com>; onap-discuss at lists.onap.org
Subject: RE: Ubuntu 16.04 VM do not have eth0
I would check and see what version of 16.04 added this version of systemd:
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
My guess is yours is after systemd v197 while rackspace's is before. Its also
possible however that since the naming is now based on the specifics of the
VMs, you may have different drivers exposed then Rackspace does that force the
difference.
Workaround is probably to change the property at the bottom, see if it works
and we can look into incorporating that into the main heat template.
Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308
From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at
lists.onap.org> [mailto:[email protected]] On Behalf Of Chris
Reece
Sent: Thursday, April 13, 2017 9:16 AM
To: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>
Subject: [onap-discuss] Ubuntu 16.04 VM do not have eth0
Hello All,
I have been able to install ONAP on a OPNFV Colorado lab (Mitaka), but for the
three vms that require Ubuntu 16.04 they become unreachable after the install.
I can ssh when they are first created, but after they do the reboot at the end
of the cloud init commands, they become unreachable.
I am able to console into the vm and see that neither eth0 or ens3 come up
after the reboot.
I can see that the grub and interfaces.d/*.cfg files are changed based on the
following commands:
sed -i 's/GRUB_CMDLINE_LINUX=.*/GRUB_CMDLINE_LINUX=\"net.ifnames=0
biosdevname=0\"/g' /etc/default/grub
grub-mkconfig -o /boot/grub/grub.cfg
sed -i 's/ens3/eth0/g' /etc/network/interfaces.d/*.cfg
But when I do a ifconfig -a it still shows the ens3 interface and it fails to
come up.
Here is a screen shot after the reboot:
[cid:image005.png at 01D2B60F.0E660F60]
The interface file:
[cid:image006.png at 01D2B60F.0E660F60]
Looking at the syslog - it looks like eth0 cannot be found:
[cid:image007.png at 01D2B60F.0E660F60]
I have tried with both Ubuntu 16.04 (from April of last year) and Ubuntu
16.04.2. Both have the same results.
Thanks in advance for any help!
Chris
[cid:image001.png at 01D1F3C0.B46A49B0]
Chris Reece
Technologist
www.AwardSolutions.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.awardsolutions.com_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=TJJr4xiGiPHUrDv5Uuv5cfISviITMJWBhEePJsYg2Mo&s=UFjQx700w0lKKzSkiqv3YntB1472j9RKFaMREN1jqdg&e=>
[cid:image003.png at
01D1F3D6.75565C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__devops2.awardsolutions.com_portal_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=TJJr4xiGiPHUrDv5Uuv5cfISviITMJWBhEePJsYg2Mo&s=w-VqzLkGlmmw4-VqABhuTHh6FFnmusrCZ3ljL92j1tk&e=>[cid:image005.png
at
01D1F3D6.75565C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_award-2Dsolutions&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=TJJr4xiGiPHUrDv5Uuv5cfISviITMJWBhEePJsYg2Mo&s=0MRHE9E4kA5a-PaHM-jvSscsjyxUxIOg6btp6G8hSw8&e=>[cid:image007.png
at
01D1F3D6.75565C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_awardsolutions&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=TJJr4xiGiPHUrDv5Uuv5cfISviITMJWBhEePJsYg2Mo&s=lvNUT6D_DTkCMD6xMgpUv3Yso3Nm4qMrFzocrn3-pvU&e=>
2100 Lakeside Blvd, Suite 300
Richardson, TX 75082 USA
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170415/73dc54cb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2326 bytes
Desc: image001.png
URL:
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170415/73dc54cb/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 2989 bytes
Desc: image002.png
URL:
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170415/73dc54cb/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 2771 bytes
Desc: image003.png
URL:
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170415/73dc54cb/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 2836 bytes
Desc: image004.png
URL:
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170415/73dc54cb/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 17039 bytes
Desc: image005.png
URL:
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170415/73dc54cb/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 11551 bytes
Desc: image006.png
URL:
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170415/73dc54cb/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 23570 bytes
Desc: image007.png
URL:
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170415/73dc54cb/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: onap_openstack_041417.yaml
Type: application/octet-stream
Size: 61732 bytes
Desc: onap_openstack_041417.yaml
URL:
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170415/73dc54cb/attachment-0001.obj>
