Bug 1428103 - Generate UUID on installation
Summary: Generate UUID on installation
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Vijay Bellur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-01 19:07 UTC by Vijay Bellur
Modified: 2019-08-02 06:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-02 06:49:26 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Vijay Bellur 2017-03-01 19:07:25 UTC
Generate UUID on installation

Summary:
- Generates UUID on installation to restore AntFarm flow to same as
  v3.3.1
- Fixed broken glusterfsd init script install (it doesn't actually exist
  as far as I can tell)

Test Plan: Tested on dev1148.prn2

Reviewers: cjh, jackl

Change-Id: I2f382c03f5fab2be01695cb020209939d4f74a9b
Signed-off-by: Kevin Vigor <kvigor>
Reviewed-on: https://review.gluster.org/16648
CentOS-regression: Gluster Build System <jenkins.org>
NetBSD-regression: NetBSD Build System <jenkins.org>
Reviewed-by: Shreyas Siravara <sshreyas>
Smoke: Gluster Build System <jenkins.org>

Comment 1 Worker Ant 2017-03-01 20:55:24 UTC
REVIEW: https://review.gluster.org/16819 (Generate UUID on installation) posted (#1) for review on master by Vijay Bellur (vbellur)

Comment 2 Amar Tumballi 2018-10-24 10:05:33 UTC
Looks like these should be handled by scripts outside of the code! I see the patch got abandon'd and no action plan on this. Should we pursue this further?

Comment 3 Vijay Bellur 2018-10-30 17:56:06 UTC
Left a comment for Shreyas on gerrit. We can act based on his response. Thanks!

Comment 4 Yaniv Kaul 2019-07-08 07:55:53 UTC
Status?

Comment 5 Vijay Bellur 2019-08-02 06:49:26 UTC
Haven't heard back from Shreyas. Closing this bug.


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