[On-premises gateway] Migration doesn't show the correct cluster.

[RubenJonkers]

Hi all,

I am trying to migrate my on-premises gateway from one server to another. I want to do this using the migration option. However, after login I can't see the right cluster, only a cluster I made before on the new server as a test. 

The problem is, I don't want to change all my reports to use the new cluster, that'll be too much work at this point. Is there a way to make the old cluster show up on the new server?

I am using the latest gatway version(June 2018) and I am logged in with the account that manages the old cluster.

If you need more information I am happy to provide. 

Thanks,

Ruben

[Anonymous]

@RubenJonkers,

I am unable to reproduce your issue. When you sign in the old gateway, do you see correct configured gateway? In my scenario, when I sign in new gateway using same account which is used in old gateway, and enter recovery key, the gateway is migrated successfully.



Regards,
Lydia

[RubenJonkers]

Hi Lydia,

You gave me an idea. I might have been using the wrong login address but then the problem could be that the original address does not exist anymore. I will try this and get back to you.

Regards,

Ruben

[RubenJonkers]

The issue seems to be that you can only migrate the gateway using the account that originally created it. This account is not available anymore, sadly. 

We decided to create a new gateway and we'll have to change the reports. 

This time we're creating the gateway under a generic email address that wouldn't need to be deleted. 

@Anonymous Thanks for the help!

[Anonymous · Accepted solution]

@RubenJonkers,

Yes. We can only migrate the gateway using the account that originally created it.

Regards,
Lydia

[runecfoyn]

What about taking ownership of a gateway, which is listed as one of the options? I find that this is not possible if the population of the cluster dropdown depends on prior ownership !? Moreover, this part of the gateway universe seems to be undocumented (and possibly unsupported) !?