Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-23313

openshift/build-machinery-go "verify" build target broken on Apple Silcon arch

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Undefined
    • None
    • 4.15
    • Build
    • None
    • No
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      Running `make verify` target from the openshift/build-machinery-go repo fails with the following error on my Apple Silcon system:
      ❯ make verify
      Running `gofmt -s -l` on 83 file(s).
      go vet -mod=vendor ./...
      Using existing yq from "_output/tools/bin/yq-v4.9.6"
      Using existing yaml-patch from "_output/tools/bin/yaml-patch-v0.0.11"
      cp -R ./manifests/* /var/folders/f6/0_0k3kns3s94_t41_sq_4zf40000gn/T/tmp.fPX51S3pRj/
      ( echo '# *** AUTOMATICALLY GENERATED FILE - DO NOT EDIT ***'; _output/tools/bin/yaml-patch-v0.0.11 -o './profile-patches/ibm-cloud-managed/07-operator.yaml-patch' < '/private/var/folders/f6/0_0k3kns3s94_t41_sq_4zf40000gn/T/tmp.fPX51S3pRj/07-operator.yaml' ) > '/private/var/folders/f6/0_0k3kns3s94_t41_sq_4zf40000gn/T/tmp.fPX51S3pRj/07-operator-ibm-cloud-managed.yaml'
      /bin/sh: line 1:  1273 Segmentation fault: 11  _output/tools/bin/yaml-patch-v0.0.11 -o './profile-patches/ibm-cloud-managed/07-operator.yaml-patch' < '/private/var/folders/f6/0_0k3kns3s94_t41_sq_4zf40000gn/T/tmp.fPX51S3pRj/07-operator.yaml'
      make: *** [verify-profile-manifests-manifests] Error 139

      Version-Release number of selected component (if applicable):

      4.15

      How reproducible:

      Always

      Steps to Reproduce:

      1. On a system with Apple Silicon architecture, clone the https://github.com/openshift/console-operator repo
      2. run `make verify`
      

      Actual results:

      The above error occurs

      Expected results:

      The command should complete successfully

      Additional info:

      This is an issue with the yaml-patch binary that is installed by the `ensure-yaml-patch` target. I was able to work around this issue by cloning the yaml-patch repo, and manually building a binary for my architecture. I suspect a similar issue also exists with the `yq` dependency.

      Attachments

        Activity

          People

            cdaley Corey Daley
            rh-ee-jonjacks Jon Jackson
            Corey Daley Corey Daley
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: