Fix setting vGMUX VES server port via honeycomb

Fixes an issue where vpp would crash if the
VES server port number was set via honeycomb
rest call.  The port value was being handled as
a byte so larger values (e.g. 8080) caused the
problem.

Change-Id: Ib42725033f92d597524bbfda1f12cc7e43c87b4a
Issue-ID: INT-63
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>

diff --git a/vnfs/vCPE/vpp-ves-agent-for-vgmux/src/patches/Hc2vpp-Add-VES-agent-for-vG-MUX.patch b/vnfs/vCPE/vpp-ves-agent-for-vgmux/src/patches/Hc2vpp-Add-VES-agent-for-vG-MUX.patch
index 0f061fc..7899ed9 100644 (file)
--- a/vnfs/vCPE/vpp-ves-agent-for-vgmux/src/patches/Hc2vpp-Add-VES-agent-for-vG-MUX.patch
+++ b/vnfs/vCPE/vpp-ves-agent-for-vgmux/src/patches/Hc2vpp-Add-VES-agent-for-vG-MUX.patch
@@ -739,7 +739,7 @@ index 0000000..e06afa7
 +        throws WriteFailedException {
 +        final VesAgentConfig request = new VesAgentConfig();
 +
-+        request.serverPort = config.getServerPort().byteValue();
++        request.serverPort = config.getServerPort().intValue();
 +        request.readInterval = config.getReadInterval().byteValue();
 +        request.isAdd = config.getIsAdd().byteValue();
 +        request.serverAddr = ipv4AddressNoZoneToArray(config.getServerAddr().getValue());
@@ -1041,7 +1041,7 @@ index 0000000..62e46cd
 +        throws WriteFailedException {
 +        final VesAgentConfig request = new VesAgentConfig();
 +
-+        request.serverPort = config.getServerPort().byteValue();
++        request.serverPort = config.getServerPort().intValue();
 +        request.readInterval = config.getReadInterval().byteValue();
 +        request.isAdd = config.getIsAdd().byteValue();
 +        request.serverAddr = ipv4AddressNoZoneToArray(config.getServerAddr().getValue());