running buildah-tssc

Step: buildah-tssc
Results: /workspace/source/source/results/buildah-tssc
Custom root CA variable is not set. Make sure CA trust is established
========Running buildah-tssc:login
--- Registry Auth Bypass Active ---
========Running buildah-tssc:build
[1/2] STEP 1/3: FROM registry.access.redhat.com/ubi9/nodejs-22:latest
Trying to pull registry.access.redhat.com/ubi9/nodejs-22:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob sha256:582096acf723fc4ed6f7e071cf8ed3ebc7f6208c4252483aa36a86d8ada7962c
Copying blob sha256:4659f647ba9358e423d7a6d11b064756eae785fadb68f83b36a662a36dcc1d2d
Copying blob sha256:82802daa14561c6530ef7fb00bcb9f5af1d332869bbf459b54f53ad0728eb02b
Copying config sha256:de2e6f236c519da903b7f179ea80c17883ba177e66995737c1f481990c01aec0
Writing manifest to image destination
Storing signatures
[1/2] STEP 2/3: COPY package.json package-lock.json* ./
[1/2] STEP 3/3: RUN   if [ -f package-lock.json ]; then npm ci;   else npm install;   fi

added 102 packages, and audited 103 packages in 2s

19 packages are looking for funding
  run `npm fund` for details

3 moderate severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
[2/2] STEP 1/6: FROM registry.access.redhat.com/ubi9/nodejs-22-minimal:latest
Trying to pull registry.access.redhat.com/ubi9/nodejs-22-minimal:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob sha256:20192c9ed207607c4d566baf1685ef6b2df874d8c73252bf3f225ccd15a2d68f
Copying blob sha256:8af57f051b373375a1be8f892172089259ad624ed8452291226c539055e60228
Copying config sha256:ccd22d9877998c66934b2d2103bb01b32fd44c01e20b4b65f81ac207da9e9160
Writing manifest to image destination
Storing signatures
[2/2] STEP 2/6: COPY --from=0 /opt/app-root/src/node_modules /opt/app-root/src/node_modules
[2/2] STEP 3/6: COPY . /opt/app-root/src
[2/2] STEP 4/6: ENV NODE_ENV production
[2/2] STEP 5/6: ENV PORT 3001
[2/2] STEP 6/6: CMD ["npm", "start"]
[2/2] COMMIT quay.io/rhtap_qe/e2e-tests-nodejs-rauueqec:on-pr-1a8330d3370212d7d29f51b9b28de1ee50f60e9d
Getting image source signatures
Copying blob sha256:eb31fffb4653a560fe98f0cdf1563599483471410f682eef43f925913573d867
Copying blob sha256:8ea24990fbb2c2de72af3fd91bf04b5a2718aaf99d9d53cebefcb16ea6dd5652
Copying blob sha256:ee3e17c8c422660118ec7a22b0328c2236d5de0b833c6eb5253997522721e611
Copying config sha256:b7e4c0d720b074d3fff51eb0aa810ab5b81d72696a5779fcfeb7905f9d98d12c
Writing manifest to image destination
--> b7e4c0d720b0
Successfully tagged quay.io/rhtap_qe/e2e-tests-nodejs-rauueqec:on-pr-1a8330d3370212d7d29f51b9b28de1ee50f60e9d
b7e4c0d720b074d3fff51eb0aa810ab5b81d72696a5779fcfeb7905f9d98d12c
Getting image source signatures
Copying blob sha256:8ea24990fbb2c2de72af3fd91bf04b5a2718aaf99d9d53cebefcb16ea6dd5652
Copying blob sha256:ee3e17c8c422660118ec7a22b0328c2236d5de0b833c6eb5253997522721e611
Copying blob sha256:eb31fffb4653a560fe98f0cdf1563599483471410f682eef43f925913573d867
Copying config sha256:b7e4c0d720b074d3fff51eb0aa810ab5b81d72696a5779fcfeb7905f9d98d12c
Writing manifest to image destination
sha256:cdb71469032356b3de00e534802ad0d17d6c3b3e385e032ad8386bd0e7f227dfquay.io/rhtap_qe/e2e-tests-nodejs-rauueqec:on-pr-1a8330d3370212d7d29f51b9b28de1ee50f60e9dGetting image source signatures
Copying blob sha256:ee3e17c8c422660118ec7a22b0328c2236d5de0b833c6eb5253997522721e611
Copying blob sha256:eb31fffb4653a560fe98f0cdf1563599483471410f682eef43f925913573d867
Copying blob sha256:8ea24990fbb2c2de72af3fd91bf04b5a2718aaf99d9d53cebefcb16ea6dd5652
Copying config sha256:b7e4c0d720b074d3fff51eb0aa810ab5b81d72696a5779fcfeb7905f9d98d12c
Writing manifest to image destination
========Running buildah-tssc:generate-sboms
{
  "bom-ref": "af63bd4c8601b7f1",
  "type": "file",
  "name": "e2e-tests-nodejs-rauueqec",
  "version": "1a8330d3370212d7d29f51b9b28de1ee50f60e9d"
}
{
  "bom-ref": "224c61ec0402cc1d",
  "type": "container",
  "name": "quay.io/rhtap_qe/e2e-tests-nodejs-rauueqec:on-pr-1a8330d3370212d7d29f51b9b28de1ee50f60e9d",
  "version": "sha256:cdb71469032356b3de00e534802ad0d17d6c3b3e385e032ad8386bd0e7f227df"
}
========RUNNING PYTHON 
========Running buildah-tssc:upload-sbom
There is a discussion in sigstore community triggered by https://github.com/sigstore/cosign/issues/3599.
It is likely that cosign attach deprecation will be reverted. Please, ignore deprecation warning for now.
WARNING: SBOM attachments are deprecated and support will be removed in a Cosign release soon after 2024-02-22 (see https://github.com/sigstore/cosign/issues/2755). Instead, please use SBOM attestations.
WARNING: Attaching SBOMs this way does not sign them. To sign them, use 'cosign attest --predicate /workspace/source/source/results/temp/files/sbom-cyclonedx.json --key <key path>'.
Uploading SBOM file for [quay.io/rhtap_qe/e2e-tests-nodejs-rauueqec:on-pr-1a8330d3370212d7d29f51b9b28de1ee50f60e9d] to [quay.io/rhtap_qe/e2e-tests-nodejs-rauueqec:sha256-cdb71469032356b3de00e534802ad0d17d6c3b3e385e032ad8386bd0e7f227df.sbom] with mediaType [application/vnd.cyclonedx+json].

========