Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Automatic Host ISO upload from Satellite to VMware datastore fails with:
----------
Failed to save: Failed to upload ISO image for instance HOSTNAME: FileAlreadyExists: Cannot complete the operation because the file or folder [DATASTORENAME] foreman_isos already exists
----------
Version-Release number of selected component (if applicable):
Satellite 6.6.1
tfm-rubygem-fog-vsphere-3.2.1-1.el7sat.noarch
How reproducible:
Every time I try to provision a host to VMware using the bootdisk method, if the foreman_isos directory already exists on VMware's datastore.
Steps to Reproduce:
1. Provision a first host to VMware using the bootdisk method.
2. Provision a second host to VMware using the bootdisk method.
Actual results:
Second host fails to upload the generated bootdisk ISO and complains that the foreman_isos directory already exists, which should not be a problem.
Expected results:
The existing foreman_isos directory should not be a problem and the bootdisk ISO should simply be copied into this directory.
Additional info:
This bug has been fixed upstream at https://github.com/fog/fog-vsphere/pull/241 and it's a very trivial change. The change has also been applied to customers and confirmed to resolve the issue on Satellite 6.6.1.
Looks like this was not fixed in 6.7, the fix will be in tfm-rubygem-fog-vsphere-3.2.3-1 which we need to pull into the release.
I am setting flags for 6.8.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:4366