The error 480 - Gluster volume replica count is not supported, seems to indicate that vdsm has not read the updated conf.
Have you made the change in all the nodes (hypervisor)?

[+users]

On 11/26/2015 07:13 AM, Punit Dambiwal wrote:

Hi Sahina,

Still the same error "480"

Engine Logs :- http://fpaste.org/294595/

-----------

2015-11-06 15:01:51,042 ERROR [org.ovirt.engine.core.bll.storage.BaseFsStorageHelper] (DefaultQuartzScheduler_Worker-78) [40bde6e1] The connection with details 'gluster1.3linux.com:/ssd' failed because of error code '480' and error message is: 480

2015-11-06 15:01:51,103 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-78) [40bde6e1] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: The error message for connection gluster.3linux.com:/sata returned by VDSM was: 480

2015-11-06 15:01:51,104 ERROR [org.ovirt.engine.core.bll.storage.BaseFsStorageHelper] (DefaultQuartzScheduler_Worker-78) [40bde6e1] The connection with details 'gluster.3linux.com:/sata' failed because of error code '480' and error message is: 480

2015-11-06 15:01:51,104 INFO  [org.ovirt.engine.core.bll.storage.ConnectHostToStoragePoolServersCommand] (DefaultQuartzScheduler_Worker-78) [40bde6e1] Host 'compute6' storage connection was failed

----------

Thanks,

Punit

On Wed, Nov 25, 2015 at 9:30 PM, Sahina Bose <sabose@redhat.com> wrote:

Hi Punit,

Based on comment 2 in https://bugzilla.redhat.com/show_bug.cgi?id=1238093, you should be able to edit /etc/vdsm/vdsm.conf

allowed_replica_counts=2,3

and restart vdsm.

Could you attach error that you continue to face (post above step?)

On 11/25/2015 08:02 AM, Punit Dambiwal wrote:

Hi Sahina,

Yes...i have restarted the vdsm and even rebooted the whole machine but not work..

On Tue, Nov 24, 2015 at 10:19 PM, Sahina Bose <sabose@redhat.com> wrote:

Have you restarted vdsm?

On 11/24/2015 07:38 AM, Punit Dambiwal wrote:

Hi Sahina,

Either after make the changes in the vdsm.conf,still not able to connect to the replica=2 storage..

Thanks,

Punit

On Mon, Nov 23, 2015 at 4:15 PM, Punit Dambiwal <hypunit@gmail.com> wrote:

Hi Sahina,

Thanks for the update...would you mind to let me know the correct syntax to add the line in the vdsm.conf ??

Thanks,

Punit

On Mon, Nov 23, 2015 at 3:48 PM, Sahina Bose <sabose@redhat.com> wrote:

You can change the allowed_replica_count to 2 in vdsm.conf - though this is not recommended in production. Supported replica count is 3.

thanks
sahina

On 11/23/2015 07:58 AM, Punit Dambiwal wrote:

Hi Sahina,

Is there any workaround to solve this issue ?

Thanks,

Punit

On Wed, Nov 11, 2015 at 9:36 AM, Sahina Bose <sabose@redhat.com> wrote:

Hi,

Thanks for your email. I will be back on 16th Nov and will get back to you then.

thanks
sahina