Could see a similar kind of post @ http://communities.bmc.com/communities/message/152911
Could you elaborate how the analysis is done and what are the different states in this.
i have seen three states
Has anyone got any clue on this please....
I think this is covered in the bladelogic user guide.
I am sorry to ask this again, we are using 126.96.36.199 BL version and i could not find in user guide.
Tried looking into the BL help index, but could not find.
Can you please tell me why "Not Analysed" status comes in the patch analysis job.
1 of 1 people found this helpful
The status NOT ANALYSED for a server means that the analysis was not executed for that server, this can happen for a number of reasons like:-
- the target/server is not relevant for the Catalog you are doing analysis against, e.g. on a Solaris Catalog you have a redhat box in the list of targets for analysis.
- there are problems with the server, like not reachable, agent not licensed etc.
You should be able to know the reason for which it was not analyzed in the log under the node for that server/target.
But the thing is if the server is not licensed or not responding the analysis gets failed for me.
There was a requirment for me to deploy couple patches for few servers(These are in live status)
so after patch analysis using the Q numbers for most of the sever it says Not Analysed.
Once the servers are live it should show me as installed or missing, but i am not sure why this is happening....
So we did couple of severity patches manually.
Please help me if there is any particular reason from BL application.
What version of Bladelogic is this?
How did you setup your analysis to run? And how did you get this qnumber list? What was telling you that the patches you applied manually were applicable for the servers?
Presently we are using BL 188.8.131.52 version.
I have copied all the QNumbers in a text file and mapped them to the patch analysis job.
Added the target servers and then run the job.
There was a client requirement of few patches on couple of servers, for which the status was not analysed so we did them manually for now.