[VOL-5178] - Fix dst iface in DT deployment files
* The deployment files for DT had a non-existing
iface name defined and the Robot tests were
failing to perform some dataplane tests. The
iface name that should be used in the DHCP
server in the Berlin lab (which is the dst
endpoint in the files) is "ens1f0".
Change-Id: I8d1e167cf2135321662002ecd48cf027ec36638c
diff --git a/deployment-configs/berlin-community-pod-1-gpon-adtran-DT.yaml b/deployment-configs/berlin-community-pod-1-gpon-adtran-DT.yaml
index 11c4551..0ccaf2e 100644
--- a/deployment-configs/berlin-community-pod-1-gpon-adtran-DT.yaml
+++ b/deployment-configs/berlin-community-pod-1-gpon-adtran-DT.yaml
@@ -125,7 +125,7 @@
noroot_ip: 10.34.90.43
noroot_user: community
noroot_pass: admin
- dp_iface_name: ens3f0
+ dp_iface_name: ens1f0
dp_iface_ip: null
dp_iface_gateway: null
container_type: null
@@ -138,7 +138,7 @@
noroot_ip: 10.34.90.43
noroot_user: community
noroot_pass: admin
- dp_iface_name: ens3f0
+ dp_iface_name: ens1f0
dp_iface_ip: null
dp_iface_gateway: null
container_type: null
@@ -151,7 +151,7 @@
noroot_ip: 10.34.90.43
noroot_user: community
noroot_pass: admin
- dp_iface_name: ens3f0
+ dp_iface_name: ens1f0
dp_iface_ip: null
dp_iface_gateway: null
container_type: null
@@ -164,7 +164,7 @@
noroot_ip: 10.34.90.43
noroot_user: community
noroot_pass: admin
- dp_iface_name: ens3f0
+ dp_iface_name: ens1f0
dp_iface_ip: null
dp_iface_gateway: null
container_type: null