possible bug in powershell command get-vboproxy

[AlexL]

This is inexplicable behaviour for me.
Below is the result for a server with only 1 organization. I see this on multiple vb365 servers, all version 8.4.

Get-VBOOrganization | Get-VBOProxy | sort id | select id,type,proxyroles

Code: Select all

Id                                     Type                                             ProxyRoles
--                                     ----                                             ----------
1b3af45c-1e7d-4ebd-8238-f4d9e61dbd2e Domain Scheduler, Orchestrator, Processor, ApplianceProcessor
78b5df61-1f5c-4819-8800-0b1b5b3a67bb Domain                                              Processor
b89155d1-66a2-401d-b90f-4a39767883ed Domain                                              Processor

Get-VBOProxy | sort id | select id,type,proxyroles

Code: Select all

Id                                     Type                                             ProxyRoles
--                                     ----                                             ----------
1b3af45c-1e7d-4ebd-8238-f4d9e61dbd2e Domain Scheduler, Orchestrator, Processor, ApplianceProcessor
78b5df61-1f5c-4819-8800-0b1b5b3a67bb Domain                                              Processor
a94799f6-0eae-4b58-8f54-21e2d72e4ccb Domain                                              Processor
b89155d1-66a2-401d-b90f-4a39767883ed Domain                                              Processor
bd081301-a78a-425c-bdf8-4a1ab093e7c2  Local Scheduler, Orchestrator, Processor, ApplianceProcessor

The 4 non local proxies are part of a proxy pool, could that possibly influence the outcome?

Is this a bug?

[Polina]

Hi Alex,

Proxies within a pool have different roles which are exposed here. Those roles are changing dynamically and cannot be managed or impacted. This information is exposed mostly to help our engineering teams with troubleshooting should it be needed.

[AlexL]

Perhaps I didn’t clearly state my issue.
This is output from the same server.

You would expect the result should be the same for both commands.

The roles are just extra informational.

This is part of a report we are using, I am 100% certain this gave the same result when we were using either v8.3 or before we configured a proxy pool.