Katello nightly pipeline failed:
https://ci.theforeman.org/job/katello-nightly-rpm-pipeline/204/
foreman-katello-upgrade-nightly-test (failed)
foreman-katello-nightly-test (failed)
[ WARN 2019-09-18T16:48:08 verbose] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: rake aborted!
[ WARN 2019-09-18T16:48:08 verbose] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: ForemanTasks::TaskError: Task 027ebb30-7f35-49f0-9cc5-4cbfaeb8326a: RestClient::ServerBrokeConnection: Katello::Resources::Candlepin::Owner: Server broke connection (POST /candlepin/owners/Default_Organization/uebercert)
Looks a lot like Candlepin crash after upgrade to 1.22.1 / https://bugzilla.redhat.com/show_bug.cgi?id=1751967
Sep 18 16:47:59 pipeline-katello-server-nightly-centos7 server: Sep 18, 2019 4:47:59 PM org.apache.catalina.startup.Catalina start
Sep 18 16:47:59 pipeline-katello-server-nightly-centos7 server: INFO: Server startup in 37227 ms
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: #
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # A fatal error has been detected by the Java Runtime Environment:
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: #
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # SIGSEGV (0xb) at pc=0x00007f20f98cda8f, pid=2334, tid=0x00007f2115633700
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: #
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build 1.8.0_222-b10)
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64 compressed oops)
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # Problematic frame:
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # C [libplds4.so+0x1a8f] PL_HashTableLookupConst+0xf
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: #
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: #
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # An error report file with more information is saved as:
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # /usr/share/tomcat/hs_err_pid2334.log
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: #
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # If you would like to submit a bug report, please visit:
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # http://bugreport.java.com/bugreport/crash.jsp
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # The crash happened outside the Java Virtual Machine in native code.
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: # See problematic frame for where to report the bug.
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 server: #
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 systemd: tomcat.service: main process exited, code=killed, status=6/ABRT
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 systemd: Unit tomcat.service entered failed state.
Sep 18 16:48:08 pipeline-katello-server-nightly-centos7 systemd: tomcat.service failed.
cc @justin_sherrill / @Jonathon_Turel https://bugzilla.redhat.com/show_bug.cgi?id=1751967#c3 suggests this may be resolved in 2.6.8. Can we tag this into nightly to see if it passes? If so, we should also tag it into releases since it’s hitting users in stable releases.
I’ll tag it in this morning!
We are using Candlepin 2.7.1 upstream and I was testing 2.8.1 locally which has the fix. Ran into another issue and the Candlepin team has a fix, just waiting on a new build and will tag it into nightly when I have it.
1 Like
Since this is also hitting users in 3.12, do we want to tag 2.6.8 into 3.12 so the next katello release has it? I’m sure some users wouldn’t mind testing a staging RPM.
Good idea. I built 2.6.8 in Koji and gave it a test on my 3.12 instance and it dropped right into place. No schema changes either! We don’t have any releases planned on the 3.12 line, but I tagged 2.6.8 for 3.12. IMO it’s safe to release. Can you kick off the pipeline?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.