ci: fix issues introduced by Go 1.10

[sboeuf]

Now that our CI has moved to Go 1.10, we need to update one file that is not formatted as the new gofmt (1.10) expects it to be formatted.

[bergwolf]

Can we have a CI policy in place that any change in CI should pass proper CI first? I hope that we are not performing a test-driven development by merging tests first and catching up with code change.

[bergwolf]

Created kata-containers/tests/issues/258 to enforce such a policy.

[sboeuf]

@bergwolf the CI always gates any PR from being merged. The problem we have/had here is that we switched the Go version directly on the Jenkins server scripts, and no PR is needed for this...
@jcvenegas @chavafg I think we should make sure that we can setup the Go version from the test scripts we have into github.com/kata-containers/tests, otherwise next Go version switch will cause the same trouble.

[chavafg]

yes, sorry for this, we will be using a script on kata-containers/tests (see kata-containers/tests#255) that will install the go version in versions.yaml file. I see that we have switched again to 1.9 for the moment. We should also update https://github.com/kata-containers/runtime/blob/master/versions.yaml#L136 to 1.9 instead of 1.10, at least until we fix the issues with go1.10.