Skip to content

Switch support-operator to golang-1.12 - #4459

Merged
openshift-merge-robot merged 1 commit into
openshift:masterfrom
smarterclayton:golang
Jul 20, 2019
Merged

Switch support-operator to golang-1.12#4459
openshift-merge-robot merged 1 commit into
openshift:masterfrom
smarterclayton:golang

Conversation

@smarterclayton

@smarterclayton smarterclayton commented Jul 20, 2019

Copy link
Copy Markdown
Contributor

Needed in order to bump vendor to 1.14 levels of apimachinery, client-go, and library-go

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 20, 2019
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 20, 2019
@smarterclayton smarterclayton added the lgtm Indicates that a PR is ready to be merged. label Jul 20, 2019
@smarterclayton

Copy link
Copy Markdown
Contributor Author

@eparis as I'm cleaning up this stuff (will tag you on a few things next week)

@openshift-merge-robot
openshift-merge-robot merged commit 0e5b39b into openshift:master Jul 20, 2019
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@smarterclayton: Updated the following 6 configmaps:

  • ci-operator-master-configs configmap in namespace ci using the following files:
    • key openshift-support-operator-master.yaml using file ci-operator/config/openshift/support-operator/openshift-support-operator-master.yaml
  • ci-operator-master-configs configmap in namespace ci-stg using the following files:
    • key openshift-support-operator-master.yaml using file ci-operator/config/openshift/support-operator/openshift-support-operator-master.yaml
  • ci-operator-4.2-configs configmap in namespace ci using the following files:
    • key openshift-support-operator-release-4.2.yaml using file ci-operator/config/openshift/support-operator/openshift-support-operator-release-4.2.yaml
  • ci-operator-4.2-configs configmap in namespace ci-stg using the following files:
    • key openshift-support-operator-release-4.2.yaml using file ci-operator/config/openshift/support-operator/openshift-support-operator-release-4.2.yaml
  • ci-operator-4.3-configs configmap in namespace ci using the following files:
    • key openshift-support-operator-release-4.3.yaml using file ci-operator/config/openshift/support-operator/openshift-support-operator-release-4.3.yaml
  • ci-operator-4.3-configs configmap in namespace ci-stg using the following files:
    • key openshift-support-operator-release-4.3.yaml using file ci-operator/config/openshift/support-operator/openshift-support-operator-release-4.3.yaml
Details

In response to this:

Needed in order to bump vendor to 1.14 levels of apimachinery, client-go, and library-go

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-ci-robot

Copy link
Copy Markdown
Contributor

@smarterclayton: The following tests failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/rehearse/openshift/support-operator/release-4.3/images 2fa6628 link /test pj-rehearse
ci/rehearse/openshift/support-operator/release-4.3/e2e-aws 2fa6628 link /test pj-rehearse
ci/rehearse/openshift/support-operator/release-4.3/e2e-aws-upgrade 2fa6628 link /test pj-rehearse
ci/prow/pj-rehearse 2fa6628 link /test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

rrasouli added a commit to rrasouli/release that referenced this pull request Aug 27, 2026
The vsphere-proxy-e2e-ote job is failing rehearsal because master doesn't
have the proxy test code yet (pending merge of WMCO PR openshift#4459).

Making it optional (like aws-e2e-ote) allows the release PR to merge.
Once openshift#4459 merges to WMCO master, a follow-up PR can remove the optional
flag and the job will work correctly.
rrasouli added a commit to rrasouli/release that referenced this pull request Aug 27, 2026
Adds standalone vsphere-proxy-e2e-ote job that runs OTE proxy tests
on a vsphere proxy cluster using the windows-machine-config-operator/proxy
test suite.

Temporary workaround: Uses custom inline test step instead of the standard
openshift-e2e-test ref to handle 0 tests gracefully. This is needed because
the proxy test code (proxy.go) is in WMCO PR openshift#4459 which hasn't merged yet.
Rehearsal runs against current WMCO master which only has the suite
registration but not the test file itself.

The custom step:
- Runs openshift-tests-extension with the proxy suite
- If exit code 1 AND output contains "no tests to run" → exit 0 (PASS)
- Otherwise → pass through original exit code
- Once openshift#4459 merges: proxy tests exist → runs normally with test results

Cleanup (after WMCO PR openshift#4459 is stable):
Create follow-up PR to replace the custom inline step with:
  - ref: openshift-e2e-test

Related: openshift/windows-machine-config-operator#4460
openshift-merge-bot Bot pushed a commit that referenced this pull request Aug 31, 2026
* WINC-1971: Add standalone OTE proxy suite job for vsphere

Adds a new vsphere-proxy-e2e-ote job that runs OTE proxy tests
on a vsphere proxy cluster. This is a separate job from the existing
vsphere-proxy-e2e-operator to keep complexity isolated per reviewer
feedback.

Signed-off-by: rrasouli <rrasouli@redhat.com>

* Add vsphere-proxy-e2e-ote job with 0-test handling

Adds standalone vsphere-proxy-e2e-ote job that runs OTE proxy tests
on a vsphere proxy cluster using the windows-machine-config-operator/proxy
test suite.

Temporary workaround: Uses custom inline test step instead of the standard
openshift-e2e-test ref to handle 0 tests gracefully. This is needed because
the proxy test code (proxy.go) is in WMCO PR #4459 which hasn't merged yet.
Rehearsal runs against current WMCO master which only has the suite
registration but not the test file itself.

The custom step:
- Runs openshift-tests-extension with the proxy suite
- If exit code 1 AND output contains "no tests to run" → exit 0 (PASS)
- Otherwise → pass through original exit code
- Once #4459 merges: proxy tests exist → runs normally with test results

Cleanup (after WMCO PR #4459 is stable):
Create follow-up PR to replace the custom inline step with:
  - ref: openshift-e2e-test

Related: openshift/windows-machine-config-operator#4460

* Add wmco-setup step to create Windows nodes in proxy environment

---------

Signed-off-by: rrasouli <rrasouli@redhat.com>
Co-authored-by: openshift-ci[bot] <75433959+openshift-ci[bot]@users.noreply.github.com>
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. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants