-
Notifications
You must be signed in to change notification settings - Fork 97
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
Check pods are created before waiting for them to be ready during publish recipes #6914
Check pods are created before waiting for them to be ready during publish recipes #6914
Conversation
…lish recipes Signed-off-by: vinayada1 <28875764+vinayada1@users.noreply.github.com>
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
35bd9fb
to
cebfc27
Compare
Signed-off-by: vinayada1 <28875764+vinayada1@users.noreply.github.com>
cebfc27
to
94f93f8
Compare
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests on ARO were failing with: "error: no matching resources found", this because it's not possible to watch a resource that hasn't been created. See kubernetes/kubernetes#83094 & radius-project/radius#6914 Fixes: 4e1bb64 ("integration: Disable installing Security Profile Operator") Signed-off-by: Mauricio Vásquez <mauriciov@microsoft.com>
Tests on ARO were failing with: "error: no matching resources found", this because it's not possible to watch a resource that hasn't been created. See kubernetes/kubernetes#87352 & radius-project/radius#6914 Fixes: 4e1bb64 ("integration: Disable installing Security Profile Operator") Signed-off-by: Mauricio Vásquez <mauriciov@microsoft.com>
Tests eere failing on ARO because of different reasons: - In order to mount host path volumes, it's needed to use a different service account. - The "no matching resources found" error was because it's not possible to watch a resource that hasn't been created. See kubernetes/kubernetes#87352 This commit fixes the previous one by: - Defining a different service account to be able to mount hostpath volumes - Use kubectl rollout instead of kubectl wait as done in radius-project/radius#6914 This also updates the logic to remove the installed seccomp profile from the host. Fixes: 4e1bb64 ("integration: Disable installing Security Profile Operator") Signed-off-by: Mauricio Vásquez <mauriciov@microsoft.com>
Tests eere failing on ARO because of different reasons: - In order to mount host path volumes, it's needed to use a different service account. - The "no matching resources found" error was because it's not possible to watch a resource that hasn't been created. See kubernetes/kubernetes#87352 This commit fixes the previous one by: - Defining a different service account to be able to mount hostpath volumes - Use kubectl rollout instead of kubectl wait as done in radius-project/radius#6914 This also updates the logic to remove the installed seccomp profile from the host. Fixes: 4e1bb64 ("integration: Disable installing Security Profile Operator") Signed-off-by: Mauricio Vásquez <mauriciov@microsoft.com>
Tests are failing on ARO because of different reasons: - In order to mount host path volumes, it's needed to use a different service account. - The "no matching resources found" error was because it's not possible to watch a resource that hasn't been created. See kubernetes/kubernetes#87352 This commit fixes the previous one by: - Defining a different service account to be able to mount hostpath volumes - Use kubectl rollout instead of kubectl wait as done in radius-project/radius#6914 This also updates the logic to remove the installed seccomp profile from the host. Fixes: 4e1bb64 ("integration: Disable installing Security Profile Operator") Signed-off-by: Mauricio Vásquez <mauriciov@microsoft.com>
Description
This is a potential fix for the flaky test issue seen #6912
It is possible that we see error: no matching resources found because the pods are not yet created. Waiting on non-existent resources can result in this error (kubernetes/kubernetes#87352)
Adding a kubectl rollout status which will ensure the pods are created before waiting on them to become ready
Type of change
Fixes: #6912
Auto-generated summary
🤖[deprecated] Generated by Copilot at 27fbda2
Summary
🚀🧪🎨
Add feature to generate and test Terraform recipes from YAML. Fix formatting in
build/recipes.mk
.Walkthrough