Red Hat Bugzilla – Bug 1248039
Unable to Importing into a new Automate Domain if a custom domain exist
Last modified: 2015-12-08 08:24:27 EST
Description of problem:
Using the Automate Import / Export if there is another domain available we're unable to import into a new empty domain. See attached screenshots, we would like to be able to import as an identically named domain (like what happens if no domains are available).
Version-Release number of selected component (if applicable): 5.4.0
Steps to Reproduce:
1. import a new automate model with the ui and a custom domain is created based on the models name
2. if a second model is imported you have to select a domain then ui will not create another domain based on that models name.
Let's try that again.
Erik - For command line importing if you only specify the "domain you wish to import from" it will import into that same domain. Optionally, you can specify the IMPORT_AS to import into a different domain. See https://access.redhat.com/solutions/1225383
DOMAIN = Name of the exported domain (name of domain created will be the same). Specify "*" to import all exported domains.
IMPORT_AS = (Optional) Name of the domain to create in the Automate database, the domain name can only be set when importing a single domain.
The enhancement here would be to add (and I think default to) a new drop-down item like "<Same as import from>" for the "Select existing domain to import into:" field.
New commit detected on manageiq/master:
Author: Erik Clarizio <email@example.com>
AuthorDate: Tue Aug 11 12:26:43 2015 -0700
Commit: Erik Clarizio <firstname.lastname@example.org>
CommitDate: Tue Aug 11 13:22:59 2015 -0700
Allow importing into a new domain with the same name as import from
app/controllers/miq_ae_tools_controller.rb | 5 ++++-
app/services/automate_import_service.rb | 2 +-
spec/controllers/miq_ae_tools_controller_spec.rb | 20 ++++++++++++++++++++
spec/services/automate_import_service_spec.rb | 12 ++++++++++++
4 files changed, 37 insertions(+), 2 deletions(-)
Good, verified in 0911 upstream build then.
Checked in 220.127.116.11-alpha1.1
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.