fix portmap port forward flakiness

Use a Describe container for the It code block of the
portmap port forward integration test.

Signed-off-by: Antonio Ojea <antonio.ojea.garcia@gmail.com>

plugins/meta/portmap/portmap_integ_test.go

@@ -96,6 +96,7 @@ var _ = Describe("portmap integration tests", func() {
 		}
 	})
 
+	Describe("Creating an interface in a namespace with the ptp plugin", func() {
 		// This needs to be done using Ginkgo's asynchronous testing mode.
 		It("forwards a TCP port on ipv4", func(done Done) {
 			var err error
@@ -171,6 +172,18 @@ var _ = Describe("portmap integration tests", func() {
 			cmd.Stdout = GinkgoWriter
 			Expect(cmd.Run()).To(Succeed())
 
+			// dump ip routes output for debugging
+			cmd = exec.Command("ip", "route")
+			cmd.Stderr = GinkgoWriter
+			cmd.Stdout = GinkgoWriter
+			Expect(cmd.Run()).To(Succeed())
+
+			// dump ip addresses output for debugging
+			cmd = exec.Command("ip", "addr")
+			cmd.Stderr = GinkgoWriter
+			cmd.Stdout = GinkgoWriter
+			Expect(cmd.Run()).To(Succeed())
+
 			// Sanity check: verify that the container is reachable directly
 			contOK := testEchoServer(contIP.String(), containerPort, "")
 
@@ -209,6 +222,7 @@ var _ = Describe("portmap integration tests", func() {
 			close(done)
 
 		}, TIMEOUT*9)
+	})
 })
 
 // testEchoServer returns true if we found an echo server on the port