-
Bug
-
Resolution: Unresolved
-
Blocker
-
1.37.0
-
False
-
-
False
-
-
-
Test and Release 1.37
Summary
During the verification of CR build, QE needs to access product jars and poms in nexus repository. Starting Nov 25th around noon, we start to experience build failure connected to artifacts not being resolvable.
Example:
[ERROR] Non-resolvable import POM: The following artifacts could not be resolved: org.kie.kogito:kogito-bom:pom:9.104.0.redhat-00003 (absent): org.kie.kogito:kogito-bom:pom:9.104.0.redhat-00003 was not found in https://baqe-nexus.apps.int.prod-scale-spoke1-aws-us-east-1.itup.redhat.com/nexus/content/groups/public-pnc during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of mirror-central has elapsed or updates are forced @ line 37, column 25 -> [Help 3]
The root cause of this is unknown.
This is a test blocker as most of the QE scenarios are requiring the nexus to be operational.
Environment
QE test suite, internal RH network
Steps to reproduce
Several options:
1. Access the nexus repo and try to download specific artifact
2. Server error will be shown - Code 500
OR
1. Create a quarkus application with workflow plugin
2. Run the application with workflow plugin
Actual results
Artifact is NOT resolvable, or accessible via Nexus UI browser
Expected results
Artifact is resolvable, or accessible via Nexus UI browser
Testing
N/A - this is blocking testing