Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1577230 - Cannot see other bricks after upgrade
Summary: Cannot see other bricks after upgrade
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.13
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-11 14:00 UTC by David Schilling
Modified: 2018-06-20 18:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)
glusterd.log (6.71 KB, text/plain)
2018-05-11 14:00 UTC, David Schilling
no flags Details
glustershd.log (525.04 KB, text/plain)
2018-05-11 14:02 UTC, David Schilling
no flags Details

Description David Schilling 2018-05-11 14:00:58 UTC
Created attachment 1434923 [details]
glusterd.log

Description of problem:

I am running glusterfs on three different vms. They are all running on Ubuntu 17.04.
The used version of glusterd is 3.11.3.

Today i wanted to upgrade the three servers starting with one to the new ubuntu lts version 18.04.

After the update when i run `gluster volume status` i can only see the bricks of the current vm and it is offline. 
`gluster peer status` returns `Peer Rejected (Connected)` for all other peers.

The new version of glusterfs which was installed with the ubuntu update is 3.13.2.


I added some logs in the attachment.

Other things i noticed after upgrading.
I now have two gluster folders in var/lib: /var/lib/glusterd_old and /var/lib/glusterd
Also i have two really similar looking systemd services glusterd.service and glusterfs-server.service.

Running `gluster volume status churchtools_de`gives the following output:

```
Status of volume: churchtools_de
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick glusterfs101.ct-srv.de:/gluster-stora
ge/churchtools.de                           N/A       N/A        N       N/A

Task Status of Volume churchtools_de
------------------------------------------------------------------------------
There are no active volume tasks

root@glusterfs101:~# gluster volume status
Status of volume: churchtools_de
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick glusterfs101.ct-srv.de:/gluster-stora
ge/churchtools.de                           N/A       N/A        N       N/A

Task Status of Volume churchtools_de
------------------------------------------------------------------------------
There are no active volume tasks

Volume churchtools_scripts is not started

Status of volume: churchtools_sites
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick glusterfs101.ct-srv.de:/gluster-stora
ge/churchtools_sites                        N/A       N/A        N       N/A

Task Status of Volume churchtools_sites
------------------------------------------------------------------------------
There are no active volume tasks

Status of volume: user_homes
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick glusterfs101.ct-srv.de:/gluster-stora
ge/user_homes                               N/A       N/A        N       N/A

Task Status of Volume user_homes
------------------------------------------------------------------------------
There are no active volume tasks
```

Comment 1 David Schilling 2018-05-11 14:02:00 UTC
Created attachment 1434924 [details]
glustershd.log

Comment 2 Shyamsundar 2018-06-20 18:28:15 UTC
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.

Comment 3 Shyamsundar 2018-06-20 18:28:16 UTC
This bug reported is against a version of Gluster that is no longer maintained
(or has been EOL'd). See https://www.gluster.org/release-schedule/ for the
versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline
gluster repository, request that it be reopened and the Version field be marked
appropriately.


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