Skip to content

Conversation

@lihongan
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot requested review from gpei and jianlinliu August 15, 2022 06:44
@lihongan
Copy link
Contributor Author

"installer-rehearse-aws" pod "installer-rehearse-aws-workers-rhel-pre-hook-sshtunnel" failed: the pod ci-op-tvbc3ccd/installer-rehearse-aws-workers-rhel-pre-hook-sshtunnel failed after 2h0m14s (failed containers: test): ContainerFailed one or more containers exited

@lihongan
Copy link
Contributor Author

/retest

@lihongan
Copy link
Contributor Author

Looks timeout again for step workers-rhel-pre-hook-sshtunnel, see https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/31307/rehearse-31307-periodic-ci-openshift-verification-tests-master-installer-rehearse-4.12-installer-rehearse-aws/1559128960380440576#1:build-log.txt%3A12

Try to check workflow cucushift-installer-rehearse-aws-ipi-disconnected-private-workers-rhcos-rhel8-sdn and re-trigger the test

@jianlinliu
Copy link
Contributor

Looks timeout again for step workers-rhel-pre-hook-sshtunnel, see https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/31307/rehearse-31307-periodic-ci-openshift-verification-tests-master-installer-rehearse-4.12-installer-rehearse-aws/1559128960380440576#1:build-log.txt%3A12

Try to check workflow cucushift-installer-rehearse-aws-ipi-disconnected-private-workers-rhcos-rhel8-sdn and re-trigger the test

Sounds like there is script bug on ssh-tunnel, we are trying to fix it.

@lihongan
Copy link
Contributor Author

Looks timeout again for step workers-rhel-pre-hook-sshtunnel, see https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/31307/rehearse-31307-periodic-ci-openshift-verification-tests-master-installer-rehearse-4.12-installer-rehearse-aws/1559128960380440576#1:build-log.txt%3A12
Try to check workflow cucushift-installer-rehearse-aws-ipi-disconnected-private-workers-rhcos-rhel8-sdn and re-trigger the test

Sounds like there is script bug on ssh-tunnel, we are trying to fix it.

Yes, looks like something wrong with ssh-tunnel, the job for workflow aws-ipi-disconnected-private-workers-rhcos-rhel8-sdn also hit the same issue.

@jianlinliu
Copy link
Contributor

jianlinliu commented Aug 16, 2022

let us hold the testing for a while, once the issue is fixed, will notify you, after that, you can sync upstream to retest it.

@jianlinliu
Copy link
Contributor

@lihongan #31362 should fix the ssh-tunnel issue, pls sync upstream, have a retest.

@lihongan
Copy link
Contributor Author

Thank you @jianlinliu , let me retest workflow cucushift-installer-rehearse-aws-ipi-proxy-workers-rhel8-sdn firstly.

@lihongan
Copy link
Contributor Author

Step installer-rehearse-aws-workers-rhel-repos failed

/retest

Copy link
Contributor

@jianlinliu jianlinliu Aug 18, 2022

Choose a reason for hiding this comment

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

How about move sdn folder to aws/ipi/disconnected/private, then we can have cucushift/installer/rehearse/aws/ipi/disconnected/private/sdn/provision/cucushift-installer-rehearse-aws-ipi-disconnected-private-sdn-provision-chain.yaml, then we can reference the provision chain in the new rhel workflow.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good idea.
Sure, I can have a try.

Copy link
Contributor

Choose a reason for hiding this comment

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

How about moving sdn to aws/ipi/proxy/, then we will have cucushift-installer-rehearse-aws-ipi-proxy-sdn-provision-chain.yaml, based that chain, we can add rhel-workers steps to have cucushift-installer-rehearse-aws-ipi-proxy-sdn-workers-rhel8-provision-chain.yaml

Copy link
Contributor

Choose a reason for hiding this comment

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

@jianlinliu
Copy link
Contributor

#31256 is trying to fix oc binary downloading issue, once that PR get merge, you can sync and retest.

@jianlinliu
Copy link
Contributor

@lihongan #31256 get merged, pls retry

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 25, 2022
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 25, 2022
@lihongan
Copy link
Contributor Author

/retest

Copy link
Contributor

Choose a reason for hiding this comment

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

Though cucushift/installer/rehearse/aws/ipi/disconnected/private/workers-rhcos-rhel8/sdn/provision/ and cucushift/installer/rehearse/aws/ipi/disconnected/private/sdn/workers-rhcos-rhel8/provision/ should have the same effect, for keeping consistent folder layout, do you mind update the layout a bit to cucushift/installer/rehearse/aws/ipi/disconnected/private/sdn/workers-rhcos-rhel8/provision/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, will update it.

@lihongan
Copy link
Contributor Author

/hold
since I need to test again for another workflow

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 26, 2022
@lihongan
Copy link
Contributor Author

/retest

@lihongan
Copy link
Contributor Author

/retest

@lihongan
Copy link
Contributor Author

The test for cucushift-installer-rehearse-aws-ipi-proxy-sdn-workers-rhel8 looks good, let's test another one.

@lihongan
Copy link
Contributor Author

/retest

1 similar comment
@lihongan
Copy link
Contributor Author

/retest

@lihongan
Copy link
Contributor Author

/unhold
both workflows look good now.

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 26, 2022
@jianlinliu
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 29, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 29, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jianlinliu, lihongan

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 Aug 29, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 29, 2022

@lihongan: all tests passed!

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.

@openshift-merge-robot openshift-merge-robot merged commit 40d31e9 into openshift:master Aug 29, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 29, 2022

@lihongan: Updated the ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:

  • key openshift-verification-tests-master__installer-rehearse-4.12.yaml using file ci-operator/config/openshift/verification-tests/openshift-verification-tests-master__installer-rehearse-4.12.yaml
Details

In response to this:

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

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.

3 participants