Bug 1488839 - glusterd service is not stopped during RHEL7 as hypervisor upgrade.
Summary: glusterd service is not stopped during RHEL7 as hypervisor upgrade.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: ---
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.1.8
: ---
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1488852 1511816
TreeView+ depends on / blocked
 
Reported: 2017-09-06 10:11 UTC by RamaKasturi
Modified: 2017-12-11 16:31 UTC (History)
21 users (show)

Fixed In Version: ovirt-engine-4.1.8.1
Clone Of:
: 1488852 (view as bug list)
Environment:
Last Closed: 2017-12-11 16:31:01 UTC
oVirt Team: Gluster
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: blocker+
mgoldboi: planning_ack+
rule-engine: devel_ack+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 82219 0 master MERGED bll: All gluster related processes stopped during host upgrade 2017-11-02 14:00:36 UTC
oVirt gerrit 84009 0 ovirt-engine-4.1 MERGED bll: All gluster related processes stopped during host upgrade 2017-11-14 10:18:49 UTC
oVirt gerrit 84101 0 master MERGED core: Fix upgrade of virt host in UP state 2017-11-15 12:58:40 UTC
oVirt gerrit 84185 0 ovirt-engine-4.1 MERGED core: Fix upgrade of virt host in UP state 2017-11-16 08:37:20 UTC

Description RamaKasturi 2017-09-06 10:11:18 UTC 
Description of problem:
When RHV-H is upgraded from UI during the upgrade process glusterd is not stopped and due to this gluster packages will not get updated since process will be running.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. click on upgrade button in the UI for RHV-H node.
2. wait for all the vms to be migrated from the node
3. Now go to the node and check for glusterd process.

Actual results:
glusterd process will be running during upgrade of the host.

Expected results:
All process related to gluster should be stopped so that upgrade of gluster packages happens successfully.

Additional info:
Comment 1 RamaKasturi 2017-09-06 10:12:26 UTC 
Version :
=====================
You are on rhvh-4.1-0.20170817.0+1
Comment 2 Ryan Barry 2017-09-06 11:13:50 UTC 
RHVH is installed as-is as a complete image which is installed on a new LV. Individual packages are not upgraded. Are you sure this is a bug?
Comment 3 RamaKasturi 2017-09-06 11:24:55 UTC 
Ryan,

   I have not got a chance to test this. I think you are right, totally missed this point. If this gets installed as a new LV then it should be fine i think. You can close this bug for now and will reopen if i see any issues.

Thanks
kasturi
Comment 5 SATHEESARAN 2017-09-08 10:08:33 UTC 
In the case RHEL 7 hosts as hypervisors, the 'upgrade' initiated from RHV UI, should also stop glusterfs services, in the case, found with 'glusterfs' package update


Based on this fact, I am re-opening the bug
Comment 6 RamaKasturi 2017-09-08 10:46:27 UTC 
Thanks sas for reopening. I totally missed this point
Comment 7 Sandro Bonazzola 2017-10-20 06:13:21 UTC 
Sahina, this is not marked as a blocker, please either block 4.1.7 or push to 4.1.8.
Comment 8 Martin Perina 2017-11-15 08:32:37 UTC 
Moving back to post as an issue was found in original patch
Comment 9 Martin Perina 2017-11-15 08:34:30 UTC 
Also marking as blocker for 4.1.8, because patch which break host upgrade in clusters without gluster services is already merged to 4.1 branch
Comment 10 Martin Perina 2017-11-16 17:38:28 UTC 
Moving back to MODIFIED, it missed the 1st 4.1.8 build
Comment 11 SATHEESARAN 2017-12-04 12:23:57 UTC 
Verified that glusterd is restarted, when update is triggered from RHV UI
Note You need to log in before you can comment on or make changes to this bug.