Hi
We have our V4A working in one region, across multiple subscriptions. But when I try to add a new Repository that's in another region, the storageaccount is not visible. I doesn't show up. It only displays storage accounts from the same region as where my V4A appliance is deployed.
Something similar happens when I try to configure worker-VMs for another region. I select the region and the VM size, but at the networking step, there is no network shown from that reqion where I want my workers to end up in. I can only create a new network. In the region where my V4A appliance is located, I can select an existing VNET/SNET when configuring my workers.
Obviously, this sounds like a permissions (IAM) issue. The service-account that V4A uses most likely doesn't have permissions in that other region and it's subscription. But it has. The Contributer role and the Custom role (created via JSON) are also applied on the subsriptions in that other region. When re-newing the V4A service account it even dislays a list of all subscriptions where I have permissions. Still, resouces in that region are not found when configuring Repo's and Helper VMs.
What am I missing here ?
-
- Enthusiast
- Posts: 44
- Liked: 7 times
- Joined: May 04, 2016 1:39 pm
- Full Name: Richard Willkomm
- Contact:
-
- Product Manager
- Posts: 5857
- Liked: 1226 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Issues adding Repo+Helper in other regions
Hi Richard,
I would say a permission issue but it seems you ruled it out already. It's hard to tell from your initial info what could cause the issue as all sounds setup correctly. Did you by any means already contact our support for some better insight via logs and maybe an extra pair of eyes? If so, could you let us know the case ID and if not, could you open a case so we can figure it out?
I would say a permission issue but it seems you ruled it out already. It's hard to tell from your initial info what could cause the issue as all sounds setup correctly. Did you by any means already contact our support for some better insight via logs and maybe an extra pair of eyes? If so, could you let us know the case ID and if not, could you open a case so we can figure it out?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Enthusiast
- Posts: 44
- Liked: 7 times
- Joined: May 04, 2016 1:39 pm
- Full Name: Richard Willkomm
- Contact:
Re: Issues adding Repo+Helper in other regions
I didn't create a support case yet. I assumed there was something trivial I overlooked. I hate digging through logs when the solution is much more obvious, but I simply have tunnelvision.
But since I pretty much tried everything else, I guess a support-case is the only remaining step to take.
But since I pretty much tried everything else, I guess a support-case is the only remaining step to take.
-
- Enthusiast
- Posts: 44
- Liked: 7 times
- Joined: May 04, 2016 1:39 pm
- Full Name: Richard Willkomm
- Contact:
Re: Issues adding Repo+Helper in other regions
Case created at support : #05654751
-
- Product Manager
- Posts: 5857
- Liked: 1226 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Issues adding Repo+Helper in other regions
Thank you, will pass it on so it hopefully gets clarified fast.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
Who is online
Users browsing this forum: No registered users and 4 guests