git describe from the Make files state `fatal: No names found, cannot describe anything.`

[kishen-v]

/kind bug /area provider/ibmcloud

What steps did you take and what happened:

A few targets that use git describe seem to complain of fatal: No names found, cannot describe anything..

What did you expect to happen: No warnings or errors.

Anything else you would like to add:

This can be fixed with --always along with git describe, which will default to the latest commit hash. However, this seems to break a few of the commands which tend to accept ldflags, such as make docker-build. Thus, the necessary changes are needed to ensure the existing functionality offered.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[mkumatag]

/remove-lifecycle rotten