I have a blueprint with that includes a software component. The initial provisioning and software component actions (install and configure) fire as expected when first deployed.
When selecting reprovision, the vm deploys without issue but the software component actions (install and configure) never fire.
Similarly, when selecting Destroy, the uninstall action also fails to fire but the VM is powered off and deleted.
Is this the expected behavior or need I configure something else to trigger the software component actions?
TIA!
I opened SR and they confirmed, that "Uninstall" part works during VM's destruction/deletion (and it's good!). But (and very big "but") - machine should be powered on. And no chance to catch any errors/issues in SA (cause all logs inside machine), so - if machine off, SA failed but you'll never know about it (in vra logs)... If machine powered off, vra just ignores uninstall step without any warnings/notification/anything. I decide to convert SA into vRO workflow, this is the only way to have control over VM lifecycle.
It does not work in Reprovision action. Tested in 7.2 and 7.3
I haven't tried the reprovision with software components, but the destroy should definitely (and does in my 7.3 environment) run the uninstall phase. Are you sure that on your template(s) you have the 7.3 agents installed?
Yes, 7.3 agents on the client. In your case, did you need to configure anything additional for it to fire or does it simply run the uninstall script?
Nope, it should just run it.
Can you share the lifecycle stage for uninstall? Is it possible it is running it but it's not producing the result you intended?
I have the same issue with "reprovision" in 7.2 - "Uninstall" part of software component doesn't fire during re-provision. If I do manual Delete/Destroy action - it works fine.
I'm pretty sure the Uninstall phase isn't supposed to run during a reprovision.
Hmm, interesting and weird decision... What if I have software component to register/connect this machine to my 3-rd party system, I would like to have a way to properly "de-register" it and add again as a part of re-provisioning process (for example, I generate SSL cert in machine and use it to establish trust with another system). What's happened with predictable application's behavior - I mean "reprovision" = destroy + deploy. Why does agent work fine in "Destroy" and "Deploy" but not when I call them in "Reprovision"? Could you please explain?
I will have to test to know for sure. I'll report back with the behavior I see.
After testing, neither the uninstall life cycle nor the install life cycle are performed for software components upon reprovisioning. Seems like this is a big feature gap to me.
Also note that if you have an archive period, the VM will shut down when expired, and then won't be able to run uninstall tasks for the destruction phase, because the VM is shut down.
I opened SR and they confirmed, that "Uninstall" part works during VM's destruction/deletion (and it's good!). But (and very big "but") - machine should be powered on. And no chance to catch any errors/issues in SA (cause all logs inside machine), so - if machine off, SA failed but you'll never know about it (in vra logs)... If machine powered off, vra just ignores uninstall step without any warnings/notification/anything. I decide to convert SA into vRO workflow, this is the only way to have control over VM lifecycle.
It does not work in Reprovision action. Tested in 7.2 and 7.3