Craig: can you log a ticket for the first issue? I've occasionally seen that in the demo environment, but we should be able to troubleshoot it. (Sonali Kshirsagar was looking at it with me).
As for the second, I believe it creates a new NSH Script Job once you complete the operation. I'll touch base with Matthew Salerno about recommended behavior. (wouldn't be a bad idea to open a ticket for this one either)
Will do on the first issue. It doesn't seem to affect anything, other than the execute option is grayed out on the operations home page. To get it to run I need to open the result and use the Execute button.
You are correct, sir, on the second issue. The result of the create operation in the portal is an NSH job in the 'Jobs' workspace. It's almost like it 'forgets' that the new job was not based on an existing job and so it disallows changes.
The first issue is kind of known issue where if we change the underline job from BSA the operation becomes orphan and cannot be synced.
If its a demo environment then we can remove these stale entries from DCAPORTALOPERATION table and avoid them showing on the UI.
>> If its a demo environment
Thanks for the information, Sonali. Unfortunately, this is in our production environment.
Case 00264003 has been opened for the portal job status showing an operation is running after being canceled in the BSA console.
Hi. Is there a solution for this issue yet?
I am also looking for a solution for the Portal issue. Have a few patch analysis jobs now in a "funny" running state, not being able to sync it.
FSM failed to execute. Got error in state start : The transition to state start [com.bmc.dcaportal.dcaportalprovider.fsm.DCAPortalOperationSyncFSM:start] generated an exception
I have done so. Without much response. ☹
Sorry to hear that - I've notified the Support Manager.
Got tickets for those?
I worked with support after I started this thread and the solution to the first issue is a little complicated. Basically, it involves viewing and editing the document source (using a DOM inspector) and enabling the 'Delete' function for the operation. Then the operation can be deleted and re-created which then allows the operation to function normally. Since the job run history is in the database, not in the portal, there is no data loss by deleteing and re-creating the operation. I've had to do this a couple of times.
The second issue is not really an issue at all, more of a message display problem. Targets can be removed or added as needed for most portal operations, at least batch and NSH script types, even when that message is displayed.
Hope this helps.
Thanx for the feedback. Sounds like I will be able to do a Webex today for case 00416756 to resolve.
Is there a doc with steps to follow to resolve?
Here is the summary of the Webex I had with support on Feb. 7, 2017. The case number and description are included in the summary.
Case #00264003-Portal shows batch job status is running after being canceled in BSA console.
Thank you for your time over the webex session !!
Please find following summary of the call for the reference:-
> During the webex session, our engineering team suggested to open browser, logged into portal, navigate to job run.
> After that we inspected an element for the same (where delete was disabled).
> Which showed class id=disabled. We just removed the class named disabled. And it shown delete menu in enabled state.
> After that we clicked on delete and zombie operation was gone.
Since after performing above steps the issue got resolved, as per confirmation, we are closing this case now, feel free to get back to us in case of any issues concerns, we will be glad to assist you further.
If you need any further assistance, please feel free to contact the BMC Support team.
Please do not hesitate to ask me any other questions or with anything else I can be of assistance.
You have a great day!!
Phone: 1 (800) 537-1813
http://www.bmc.com/support/support-contacts Alternate Support Contacts