Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1361591 - Running ipa-client-install creates /root/.cache directory structure with some content
Summary: Running ipa-client-install creates /root/.cache directory structure with some...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Kaleem
Depends On:
TreeView+ depends on / blocked
Reported: 2016-07-29 13:10 UTC by Jan Pazdziora
Modified: 2016-08-03 12:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-08-03 12:48:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jan Pazdziora 2016-07-29 13:10:00 UTC
Description of problem:

When ipa-client-install, new directory /root/.cache gets created.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Run ls -la /root/.cache, check that it says

ls: cannot access /root/.cache: No such file or directory

2. Run ipa-client-install
3. Run ls -la /root/.cache

Actual results:

# ls -la /root/.cache
total 0
drwxr-xr-x. 3 root root  17 Jul 29 18:35 .
dr-xr-x---. 4 root root 207 Jul 29 18:35 ..
drwxr-xr-x. 4 root root  35 Jul 29 18:35 ipa

Expected results:

ls: cannot access /root/.cache: No such file or directory

Additional info:

# find /root/.cache

The /root/.cache/ipa/schema/5966d774 is some ZIP file and /root/.cache/ipa/servers/ipa.example.test contains

{"expiration": 1469801129.888574, "fingerprint": "5966d774"}

Comment 2 Petr Vobornik 2016-08-03 12:48:37 UTC
This is expected behavior. $homedir/.cache/ipa serves as CLI's IPA API schema cache

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