Hello, The PR mentioned by Can is now released as a patch on top of Uyuni 2022.01. Please check my announcement, so you can apply it instead of waiting for Uyuni 2022.02. And of course, please remember to provide feedback :-) Best regards. On martes, 8 de febrero de 2022 11:39:18 (CET) Can Bulut Bayburt wrote:
Hi Janne,
It's a known issue, and it's fixed with this PR: https://github.com/uyuni-project/uyuni/pull/4731. So please expect the fix to be available in the next release.
Meanwhile, increasing the stack size for the JVM may help avoid the error.
Cheers, Can
On 08.02.22 10:44, Karjanlahti Janne wrote:
Hello!
Yesterday Content Lifecycle Project build failed without any additional information. It was our test environment and it was never happened before. I (re)synced all source repos by hand (just in case) and after that build succeeded and all seemed to be ok. I was a bit hurry and I didn’t find any errors in log files at first glance so I leave it…
This morning I encountered same “failed” notice in our production Uyuni server. This time I clicked “Build” again without additional repo resync and the second build succeeded.
However repository content seems to be somewhat messed up, in both Uyuni servers. Client servers found a lot of updates, mainly different Perl packages but couldn’t update because of many conflicting dependencies. There is a lot of Perl 5.30 -version updates available even if I have not enabled this module stream. Default Perl version branch in Redhat EL8 derived distributions is 5.26 and additional versions is provided with module streams. Currently installed Perl version in my servers is 5.26. In fact there isn’t any filters concerning Perl at all in this Content Lifecyle Project.
I found errors in /var/log/rhn/ rhn_web_ui.log -file corresponding the failed environment build:
2022-02-08 07:03:03,580 [RHN Message Dispatcher] ERROR com.redhat.rhn.frontend.events.TransactionHelper - com.redhat.rhn.frontend.events.AlignSoftwareTargetAction$AlignSoftwareTarg etException:
java.lang.StackOverflowError
2022-02-08 07:03:03,656 [RHN Message Dispatcher] ERROR com.redhat.rhn.frontend.events.AlignSoftwareTargetAction - Error aligning target 3
com.redhat.rhn.frontend.events.AlignSoftwareTargetAction$AlignSoftwareTarg etException:
java.lang.StackOverflowError
at com.redhat.rhn.frontend.events.AlignSoftwareTargetAction.execute(AlignSoft wareTargetAction.java:71)
at com.redhat.rhn.common.messaging.ActionExecutor.lambda$run$0(ActionExecutor .java:67)
at com.redhat.rhn.frontend.events.TransactionHelper.run(TransactionHelper.jav a:63)
at com.redhat.rhn.frontend.events.TransactionHelper.handlingTransaction(Trans actionHelper.java:47)
at com.redhat.rhn.common.messaging.ActionExecutor.run(ActionExecutor.java:67)
at com.redhat.rhn.common.messaging.MessageDispatcher.run(MessageDispatcher.ja va:91)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.StackOverflowError
at java.base/java.util.function.Predicate.lambda$or$2(Predicate.java:101)
at java.base/java.util.function.Predicate.lambda$or$2(Predicate.java:101)
at java.base/java.util.function.Predicate.lambda$or$2(Predicate.java:101)
Last message continues about thousand lines.
Is there any other log files I should check?
We are using openSUSE Leap 15.3 and Uyuni 2022.01 version.
All the client servers and repositories/channels are Rocky Linux 8.
I think we must ditch current Lifecycle Environment and build totally new for our Rocky Linux servers. I wonder however is this a bug or is there something we should do differently this time to avoid this kind of errors?
Br, Janne
Janne Karjanlahti (Mr.) Vastaava järjestelmäasiantuntija | Senior Systems Specialist ICT- ja digitaaliset palvelut | ICT and Digital Services
Satakunnan ammattikorkeakoulu | Satakunta University of Applied Sciences
Satakunnankatu 23 | 28130 | PORI | Finland +358 44 710 3339
janne.karjanlahti@samk.fi mailto:janne.karjanlahti@samk.fi
www.samk.fi http://www.samk.fi
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com