gRPC plugin config issue

[sbezverk]

Hello,

Here is the config I am using:

# GRPC endpoint defines IP address and port (if tcp type) or unix domain socket file (if unix type).
endpoint: /var/lib/networkservicemesh/dataplane.sock

# If unix domain socket file is used for GRPC communication, permissions to the file can be set here.
# Permission value uses standard three-or-four number linux binary reference.
permission: 000

# If socket file exists in defined path, it is not removed by default, GRPC plugin tries to use it.
# Set the force removal flag to 'true' ensures that the socket file will be always re-created
force-socket-removal: false

# Available socket types: tcp, tcp4, tcp6, unix, unixpacket. If not set, defaults to tcp.
network: unix

# Maximum message size in bytes for inbound mesages. If not set, GRPC uses the default 4MB.
max-msg-size: 4096

# Limit of server streams to each server transport.
max-concurrent-streams: 0

It seems it does not get parsed correctly as grpc plugin still looks for TCP type and not Unix type as requested by the config.

time="2018-07-18 17:05:24.54274" level=error msg="Error loading core: plugin GRPC: Init error 'listen tcp: address /var/lib/networkservicemesh/dataplane.sock: missing port in address', took 256.069µs" loc="core/event_loop.go(29)" logger=agentcore
2018-07-18 17:05:24,547 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 140375511230656 for <Subprocess at 140375511229432 with name agent in state STARTING> (stdout)>
2018-07-18 17:05:24,547 INFO exited: agent (exit status 0; not expected)
2018-07-18 17:05:24,547 DEBG received SIGCLD indicating a child quit
2018-07-18 17:05:25,548 INFO gave up: agent entered FATAL state, too many start retries too quickly

[edwarnicke]

+1 this would be most helpful to resolve.

[sbezverk]

Closing this issue as the issue is with vpp-agent's vendored version of cn-infra, currently vpp-agent comes with older version which does not support grpc for unix sockets.