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

[BUG] crc and snc don't use the same routes-controller image #3502

Closed
cfergeau opened this issue Feb 7, 2023 · 5 comments
Closed

[BUG] crc and snc don't use the same routes-controller image #3502

cfergeau opened this issue Feb 7, 2023 · 5 comments
Assignees
Labels
kind/bug Something isn't working

Comments

@cfergeau
Copy link
Contributor

cfergeau commented Feb 7, 2023

snc uses quay.io/crcont/routes-controller:${image_tag}
https://github.com/crc-org/snc/blob/4ada0a93e0e3de2b0fbd328ef43096c7563a7ed9/createdisk.sh#L79-L80

crc uses quay.io/crcont/routes-controller:latest

Spec: v1.PodSpec{
ServiceAccountName: "router",
Containers: []v1.Container{
{
Name: "routes-controller",
Image: "quay.io/crcont/routes-controller:latest",
ImagePullPolicy: v1.PullIfNotPresent,
},
},
},

Not sure which one should be changed, the easiest would be to tag quay.io/crcont/routes-controller:${image_tag} as latest when pulling it in snc, but I'm not sure crictl supports setting tags.

@cfergeau cfergeau added kind/bug Something isn't working status/need triage labels Feb 7, 2023
@cfergeau
Copy link
Contributor Author

cfergeau commented Feb 7, 2023

I suspect because of this inconsistency crc pulls the routes-controller image from quay at cluster creation instead of reusing the cached one. If the cached image is still the latest one, it's not very important, but if the cached one is no longer also the latest, this is more problematic

@gbraad
Copy link
Contributor

gbraad commented Feb 8, 2023

If the cached image is still the latest one, it's not very important,

inconsistencies like this can lead to hard to track issues. we can't assume these are both pointing to 'latest'. It would be better to use a tag that is identical on both ends.

@praveenkumar
Copy link
Member

praveenkumar commented Feb 13, 2023

In case of openshift preset we should use the image tag as openshift_version since we are now building it for each openshift release and for podman preset we should use the latest tag.

Edit: looks like we don't need this image for podman preset and we might put this logic to the snc side and in crc side just create the deployment/pod.

@cfergeau cfergeau moved this to Scheduled in Project planning: crc Feb 14, 2023
praveenkumar added a commit to praveenkumar/snc that referenced this issue Jun 13, 2023
This PR adds deployment resource for route controller which use correct
image tag, what we cached. Once the bundle is created using this PR, we
will also need to make change on crc side. The resource file is located
in `/opt` dir same as `kubeconfig` file.

- crc-org/crc#3502
praveenkumar added a commit to praveenkumar/snc that referenced this issue Jun 14, 2023
This PR adds deployment resource for route controller which use correct
image tag, what we cached. Once the bundle is created using this PR, we
will also need to make change on crc side. The resource file is located
in `/opt` dir same as `kubeconfig` file.

- crc-org/crc#3502
praveenkumar added a commit to praveenkumar/snc that referenced this issue Jun 14, 2023
This PR adds deployment resource for route controller which use correct
image tag, what we cached. Once the bundle is created using this PR, we
will also need to make change on crc side. The resource file is located
in `/opt` dir same as `kubeconfig` file.

- crc-org/crc#3502
praveenkumar added a commit to praveenkumar/snc that referenced this issue Jun 14, 2023
This PR adds deployment resource for route controller which use correct
image tag, what we cached. Once the bundle is created using this PR, we
will also need to make change on crc side. The resource file is located
in `/opt/crc` dir.

- crc-org/crc#3502
praveenkumar added a commit to praveenkumar/snc that referenced this issue Jun 15, 2023
This PR adds deployment resource for route controller which use correct
image tag, what we cached. Once the bundle is created using this PR, we
will also need to make change on crc side. The resource file is located
in `/opt/crc` dir.

- crc-org/crc#3502
praveenkumar added a commit to praveenkumar/snc that referenced this issue Jun 21, 2023
This PR adds deployment resource for route controller which use correct
image tag, what we cached. Once the bundle is created using this PR, we
will also need to make change on crc side. The resource file is located
in `/opt/crc` dir.

Also if we take this in it will not going to have any effect on created
bundle until we implement the logic on crc side and it will be just a
unused extra file in the bundle.

- crc-org/crc#3502
praveenkumar added a commit to crc-org/snc that referenced this issue Jun 21, 2023
This PR adds deployment resource for route controller which use correct
image tag, what we cached. Once the bundle is created using this PR, we
will also need to make change on crc side. The resource file is located
in `/opt/crc` dir.

Also if we take this in it will not going to have any effect on created
bundle until we implement the logic on crc side and it will be just a
unused extra file in the bundle.

- crc-org/crc#3502
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/snc that referenced this issue Jun 21, 2023
This PR adds deployment resource for route controller which use correct
image tag, what we cached. Once the bundle is created using this PR, we
will also need to make change on crc side. The resource file is located
in `/opt/crc` dir.

Also if we take this in it will not going to have any effect on created
bundle until we implement the logic on crc side and it will be just a
unused extra file in the bundle.

- crc-org/crc#3502
praveenkumar added a commit to crc-org/snc that referenced this issue Jun 23, 2023
This PR adds deployment resource for route controller which use correct
image tag, what we cached. Once the bundle is created using this PR, we
will also need to make change on crc side. The resource file is located
in `/opt/crc` dir.

Also if we take this in it will not going to have any effect on created
bundle until we implement the logic on crc side and it will be just a
unused extra file in the bundle.

- crc-org/crc#3502
@praveenkumar praveenkumar moved this from Scheduled to Done in Project planning: crc Jun 27, 2023
@praveenkumar
Copy link
Member

This is fixed by crc-org/snc@fe6a6d2

/close

@openshift-ci openshift-ci bot closed this as completed Sep 5, 2023
@openshift-ci
Copy link

openshift-ci bot commented Sep 5, 2023

@praveenkumar: Closing this issue.

In response to this:

This is fixed by crc-org/snc@fe6a6d2

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

4 participants