Comment 12 for bug 1781121

Hi Amudha

I took the latest ovf from the specified location.

Ran ansible-playbook playbooks/vcenter.yml . There is still something missing.Please fix it.

[root@nodek4-compute-vm ~]#
[root@nodek4-compute-vm ~]# ifconfig
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet6 fe80::9288:aba4:d2e0:e6e prefixlen 64 scopeid 0x20<link>
        ether 00:50:56:a4:92:2a txqueuelen 1000 (Ethernet)
        RX packets 38 bytes 9120 (8.9 KiB)
        RX errors 0 dropped 1 overruns 0 frame 0
        TX packets 54 bytes 8996 (8.7 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens192: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 10.204.216.181 netmask 255.255.255.0 broadcast 10.204.216.255
        inet6 fe80::a0af:9125:f772:13ad prefixlen 64 scopeid 0x20<link>
        ether 00:50:56:aa:aa:03 txqueuelen 1000 (Ethernet)
        RX packets 476 bytes 44433 (43.3 KiB)
        RX errors 0 dropped 1 overruns 0 frame 0
        TX packets 73 bytes 9173 (8.9 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens224: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet6 fe80::9ee2:b14c:219:186b prefixlen 64 scopeid 0x20<link>
        ether 00:50:56:a4:20:56 txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 51 bytes 8994 (8.7 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 1000 (Local Loopback)
        RX packets 32 bytes 2592 (2.5 KiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 32 bytes 2592 (2.5 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@nodek4-compute-vm ~]#

[root@nodek6-compute-vm ~]#
[root@nodek6-compute-vm ~]#
[root@nodek6-compute-vm ~]# ifconfig
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        ether 00:25:90:c7:7f:f4 txqueuelen 1000 (Ethernet)
        RX packets 44 bytes 11540 (11.2 KiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 59 bytes 9290 (9.0 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
        device memory 0xfd400000-fd4fffff

ens192: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 10.204.216.183 netmask 255.255.255.0 broadcast 10.204.216.255
        inet6 fe80::3a64:a693:b05:b908 prefixlen 64 scopeid 0x20<link>
        ether 00:50:56:aa:aa:05 txqueuelen 1000 (Ethernet)
        RX packets 654 bytes 57651 (56.2 KiB)
        RX errors 0 dropped 1 overruns 0 frame 0
        TX packets 76 bytes 9519 (9.2 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens224: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        ether 00:50:56:a4:f6:c6 txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 50 bytes 8652 (8.4 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 1000 (Local Loopback)
        RX packets 32 bytes 2592 (2.5 KiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 32 bytes 2592 (2.5 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@nodek6-compute-vm ~]#

From: Amudha R <email address hidden>
Date: Friday, August 10, 2018 at 10:23 AM
To: Sandip Dey <email address hidden>, Sudheendra Rao <email address hidden>
Cc: Sachchidanand Vaidya <email address hidden>, Yuvaraja Mariappan <email address hidden>
Subject: Re: 5.0.1 - #1782515 - ContrailVM interface name change on reboot

Yes, it is the same vmdk.

-Amudha

From: Sandip Dey <email address hidden>
Date: Thursday, August 9, 2018 at 11:38 PM
To: Amudha R <email address hidden>, Sudheendra Rao <email address hidden>
Cc: Sachchidanand Vaidya <email address hidden>, Yuvaraja Mariappan <email address hidden>
Subject: Re: 5.0.1 - #1782515 - ContrailVM interface name change on reboot

Can the same image be used for ram also?I am planning to test everything using eam now

From: Sandip Dey <email address hidden>
Date: Friday, August 10, 2018 at 10:05 AM
To: Amudha R <email address hidden>, Sudheendra Rao <email address hidden>
Cc: Sachchidanand Vaidya <email address hidden>, Yuvaraja Mariappan <email address hidden>
Subject: Re: 5.0.1 - #1782515 - ContrailVM interface name change on reboot

This was exactly what was needed.

What if there are multiple-ctrl interface ?In case of bond we need it.What will be the naming?

                            mgmt ctrl-data vmware_phy_int

single-intf ens160 — ens192 >>>>>> can we make it ‘ens224’ to be consistent in all the cases?

Regards
Sandip

From: Amudha R <email address hidden>
Date: Friday, August 10, 2018 at 10:02 AM
To: Sandip Dey <email address hidden>, Sudheendra Rao <email address hidden>
Cc: Sachchidanand Vaidya <email address hidden>, Yuvaraja Mariappan <email address hidden>
Subject: Re: 5.0.1 - #1782515 - ContrailVM interface name change on reboot

https://bugs.launchpad.net/juniperopenstack/+bug/1782515
https://bugs.launchpad.net/juniperopenstack/+bug/1781121

For the above two bugs,

- I have removed the /firstboot script which was renaming the PCI/SRIOV interfaces,
  and saved the vmdk at /cs-shared/contrail-vcenter/vmdk/centos-7.5/LATEST.
  Note: This was added in ubuntu to keep interface names consistent across reboots,
  and does not seem needed in centos7.5. Have tested the latest vmdk and the
  interface names are consistent across reboots.

- Check for driver type to be vmxnet3 while picking the vmware_physical_nterface,
  fixed in https://review.opencontrail.org/#/c/45470/ .

With this, the interfaces will come up as below:

                            mgmt ctrl-data vmware_phy_int

single-intf ens160 — ens192

multi-intf ens160 ens192 ens224
(ctrl-data)

multi-intf ens160 ens192 ens224
(pci/sriov)

Please test with the latest vmdk and the review above merged, and let me know of any issues.

Thanks,
Amudha