Description of problem: If a new upgraded container is available, the administrator can type: $ oc deploy heketi --latest To deploy the latest Heketi container. The problem is that using a "Rolling" strategy will not deploy the new Heketi, since the old one still has access the to the database. Need to change the strategy to "Recreate" so that the previous container is shut down first before deploying the new one.
This is a blocker because we cannot upgrade Heketi or GlusterFS without the correct setting. This affects both the Heketi and GlusterFS templates.
I believe this is not expected behaviour. @Humble , could you please give a look.
(In reply to Neha from comment #8) > I believe this is not expected behaviour. @Humble , could you please give a > look. @Neha, the 'recreate' strategy should stop the pod and deploy the new one without issues. We have analysed the root cause and the solution for this issue which will be updated soon in this bugzilla.
Verified on build - heketi-client-3.0.0-2.el7rhgs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2017-0148.html