Uploaded image for project: 'OpenShift Windows Containers'
  1. OpenShift Windows Containers
  2. WINC-1350

Fix error outputs of check-payload script

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • 3
    • False
    • None
    • False

      Description

      Currently, the check-payload script gives 2 errors when scanning our operator image:

      [mohashai@mohashai check-payload]$ ./check-payload scan local --path ../windows-machine-config-operator/build/_output/bin/ --verbose -p
      I1111 12:15:22.297727   56815 main.go:103] "scan" version="0.3.1-189-g454f59f3"
      I1111 12:15:22.395388   56815 validations.go:402] can't find rpmdb under "../windows-machine-config-operator/build/_output/bin"
      I1111 12:15:22.395426   56815 scan.go:460] "scanning failed" image="" path="/windows-machine-config-operator" error="go binary does not contain required symbol(s)" component="" tag="" rpm="" status="failed"
      ---- Failure Report
      +---------------------------+
      STATUS                                   
      +---------------------------+
      openssl library not present
      go binary does not contain required symbol(s)
      
      
      [[ignore]]
      error = "ErrGoMissingSymbols"
      files = [ "/windows-machine-config-operator" ]

       
      Both may be solved by moving to using a golang image with openssl like MCO has done. These are builder images published by ART

      Acceptance Criteria

      The above subset of errors in check-payload script (in the CI job and manually) are fixed

              Unassigned Unassigned
              mohashai Mohammad Shaikh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: