Issues with LCM promotions since migration to containerized release #10731
Closed
ppanon2022
started this conversation in
General
Replies: 1 comment 8 replies
-
|
We just did our first LCM build cycle since upgrading to 2025.10 and the LCM builds appeared to run much faster. |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We've had a few database-related issues since migrating to the containerized version of Uyuni. Some of which I've now figured out how to resolve, some of which are possibly more due to concomitant application changes (i.e. not a result of containerization), and some of which are still a problem.
pg_hba.conf and postgresql logging. PG used to create a few KB's worth of information/error logs per day before migration. Afterwards it's been a few megabytes. A huge part of it has to do with ident permission entries like
host all all 127.0.0.1/32 ident. Before containerization we were running an ident daemon but haven't been able to after since I think there is no option or files for that service in the server container, and there probably isn't any in MicroOS either. The log was filling with periodic errors (watchdog checks by podman?). Editing the conf file is challenging in the context of the post-2025.05, bare-bones postgresql container. Wound up using sed, remembering that the separation between columns is using tabs, \t. You might also need to add a rule to allow specifically for the polling using the postgres account to the postgres db on the 127.0.0.1 loopback.There was still old pg14 data post-migration under /var/lib/pgsql/data/data-pg14. It takes up a lot of room. I've kept the config files and the (quite small) log files for history and recycled the rest to recover a lot of space.
The above is important because our LCM project version builds and promotions have started using a lot of temp storage under /var/lib/pgsql/data/base/pgsql_tmp/, so our LCM project version builds were failing. Clearing up all the above space and adding a little more seems to have helped.
Those LCM builds are also taking way longer. Most of the time seems to be running various queries populating the rhnServerNeededCache table. I mean many, many hours for each project build. Are these new, or has there been some changes to the way they are populated which decreases their efficiency? Some of these queries seem to be at least partially dynamically generated and yet also parameterized. For example,
Is there something that can be done to improve performance here? What is rhnServerNeededCache needed for anyways? Because I don't understand why it would be taking hours to populate for the very small handful of servers attached to our first-stage test environment channels. It's causing us way more pain than it likely helps. Something seems wrong with this approach. In addition to the core O/S channels, we also have a number of custom 3rd-party child channels and queries like the above seem like massive overkill for those channels which wouldn't have anything to do with revoked packages, among other things.
but there also is an actual real version 10
and the current version number is much higher (due to failures caused by the above-mentioned space issues). If we try to build a new version, the dialog box shows 10 in the [greyed-out] Version field. Where is it picking that up from and how do I clear it up? I couldn't find a PG sequence that would be responsible and there seems to be no row for it in susecontentprojecthistoryentry like there is for the other versions. So how do I get rid of it - where is it coming from? Almost all of our projects appear to have these. We're using the REST API to schedule a lot of LCM project version/env builds, except when one fails and we need to manually fill the gap with the GUI. Maybe the REST API isn't updating something the GUI uses for tracking the next version?
Beta Was this translation helpful? Give feedback.
All reactions