Error: annotation "app.openshift.io/vcs-uri"=git@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" value length exceeds Kubernetes max 63

[jeffgus]

/kind bug

What versions of software are you using?

Fedora 39

odo v3.15.0 (10b5e8a)

How did you run odo exactly?

odo dev --platform podman

Actual behavior

Error occurred on Push - exit status 125: 
Complete Podman output:
Error: annotation "app.openshift.io/vcs-uri"="xxxxxxxxx" value length exceeds Kubernetes max 63

odo dev used against Openshift seems to work. It doesn't complain about any annotation.

Expected behavior

Pods should start.

Any logs, error output, etc?

Error occurred on Push - exit status 125: 
Complete Podman output:
Error: annotation "app.openshift.io/vcs-uri"="xxxxxxxxx" value length exceeds Kubernetes max 63

[jeffgus]

If I change the repo to a shorter string in the .git/config, then pod will start using odo dev --platform podman

[jeffgus]

I installed podman 5 from (currentlly pre-release) Fedora 40 repo. The new podman does NOT trigger this error. Should this ticket be closed if the problem only happens on pre-podman 5 releases?

[rm3l]

I installed podman 5 from (currentlly pre-release) Fedora 40 repo. The new podman does NOT trigger this error. Should this ticket be closed if the problem only happens on pre-podman 5 releases?

Thanks for reporting this issue, @jeffgus ! Indeed, I found this related issue (containers/podman#21663), which has been fixed in Podman v5.0.0.

So the recommendation would be to use Podman v5+. Or, if not possible, as a temporary workaround, rename the Git remote into anything other than origin (so that odo won't try to add the annotation).

Closing this issue then, but feel free to reopen if you think otherwise.

/close not-planned

[openshift-ci]

@rm3l: Closing this issue, marking it as "Not Planned".

In response to this:

I installed podman 5 from (currentlly pre-release) Fedora 40 repo. The new podman does NOT trigger this error. Should this ticket be closed if the problem only happens on pre-podman 5 releases?

Thanks for reporting this issue, @jeffgus ! Indeed, I found this related issue (containers/podman#21663), which has been fixed in Podman v5.0.0.

So the recommendation would be to use Podman v5+. Or, if not possible, as a temporary workaround, rename the Git remote into anything other than origin (so that odo won't try to add the annotation).

Closing this issue then, but feel free to reopen if you think otherwise.

/close not-planned

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.