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.
DescriptionGianluca Cecchi
2012-02-13 13:37:43 UTC
Description of problem:
As far as I read, repackage option is not available in rh el 6 and it should be substituted with
- yum history and undo/redo functionalities
- yum-plugin-fs-snapshot functionality
but it is still present in yum man page
Version-Release number of selected component (if applicable):
yum-3.2.29-22.el6.noarch
How reproducible:
always
Steps to Reproduce:
1. man yum.conf
2.
3.
Actual results:
tsflags Comma or space separated list of transaction flags to
pass to the rpm transaction set. These include ’noscripts’,
’notriggers’, ’nodocs’, ’test’, ’justdb’ and ’nocontexts’.
’repackage’ is also available but that does nothing with newer
rpm versions. You can set all/any of them. However, if you
don’t know what these do in the context of an rpm transaction
set you’re best leaving it alone. Default is an empty list.
Expected results:
no mention of repackage options
Additional info:
I initially searched for repackage options in RH EL 6 and came to this thread and its dependencies...
https://www.redhat.com/archives/rhelv6-beta-list/2010-June/msg00056.html
BTW: is yum-plugin-fs-snapshot available in RH EL 6.2? Is it supported/reccomended with LVM?
Sorry, I misread the man page and indeed inside the phrases I reported there is
’repackage’ is also available but that does nothing with newer rpm versions
Still it would be fine to have some KB related to this matter.
I only found these ones:
https://access.redhat.com/kb/docs/DOC-8139https://access.redhat.com/kb/docs/DOC-2915
Thanks in advance,
Gianluca
Ok. For some reason I didn't find the plugin rpm when I posted the answer, so I was in doubt about where to find/enable it...
Now I tried again and I'm able to run without problems
# yum install yum-plugin-fs-snapshot
The guide seems ok.
I'm going to test some scenarios.
Only by reading, two things on which I would elaborate are these ones:
- overall file systems layout of the entire system
The guide only say
"In order for the plug-in to work, the root file system (that is, /) must be on an LVM (Logical Volume Manager) or Btrfs volume."
Actually this could lead to a problematic system if for example I have
/ on lvm
/usr in another file system (not necessarily on LVM)
/var in another file system (not necessarily on LVM)
or not?
If I decide to revert the changes, I will then have / with previous data, while /usr and /var with new updated data (eg the rpm database itself)... or not?
What if the 3 fs above are all on LVM? Will the update process create 3 snapshots allowing me to come back on all the three fs or not?
- btrfs
same doubts as with LVM
+
In case of reverting changes I would add something like
d. Verify that the system is working as expected and then delete the subvolume of the unwanted update transaction (or something similar)
Gianluca
As the man page says, the repackage option is _available_ but does nothing in later versions of rpm. Not documenting it at all (removing it from the man page) doesn't seem like a great idea for RHEL-6 ... maybe worth it upstream before RHEL-7 though.
The fs-snapshot plugin will create snapshots for all mount points that it can create snapshots for (currently LVM and btrfs). There is no native rollback/release support ... the plugin just creates the snapshots.
If /foo is on LVM and /bar is on direct ext4 then you get a snapshot for /foo only.
Description of problem: As far as I read, repackage option is not available in rh el 6 and it should be substituted with - yum history and undo/redo functionalities - yum-plugin-fs-snapshot functionality but it is still present in yum man page Version-Release number of selected component (if applicable): yum-3.2.29-22.el6.noarch How reproducible: always Steps to Reproduce: 1. man yum.conf 2. 3. Actual results: tsflags Comma or space separated list of transaction flags to pass to the rpm transaction set. These include ’noscripts’, ’notriggers’, ’nodocs’, ’test’, ’justdb’ and ’nocontexts’. ’repackage’ is also available but that does nothing with newer rpm versions. You can set all/any of them. However, if you don’t know what these do in the context of an rpm transaction set you’re best leaving it alone. Default is an empty list. Expected results: no mention of repackage options Additional info: I initially searched for repackage options in RH EL 6 and came to this thread and its dependencies... https://www.redhat.com/archives/rhelv6-beta-list/2010-June/msg00056.html BTW: is yum-plugin-fs-snapshot available in RH EL 6.2? Is it supported/reccomended with LVM?