tektoncd-results update

[rh-tap-build-team[bot]]

Included PRs:

• https://github.com/openshift-pipelines/tektoncd-results/pull/65

[gabemontero]

hitting known CI flake with annotating ingress from rosa

per https://github.com/redhat-appstudio/infra-deployments/pull/3425#issuecomment-1992323653 this change looks clean in e2e

[gabemontero]

the chains failure in test deployment is related to the chains change https://github.com/openshift-pipelines/pipeline-service/pull/962 that @Roming22 just merged I believe

will rebase momentarily after the upgrade test is finished

[gabemontero]

test-donwgrade failure in upgrade test seems unrelated to tekton results ... I've pinged @xinredhat about it in https://redhat-internal.slack.com/archives/C032EJ007C0/p1710262888075899

Here is the log for reference

step-run-tests
Run pipeline-service tests...
+ echo 'Run pipeline-service tests...'
+ kubectl -n default exec pod/ci-runner -- sh -c /workspace/sidecar/bin/plnsvc_test.sh
Start executing pipeline cases ...
+ echo 'Start executing pipeline cases ...'
++ find /workspace/source -type f -name test.sh -exec dirname '{}' +
+ TEST_DIR=/workspace/source/operator/test
+ /workspace/source/operator/test/test.sh --kubeconfig /kubeconfig --debug
+ shift
+ [[ 0 -gt 0 ]]
+ DEBUG=--debug
+ '[' 0 = 0 ']'
+ TEST_LIST=("chains" "pipelines" "results" "security" "metrics")
+ init
+++ dirname /workspace/source/operator/test/test.sh
++ cd /workspace/source/operator/test
++ pwd
[Setup]
  - Namespace configuration: + SCRIPT_DIR=/workspace/source/operator/test
+ export KUBECONFIG
+ NAMESPACE=plnsvc-tests
+ RESULTS_SA=tekton-results-tests
+ setup_test
+ echo '[Setup]'
+ echo -n '  - Namespace configuration: '
+ kubectl apply -k /workspace/source/operator/test/manifests/setup/pipeline-service
clusterrole.rbac.authorization.k8s.io/appstudio-pipelines-runner-clusterrole unchanged
Error from server (Forbidden): error when retrieving current configuration of:
Resource: "/v1, Resource=namespaces", GroupVersionKind: "/v1, Kind=Namespace"
Name: "plnsvc-tests", Namespace: ""
from server for: "/workspace/source/operator/test/manifests/setup/pipeline-service": namespaces "plnsvc-tests" is forbidden: User "system:serviceaccount:default:default" cannot get resource "namespaces" in API group "" in the namespace "plnsvc-tests"
Error from server (Forbidden): error when retrieving current configuration of:
Resource: "/v1, Resource=serviceaccounts", GroupVersionKind: "/v1, Kind=ServiceAccount"
Name: "appstudio-pipeline", Namespace: "plnsvc-tests"
from server for: "/workspace/source/operator/test/manifests/setup/pipeline-service": serviceaccounts "appstudio-pipeline" is forbidden: User "system:serviceaccount:default:default" cannot get resource "serviceaccounts" in API group "" in the namespace "plnsvc-tests"
Error from server (Forbidden): error when retrieving current configuration of:
Resource: "rbac.authorization.k8s.io/v1, Resource=rolebindings", GroupVersionKind: "rbac.authorization.k8s.io/v1, Kind=RoleBinding"
Name: "appstudio-pipelines-runner-rolebinding", Namespace: "plnsvc-tests"
from server for: "/workspace/source/operator/test/manifests/setup/pipeline-service": rolebindings.rbac.authorization.k8s.io "appstudio-pipelines-runner-rolebinding" is forbidden: User "system:serviceaccount:default:default" cannot get resource "rolebindings" in API group "rbac.authorization.k8s.io" in the namespace "plnsvc-tests"
command terminated with exit code 1
+ exit 1

[gabemontero]

getting a weird error here ^^ in the UI about branch could not be rebased, but looking at https://github.com/openshift-pipelines/pipeline-service/tree/tektoncd-results the branch is 1 commit ahead of main so it appears the rebase worked but the UI had a hiccup

[gabemontero]

yeah the command line options are not working ... I'm going to have to replace this PR with my own PR that pull in this change

[gabemontero]

OK the downgrade of pipeline service somehow failed with results though the reason is unclear to me from the debug

if it shows up in #968 we'll have to sort out how to do the downgrade test manually, so we can look at the gitops status