Skip to content

Power VS: Separating bootstrap resources to own stage for clean destroy#5901

Merged
openshift-ci[bot] merged 1 commit intoopenshift:masterfrom
miyamotoh:separate-bootstrap-stage
May 13, 2022
Merged

Power VS: Separating bootstrap resources to own stage for clean destroy#5901
openshift-ci[bot] merged 1 commit intoopenshift:masterfrom
miyamotoh:separate-bootstrap-stage

Conversation

@miyamotoh
Copy link
Copy Markdown

As eluded to in #5780, this is to move the bootstrap resource creation to its own TF stage so it can be called for quick terraform destory after bootstrap-complete for PowerVS platform. Also introduced is the bootstrap-routing stage which takes care of the necessary network routing components that live beyond the bootstrap phase, but need adjustments when bootstrap VM is around and gone.

Signed-off-by: Hiro Miyamoto miyamotoh@us.ibm.com

@openshift-ci openshift-ci Bot requested review from jhixson74 and sadasu May 12, 2022 14:09
@miyamotoh miyamotoh changed the title Separating bootstrap resources to own stage for clean destroy Power VS: Separating bootstrap resources to own stage for clean destroy May 12, 2022
@patrickdillon
Copy link
Copy Markdown
Contributor

@miyamotoh required tf-fmt test is failing

Signed-off-by: Hiro Miyamoto <miyamotoh@us.ibm.com>
@miyamotoh miyamotoh force-pushed the separate-bootstrap-stage branch from 729a422 to 0e4da38 Compare May 12, 2022 19:22
@clnperez
Copy link
Copy Markdown
Contributor

/lgtm

my only comment is that, the name bootstrap-routing is a bit confusing (to me at least) b/c it seems to imply that the things from this phase will be deleted, so i'd like to see it renamed to something like loadbalancers. but that's just a nit and we can update it later

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 12, 2022
@patrickdillon
Copy link
Copy Markdown
Contributor

/approve
/lgtm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 12, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 12, 2022
@miyamotoh
Copy link
Copy Markdown
Author

/retest-required

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 12, 2022

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

Test name Commit Details Required Rerun command
ci/prow/e2e-metal-assisted 0e4da38 link false /test e2e-metal-assisted
ci/prow/okd-e2e-aws 0e4da38 link false /test okd-e2e-aws

Full PR test history. Your PR dashboard.

Details

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.

@Prashanth684
Copy link
Copy Markdown
Contributor

/lgtm

my only comment is that, the name bootstrap-routing is a bit confusing (to me at least) b/c it seems to imply that the things from this phase will be deleted, so i'd like to see it renamed to something like loadbalancers. but that's just a nit and we can update it later

maybe call it post-bootstrap like gcp does

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

3 similar comments
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci openshift-ci Bot merged commit f65c386 into openshift:master May 13, 2022
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants