search

redhat-developer / odo

odo - Developer-focused CLI for fast & iterative container-based application development on Podman and Kubernetes. Implementation of the open Devfile standard.
https://odo.dev
Apache License 2.0
773 stars 244 forks source link

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

Closed jeffgus closed 2 months ago

jeffgus commented 2 months ago

/kind bug

What versions of software are you using?

Fedora 39

odo v3.15.0 (10b5e8a8f)

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 commented 2 months ago

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

jeffgus commented 2 months ago

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 commented 2 months ago

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 (https://github.com/containers/podman/issues/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[bot] commented 2 months ago

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

In response to [this](https://github.com/redhat-developer/odo/issues/7237#issuecomment-2083566391): >> 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 (https://github.com/containers/podman/issues/21663), which has been fixed in Podman [v5.0.0](https://github.com/containers/podman/releases/tag/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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.