RHEA-2018:0871 - Product Enhancement Advisory

Topic

An update for vdo is now available for Red Hat Enterprise Linux 7.

Description

The vdo packages provide Virtual Data Optimizer (VDO), which is a block virtualization technology that allows you to create compressed and deduplicated pools of block storage.

For detailed information on changes in this release, see the Red Hat Enterprise Linux 7.5 Release Notes linked from the References section.

Users of vdo are advised to upgrade to these updated packages.

Solution

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise Linux Server 7 x86_64
• Red Hat Enterprise Linux for x86_64 - Extended Update Support 7.7 x86_64
• Red Hat Enterprise Linux for x86_64 - Extended Update Support 7.6 x86_64
• Red Hat Enterprise Linux Server - AUS 7.7 x86_64
• Red Hat Enterprise Linux Server - AUS 7.6 x86_64
• Red Hat Enterprise Linux Server - Extended Life Cycle Support 7 x86_64
• Red Hat Enterprise Linux Workstation 7 x86_64
• Red Hat Enterprise Linux Desktop 7 x86_64
• Red Hat Enterprise Linux for Scientific Computing 7 x86_64
• Red Hat Enterprise Linux Server - TUS 7.7 x86_64
• Red Hat Enterprise Linux Server - TUS 7.6 x86_64
• Red Hat Enterprise Linux EUS Compute Node 7.7 x86_64
• Red Hat Enterprise Linux EUS Compute Node 7.6 x86_64
• Red Hat Enterprise Linux for x86_64 - Update Services for SAP Solutions 7.7 x86_64
• Red Hat Enterprise Linux for x86_64 - Update Services for SAP Solutions 7.6 x86_64

Fixes

• BZ - 1505885 - vdo --blockMapPeriod accepts values outside bound <1, 16380> and sets them to bounds
• BZ - 1505891 - vdo --vdoAckThreads, --vdoBioRotationInterval, --vdoBioThreads, --vdoCpuThreads, --vdoLogicalThreads, --vdoPhysicalThreads do not check input properly
• BZ - 1505936 - vdo --readCacheSize allows extremely high values without warning
• BZ - 1507927 - VDO modify --blockMapPeriod does not change the period
• BZ - 1507996 - vdo create allows creation on block device that is already used by another vdo
• BZ - 1507999 - Interruption vdo create before superblock is created hangs the vdo without enough info to remove it
• BZ - 1508452 - VDO does not allow --vdoLogicalSize > 4096T, but there is no limit in man/help
• BZ - 1508544 - vdo cli allows all options for all commands
• BZ - 1508918 - Some vdo commands do not return missing argument error when run without needed options
• BZ - 1510405 - vdo create --indexMem=0 is not accepted anymore
• BZ - 1510581 - issues when attempting vdo creation on live filesystem
• BZ - 1510585 - vdo creation fails on multiple partitioned devices
• BZ - 1511034 - vdoformat program erroneously prints "Exceeds maximum number of slabs" for case where index size is too big
• BZ - 1511042 - 'vdo: ERROR - Insufficient block map cache for vdo' with --vdoLogicalThreads HIGH, missing info in manpage about this link
• BZ - 1511075 - vdo manpage: Wrong maximum --vdoPhysicalThreads count
• BZ - 1511085 - vdo crate --vdoHashZoneThreads does not allow value 0
• BZ - 1511091 - vdo create --vdoLogicalThreads 0 does not check if --vdoPhysicalThreads and --vdoHashZoneThreads are both 0
• BZ - 1511109 - RFE: attempt to quiet vdo remove messages
• BZ - 1512127 - Creating a VDO volume over the metadata of a previously removed VDO volume fails
• BZ - 1512157 - vdo man page spells "vdoHashZoneThreads" with extra "s" in some places
• BZ - 1512968 - Clean up UDS threads when removing last vdo.
• BZ - 1513438 - vdo backing device is not recognized by blkid/wipefs
• BZ - 1515183 - "vdo create" should set the device mapper UUID
• BZ - 1519330 - VDO physical size does not reflect actual physical size usable by user
• BZ - 1520927 - vdo create --confFile with path to block_device should not be allowed
• BZ - 1520972 - vdoformat does not clean up metadata properly after fail
• BZ - 1520991 - vdo create --indexMem > 1024 gives wrong error
• BZ - 1522750 - vdo --logfile should not allow block device
• BZ - 1522754 - vdo create --noRun ends with "ERROR - 'NoneType' object has no attribute 'read'"
• BZ - 1522906 - vdo volumes should persist across reboot
• BZ - 1522943 - Remove nagios_check_albserver.pl from VDO RPM
• BZ - 1525560 - vdo --help is not listed correctly
• BZ - 1530358 - Running "vdo remove" for a non-existent device creates zero-byte regular file in old device path
• BZ - 1531047 - VDO should remove symlink to vdo.service when uninstalled
• BZ - 1532653 - vdo growLogical by less than 4K gives wrong error
• BZ - 1535127 - vdo growLogical changes write policy to the same
• BZ - 1536214 - VDO Ansible module in the 6.1.0.114 package fails on modification operations
• BZ - 1539059 - VDO RPM refer to Red Hat URL, and not Github URL

CVEs

(none)

References

• https://access.redhat.com/documentation/en-US/red_hat_enterprise_linux/7/html/7.5_release_notes/index.html