-
Notifications
You must be signed in to change notification settings - Fork 142
WIP: More work on probes, especially on rpmbuild ones #1603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
… forks (cherry picked from commit ef92203)
(cherry picked from commit ec8420c)
…429 from quay.io, 2 times in last 24 hours
…ically generated names and such)
…e where on missing metric it would say KPI errors = 0
…ips value even when running without --debug or so
Generated-by: Gemini
…ame namespace which turns out to need to set both new repo Name and Path
…et a change to collect whatever we have so far
…and also it does not make sense to condition fatal message esp. when it also does exit
… repo and will not wait for it to be deleted before forking to it
Assisted-by: Gemini
Assisted-by: Gemini
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
e7c80d6
to
0c005e9
Compare
…s already been taken, The project is still being deleted' even when target repo is already gone (returning 404)
…AB_BOT_TOKEN and GITLAB_API_URL
…crets: Unable to add secret ... to service account ...: serviceaccounts ... not found' errors, so adding explicit step to check component build SA presence
… Failed to fork, trying again: POST https://gitlab.cee.redhat.com/api/v4/projects/jhutar/libecpg-test-fork/fork: 403 {message: You cannot perform write operations on a read-only instance}
…ut that does not make RPM build pipeline to timeout
…ave seen once today
@jhutar: The following test has Failed, say /retest to rerun failed tests.
Inspecting Test ArtifactsTo inspect your test artifacts, follow these steps:
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/e2e-tests:konflux-e2e-5hb4l Test results analysis🚨 No JUnit file found, see the log from running tests: Click to view logs./mage -v ci:teste2e Running target: CI:TestE2E I0602 05:39:20.491574 15670 magefile.go:521] setting up new custom bundle for testing... Creating Tekton Bundle: - Added Pipeline: docker-build to image I0602 05:39:22.769971 15670 bundle.go:57] image digest for a new tekton bundle quay.io/redhat-appstudio-qe/test-images:pipeline-bundle-1748842761-zgew: quay.io/redhat-appstudio-qe/test-images@sha256:30afbafc57d9dfe5007374fff89508e36441cf56b78108be3c87fa62eb5d64db I0602 05:39:22.769993 15670 magefile.go:527] To use the custom docker bundle locally, run below cmd:
========================================================================= Argo CD URL is: https://openshift-gitops-server-openshift-gitops.apps.rosa.kx-1a3b60b374.5beq.p3.openshiftapps.com (NOTE: It may take a few moments for the route to become available) Waiting for the route: .OK Login/password uses your OpenShift credentials ('Login with OpenShift' button) |
Description
Changes needed for rpmbuild probe using loadtest and additional improvements and fixes for normal container building probes.
Issue ticket number and link
https://issues.redhat.com/browse/KONFLUX-7567
Type of change
How Has This Been Tested?
Running it in my fork and besides that I would rely on CI.