Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Also happens for yum-3.2.29-73.el6
+++ This bug was initially created as a clone of Bug #1208803 +++
Description of problem:
First seen this auto-save-transaction "feature" in CentOS7 (yum-3.4.3-125)
I hate it from the first moment. This should be configurable.
Found this https://bugzilla.redhat.com/show_bug.cgi?id=684369 as CLOSED NOTABUG. So let it be a feature request.
Version-Release number of selected component (if applicable):
yum-3.4.3-125.el7.centos.noarch
CentOS Linux release 7.1.1503 (Core)
How reproducible:
Every time.
Steps to Reproduce:
1. Run as root 'yum install <any_package>'
2. Answer "N" to "Is this ok?' question
Actual results:
Yum creates file /tmp/yum_save_tx*.yumtx
Expected results:
Should be configurable.
i.e. after setting 'autosavets = 0' in /etc/yum/yum.conf no file should be created.
Additional info:
diff -Nurp /usr/lib/python2.7/site-packages/yum.orig/config.py /usr/lib/python2.7/site-packages/yum/config.py
--- /usr/lib/python2.7/site-packages/yum.orig/config.py 2015-03-09 21:39:15.000000000 +0100
+++ /usr/lib/python2.7/site-packages/yum/config.py 2015-04-03 10:15:20.224220449 +0200
@@ -876,6 +876,7 @@ class YumConf(StartupConf):
loadts_ignoremissing = BoolOption(False)
loadts_ignorerpm = BoolOption(False)
loadts_ignorenewrpm = BoolOption(False)
+ autosavets = BoolOption(True)
clean_requirements_on_remove = BoolOption(False)
diff -Nurp /usr/lib/python2.7/site-packages/yum.orig/__init__.py /usr/lib/python2.7/site-packages/yum/__init__.py
--- /usr/lib/python2.7/site-packages/yum.orig/__init__.py 2015-03-09 21:39:15.000000000 +0100
+++ /usr/lib/python2.7/site-packages/yum/__init__.py 2015-04-03 10:32:45.885187304 +0200
@@ -1355,7 +1355,8 @@ much more problems).
self._depsolving_failed = False
if rescode == 2:
- self.save_ts(auto=True)
+ if self.conf.autosavets != False:
+ self.save_ts(auto=True)
self.verbose_logger.debug('Depsolve time: %0.3f' % (time.time() - ds_st))
return rescode, restring
Comment 1Valentina Mukhamedzhanova
2016-07-25 15:11:14 UTC
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.