Hi Friends,
I have pre-patch fixlet, baseline for patches, reboot fixlet and post-patch fixlet. All the fixlets have their own success criteria. We are manually doing one by one execution.
Now we want to define this workflow in single template or single baseline or single task which need to run in the above sequence order after each result is successful and we want the final output which is success or failed. Can please help us how to achieve this.
you’re basically half way there.
Add your fixlets to the baseline in the order your want. For any fixlets that should not make a baseline relevant for a computer, you can unselect “Baseline will be relevant on applicable computers where this component is relevant”.
For the fixlets you mention, I typically like to create ~3 groups in the baseline. A pre-patch section, a section with patches, and then a post patching group just to make it easier to review and manage.
I don’t know if you do Windows patching, but here is a helpful video https://www.youtube.com/watch?v=M882pAq4tOw (there are also some webinars posted to this forum, but I found this quickly).
Hi Derrick,
Good Morning.
Thank you for your ideas and suggestions.
I will take note of your suggestion. As I mentioned earlier,
I have few pre-patch fixlet that has its own success criteria if the outfile file /report/success_prepatch.txt exists then the fixlet is success else fail.
And same applicable to post it has /report/success_postpatch.txt
Also, I have reboot fixlet which has success criteria in which all lines of commands are executed means it will success else fail.
Now I have query when I put all these fixlet in the baseline, let’s assume,
I have created a workflow baseline as below,
Let’s say if I created like the above, how the workflow will work. Is it based on the order I created. If yes, then how it will see whether the step 1 is success or fail.
If step 1 fails due to some reason, will it continue to next steps, or the entire flow will stop at step1 itself.
Another thing, for step 3 there is reboot fixlet. If step 3 executed then how will the step 4 will run, will the step 4 will wait for the server to come back online.
I have big confusions on how to define the success criteria for each task inside the baseline.
Sorry for the big para.
Thanks, your help will be really appreciable.
Yes, top to bottom.
Yes!
Yes, the machine will move on to the next stage after rebooting.
If your deployment depends on success criteria, I would suggest server automation.
You could have controlled deployment based on specific criteria (by defining detection of success/failure) relevance within your fixlets, if your baseline was for the execution of tasks other than patching, but since patches will be part of your baseline deployment, you can’t define success criteria for each one of them, making this an unscalable solution.
Hi Khurava,
Thank you so much.
I think we will need to see the success criteria of each fixlet/baseline in order to proceed to next steps inside the same baseline. So that we can have a clear visibility of which was failed.
From what you have mentioned I understand is regardless of success or failure the complete baseline will run from top to bottom. Just want clarification on reboot portion only, so when we execute reboot (step3), the step 4 will wait until the server comes online or the step 4 have any time limit to skip/fail. Thanks.
Yes, it will wait!
see below post from @JasonWalker for better clarity on reboot & wait.
Hi Khurava,
Thanks for the confirmation.
Just add to this, I will attach my complete baseline here before going for testing. kindly advice if anything need changes or modification.
Looks good to me, but before going for mass roll out, please do test it on your test devices 1st.
my bad ! I didn’t see the significance or your script, but I just realized that your success conditions are off.
The parameter must be hard coded because Relevance is unable to decode it outside of actionscript.
It needs to be as follows:
not exists file "/reports/success_prepatch.txt"
Likewise, for your post script success criteria.
Hi Khurava,
GM. Thank you for your support.
Sure will take note of the above and will try on one server first. Thanks.
Hi khurava,
sorry bit confused about the relevance.
I understand as we need to hard core the value instead of parameter but why we need to put not exists file instead of exists file as I want to check if the file exists then success else fail.
I changed as per your advice but the result status is showing fixed instead of success.
And the main relevance is as below,
My main agenda is I want to check the file exists and then it is success if not fail as a result not fixed.
In short Success = Fixed!
refer to below link for action statues:
Action Status Messages | BigFix Developer
You have already answered your question; that is exactly what we have done when we state not exists… and evaluate as FALSE.
Action Success Criteria states: Consider this action successful when …the following relevance clause evaluates to FALSE.
If we say exist file…, it will return True rather than False, indicating that your success criteria is failing, whereas not exists… will return False rather than True, indicating that the file exists.
Hi Khurava,
Thank you for the explanation.
Will try it on the test machine and come back if any issue. Thanks.