Endpoint 1.0/events dont comming message "instance-running"

Bug #2082069 reported by puivan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Anbox Cloud
New
Undecided
Unassigned

Bug Description

Greetings to your team! Continuing the topic of events, I noticed another problem, but already related to tracking the status of the session. The fact is that messages come from the websocket at the time of session creation (instance) when the status changes to STARTED, the message comes like this: {
"type": "lifecycle",
"timestamp": "2024-09-25T07:26:02.585971312Z",
"metadata": {
"action": "instance-started",
        "source": "/1.0/instances/crprl3np0q7s01sfhfgg"
}
but when the status changes to RUNNING, the same message comes from the websocket {
"type": "lifecycle",
    "timestamp": "2024-09-25T07:26:02.585971312Z",
    "metadata": {
        "action": "instance-started",
        "source": "/1.0/instances/crprl3np0q7s01sfhfgg"
    }
 and then the question arises, isn't it an error? maybe a message should come here that the status is no longer STARTED but RUNNING? This problem can be solved by making an additional request to check the status, then the question arises what is the point of using a websocket at all?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.