s390x related fixes for tekton pipeline

[barthy1]

At this moment tekton pipeline is tested and released only for amd64 architecture.
I'd like to use this issue to track issues/work to run and test tekton pipeline on s390x architecture (IBM Z).
This work is part of tektoncd/plumbing#495 discussion.
List of issues/PRs can be updated in the future.

Bugs in the code:

• fail to run task with multi-arch image on non amd64 cluster (issue, PR)

e2e test errors:

• amd64 only test images (fails to run on s390x):
  • alpine/git (merged PR)
  • alpine/helm
  • gcr.io/kaniko-project/executor (merged PR)
  • gcr.io/tekton-releases/dogfooding/skopeo (PR)
  • quay.io/rhpipeline/skopeo:alpine (issue, PR)
• sha for busybox is amd64 specific for TestTaskRunStatus test -> fix TestTaskRunStatus e2e test to run on s390x #3061

examples test errors:

• amd64 only test images (fails to run on s390x):
  • quay.io/rhpipeline/skopeo:alpine (issue, PR)
  • gcr.io/cloud-builders/git (merged PR)
  • gcr.io/kaniko-project/executor:v0.17.1 (PR)
  • registry (replaced by available image for s390x) (merged PR)
  • gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/git-init:v0.11.0
  • docker:dind
  • docker
  • alpine/git:v2.24.3 (merged PR)
  • gcr.io/tekton-releases/dogfooding/alpine-git-nonroot:mario (PR)
  • node (merged PR)

PR #3107 to temporarily exclude failing tests is done

[pritidesai]

@barthy1 how about the examples? any changes needed in sample YAMLs?

[barthy1]

@pritidesai yeah, examples are actually in worse state for non Intel architectures :(
I am working now to identify at least most common reasons of the failures. Most of the errors are still connected to test images, available only for amd64. So soon the issue will be extended with examples section

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

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.