Skip to content

Conversation

@yselkowitz
Copy link
Contributor

In order for console-operator deployment to succeed, cli-artifacts needs to be available on all arches for downloads-openshift-console. However, in that case, /usr/bin/oc (inherited from cli) is a native binary, and we want to provide all primary Linux architectures to match those on mirror.openshift.com.

In order to do so, this provides cross-compiled Linux binaries for multiple architectures. Cross-compiling oc fails with gssapi enabled, therefore it is disabled in the cross builds.

Cherry-pick of #153 to 4.2.

@openshift-ci-robot
Copy link

@yselkowitz: This pull request references Bugzilla bug 1773807, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Bug 1773807: Enable all Linux arches in cli-artifacts [4.2]

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 openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Nov 19, 2019
@openshift-ci-robot
Copy link

Hi @yselkowitz. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@openshift-ci-robot openshift-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 19, 2019
Copy link
Member

@wking wking left a comment

Choose a reason for hiding this comment

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

a41e4f9 is a clean cherry pick.

/ok-to-test
/lgtm

@openshift-ci-robot openshift-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. lgtm Indicates that a PR is ready to be merged. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 19, 2019
@yselkowitz
Copy link
Contributor Author

/retest

2 similar comments
@yselkowitz
Copy link
Contributor Author

/retest

@yselkowitz
Copy link
Contributor Author

/retest

@yselkowitz
Copy link
Contributor Author

This passed CI on master. Is there actually a problem here or is CI just flaky (yet again)?

@yselkowitz
Copy link
Contributor Author

/retest

@yselkowitz
Copy link
Contributor Author

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 20, 2019
In order for console-operator deployment to succeed, cli-artifacts needs
to be available on all arches for downloads-openshift-console.  However,
in that case, /usr/bin/oc (inherited from cli) is a native binary, and
we want to provide all primary Linux architectures to match those on
mirror.openshift.com.

In order to do so, this provides cross-compiled Linux binaries for
multiple architectures.  Cross-compiling oc fails with gssapi enabled,
therefore it is disabled in the cross builds.

(cherry picked from commit e949088)
(squashed commit 2510f47)
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Nov 21, 2019
@yselkowitz
Copy link
Contributor Author

/hold cancel
squashed #171 to avoid breaking oc adm release extract

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 21, 2019
@yselkowitz
Copy link
Contributor Author

/retest

@yselkowitz
Copy link
Contributor Author

/test unit
/test e2e-cmd

1 similar comment
@yselkowitz
Copy link
Contributor Author

/test unit
/test e2e-cmd

@yselkowitz
Copy link
Contributor Author

/retest

@yselkowitz
Copy link
Contributor Author

yselkowitz commented Nov 25, 2019

This passed CI on master. Is there actually a problem here or is CI just flaky (yet again)?

Ping?

@crawford
Copy link
Contributor

/retest

@crawford
Copy link
Contributor

@yselkowitz it appears as though the unit tests are routinely failing:

FAIL: github.com/openshift/oc/pkg/helpers/newapp/newapptest TestNewAppRunAll/successful_docker_app_generation 1.4s
FAIL: github.com/openshift/oc/pkg/helpers/newapp/newapptest TestNewAppRunAll/Docker_build 910ms
FAIL: github.com/openshift/oc/pkg/helpers/newapp/newapptest TestNewAppRunAll/Docker_build_with_no_registry_image 1.06s
FAIL: github.com/openshift/oc/pkg/helpers/newapp/newapptest TestNewAppRunAll 11.93s
FAIL: github.com/openshift/oc/pkg/helpers/newapp/newapptest TestNewAppRunBuilds/successful_input_image_source_build_with_a_repository 1.61s
FAIL: github.com/openshift/oc/pkg/helpers/newapp/newapptest TestNewAppRunBuilds 12.22s

@wking
Copy link
Member

wking commented Nov 26, 2019

From unit:

set -o pipefail; go test -race -json ./... ./vendor/k8s.io/kubernetes/pkg/kubectl/... | gotest2junit > /tmp/artifacts/unit_report.xml

So check the report?

@yselkowitz
Copy link
Contributor Author

Thanks for the pointer. #158 should fix the unit test but is currently blocked, and it is noted there that e2e-cmd is failing there as well. Since those issues should be unrelated to this PR, how should we proceed?

@yselkowitz
Copy link
Contributor Author

/retest

@yselkowitz
Copy link
Contributor Author

CI blocked by #195, can we please either get that fixed or this waived?

@crawford
Copy link
Contributor

crawford commented Dec 2, 2019

@yselkowitz We're going to get #195 merged soon. I'll kick off the tests again once that happens.

@crawford
Copy link
Contributor

crawford commented Dec 2, 2019

/retest

@crawford
Copy link
Contributor

crawford commented Dec 2, 2019

/lgtm
/approve

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 2, 2019
@yselkowitz
Copy link
Contributor Author

/assign @mfojtik

Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve
/retest

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: crawford, soltysh, wking, yselkowitz

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 Dec 3, 2019
@yselkowitz
Copy link
Contributor Author

@soltysh thanks for approval. Testing has completed but it looks like /cherry-pick-approved is stil needed for this to merge.

@soltysh
Copy link
Contributor

soltysh commented Dec 3, 2019

@soltysh thanks for approval. Testing has completed but it looks like /cherry-pick-approved is stil needed for this to merge.

That is correct patch-manager will apply one when going through approved PRs.

@crawford crawford added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Dec 3, 2019
@crawford
Copy link
Contributor

crawford commented Dec 3, 2019

From the failure:

Error waiting for instance (i-0e84164cc2fa1f74a) to become ready: Failed to reach target state. Reason: Server.InternalError: Internal error on launch

/retest

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit 4ac9078 into openshift:release-4.2 Dec 3, 2019
@openshift-ci-robot
Copy link

@yselkowitz: All pull requests linked via external trackers have merged. Bugzilla bug 1773807 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1773807: Enable all Linux arches in cli-artifacts [4.2]

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.

@yselkowitz yselkowitz deleted the release-4.2 branch July 5, 2022 22:59
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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants