Red Hat Bugzilla – Bug 1051828
packstack: add symlink in /var/tmp/packstack to most recent results
Last modified: 2016-04-07 16:58:51 EDT
Description of problem: Feature request: When packstack is run a symlink from the most recent results: /var/tmp/packstack/packstack_run_hash_ID To a standard name like: /var/tmp/packstack/Latest should be created. This would aid in finding the most recent results when trouble shooting a problem. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I would close this bug because it's easy to recognize which one was the latest installation of packstack due to the date and time, is not that cumbersome to identify which one is the last installed release. Anyway, if David want to do it and send the review, I would be more than pleased to follow up.
I'd like to try to add a symlink for it, please let me have a try. Thanks
I agree that a "ls -t" will show you the latest. But if I recall correctly taking the assumption that the last entry in a simple "ls" does not. I.e. The directory names are not named alpha-numerically sequentially. Adding a symlink to the latest aids with troubleshooting. Rather than saying: "Do a 'ls -t' in /var/tmp/packstack. Find the last entry. 'cd' to that directory" You can simply say: "'cd' to /var/tmp/packstack/latest"
Hey guys, I think I have done something. How can I submit my patch? On launchpad or?
Created attachment 855679 [details] add symbol link for latest log dir
Looks OK to me: # ls -l /var/tmp/packstack/ total 8 drwx------. 2 root root 4096 Jan 25 15:32 20160125-153211-fwTCE6 drwx------. 4 root root 4096 Jan 25 15:32 20160125-153212-5A99YH lrwxrwxrwx. 1 root root 41 Jan 25 15:32 latest -> /var/tmp/packstack/20160125-153212-5A99YH
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, 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://rhn.redhat.com/errata/RHEA-2016-0603.html