[
https://issues.apache.org/jira/browse/DATALAB-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337245#comment-17337245
]
Leonid Frolov commented on DATALAB-2333:
----------------------------------------
vi-aws-274a-ssn-role has been created at 7 AM, at 11 PM the same day
AmazonSSMManagedInstanceCore policy has been attached to the role by some
server using boto3, running Windows 10.
currently during ssn termination first policy ending with "-ssn-policy" is
deleted, after that "-ssn-role" is deleted.
Probably it would be best to first detach all policies from role that will be
deleted, and then to delete resources
> Investigate why Some role is added during SSN deployment. It leads to collect
> resources (route table/vpc/subnet etc) after SSN termination
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DATALAB-2333
> URL: https://issues.apache.org/jira/browse/DATALAB-2333
> Project: Apache DataLab
> Issue Type: Task
> Security Level: Public(Regular Issues)
> Components: DataLab Main
> Reporter: Vira Vitanska
> Assignee: Leonid Frolov
> Priority: Minor
> Labels: AWS, Debian, DevOps, RedHat
> Fix For: v.2.5
>
>
> On AWS SSN termination fails with error:
> {code:java}
> DeleteConflictException: An error occurred (DeleteConflict) when calling the
> DeleteRole operation: Cannot delete entity, must detach all policies first.
> {code}
> And sometime the role somehow is assigned to the instance.
> Please investigate why this role is assigned and if you could fix it in the
> scope of this ticket.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
