Hello,
I'm seeing a strange result when trying to add a subscription to a Local Published Content Library, Here is a description of the situation:
- Local Published Content Library (I'll call this, CL "A")
- Subscribed Content Library (I'll call this CL "B")
I'm trying to subscribe to all Content that is in CL "A" -> CL "B". I can create CL "B" with PowerCLI, provide the CL "A" Subscription URL and sync OVA's perfectly fine.
When I try to add a subscription to CL "A" (Menu > Content Libraries > CL "A" > Actions > Edit Settings > New Subscription), CL "B" is never discovered as a subscribing Content Library. Without being able to set up this subscription, I cannot set CL "B" to get CL "A" VM Templates.
Here is the command used to create CL "B":
New-ContentLibrary -Name <CL_B_NAME> -SubscriptionURL $subscriptionURL -Password <CL_A_PASSWORD> -DownloadContentOnDemand:$true -Datastore <DATASTORE>
If I use the UI to create CL "B", it is discovered and shown as expected when trying to add a Subscription. It's only when I create the CL with PowerCLI that it isn't found. Based on the fact that it's syncing OVA templates I know the initial subscription is working, but the bi-directional relationship doesn't seem to be working properly.
My only theory is that because this is a demo environment, both Content Libraries are on the same vCenter host, which I understand is not reflective of typical usage of this feature.
Additionally, I'm not seeing anything in PowerCLI or API documentation that I can use to script this out. Is adding a subscription to an existing Published Content Library supported?
UPDATE:
Since it doesn't seem to be possible with PowerCLI (at least as far as I can tell), I just tried to record my browser actions with a browser-based scripting tool. This was successful in that it sets up the Subscribed Content Library in the UI, but vSphere still does not discover this Subscribed Library as expected.
