🐛 Fix log in clusterctl move

[mnitchev]

What this PR does / why we need it:
The clusterObj will be empty after failure and the log will not print the actual cluster that the cli is trying to get. If there is a bad reference in one of the objects in the graph this leads to a lot of confusion about what's actually failing.

/area clusterctl

[k8s-ci-robot]

@mnitchev: The label(s) area/clustectl cannot be applied, because the repository doesn't have them.

In response to this:

What this PR does / why we need it:
The clusterObj will be empty after failure and the log will not print the actual cluster that the cli is trying to get. If there is a bad reference in one of the objects in the graph this leads to a lot of confusion about what's actually failing.

/area clustectl

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

Welcome @mnitchev!

It looks like this is your first PR to kubernetes-sigs/cluster-api 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @mnitchev. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mnitchev]

/area clusterctl

[killianmuldoon]

Looks good - thanks!

/lgtm
/ok-to-test

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: bab6af65d660aee5f82f5b8607f94eea3dafd81d

[sbueringer]

Thx!

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sbueringer]

/retest