Bug 1634837 - Glusterfs-registry pods also get removed while only glusterfs is being uninstalled
Summary: Glusterfs-registry pods also get removed while only glusterfs is being uninst...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: CNS-deployment
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Michael Adam
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On: 1634835
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-01 18:54 UTC by Neha Berry
Modified: 2019-12-02 21:55 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1634835
Environment:
Last Closed: 2019-04-15 06:57:21 UTC
Embargoed:

Attachments (Terms of Use)

Comment 3 Yaniv Kaul 2019-04-01 06:49:44 UTC 
It's a clone of a bug that was fixed in an errata already. What's the status of this BZ?
Comment 4 Neha Berry 2019-04-15 06:03:07 UTC 
(In reply to Yaniv Kaul from comment #3)
> It's a clone of a bug that was fixed in an errata already. What's the status
> of this BZ?

Hi Yaniv,

The cloned bug in OCP was verified and closed - https://bugzilla.redhat.com/show_bug.cgi?id=1634835#c8

But, since the status of this bug in OCS component was not yet changed to ON_QA, we couldn't move this bug to Verified state. 

Maybe I can put a needinfo on michael & Jose for this bugs's status.

@Jose , Michael - Please confirm the correct status of this bug as the cloned OCP bug is already fixed and verified.

Thanks,
Neha
Comment 5 Yaniv Kaul 2019-04-15 06:57:21 UTC 
(In reply to Neha Berry from comment #4)
> (In reply to Yaniv Kaul from comment #3)
> > It's a clone of a bug that was fixed in an errata already. What's the status
> > of this BZ?
> 
> Hi Yaniv,
> 
> The cloned bug in OCP was verified and closed -
> https://bugzilla.redhat.com/show_bug.cgi?id=1634835#c8
> 
> But, since the status of this bug in OCS component was not yet changed to
> ON_QA, we couldn't move this bug to Verified state. 

We can just close this. The whole cloning process is wrong.
Note You need to log in before you can comment on or make changes to this bug.