Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postinstallation Job "storage-version-migration-eventing" inmemorychannels #8415

Open
VikSh404 opened this issue Jan 21, 2025 · 2 comments
Open
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. triage/accepted Issues which should be fixed (post-triage)

Comments

@VikSh404
Copy link

The post-installation job went down when we upgraded the version from 1.14 to 1.15.

To Reproduce:

kubectl create -f eventing-post-install.yaml
clusterrole.rbac.authorization.k8s.io/knative-eventing-post-install-job-role created
serviceaccount/knative-eventing-post-install-job created
clusterrolebinding.rbac.authorization.k8s.io/knative-eventing-post-install-job-role-binding created
job.batch/storage-version-migration-eventing-kfm2q created

We had an error in storage-version-migration-eventing job:

Image

Image

We needed to delete the CRD from the list of the args of the storage-version-migration-eventing:

          args:
            - "apiserversources.sources.knative.dev"
            - "brokers.eventing.knative.dev"
            - "channels.messaging.knative.dev"
            - "containersources.sources.knative.dev"
            - "eventtypes.eventing.knative.dev"
            - "inmemorychannels.messaging.knative.dev"    <------ deleted this CRD
            - "parallels.flows.knative.dev"
            - "pingsources.sources.knative.dev"
            - "sequences.flows.knative.dev"
            - "sinkbindings.sources.knative.dev"
            - "subscriptions.messaging.knative.dev"
            - "triggers.eventing.knative.dev"
            - "jobsinks.sinks.knative.dev"

It helped us to apply the post-install script. Is it expected behavior? It looks like the "inmemorychannels.messaging.knative.dev" should be optional.

@VikSh404 VikSh404 added the kind/bug Categorizes issue or PR as related to a bug. label Jan 21, 2025
@pierDipi
Copy link
Member

pierDipi commented Feb 3, 2025

Copy link

knative-prow bot commented Feb 3, 2025

@pierDipi:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

I think there is an IGNORE_NOT_FOUND env variable [1] we could configure in the Job [2].

[1] https://github.com/knative/pkg/blob/efddeac3ec350b35316c3e1f9f0d79092a13eed1/apiextensions/storageversion/cmd/migrate/main.go#L37-L60
[2] https://github.com/knative/eventing/blob/main/config/post-install/storage-version-migrator.yaml

/good-first-issue

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-sigs/prow repository.

@knative-prow knative-prow bot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Feb 3, 2025
@pierDipi pierDipi added the triage/accepted Issues which should be fixed (post-triage) label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Development

No branches or pull requests

2 participants