Bug 1462078 - Include wrong glusterfs in redhat-virtualization-host-4.1-20170613.0(Initial 7.4 build)
Include wrong glusterfs in redhat-virtualization-host-4.1-20170613.0(Initial ...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhev-hypervisor-ng (Show other bugs)
4.1.4
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Ryan Barry
cshao
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-16 02:47 EDT by cshao
Modified: 2017-06-16 02:56 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-16 02:56:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Node
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description cshao 2017-06-16 02:47:57 EDT
Description of problem:
Include wrong glusterfs in redhat-virtualization-host-4.1-20170613.0(Initial 7.4 build)


Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.1-20170613.0
imgbased-0.9.31-0.1.el7ev.noarch


How reproducible:
100%

Steps to Reproduce:
1. Install redhat-virtualization-host-4.1-20170613.0
2. Login RHVH, check glusterfs version.
# rpm -qa| grep glusterfs
glusterfs-rdma-3.8.4-18.2.el7rhgs.x86_64
glusterfs-3.8.4-18.2.el7rhgs.x86_64
glusterfs-api-3.8.4-18.2.el7rhgs.x86_64
glusterfs-cli-3.8.4-18.2.el7rhgs.x86_64
glusterfs-server-3.8.4-18.2.el7rhgs.x86_64
glusterfs-fuse-3.8.4-18.2.el7rhgs.x86_64
glusterfs-client-xlators-3.8.4-18.2.el7rhgs.x86_64
glusterfs-libs-3.8.4-18.2.el7rhgs.x86_64
glusterfs-geo-replication-3.8.4-18.2.el7rhgs.x86_64



Actual results:
 Include wrong glusterfs in redhat-virtualization-host-4.1-20170613.0(Initial 7.4 build)

Expected results:
1. After step2, RHVH should include newer glusterfs version(glusterfs-3.8.4-18.4.el7).

Additional info:

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