I have tested an upgrade from engine 3.3.3 to 3.3.4 under centos 6. It
seems that the vdsm nodes are now showing as non-operational and the only
way I have been able to cure this was to:
- Upgrade the vdsm version on a node to 4.13.3-4
- install vdsm-gluster
- start glusterd service
We are only c
On 03/19/2014 05:19 PM, Gary Lloyd wrote:
I have tested an upgrade from engine 3.3.3 to 3.3.4 under centos 6. It
seems that the vdsm nodes are now showing as non-operational and the
only way I have been able to cure this was to:
- Upgrade the vdsm version on a node to 4.13.3-4
- install vdsm-glu
This issue aside, the new point release should still support
older vdsm versions.
I haven't done the upgrade in my dev environment yet so I'm
glad for the report.
Maybe worth filing a BZ (after some more investigation)?
Am 19.03.2014 18:15, schrieb René Koch:
> Did you check "Enable Gluster Serv
I must have checked that box at some point and forgot about it. It is
working fine now thanks.
*Gary Lloyd*
--
IT Services
Keele University
---
On 19 March 2014 17:15, René Koch wrote:
> On 03/19/2014 05:19 PM, Gary Lloyd wrote:
>
4 matches
Mail list logo