-
Bug
-
Resolution: Done
-
Critical
-
Pipelines 1.11.0
-
None
-
3
-
False
-
None
-
False
-
-
-
Pipelines Sprint 241, Pipelines Sprint 242, Pipelines Sprint 243
Description of problem:
Started acceptance test using
by modifying these two params
- name: TEMPLATE
value: private-templates/functionality-testing/aos-4_13/ipi-on-aws/versioned-installer-fips - name: TAGS
value: "sanity"
The output of the result:
STEP-EVALUATE-TEST-SUITES
Passed test suites
INSTALL-PIPELINES-OPERATOR
RELEASE-TESTS-METRICS
RELEASE-TESTS-TRIGGERS-TLS
RELEASE-TESTS-CLUSTERTASKS-MULTIARCH
RELEASE-TESTS-PIPELINES
RELEASE-TESTS-CLUSTERTASKS-S2I
RELEASE-TESTS-TRIGGERS
RELEASE-TESTS-RBAC
RELEASE-TESTS-ADDON
RELEASE-TESTS-AUTO-PRUNE
----------------------------------
----------------------------------
Failed Test suites
RELEASE-TESTS-CLUSTERTASKS
The RELEASE-TESTS-CLUSTERTASKS failed with
sign_and_send_pubkey: no mutual signature supported\r\ngit@github.com: Permission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists
for git-clone-read-private-pipeline-run test
The reason for the issue is mismatch algorithm used to verify
Creating separate issue to track this and closing this issue as its not a blocker
Slack Discussion:
https://redhat-internal.slack.com/archives/C03A1MBHN81/p1686656270800839
https://redhat-internal.slack.com/archives/CQ7BBRNQN/p1686725622755979
Original Issue: https://issues.redhat.com/browse/SRVKP-3184
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
# <steps>
Actual results:
Expected results:
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):