[Bugs] [Bug 1620580] Deleted a volume and created a new volume with similar but not the same name. The kubernetes pod still keeps on running and doesn 't crash. Still possible to write to gluster mount

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1620580

Amar Tumballi <atumball at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|unspecified                 |high
                 CC|                            |atumball at redhat.com
          Component|unclassified                |core
           Assignee|bugs at gluster.org            |bgoyal at redhat.com
           Severity|urgent                      |high



--- Comment #1 from Amar Tumballi <atumball at redhat.com> ---
Thanks for the bug report! Interesting observation, and use case. We generally
don't recommend re-use of the bricks.

The original mount is interestingly still active, mainly because of 'brick'
mapping. A client protocol connects to brick which is expected to be
'hostname:/path' combination, and if a brick path is never reused, it would
always work as expected.

We need to get ID based authentication for the handshakes.


Reducing the severity, as recommended usecase, is not to re-use the same
bricks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.