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.

Sign up for GitHub

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

Jump to bottom

SO-102: Spike on helmchart install #508

Closed
wants to merge 1 commit into from
Closed

SO-102: Spike on helmchart install #508

wants to merge 1 commit into from

Conversation

fbm3307
Copy link
Contributor

@fbm3307 fbm3307 commented Jul 6, 2023

POC on whether CSO can install helmchart

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 6, 2023
@fbm3307
Copy link
Contributor Author

fbm3307 commented Jul 6, 2023

/approve cancel

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 6, 2023

[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 fbm3307 for approval. 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:

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 removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 6, 2023
@openshift-cherrypick-robot
Copy link

@fbm3307: once the present PR merges, I will cherry-pick it on top of release-4.13 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.13

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.

@fbm3307 fbm3307 changed the title Spike on helmchart install SO-102: Spike on helmchart install Jul 20, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 20, 2023
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 20, 2023 •
edited by openshift-ci bot

@fbm3307: This pull request references SO-102 which is a valid jira issue.

In response to this:

POC on whether CSO can install helmchart

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.

@fbm3307
Spike on helmchart install
6317e7d 
Signed-off-by: Feny Mehta <fbm3307@gmail.com>

Semeru chart install

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

Logger

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

testing the install

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

Adding logger files

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

Logfor helm

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

Checking the install

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

Checking the install method

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

install

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

checking persistant chart

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

Helmchart via CRD

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

Test1

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

test2

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

Test3

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

Working changes

Signed-off-by: Feny Mehta <fbm3307@gmail.com>

cleanup code

Signed-off-by: Feny Mehta <fbm3307@gmail.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 20, 2023

@fbm3307: 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/okd-e2e-aws-ovn-builds 6317e7d link false /test okd-e2e-aws-ovn-builds
ci/prow/okd-scos-e2e-aws-ovn-upgrade 6317e7d link false /test okd-scos-e2e-aws-ovn-upgrade
ci/prow/okd-images 6317e7d link true /test okd-images
ci/prow/okd-e2e-aws-ovn-image-ecosystem 6317e7d link false /test okd-e2e-aws-ovn-image-ecosystem
ci/prow/okd-e2e-aws-ovn-upgrade 6317e7d link false /test okd-e2e-aws-ovn-upgrade
ci/prow/okd-scos-e2e-aws-ovn-image-ecosystem 6317e7d link false /test okd-scos-e2e-aws-ovn-image-ecosystem
ci/prow/e2e-aws-ovn-proxy 6317e7d link false /test e2e-aws-ovn-proxy
ci/prow/okd-e2e-aws-operator 6317e7d link false /test okd-e2e-aws-operator
ci/prow/okd-scos-images 6317e7d link true /test okd-scos-images
ci/prow/okd-scos-e2e-aws-ovn 6317e7d link false /test okd-scos-e2e-aws-ovn
ci/prow/okd-e2e-aws-ovn-jenkins 6317e7d link false /test okd-e2e-aws-ovn-jenkins
ci/prow/okd-scos-e2e-aws-ovn-jenkins 6317e7d link false /test okd-scos-e2e-aws-ovn-jenkins
ci/prow/okd-e2e-aws-ovn 6317e7d link false /test okd-e2e-aws-ovn
ci/prow/okd-scos-e2e-aws-operator 6317e7d link false /test okd-scos-e2e-aws-operator
ci/prow/okd-scos-e2e-aws-ovn-builds 6317e7d link false /test okd-scos-e2e-aws-ovn-builds

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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 20, 2023
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 19, 2023
@fbm3307
Copy link
Contributor Author

fbm3307 commented Oct 25, 2023

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 25, 2023
@fbm3307
Copy link
Contributor Author

fbm3307 commented Oct 25, 2023

/lifecycle frozen

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2023

@fbm3307: The lifecycle/frozen label cannot be applied to Pull Requests.

In response to this:

/lifecycle frozen

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.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 24, 2024
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 23, 2024
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Mar 25, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 25, 2024

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@adambkaplan adambkaplan Awaiting requested review from adambkaplan

@gabemontero gabemontero Awaiting requested review from gabemontero

Assignees
No one assigned
Labels
jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
5 participants
@fbm3307 @openshift-cherrypick-robot @openshift-ci-robot @openshift-merge-robot @openshift-bot