So we have a Autosys job (let's say JobA) that's stuck in a loop due to the condition NotRunning (jobA). So, the job continuously restarting itself, moving from STARTING state to RUNNING state, completing either in SU or FA & restarting itself.
To support the look-back feature, you must add an additional operand to the condition statement. You can apply the look-back feature to job status, cross-instance or external dependency job status, and exit code condition types only. You cannot apply it to the global variable condition type.
When i am studying the look back condition, its taking the last instance run of the condition or predecessor job.Just want to know when to use this look back co
Hi All,I have a request from my client to enable Virtual Machine condition counter (in alarms) >>> VM Max Total Disk Latency (ms).VMware states by default the v
Hi there, FYI, I am new to autosys. I am trying to use success (job_a, 01.00) condition, which I believe according to docs check if job_a is successsfull within the last hour or not right? But in autosys workload automation. It is always showing condtion not satisfied. May I know why? Does it depends on any other things. I tested it by manually changing the status of job_a to Success. But in ...
i want to use if else statement in OGNL scenario: i have 3 input parameters .i have to run an action for 3rd input with help of input 1 and input 2. i have to pass input 1 or input 2 to the action item which is added in input 3. kindly help me with ONGL expression to get the desired output.
Update- Just removed and reinstalled everything, using a 4.1.1 version, (slightly older than what failed earlier) and it still halts at 10percent in the NAPP deployment, with the same error: Helm install chart operation failed. I verified routing between the NSX manager, auto-deploy VM, the Mgmt, FrontEnd, and WorkLoad networks, and between all those networks and the Internet.
esxcli system module set --enabled=true --module=usb Any ideas on if it's possible to get this vmhba32 dead path condition fixed without rebooting host or re-seating the SD cards? For some reason this is plaguing a lot of our host and causing issues since we need to get maintenance windows to migrate VM's off to reboot the host.
