Added owner reference for nns to node

[pitiK3U]

Resolves #13

[ovirt-infra]

Hello contributor, thanks for submitting a PR for this project!

I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.

In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

1. Type ci test please on this PR to trigger automated tests for it.
2. Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically. ( keep in mind this list might be overwritten if the job XML is refreshed, for permanent whitelisting, please follow add status object to NodeNetworkState with nmstate error #3 option )
3. If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

[SchSeba]

there is a reason why we update the go modules on this PR?

[pitiK3U]

Oh, no. Sorry I forgot to delete unused import.

[phoracek]

Tested manually. (We can add a test removing Nodes, but we don't know how to add them back)

[SchSeba]

I still see a change in the lock file.

I think you need to revert this also or the lock file will not be in sync

[SchSeba]

Tested manually. (We can add a test removing Nodes, but we don't know how to add them back)

@phoracek I think the best solution for this is to create another lane in the STD-CI with just one test (ginkgo focus) to remove the node.

[phoracek]

@SchSeba it looks like there was an issue with the lock before and we just randomly fixed it here by running dep ensure.

[phoracek]

ci test please

[phoracek]

ci test please

[phoracek]

@SchSeba let's do the test :) thanks for not letting me to be lazy

[phoracek]

ci test please

[phoracek]

ci test please

[phoracek]

ci test please