Bug 762319 (GLUSTER-587) - Update to 3.0.2 should be atomic
Summary: Update to 3.0.2 should be atomic
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-587
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-04 13:03 UTC by Raghavendra Bhat
Modified: 2010-02-07 22:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Raghavendra Bhat 2010-02-04 10:07:22 UTC 
If a user does not update with 3.0.2 and stops after 3.0.1, then even though the user has updated, user will still see the errors present in 3.0.1. This leads to a bad user experience. Ideally it should be an atomic update without the choice of stopping between 3.0.0 and 3.0.2.

The other problem is after 3.0.1 also user has to reboot and then again after 3.0.2 the user has to reboot. An atomic update from 3.0.0 to 3.0.2 should only require one reboot.

This is observed in  3.0.0
Comment 1 Raghavendra Bhat 2010-02-04 13:03:41 UTC 
When a user gives update for 3.0.0 it should be updated directly to 3.0.2. Otherwise if a user conducts some tests he may see the same problems present in 3.0.0.
Comment 2 Balamurugan Arumugam 2010-02-07 19:31:57 UTC 
Update policy is based on what the update has.  Its not possible to install all updates at once.
Note You need to log in before you can comment on or make changes to this bug.