WIP: 🌱 Remove Metal3Machine owner reference from BMH

[kashifest]

Metal3Machine should not own BMH. It should consume it and release it when not needed. we already put a M3M consumer reference on BMH. This also would mean that for pivoting use cases we must add the clusterctl move labels in the CRDs. Otherwise BMH wont be pivoted to target clusters.

[metal3-io-bot]

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

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

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kashifest]

/hold
This is a WIP

[kashifest]

/test metal3-ubuntu-e2e-integration-test-main

[kashifest]

/test metal3-ubuntu-e2e-integration-test-main

[metal3-io-bot]

@kashifest: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
metal3-ubuntu-e2e-integration-test-main	0e5ff05	link	true	/test metal3-ubuntu-e2e-integration-test-main

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[metal3-io-bot]

@kashifest: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
metal3-ubuntu-e2e-integration-test-main	0e5ff05	link	true	/test metal3-ubuntu-e2e-integration-test-main

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/test-infra repository. I understand the commands that are listed here.

[kashifest]

/test ?

[metal3-io-bot]

@kashifest: The following commands are available to trigger required jobs:

• /test build
• /test generate
• /test gomod
• /test manifestlint
• /test markdownlint
• /test metal3-centos-e2e-integration-test-main
• /test metal3-ubuntu-e2e-integration-test-main
• /test shellcheck
• /test test
• /test unit

The following commands are available to trigger optional jobs:

• /test metal3-centos-e2e-basic-test-main
• /test metal3-centos-e2e-feature-test-main
• /test metal3-e2e-1-26-1-27-upgrade-test-main
• /test metal3-e2e-1-27-1-28-upgrade-test-main
• /test metal3-e2e-1-28-1-29-upgrade-test-main
• /test metal3-e2e-clusterctl-upgrade-test-main
• /test metal3-ubuntu-e2e-basic-test-main
• /test metal3-ubuntu-e2e-feature-test-main

Use /test all to run the following jobs that were automatically triggered:

• generate
• gomod
• manifestlint
• unit

In response to this:

/test ?

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/test-infra repository.

[shibaPuppy]

@kashifest
It seems to be PR for the same purpose.
can I close my PR?

[kashifest]

@kashifest It seems to be PR for the same purpose. can I close my PR?

Yes, I am doing the same thing here, I didn't notice you had the same thing in another PR, didnt mean to over step. I am currently testing this since it seems to not passing the pivot scenario so it would need more changes. I am also ok to close my one if you have progressed more.

[shibaPuppy]

@kashifest
i can't spend much time working, so I don't come often.
i will close my PR. :)