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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the e2e K8s test #1842

Merged
merged 3 commits into from
Dec 17, 2021
Merged

Fix the e2e K8s test #1842

merged 3 commits into from
Dec 17, 2021

Conversation

mattmoor
Copy link
Collaborator

@mattmoor mattmoor commented Dec 16, 2021

The K8s e2e test has been failing since the move to actions. This adds a bunch of instrumentation I used to track down the failure. The biggest change was trying to consolidate test output to go through t.Log so that the logs are properly correlated. I disabled -v because I find the resulting interleaving to be incredibly difficult to parse the failures out of.

The crux of the issue was that the kaniko images were in ErrImgPull because the registry wasn't visible to the cluster. This was fixed by migrating to the minikube registry addon, but the next problem was that hostPath wasn't working properly with the --driver=docker. So I migrated back to what was being successfully used on Travis and 馃帀 things pass.

The main "fix" was a few parts:

  1. Use the minikube registry addon instead of registry:2,
  2. Revert to the way minikube was spun up on Travis.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes unit tests
  • Adds integration tests if needed.

See the contribution guide for more details.

Reviewer Notes

  • The code flow looks good.
  • Unit tests and or integration tests added.

Release Notes

The e2e test is finally passing 馃帀 

@mattmoor mattmoor force-pushed the fix-e2e branch 2 times, most recently from c755a97 to 75dff85 Compare December 17, 2021 00:27
It seems to be consistently failing (also fix a typo in the file/leg name).

I'm disabling `-v` for `go test` because it interleaves the test output in ways that make it painful to read a single failing test's output when `t.Parallel` is involved.
@mattmoor mattmoor force-pushed the fix-e2e branch 7 times, most recently from 47b33d0 to 81cf500 Compare December 17, 2021 15:42
@mattmoor
Copy link
Collaborator Author

Trying a YOLO revert to the old minikube setup, which used --vm-driver=none 馃し

@mattmoor mattmoor force-pushed the fix-e2e branch 4 times, most recently from c2c1cf3 to 6adda00 Compare December 17, 2021 17:15
@mattmoor mattmoor changed the title [WIP] Debugging the integration testing. Fix the e2e K8s test Dec 17, 2021
@mattmoor
Copy link
Collaborator Author

cc @priyawadhwa @imjasonh @dlorenc

Copy link
Collaborator

@imjasonh imjasonh left a comment

Choose a reason for hiding this comment

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

馃憦馃憦馃憦

integration/images.go Show resolved Hide resolved
scripts/minikube-setup.sh Show resolved Hide resolved
@imjasonh imjasonh merged commit 49f0154 into GoogleContainerTools:master Dec 17, 2021
@mattmoor mattmoor deleted the fix-e2e branch December 17, 2021 20:42
@priyawadhwa
Copy link
Collaborator

amazing!! 馃帀 馃コ

gcalmettes pushed a commit to gcalmettes/kaniko that referenced this pull request Dec 24, 2021
* Debugging the integration testing.

It seems to be consistently failing (also fix a typo in the file/leg name).

I'm disabling `-v` for `go test` because it interleaves the test output in ways that make it painful to read a single failing test's output when `t.Parallel` is involved.

* Try swapping registry:2 for the registry add-on

* Drop logf and make Logger private
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants