Skip to content

Conversation

@smoshiur1237
Copy link
Member

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

@metal3-io-bot metal3-io-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 24, 2025
@metal3-io-bot metal3-io-bot requested review from honza and kashifest July 24, 2025 09:17
@metal3-io-bot metal3-io-bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jul 24, 2025
@smoshiur1237 smoshiur1237 changed the title WIP🌱Decouple CAPM3 from using dev-env in E2E setup 🌱Decouple CAPM3 from using dev-env in E2E setup Jul 24, 2025
@metal3-io-bot metal3-io-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 24, 2025
@smoshiur1237
Copy link
Member Author

/hold

@metal3-io-bot metal3-io-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 24, 2025
@smoshiur1237 smoshiur1237 force-pushed the decouple-dev-moshiur branch 4 times, most recently from a3154a7 to 264c573 Compare July 31, 2025 06:41
@metal3-io-bot metal3-io-bot added the needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. label Jul 31, 2025
@smoshiur1237 smoshiur1237 force-pushed the decouple-dev-moshiur branch from 264c573 to f151607 Compare August 5, 2025 06:39
@metal3-io-bot metal3-io-bot added needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. labels Aug 5, 2025
@metal3-io-bot metal3-io-bot added needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. labels Aug 13, 2025
@smoshiur1237
Copy link
Member Author

I will open it when start working on this .

@smoshiur1237
Copy link
Member Author

We will start working on it

@smoshiur1237 smoshiur1237 reopened this Nov 4, 2025
@smoshiur1237
Copy link
Member Author

/cc @adilGhaffarDev

@adilGhaffarDev
Copy link
Member

/close
Lets open new one . This is sending too many notifications.

@metal3-io-bot
Copy link
Contributor

@adilGhaffarDev: Closed this PR.

Details

In response to this:

/close
Lets open new one . This is sending too many notifications.

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.

@smoshiur1237
Copy link
Member Author

rebasing it

@smoshiur1237 smoshiur1237 reopened this Nov 5, 2025
@metal3-io-bot metal3-io-bot added needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. labels Nov 5, 2025
@metal3-io-bot metal3-io-bot removed the needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. label Nov 26, 2025
@smoshiur1237 smoshiur1237 force-pushed the decouple-dev-moshiur branch 2 times, most recently from 8953fbc to f276218 Compare November 26, 2025 09:48
@metal3-io-bot metal3-io-bot added the needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. label Nov 28, 2025
Copy link
Member

@peppi-lotta peppi-lotta left a comment

Choose a reason for hiding this comment

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

I think this is a bit outdated overall if the idea is to follow what BMO is doing for e2e. I think you should wait until use irso PR merges as it will have quite many changes you are touching here as well. Using IRSO in CAPM3 will allow you to follow the BMO way or doing e2e more closely and I would suggest you start by checking that everything that is copied from BMO is up to date here.

Comment on lines -44 to -57
cat <<-EOF >"${M3_DEV_ENV_PATH}/config_${USER}.sh"
export CAPI_VERSION="v1beta2"
export CAPM3_VERSION=${CAPM3_VERSION:-"v1beta1"}
export NUM_NODES=${NUM_NODES:-"4"}
export KUBERNETES_VERSION=${KUBERNETES_VERSION}
export IMAGE_OS=${IMAGE_OS}
export FORCE_REPO_UPDATE="false"
export SKIP_NODE_IMAGE_PREPULL="true"
export USE_IRSO="${USE_IRSO:-false}"
EOF
Copy link
Member

Choose a reason for hiding this comment

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

Do these need to be exported somewhere else for example environment.sh?

Copy link
Member Author

Choose a reason for hiding this comment

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

We are not using dev-evn, thats why the config was deleted. But we can keep them in environment.sh file

virsh -c qemu:///system net-start "${network}"
virsh -c qemu:///system net-autostart "${network}"
done

Copy link
Member

Choose a reason for hiding this comment

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

fi
done

for overlay in "${IRONIC_OVERLAYS[@]}"; do
Copy link
Member

Choose a reason for hiding this comment

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

This will change to IRSO_OVELAYS once you rebase ontop of Use IRSO in e2e tests -PR. The username and password stuff will change as well.

hack/e2e/net.xml Outdated
@@ -0,0 +1,16 @@
<network>
<name>baremetal-e2e</name>
Copy link
Member

Choose a reason for hiding this comment

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

This file is probably not needed or should be rename.

@metal3-io-bot
Copy link
Contributor

[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 smoshiur1237 for approval. For more information see the Code Review Process.

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

Details 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 removed the needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. label Dec 15, 2025
@smoshiur1237 smoshiur1237 force-pushed the decouple-dev-moshiur branch 2 times, most recently from fcb1049 to 1033bcd Compare December 15, 2025 12:37
@metal3-io-bot metal3-io-bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Dec 15, 2025
Copy link
Member Author

@smoshiur1237 smoshiur1237 left a comment

Choose a reason for hiding this comment

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

Thanks @peppi-lotta for your review. I will address them

@smoshiur1237 smoshiur1237 force-pushed the decouple-dev-moshiur branch 2 times, most recently from 36afe84 to 9c98b90 Compare December 15, 2025 13:36
@metal3-io-bot metal3-io-bot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Dec 15, 2025
@smoshiur1237 smoshiur1237 force-pushed the decouple-dev-moshiur branch 2 times, most recently from c2070a5 to af5bdcd Compare December 16, 2025 08:56
This commit pushes changes needed so that we no longer need to run
dev-env's make in preparation for E2E.

Signed-off-by: Huy Mai <[email protected]>
Signed-off-by: smoshiur1237 <[email protected]>
@metal3-io-bot metal3-io-bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Dec 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants