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 VM selection in clean-e2e.sh #1537

Merged
merged 1 commit into from
Feb 2, 2024

Conversation

mquhuy
Copy link
Member

@mquhuy mquhuy commented Feb 1, 2024

Fixes #1531

This PR takes the tools/bmh_test/clean_local_bmh_test_setup.sh into use:

  • Removed -e as many operations could fail, but the script should keep going

@metal3-io-bot metal3-io-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 1, 2024
@mquhuy
Copy link
Member Author

mquhuy commented Feb 1, 2024

/test metal3-bmo-e2e-test-pull

@maxrantil
Copy link
Member

LGTM

Copy link
Member

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

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

Great! Just one small comment

@@ -4,21 +4,10 @@ REPO_ROOT=$(dirname "${BASH_SOURCE[0]}")/..
cd "${REPO_ROOT}" || exit 1

minikube delete
docker rm -f vbmc
Copy link
Member

Choose a reason for hiding this comment

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

Could you add this back? It feels weird to delete sushy-tools here but not vbmc.
In the long run we can move all of it to the other script but for now I think we can keep it here and just fix the bug.

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure. I removed it since it felt weird to me that we clean it in both places while it may not even be there, but no big issue.

Signed-off-by: Huy Mai <huy.mai@est.tech>
Copy link
Member

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

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

/lgtm

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 2, 2024
@lentzi90
Copy link
Member

lentzi90 commented Feb 2, 2024

/test metal3-bmo-e2e-test-pull

@lentzi90
Copy link
Member

lentzi90 commented Feb 2, 2024

/test-centos-e2e-integration-main

@peppi-lotta
Copy link
Member

LGTM

@lentzi90
Copy link
Member

lentzi90 commented Feb 2, 2024

/test metal3-bmo-e2e-test-pull

done
else
echo "No virtual machines found. Skipping..."
fi

# Clear vbmc
docker stop vbmc
Copy link
Member

Choose a reason for hiding this comment

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

whats the harm if we stop it first, why are we removing this? Is there a possibility that it might not exist?

Copy link
Member

Choose a reason for hiding this comment

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

The -f makes it unnecessary. We remove it no matter if it runs or not

@kashifest
Copy link
Member

/approve

@metal3-io-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kashifest

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

The pull request process is described 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

@metal3-io-bot metal3-io-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 2, 2024
@lentzi90
Copy link
Member

lentzi90 commented Feb 2, 2024

Seems this did not start...
/test-centos-e2e-integration-main

@metal3-io-bot metal3-io-bot merged commit 3b2d4ac into metal3-io:main Feb 2, 2024
20 checks passed
@metal3-io-bot metal3-io-bot deleted the mquhuy/fix-e2e-vm-cleanup branch February 2, 2024 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BMO e2e cleanup potentially leaving VMs?
6 participants