Description of problem:
After upgrading to 6.13, this warning message started happening on Candlepin.
The error.log has below traceback:
2023-09-27 00:00:00,786 [thread=https-jsse-nio-127.0.0.1-23443-exec-93] [req=d8b0e463-dadc-4521-8da1-856ef5e22509, org=UBCITServices, csid=] ERROR org.candlepin.exceptions.mappers.CandlepinExceptionMapper - Runtime Error Text 'Sun, 11 Jun 2023 17:51:29 GMT' could not be parsed at index 0 at java.time.format.DateTimeFormatter.parseResolved0:2,046
java.time.format.DateTimeParseException: Text 'Sun, 11 Jun 2023 17:51:29 GMT' could not be parsed at index 0
at java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2046)
at java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1948)
at java.base/java.time.ZonedDateTime.parse(ZonedDateTime.java:598)
at org.candlepin.resource.ConsumerResource.getContentAccessBody(ConsumerResource.java:2137)
at jdk.internal.reflect.GeneratedMethodAccessor212.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:151)
at org.jboss.resteasy.core.MethodInjectorImpl.lambda$invoke$3(MethodInjectorImpl.java:122)
at java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
at java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
at java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
at java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:143)
Version-Release number of selected component (if applicable):
candlepin-4.2.15-1.el8sat.noarch
How reproducible:
Hard
Steps to Reproduce:
Only in some of the customer environments.
Actual results:
This warning message is filling up rhsm.log on the candlepin error.log as well as all the content hosts rhsm.log files.
Expected results:
Should have no such warning
Additional info:
QE Tracker for https://issues.redhat.com/browse/SAT-20593
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2242214