Bug 1516139 - on removing a bootdisk host should also remove the attached boot iso from datastore
Summary: on removing a bootdisk host should also remove the attached boot iso from dat...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Bootdisk Plugin
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-22 07:16 UTC by Sachin Ghai
Modified: 2019-02-07 12:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 12:03:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
bootdisk_isos should also be removed from datastore when host is removed (66.78 KB, image/png)
2017-11-22 07:16 UTC, Sachin Ghai
no flags Details

Description Sachin Ghai 2017-11-22 07:16:37 UTC
Created attachment 1357261 [details]
bootdisk_isos should also be removed from datastore when host is removed

Description of problem: I was trying to provision hosts through BOOtdisk provisioning method on vmware compute resource. Later, I removed a few hosts from satellite and hosts removed from backend, which is expected. Though I still see the bootdisk ISO in the datastore and for those hosts which are already removed.

Please see the attachment.


Version-Release number of selected component (if applicable):
sat6.3 GA snap25

How reproducible:


Steps to Reproduce:
1. create a host using bootdisk method on vmware
2. remove host from satellite
3.

Actual results:
on removing host from satellte, host was removed from vmware but not the attached bootdisk iso

Expected results:
on removing a bootdisk host should also remove the attached boot iso from datastore


Additional info:

Comment 2 Lukas Zapletal 2017-11-23 15:07:43 UTC
Sachin, can you test something for me? If you create another host with the same hostname, will it break the workflow because the ISO is already present?

If not, it's low priority bug, perhaps only backlog.

Comment 3 Sachin Ghai 2017-12-06 12:14:50 UTC
Yeah, I tried to create  another host with same name. Host was provisioned and ISO was over written as I see the modified date of today. 

So its just that ISO won't be deleted which may create amny small files in datastore.

Comment 5 Bryan Kearney 2018-11-30 15:01:02 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Rich Jerrido or Bryan Kearney or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 6 Bryan Kearney 2019-02-07 12:03:52 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.


Note You need to log in before you can comment on or make changes to this bug.