6 Replies Latest reply on Aug 8, 2019 3:46 AM by bmcm

    Payload Properties Question vRO 7.3

    BillStreet00 Enthusiast

      I am finding that the payload property does not pull properties from my VM requests when the workflow is in the VMPSMasterWorkflow32.WaitingToBuild and VMPSMasterWorkflow32.MachineProvisioned states. Specifically I am trying to find the IP address of the VM being built and I always end up with a NULL value.  VMPSMasterWorkflow32.Requested and VMPSMasterWorkflow32.BuildingMachine states pull the payload with no issues. I have verified that the correct extensibility properties are included in the blueprint.

       

      Has anyone else seen this issue after upgrading to vRA and vRO to 7.3?

        • 1. Re: Payload Properties Question vRO 7.3
          parmarr Expert
          Knowledge ChampionVMware Employees

          Need more information :

          1. Any errors messages in the vRA logs.

          2. Are you facing this in a particular blueprint or all blueprints.

          See this blog for few clues on how to get the values:

          https://communities.vmware.com/message/2584446#2584446

          • 2. Re: Payload Properties Question vRO 7.3
            BillStreet00 Enthusiast

            The error logs just say a very bland error about performing a GET on a null value.

             

            The problem happens on every blueprint, even brand new ones, and it is consistant on the state.  The two I have found are VMPSMasterWorkflow32.MachineProvisioned and VMPSMasterWorkflow32.WaitingToBuild.

             

            Here is what I get on the vRO log panel:

             

            2017-09-08 07:48:31.232] [I] BlueprintName: ExtensibilityWF

            [2017-09-08 07:48:31.233] [I] ComponentId: w2k12prod

            [2017-09-08 07:48:31.234] [I] ComponentTypeId: Infrastructure.CatalogItem.Machine.Virtual.vSphere

            [2017-09-08 07:48:31.235] [I] EndpointId: af7a34a4-cdfa-43f3-893d-3490bab38d67

            [2017-09-08 07:48:31.236] [I] RequestId: dc3fcf08-a789-44d3-8c23-12322d765977

            [2017-09-08 07:48:31.237] [I] VirtualMachineEvent: null

            [2017-09-08 07:48:31.238] [I] WorkflowNextState: null

            [2017-09-08 07:48:31.239] [I] State: VMPSMasterWorkflow32.WaitingToBuild

            [2017-09-08 07:48:31.240] [I] Phase: POST

            [2017-09-08 07:48:31.241] [I] Event: null

            [2017-09-08 07:48:31.242] [I] ID: 7652246d-a064-46f2-a77d-ec39ed49d64c

            [2017-09-08 07:48:31.243] [I] Name: iteng0413

            [2017-09-08 07:48:31.244] [I] ExternalReference: null

            [2017-09-08 07:48:31.245] [I] Owner: XXXXXXXXXXXXXXXXXXX

            [2017-09-08 07:48:31.246] [I] Type: 0

            [2017-09-08 07:48:31.247] [I] Properties: null

            [2017-09-08 07:48:31.248] [E] Error in (Workflow:Custom email notifications / Get Properties (item3)#39) TypeError: Cannot call method "get" of null

            [2017-09-08 07:48:31.255] [E] Workflow execution stack:

            ***

            item: 'Custom email notifications/item3', state: 'failed', business state: 'null', exception: 'TypeError: Cannot call method "get" of null (Workflow:Custom email notifications / Get Properties (item3)#39)'

            workflow: 'Custom email notifications' (98d7f1d2-a487-4135-b855-0da4847caaf3)

            • 3. Re: Payload Properties Question vRO 7.3
              FMbanusi Novice

              Hi, 

              I'm having the same issue on MachineProvisioned states.. 

              Did you happen to figure this out? Did you have to use a different state to pull your values?

              • 4. Re: Payload Properties Question vRO 7.3
                andrewrNZ Lurker

                I also am missing the payload properties on VMPSMasterWorkflow32.MachineProvisioned state. I have triple-checked the custom property Extensibility.Lifecycle.Properties.VMPSMasterWorkflow32.MachineProvisioned in the blueprint, but still no payload.

                • 5. Re: Payload Properties Question vRO 7.3
                  Jeremy_VE Enthusiast

                  Just in case anyone has a similar issue, be sure to check that the workflow which is being called by vRA only has a single input, which is the payload (properties) input.  Any other inputs and the value of the payload will be null.

                  1 person found this helpful
                  • 6. Re: Payload Properties Question vRO 7.3
                    bmcm Lurker

                    Great, thanks for this!!!! I never would have spotted that was the reason. This fixed my issue.