You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dlab.apache.org by "Anna Orlovska (JIRA)" <ji...@apache.org> on 2019/04/30 13:25:00 UTC
[jira] [Commented] (DLAB-542) Custom AMI is not deleted after
deleting SSN by Jenkins Job
[ https://issues.apache.org/jira/browse/DLAB-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830294#comment-16830294 ]
Anna Orlovska commented on DLAB-542:
------------------------------------
The bug is still reproduced for Nexus environment. For environment without Nexus custom AMIs are deleted after ssn deleting.
!custom_AMI_are_not_deleted.png!
> Custom AMI is not deleted after deleting SSN by Jenkins Job
> -----------------------------------------------------------
>
> Key: DLAB-542
> URL: https://issues.apache.org/jira/browse/DLAB-542
> Project: Apache DLab
> Issue Type: Bug
> Components: AWS
> Reporter: Anna Orlovska
> Assignee: Oleh Martushevskyi
> Priority: Major
> Labels: DevOps
> Fix For: v.2.2
>
> Attachments: AMI_are_not_deleted.png, Terminate_Nexus_ssn_Job.png, custom_AMI_are_not_deleted.png
>
>
> *Preconditions:*
> SSN is created. Custom AMI is created.
> *Steps to reproduce:*
> # Terminate SSN with “Amazon_Terminate_environment-develop” Jenkins Job.
> # Verify absence of AMI in AWS Console.
> *Expected result:*
> Corresponding to SSN AMI is absent.
> *{color:#333333}Actual result:{color}*{color:#333333}
> {color}{color:#24292e}Corresponding to SSN AMI is present.{color}{color:#333333} {color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@dlab.apache.org
For additional commands, e-mail: dev-help@dlab.apache.org