Description of problem: After setting ticket to a VM , there is no event in events tab . Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: RHEVM shell (connected)]# action vm 0c373c97-0a72-4e4e-a9fd-7d7d906e9531 ticket status-state : complete ticket-expiry: 7200 ticket-value : kDTtdOYAngVx [RHEVM shell (connected)]# list events --max 1 id : 1534 description: User admin@internal logged in.
why do we need one? I would expect it's useful only for some more longterm tasks
Currently you have no way to know if manual ticket command succeeded or not , I don't see why this command is different from other commands . (In reply to comment #1) > why do we need one? I would expect it's useful only for some more longterm > tasks
we can add it for explicit usages, e.i when invoking /api/xxx/ticket but this means we have to flag the engine somehow about explicit call of this verb. I'm not a big fan of shouldBeLogged flag in VdcActionParameterBase (and I know ofrenkel isn't either) and 2nd option is that we can always log this one, its informative and not costly really. thoughts?
this command is basically internal (in the UI, user click the console, shouldn't be aware of internal implementation of setting a ticket). i suggest adding a message that will describe the process and not the action, something like "user initiated console session"
It will not be accurate when calling ticket vm explicitly ( from Rest / SDK / CLI ) (In reply to comment #4) > this command is basically internal (in the UI, user click the console, > shouldn't be aware of internal implementation of setting a ticket). > > i suggest adding a message that will describe the process and not the > action, something like "user initiated console session"
(In reply to comment #5) > It will not be accurate when calling ticket vm explicitly ( from Rest / SDK > / CLI ) > > (In reply to comment #4) > > this command is basically internal (in the UI, user click the console, > > shouldn't be aware of internal implementation of setting a ticket). > > > > i suggest adding a message that will describe the process and not the > > action, something like "user initiated console session" agree - we do support setting the ticket directly, but i think the suggested message ("user initiated console session") covers this use case as well.