Look at the date the server object was created ?
Thanks Bill for response. Date was old date and showing other new servers. But my point is here to identify the list of servers from the group when user imported for past time frame.
‘date was old date and showing other new servers’ -> means what ?
What date were you looking at? On what objects? what does ‘old date’ mean ? old date on what?. what does ‘showing other new servers’ mean ? what was showing other new servers ?
The date_created property on the server object is when someone added the server to bsa. is that what you are looking for ?
My question is to know the target servers list which were there in one particular "static group" when anyone was imported to that static group. There were X number of hosts earlier but currently it was modified and showing other data.
It is for server objects. So here I would like to know if there is any possibility to capture the servers lists which were there in group for old time frame.
No, why ?
The actual issue here is:
A user's Deploy job is defined with a Server Group (with just 2 servers in it) in Targets. This deploy job requires a reboot after successful completion of the software deployment. When user executed the job, it ran against 850+ servers. Now the user claims that He just executed the job as it is but, Bladelogic picked up this incorrect servers' list and executed against them.
Now, we are trying to identify -
1. whether this job was executed against the same group but, it had those 850+ servers in it at the time of execution. The Server Group used in the job definition, has some ServerGroup.Write in Audit Trial just 5 mins prior to the job execution. User states that he imported only 4 servers then, removed 2 of them. We need to identify the actual servers count imported here?
2. He kicked-off the job by Execute Against option and selected those servers or a different group. But, when we right click on the specific Job Run/Result and Show Job -> it shows only the server group defined in the job under Targets tab. This seems to be a bug where the Show Job option from a Job Run/Result doesn't show the actual targets selected during the job execution.
In either case, though it completely sounds like a human error, we will have to show them the evidences that it is not a Bladelogic's fault. We have gone through a number of tables in core Database but, left with no clue. Also, I was wondering that JOB_RESULT_BLGROUP table is empty which could be a reason for Execute Against not to show the selected groups.
Anyway, it may become a question of Bladelogic's effective Audit System?
Also, we should have some additional audit trial like ServerGroup.Execute or ServerGroup.Deploy if the job is executed against a Server Group. Just like we have it for Server as Server.Deploy, Server.ExecuteNSHScript, etc..
2 of 2 people found this helpful
1 - there may be something in the appserver log for this - do you still have those from the time of the job run? what bsa version is this ?
2 - if the target of the job is a server group, why would you expect 'show job' to list the resolved targets? that's a rfe, not a defect.
Thanks for the response, Bill.
1. We are trying to identify analyze from AppServer logs too. BSA Version is 8.3.03
2. Resolved targets will anyway shown up in the job results. But, the defect/RFE I am referring here is:
If a user executes the job against /Servers/Test/ABC when the Job is defined with /Servers/Test/XYZ. The job run is just showing XYZ rather than ABC where the job was actually executed. This is bit challenging in Audit.
We have figured out the Server Group selected during the job execution from the AppServer logs as a below entry logged there.
[12 Apr 2016 08:06:55,394] [Client-Connections-Thread-101]
[INFO] [USER_ID@XXXXX.COM:ROLE_NAME:IP.ADD.RE.SS] [Client]
Executing <Execute Against> Action against group targets:
Servers/WorkAreas/TARGET_GROUP for job: /WorkAreas/User's/Job/Folder/Job_Name
However, the Show Job option on any Job Run/Result should be showing the actual Targets or Server Group selected in the execution while it shows the respective Job Version, parameters, other modifications correctly. It is bit misleading and If the AppServer log entries are truncated, we would be clueless.
when you use 'execute against' the job is not modified. so i'm assuming 'show job' shows whatever version of the job the run is associated w/ and that is the confusing since the targets are different ? if so, that should certainly be handled better where it shows the settings used for that run.
We have AppServers configured as CONFIG and JOB servers separately. As it is job execution, we were searching in the JOB server logs where the job was executed. And, we got the above clue from one of the CONFIG servers' logs which is another crazy factor here.
Either the Show Job should show the actual targets or the job run log should have an entry as in the AppServer log.
... started executing the job Job_Name against group targets: Servers/WorkAreas/TARGET_GROUP
why is it a ‘crazy factor’ that when a job was executed, by the gui, it was logged in the config server ? that is what handles the user interaction.
I understand the UI level task logging and expected this comment from you. It is crazy from our side while debating with user groups, not the Product logging indeed.
We were under assumption that User just used Execute option rather than Execute Against. So, we were not expecting much info from there.