openshift-pipelines / pipeline-service

SaaS for Tekton Pipelines
Apache License 2.0
23 stars 44 forks source link

temporarily revert results to current prod level to simplify switch to nightlies #975

Closed gabemontero closed 6 months ago

gabemontero commented 6 months ago

prod currently at 1c5b3054ffb52f172fda31587d7dfd88a9724c8f

remove the threadiness to 32

migrator benign but reverting to simplify things

enarha commented 6 months ago

/lgtm

enarha commented 6 months ago

/test test-pipeline-service-upgrade-ocp-414

gabemontero commented 6 months ago

The previous test-downgrade failed with this @enarha

step-run-tests
+ echo 'Run pipeline-service tests...'
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 ']'
[Setup]
  - Namespace configuration: + TEST_LIST=("chains" "pipelines" "results" "security" "metrics")
+ init
+++ dirname /workspace/source/operator/test/test.sh
++ cd /workspace/source/operator/test
++ pwd
+ 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

I think this is unrelated to our change here.

If upgrade fails again, based on the failure, I saw we merge.

gabemontero commented 6 months ago

the results watcher is not passing upgrade in the last run

I am attempting to test upgrade scenario manually

gabemontero commented 6 months ago

manual baseline from latest main branch -> upgrade to this PR's reverting -> downgrade back to the main branch plus tests each step along the way using the results CLI worked just fine for me using dev_setup.sh with --use-current-branch

I'm merging this @enarha