gbeke
Enthusiast
Enthusiast

ABX action not running

Jump to solution

Hi,

I want to use vRA 8.4 (On-prem) to create self-service for namespace creation. Namespace creation works natively from vRA, but i need to set the storage policy and add permissions. So I then decided to try to use powershell to set this to properties after the namespace has been created. I followed this blog to create the action. I created a subscription that should run the action after the namespace is created.

The subscription was created using the event "Kubernetes namespace post provision" and I've also tried using "Deployment completed". The problem is that the action never runs. In Events I see an event called "Kubernetes supervisor namespace post provision" and shows this under notified subscriptions. 

gbeke_0-1629956639946.png

I've looked through the documentation about extensibility and subscriptions and done a Google search but I cannot figure out why the action does not run. So I'm hoping that someone has suggestions to what might cause the action not to run. If more information is needed, let me know. I've worked a bit with vRA 7 and but are to vRA 8. Thanks in advance.

0 Kudos
1 Solution

Accepted Solutions
bdamian
Expert
Expert

Create an simple Action with just a "Write-Host hello" instruction, then create subscriptions for all the event types you think should work.

After the execution of the task, check the "Action Runs" section for any execution of your Action. If there is one, you can check the details and find out what subscription fired the Action.

bdamian_1-1629977707779.png

 


---
Damián Bacalov
vExpert 2017-2018-2019-2020-2021-2022
https://www.linkedin.com/in/damianbacalov/
twitter @bdamian

View solution in original post

0 Kudos
2 Replies
bdamian
Expert
Expert

Create an simple Action with just a "Write-Host hello" instruction, then create subscriptions for all the event types you think should work.

After the execution of the task, check the "Action Runs" section for any execution of your Action. If there is one, you can check the details and find out what subscription fired the Action.

bdamian_1-1629977707779.png

 


---
Damián Bacalov
vExpert 2017-2018-2019-2020-2021-2022
https://www.linkedin.com/in/damianbacalov/
twitter @bdamian
0 Kudos
gbeke
Enthusiast
Enthusiast

Thanks for the suggestion. The event type deployment.request.post works but not kubernetes.namespace.provision.post. I also found out that the subscription I created using deployment.request.post would never run due to a typo in the filter I had defined. Now I just have to figure out why the action fails. Thanks for pointing me in the right direction!

0 Kudos