Add an explanatory messages around TCP-MD5

Just pointing to epoll unavailabality reason is not enough, we
should also explain that the user can get PCEP working without
TCP/MD5 keys.

JIRA: BGPCEP-916
Change-Id: I95d5d087f99a29a6d823041e40a841b2f0367be8
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
(cherry picked from commit 7bfa8189dafc5bbc5e1f6ab7da1e7377a059b944)

diff --git a/pcep/impl/src/main/java/org/opendaylight/protocol/pcep/impl/PCEPDispatcherImpl.java b/pcep/impl/src/main/java/org/opendaylight/protocol/pcep/impl/PCEPDispatcherImpl.java
index d89095cfee7feb801aa612ff5311415b2b1c3397..4da6a70d266a987e2ec5714c85a7f6a0fbaf2482 100644 (file)
--- a/pcep/impl/src/main/java/org/opendaylight/protocol/pcep/impl/PCEPDispatcherImpl.java
+++ b/pcep/impl/src/main/java/org/opendaylight/protocol/pcep/impl/PCEPDispatcherImpl.java
@@ -120,7 +120,8 @@ public class PCEPDispatcherImpl implements PCEPDispatcher, Closeable {
             if (Epoll.isAvailable()) {
                 b.option(EpollChannelOption.TCP_MD5SIG, this.keys);
             } else {
-                throw new UnsupportedOperationException(Epoll.unavailabilityCause().getCause());
+                throw new UnsupportedOperationException("Setting TCP-MD5 signatures is not supported",
+                        Epoll.unavailabilityCause().getCause());
             }
         }