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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NO-ISSUE: Adjust OCI to work with UI flow #2624

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

dudyas6
Copy link
Contributor

@dudyas6 dudyas6 commented Jan 29, 2025

Re-opening #2609 after discussing with Elior

Work process of UI :
use make deploy_nodes_oci to deploy oci resources and leave them up, once ui flow finishes run make destroy_nodes_oci which finds all the used resources and removes them

@openshift-ci-robot
Copy link

@dudyas6: This pull request explicitly references no jira issue.

In response to this:

Re-opening #2609 after discussing with Elior

Work process of UI :
use make deploy_nodes_oci to deploy oci resources and leave them up, once ui flow finishes run make destroy_nodes_oci which finds all the used resources and removes them

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 29, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 29, 2025
Copy link

openshift-ci bot commented Jan 29, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 29, 2025
Copy link

openshift-ci bot commented Jan 29, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dudyas6
Once this PR has been reviewed and has the lgtm label, please assign tsorya for approval. For more information see the 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:

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

@dudyas6 dudyas6 marked this pull request as ready for review January 29, 2025 16:31
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 29, 2025
@openshift-ci openshift-ci bot requested review from eliorerz and omertuc January 29, 2025 16:32
@dudyas6
Copy link
Contributor Author

dudyas6 commented Jan 29, 2025

/cc @bkopilov @adriengentil @talhil-rh

@openshift-ci openshift-ci bot requested a review from adriengentil January 29, 2025 16:40
Copy link

openshift-ci bot commented Jan 29, 2025

@dudyas6: GitHub didn't allow me to request PR reviews from the following users: talhil-rh, bkopilov.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @bkopilov @adriengentil @talhil-rh

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.

@dudyas6 dudyas6 force-pushed the add-oci-ui-support branch from 0983c18 to 6b5a000 Compare January 29, 2025 16:42
Copy link

openshift-ci bot commented Jan 29, 2025

@dudyas6: 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-static-ip-suite-4-18 6b5a000 link false /test e2e-metal-assisted-static-ip-suite-4-18
ci/prow/e2e-metal-assisted-none-4-18 6b5a000 link false /test e2e-metal-assisted-none-4-18

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

Comment on lines +547 to 549
self._upload_data_to_bucket(
terraform_output, f"terraform-output-{self._entity_config.cluster_id}.yml", namespace, bucket_name
)
Copy link
Contributor

Choose a reason for hiding this comment

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

already tackled here: #2605 (comment), can it be removed from this PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I actually need it to upload the manifests in the UI flow instead of fetching it from the stack in someway, so i temporarily save it in /tmp folder, i can skip the upload to bucket part, but i'll still need to save it somewhere unless u have other suggestion

Copy link
Contributor

@adriengentil adriengentil Jan 30, 2025

Choose a reason for hiding this comment

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

well, we need to choose in which PR we want to talk about it, it's confusing at the moment, and I would need to understand why we need this file to be in the bucket.

Also I would need this cleanup logic be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants