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

Updated scripts and workflows to test kruize docker image from the manifest yaml #875

Merged
merged 6 commits into from
Nov 3, 2023

Conversation

chandrams
Copy link
Contributor

Updated scripts and workflows to test kruize docker image from the manifest yaml

@chandrams chandrams self-assigned this Jul 4, 2023
@chandrams chandrams added this to the Kruize 0.0.17_rm Release milestone Jul 4, 2023
@chandrams chandrams linked an issue Jul 7, 2023 that may be closed by this pull request
@chandrams chandrams force-pushed the manifest_build branch 2 times, most recently from 8d0c82f to f48507b Compare August 24, 2023 11:43
Comment on lines 216 to 220
#if [ -z "${AUTOTUNE_DOCKER_IMAGE}" ]; then
# if [ ${testsuite} != "remote_monitoring_tests" ]; then
# AUTOTUNE_DOCKER_IMAGE="${AUTOTUNE_IMAGE}"
# fi
#fi
Copy link
Contributor

Choose a reason for hiding this comment

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

Please remove commented out code

@chandrams
Copy link
Contributor Author

run functional tests

@dinogun
Copy link
Contributor

dinogun commented Nov 2, 2023

@chandrams Please fix the conflicts

@chandrams chandrams force-pushed the manifest_build branch 2 times, most recently from 466f2fc to 2736d80 Compare November 2, 2023 12:13
@dinogun
Copy link
Contributor

dinogun commented Nov 2, 2023

@chandrams Please fix the conflicts

… image in the manifest file for remote monitoring

Signed-off-by: Chandrakala Subramanyam <[email protected]>
Signed-off-by: Chandrakala Subramanyam <[email protected]>
Signed-off-by: Chandrakala Subramanyam <[email protected]>
@chandrams
Copy link
Contributor Author

@dinogun I have resolved the conflicts, please review.

@dinogun
Copy link
Contributor

dinogun commented Nov 3, 2023

So is the test_crc_manifest_build job expected to fail?

@chandrams
Copy link
Contributor Author

From the Logs I see it is still using 0.0.19.4_rm build, let me push a change and trigger the build again

 Normal  Pulling    108s  kubelet            Pulling image "kruize/autotune_operator:0.0.19.4_rm"
 Normal  Pulled     102s  kubelet            Successfully pulled image "kruize/autotune_operator:0.0.19.4_rm" in 6.383105776s

Signed-off-by: Chandrakala Subramanyam <[email protected]>
@chandrams
Copy link
Contributor Author

Now it picked the build from the manifest which is 0.0.20_rm but failed as the build is not available on docker.hub

 Normal   Pulling    12m (x4 over 14m)     kubelet            Pulling image "kruize/autotune_operator:0.0.20_rm"
  Warning  Failed     12m (x4 over 14m)     kubelet            Failed to pull image "kruize/autotune_operator:0.0.20_rm": rpc error: code = Unknown desc = Error response from daemon: manifest for kruize/autotune_operator:0.0.20_rm not found: manifest unknown: manifest unknown

Copy link
Contributor

@dinogun dinogun left a comment

Choose a reason for hiding this comment

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

Merging as the manifest job is expected fail during a release

@dinogun dinogun merged commit 5444752 into kruize:mvp_demo Nov 3, 2023
2 of 4 checks passed
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.

PR check needs to use the docker image mentioned in the manifest
3 participants