Posts made by Al.cmb

Thanks for all your answers!!

I know that my configuration is not standard but i am quite sure that was working for the deploy part:

My Fog Server is a VM that has not enough space to store images.
Only the Synology Nodes stores the images, snappins and tftp files.
I know that Synology Node cannot perform replication so i have made the replication by CloudShare Sync.

The workaround i have applied to deploy or capture my images since the problem appeared is to disable the storage node of the remote site when i make a deploy or capture.

I have tried to capture an image in this way and deploy on the other site ans it works.
Only the location is not working.

How can i debug that?
Log files to check or anything else?

Sorry that was for tests. I have corrected that but still the same issue:

The 2 cases: Deploy and Capture.
This is my config. As you can see i have set UN002-CDF as location (that contains UN-Syno2) and the working node is wrong (UN-Syno1 the other location)

Server

• FOG Version: 1.4.4
• OS: Ubuntu 16.04.2 LTS

Client

• Service Version: 0.11.12
• OS: All

Description

Location plugin not working after update to 1.4.4

After the upgrade the location plugin does not work as expected.
It does not take care of the site and always take the 1st node available instead of the location setted one.
I have remove and reinstalled the plugin related to this topic (https://forums.fogproject.org/topic/10364/issues-after-upgrading-from-1-4-3-to-1-4-4/6) and executed the command but no luck. Still taking the 1st node.

i have 2 storage nodes in the same storage group, and each one on different location.
What i’am doing wrong?

Thanks