RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2051582 - Enable ipa-ccache-sweep.timer during server installation
Summary: Enable ipa-ccache-sweep.timer during server installation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: ipa
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On: 2051575
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-07 14:41 UTC by Rob Crittenden
Modified: 2022-05-17 13:01 UTC (History)
5 users (show)

Fixed In Version: ipa-4.9.8-3.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2051575
Environment:
Last Closed: 2022-05-17 12:44:20 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-7816 0 None None None 2022-02-07 14:51:26 UTC
Red Hat Issue Tracker RHELPLAN-111363 0 None None None 2022-02-07 15:05:02 UTC
Red Hat Product Errata RHBA-2022:2387 0 None None None 2022-05-17 12:44:43 UTC

Description Rob Crittenden 2022-02-07 14:41:04 UTC
+++ This bug was initially created as a clone of Bug #2051575 +++

Cloned from upstream: https://pagure.io/freeipa/issue/9107

### Issue
Currently the ipa-ccache-sweep.timer is only enabled via the spec file when a server is already configured:
```
%posttrans server
# don't execute upgrade and restart of IPA when server is not installed
%{__python3} -c "import sys; from ipalib import facts; sys.exit(0 if facts.is_ipa_configured() else 1);" > /dev/null 2>&1

if [  $? -eq 0 ]; then
...
    /bin/systemctl is-enabled ipa-ccache-sweep.timer >/dev/null 2>&1
    if [  $? -eq 1 ]; then
        /bin/systemctl enable ipa-ccache-sweep.timer>/dev/null
    fi
fi
```
It should be explicitly enabled in the installer with: ```systemctl enable ipa-ccache-sweep.timer```

Noticed in 4.9.8 but this has been present since 4.9.0 when the feature was introduced.

--- Additional comment from Rob Crittenden on 2022-02-07 14:38:46 UTC ---

Upstream ticket:
https://pagure.io/freeipa/issue/9107

Comment 1 Rob Crittenden 2022-02-07 15:53:44 UTC
Upstream PR: https://github.com/freeipa/freeipa/pull/6168

Verification is, post-install on a fresh system:

/bin/systemctl is-enabled ipa-ccache-sweep.timer

Comment 7 Mohammad Rizwan 2022-02-22 07:11:21 UTC
version:
ipa-server-4.9.8-5.el9.x86_64
ipa-server-dns-4.9.8-5.el9.noarch



============================= test session starts ==============================
platform linux -- Python 3.9.10, pytest-6.2.2, py-1.10.0, pluggy-0.13.1 -- /usr/bin/python3
cachedir: /home/cloud-user/.pytest_cache
metadata: {'Python': '3.9.10', 'Platform': 'Linux-5.14.0-58.el9.x86_64-x86_64-with-glibc2.34', 'Packages': {'pytest': '6.2.2', 'py': '1.10.0', 'pluggy': '0.13.1'}, 'Plugins': {'metadata': '1.7.0', 'multihost': '3.0', 'sourceorder': '0.5', 'html': '3.1.1'}}
rootdir: /usr/lib/python3.9/site-packages/ipatests
plugins: metadata-1.7.0, multihost-3.0, sourceorder-0.5, html-3.1.1
collecting ... collected 4 items

test_integration/test_installation.py::TestInstallMasterKRA::test_install_master PASSED [ 25%]
test_integration/test_installation.py::TestInstallMasterKRA::test_ipa_ccache_sweep_timer_enabled PASSED [ 50%]
test_integration/test_installation.py::TestInstallMasterKRA::test_install_dns PASSED [ 75%]
test_integration/test_installation.py::TestInstallMasterKRA::test_kra_certs_renewal PASSED [100%]

=============================== warnings summary ===============================
../pytest_sourceorder.py:31
  /usr/lib/python3.9/site-packages/pytest_sourceorder.py:31: PytestUnknownMarkWarning: Unknown pytest.mark.source_order - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    cls = pytest.mark.source_order(cls)

-- Docs: https://docs.pytest.org/en/stable/warnings.html
---------------- generated xml file: /home/cloud-user/junit.xml ----------------
----------- generated html file: file:///home/cloud-user/report.html -----------
=================== 4 passed, 1 warning in 910.33s (0:15:10) ===================


Automation test passed, hence marking the test as verified.

Comment 10 errata-xmlrpc 2022-05-17 12:44:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: ipa), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2387


Note You need to log in before you can comment on or make changes to this bug.