Activity
From 05/07/2023 to 06/05/2023
06/05/2023
- 04:00 PM Bug #36467 (Closed): foreman-maintain restart does not always ensure all services are started
- Applied in changeset commit:foreman_maintain|7cdffe78727b48ca148ba50e9eb069fc522429f8.
- 01:22 PM Bug #36467 (Ready For Testing): foreman-maintain restart does not always ensure all services are started
- 01:20 PM Bug #36467 (Closed): foreman-maintain restart does not always ensure all services are started
- 03:03 PM Revision 7cdffe78 (foreman_maintain): Fixes #36467 - Use systemctl restart to restart services
- 01:25 PM Feature #20027 (Closed): Sat6.1->6.2 upgrade leaves 3 directories under /var/lib/pulp as orphaned with lots of content
- 01:24 PM Bug #36468 (Rejected): Service management should rely on systemd dependencies rather than priorities in foreman-maintain
- See https://github.com/theforeman/foreman_maintain/pull/733#discussion_r1213998571
- 01:17 PM Revision 1df54ccf (foreman_maintain): Default to INFO level logging
06/02/2023
- 07:00 AM Bug #36464 (Closed): satellite-maintain service enable fails to enable all services previously disabled by satellite-maintain service disable
- Applied in changeset commit:foreman_maintain|079baecc4417f6d218c93ab9df0217e8672ffaaf.
- 06:35 AM Bug #36464 (Closed): satellite-maintain service enable fails to enable all services previously disabled by satellite-maintain service disable
- Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2055790
*Description of problem:*
After disabling Satell... - 06:39 AM Revision 079baecc (foreman_maintain): Fixes #36464 - always manage pulpcore services
- Old, old code confined Pulp services to if they were enabled or not.
However, if the 'service disable' command is use...
05/31/2023
- 07:38 PM Revision f5f27a1c (foreman_maintain): don't overwrite dnf.Plugin.__init__
- we do the very same as the main init method, so no need to do it at all.
05/26/2023
- 08:37 AM Bug #36443 (Ready For Testing): foreman-protector plugin should not lock packages for reposync
- 08:37 AM Bug #36443 (Closed): foreman-protector plugin should not lock packages for reposync
- Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2192841
*Description of problem:*
https://access.redhat....
05/19/2023
- 01:38 PM Revision 1df5ba58 (foreman_maintain): Stop caching the package_manager
- Since facts are cached there is no need to cache the package manager
class and doing so causes inconsistencies among ...
05/17/2023
- 09:23 PM Revision 0436eabc (foreman_maintain): Fix foreman service being enabled after disable
- The conditional is no longer needed since having Puma as our app
server for foreman. This code path introduced a bug ...
05/08/2023
- 06:01 PM Bug #36369 (Closed): Consider both 0 and 100 as valid exit codes for check-update yum action
- Applied in changeset commit:foreman_maintain|f4f5e6252db4e6a1f9af689d35273eb3428cf0c1.
- 05:40 PM Bug #36369 (Ready For Testing): Consider both 0 and 100 as valid exit codes for check-update yum action
- 05:36 PM Bug #36369 (Closed): Consider both 0 and 100 as valid exit codes for check-update yum action
- Right now in https://github.com/theforeman/foreman_maintain/blob/master/lib/foreman_maintain/package_manager/yum.rb#L...
- 05:49 PM Revision f4f5e625 (foreman_maintain): Fixes #36369 - Exit code 0 is a valid exit status
- 05:42 PM Revision 9028d6f4 (foreman_maintain): Refactor pulpcore-manager call to a function
- 02:00 PM Bug #36365 (Closed): Drop the usage of sudo during any pulpcore-manager command executions
- Applied in changeset commit:foreman_maintain|da7460cc63e7eb5be3dcf33da9366dd02dfcca20.
- 01:41 PM Revision da7460cc (foreman_maintain): Fixes #36365 - Drop usage of sudo for any pulpcore-manager commands
Also available in: Atom