Rebooted two of the rhgs node, now dont see heketi.db file under heketidb volume due to that heketi container is crashing. docker logs -f 87fcbdb9da33 Heketi 2.0.2 [heketi] INFO 2016/07/13 06:43:13 Loaded kubernetes executor [heketi] ERROR 2016/07/13 06:43:13 /src/github.com/heketi/heketi/apps/glusterfs/app.go:149: write /var/lib/heketi/heketi.db: read-only file system ERROR: Unable to start application heketi container status : CrashLoopBackOff
Humble, could you please investigate why a volume would go Read Only?
(In reply to Luis Pabón from comment #3) > Humble, could you please investigate why a volume would go Read Only? Luis, below error message clearly says 'The FS is READONLY' which is different from 'No Such File or Directory' reported here in the bugzilla. Can you confirm in this error scenario, the path exist, but its READONLY causing this issue? [heketi] INFO 2016/07/13 06:43:13 Loaded kubernetes executor [heketi] ERROR 2016/07/13 06:43:13 /src/github.com/heketi/heketi/apps/glusterfs/app.go:149: write /var/lib/heketi/heketi.db: read-only file system ERROR: Unable to start application
@Neha, once again FS goes readonly in this scenario is expected as mentioned here https://bugzilla.redhat.com/show_bug.cgi?id=1355689. I dont know why you say the DB file *does not* exist eventhough there is a clear error message says FS is READONLY. I am confused with the bug report and the error message captured here in this bz as it does not match.
Regarding read only volume , it might be because few of the brick process are not up and not because of data loss.
closing this bug as heketi issue is being tracked in BZ 1355689. For data loss I will create a new BZ to avoid confusion.