Started container cannot be stopped

Bug #2052504 reported by Simon Fels
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Anbox Cloud
Triaged
High
Unassigned

Bug Description

When I have an instance in AMS which is not marked as running yet (irrelevant why)

ubuntu@ip-172-31-15-223:~$ amc ls
+----------------------+-------------------+---------+---------+------+------+--------------+-----------+-------+----------------+
| ID | APPLICATION | TYPE | STATUS | TAGS | NODE | ADDRESS | ENDPOINTS | VM | STATUS MESSAGE |
+----------------------+-------------------+---------+---------+------+------+--------------+-----------+-------+----------------+
| cn10ad95rbk603isvl0g | morphis-aaos-test | regular | started | | lxd0 | 192.168.96.2 | | false | |
+----------------------+-------------------+---------+---------+------+------+--------------+-----------+-------+----------------+

and if I then try to stop the instance I got an error saying it cannot be stopped:

ubuntu@ip-172-31-15-223:~$ amc stop cn10ad95rbk603isvl0g
Error: container status is not running

It is expected that the user can stop the container in this case and not only when it is marked as running.

Simon Fels (morphis)
Changed in anbox-cloud:
assignee: nobody → Jatin Arora (jatinarora)
milestone: none → 1.21.1
Simon Fels (morphis)
Changed in anbox-cloud:
milestone: 1.21.1 → 1.22.0
assignee: Jatin Arora (jatinarora) → nobody
status: New → Triaged
importance: Undecided → High
Simon Fels (morphis)
Changed in anbox-cloud:
milestone: 1.22.0 → 1.22.1
milestone: 1.22.1 → none
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.