-
Bug
-
Resolution: Done-Errata
-
Normal
-
6.15.4
Description of problem:
When shutting down Satellite services there is a HUGE scroll of pulpcore-[content,api] Python 3.11 backtrace due to the loss of PostgreSQL connection. This is... disconcerting to say the least.
How reproducible:
Any time Satellite services are stopped. Even in the correct manner.
Is this issue a regression from an earlier version:
Seems to be.
Steps to Reproduce:
1. "satellite-maintain service stop"
2. Observe /var/log/messages
Actual behavior:
The log file gains a few hundred lines of moderately scary backtrace scroll, which surely isn't anything other than worrying to sysadmins.
Expected behavior:
The expected way to stop Satellite services shouldn't generate errors like this.
Business Impact / Additional info:
Reduced confidence in Satellite's correct functionality and data integrity (given it's to do with the back end DB).
- depends on
-
SAT-28713 make pulpcore-(api|content) same priority as workers by evgeni · Pull Request #934 · theforeman/foreman_maintain · GitHub
-
- Closed
-
- links to
-
RHEA-2025:148331 Satellite 6.17.0 release