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

[QE]update the squid image version #4555

Closed
wants to merge 1 commit into from

Conversation

lilyLuLiu
Copy link
Contributor

Description

Relates to: #4551

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change
  • Chore (non-breaking change which doesn't affect codebase;
    test, version modification, documentation, etc.)

Proposed changes

Testing

Contribution Checklist

  • I Keep It Small and Simple: The smaller the PR is, the easier it is to review and have it merged
  • I have performed a self-review of my code
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Which platform have you tested the code changes on?
    • Linux
    • Windows
    • MacOS

@openshift-ci openshift-ci bot requested review from adrianriobo and cfergeau January 8, 2025 09:08
Copy link

openshift-ci bot commented Jan 8, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign adrianriobo for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@lilyLuLiu lilyLuLiu self-assigned this Jan 8, 2025
Copy link

openshift-ci bot commented Jan 8, 2025

@lilyLuLiu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/integration-crc 1913cab link true /test integration-crc
ci/prow/e2e-crc 1913cab link true /test e2e-crc

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@@ -215,7 +215,7 @@ func InitializeScenario(s *godog.ScenarioContext) {
if tag.Name == "@proxy" {

// start container with squid proxy
err := util.ExecuteCommand("podman run --name squid -d -p 3128:3128 quay.io/crcont/squid")
err := util.ExecuteCommand("podman run --name squid -d -p 3128:3128 quay.io/crcont/squid:5.5")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://quay.io/repository/crcont/squid?tab=tags has a 5.5 tag which was just created, and a latest tag which is 4 years old. Is there any reason for not updating the latest tag to point to the same image as the 5.5 tag? Then the test suite would automatically pick up the new image.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer to use latest tag. But the drawback is difficult to track back if image change.
@praveenkumar WDYT?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am mapping 5.5 to latest and keeping both the tag so we can also able to track back.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer to use latest tag. But the drawback is difficult to track back if image change.

I think it is fairly common to have a moving latest tag, plus non-moving versioned tags (eg 5.5), this way we get the best of both worlds :)

@praveenkumar
Copy link
Member

/close

@openshift-ci openshift-ci bot closed this Jan 9, 2025
Copy link

openshift-ci bot commented Jan 9, 2025

@praveenkumar: Closed this PR.

In response to this:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants