Closed GoneWacko closed 1 year ago
@GoneWacko - Thank you for your post. I am able to reproduce the issue. Marking this as bug. I will see to get this one fixed.
Is there any update? same situation occurs for get_waiter('fleet_started')
Hi all, thanks for your patience. Waiter models are now owned by the respective service teams, so we'll need to contact the AppStream team for feedback on this. I created a new issue for tracking this in our cross-SDK repository since waiters are shared across AWS SDKs: https://github.com/aws/aws-sdk/issues/423. Please refer to that issue for updates going forward.
Describe the bug The FleetStarted and FleetStopped waiters for the 'appstream' service wait for the appstream fleet(s) to reach the 'ACTIVE' and 'INACTIVE' states, respectively. However, fleets never reach these states; instead, the states the waiters should be polling for are 'RUNNING' and 'STOPPED'.
Botocore version: botocore-1.16.16
Steps to reproduce E.g. with boto3 (though I believe the issue to be in botocore), and given a running AppStream 2.0 fleet called 'SomeFleetName':
Expected behavior The FleetStopped waiter should wait for the fleet to reach the 'STOPPED' state, not 'INACTIVE' The FleetStarted waiter should wait for 'RUNNING' rather than 'ACTIVE'. Other failure states should probably be modified as well (e.g. the 'PENDING_ACTIVATE' state should be 'STARTING' instead).
Debug logs Probably of limited use, but as can be seen from this log, the waiter continues to poll the DescribeFleets operation even though the fleet has reached the desired STOPPED state: