Bug 1381370 - AwesomeSpawn::CommandResultError when joining external db via appliance_console, does not start evm process
Summary: AwesomeSpawn::CommandResultError when joining external db via appliance_conso...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: cfme-future
Assignee: Nick Carboni
QA Contact: Alex Newman
URL:
Whiteboard: db
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-03 21:18 UTC by Alex Newman
Modified: 2016-10-25 16:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-25 16:03:27 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Alex Newman 2016-10-03 21:18:53 UTC 
Activating the configuration using the following settings...
Host:     10.16.6.133
Username: root
Database: vmdb_production


Configuration activated successfully.

Press any key to continue.
/opt/rh/cfme-gemset/gems/awesome_spawn-1.4.1/lib/awesome_spawn.rb:105:in `run!': /bin/systemctl exit code: 1 (AwesomeSpawn::CommandResultError)
                                                               	from /opt/rh/cfme-gemset/gems/linux_admin-0.18.0/lib/linux_admin/common.rb:24:in `run!'
                                                                       	from /opt/rh/cfme-gemset/gems/linux_admin-0.18.0/lib/linux_admin/service/systemd_service.rb:21:in `start'
                 	from /var/www/miq/vmdb/gems/pending/appliance_console/database_configuration.rb:224:in `block in start_evm'
                                                   	from /var/www/miq/vmdb/gems/pending/appliance_console/database_configuration.rb:224:in `fork'
                                                                     	from /var/www/miq/vmdb/gems/pending/appliance_console/database_configuration.rb:224:in `start_evm'
          	from /var/www/miq/vmdb/gems/pending/appliance_console/external_database_configuration.rb:28:in `post_activation'
                                                	from /var/www/miq/vmdb/gems/pending/appliance_console/database_configuration.rb:49:in `run_interactive'
                                                                               from /var/www/miq/vmdb/gems/pending/appliance_console.rb:461:in `block in <module:ApplianceConsole>'
                   	from /var/www/miq/vmdb/gems/pending/appliance_console.rb:108:in `loop'
              	from /var/www/miq/vmdb/gems/pending/appliance_console.rb:108:in `<module:ApplianceConsole>'
                           	from /var/www/miq/vmdb/gems/pending/appliance_console.rb:94:in `<main>'
Comment 6 Nick Carboni 2016-10-10 21:01:11 UTC 
I was able to do this without issues using the 5.7.0.4 build.

The steps I followed were as follows:
1. Deploy two appliances (db and app)
2. On db appliance
  - Configure Database (8)
  - Create Internal Database (1)
  - Answer no (N) to the prompt about using the server as an application server.
  - Follow the prompts
3. On the app appliance
  - Configure Database (8)
  - Create Region in External Database (2)
  - Follow the prompts

My guess is that you selected "Join Region in External Database" rather than "Create Region in External Database"

Maybe the join region logic needs a more robust check to make sure the database is indeed initialized as a region before connecting ...

Alex, can you confirm this works?
Note You need to log in before you can comment on or make changes to this bug.