Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1416561

Summary: ca-certificates upgrade breaking maven central pom retrieval
Product: [Fedora] Fedora Reporter: Justin Venus <justin.venus>
Component: ca-certificatesAssignee: Kai Engert (:kaie) (inactive account) <kengert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 25CC: jorton, justin.venus, kengert, pwouters, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-26 16:54:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Maven build failure with updated ca-certificates installed none

Description Justin Venus 2017-01-25 19:57:09 UTC 
Created attachment 1244397 [details]
Maven build failure with updated ca-certificates installed

Description of problem:
Updated ca-certificates package breaks mvn.  The first package released with fc25 works as expected.


Version-Release number of selected component (if applicable):
ca-certificates-2017.2.11-1.0.fc25.noarch.rpm

How reproducible:
100% with a mesos build


Steps to Reproduce:
1. install/upgrade to ca-certificates-2017.2.11-1.0.fc25.noarch.rpm
2. git clone https://github.com/apache/mesos.git
3. cd mesos && git checkout tags/1.0.0
4. mkdir build && ./bootstrap && cd build
5. ../configure --without-python --with-java  # ignore warning about flags
6. cd src/mesos/java
7. MAVEN_OPTS="-Xmx1024m" mvn -X -B -f mesos.pom clean package

Actual results:
#see attachement `maven-failure.log` for more detail
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/jvenus/.m2/repository
[INFO] Scanning for projects...
[DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2
[DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2
[INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom
[DEBUG] Writing tracking file /home/jvenus/.m2/repository/org/apache/apache/11/apache-11.pom.lastUpdated
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.apache.mesos:mesos:1.0.0: Could not transfer artifact org.apache:apache:pom:11 from/to central (https://repo.maven.apache.org/maven2): java.security.ProviderException: java.lang.NegativeArraySizeException and 'parent.relativePath' points at wrong local POM @ line 18, column 11
 @
[ERROR] The build could not read 1 project -> [Help 1]
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.apache.mesos:mesos:1.0.0: Could not transfer artifact org.apache:apache:pom:11 from/to central (https://repo.maven.apache.org/maven2): java.security.ProviderException: java.lang.NegativeArraySizeException and 'parent.relativePath' points at wrong local POM @ line 18, column 11

    at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:422)


Expected results:
resolve dependencies

Additional info:
Comment 1 Kai Engert (:kaie) (inactive account) 2017-01-26 13:40:52 UTC 
Are you sure the problem is caused by the ca-certificates package, and can be fixed by downgrading the ca-certificates package, only?

Or could this bug be a duplicate of bug 1415137 which is about openjdk being incompatible with latest NSS 3.28 (because openjdk uses a private interface of NSS, which requires openjdk to be rebuilt).

I'm asking, because I see an exception related to ECKeyPairGenerator in your attachment.

Could you please try to upgrade to the newer java package that is made available in that bug, and check if it fixes your issue?
Comment 2 Justin Venus 2017-01-26 16:23:20 UTC 
Kai, yeah I've seen that exact segfault (randomly) and erroneously attributed it to running a build in docker.  I believe we can close this as a duplicate.
Comment 3 Justin Venus 2017-01-26 16:54:45 UTC 

*** This bug has been marked as a duplicate of bug 1415137 ***