Bug 1331852

Summary:	5.6.0 beta appliance_console_api error for same command working in 5.5.2
Product:	Red Hat CloudForms Management Engine	Reporter:	Fabien CAMBI <fcambi>
Component:	Appliance	Assignee:	Gregg Tanzillo <gtanzill>
Status:	CLOSED DUPLICATE	QA Contact:	luke couzens <lcouzens>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	5.6.0	CC:	abellott, dajohnso, jhardy, jkrocil, lcouzens, ncarboni, obarenbo
Target Milestone:	GA
Target Release:	5.6.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	appliance:black
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-08 14:24:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Fabien CAMBI 2016-04-29 19:37:04 UTC

Description of problem:

I get an error when I try to configure a remote DB on a CFME 5.6.0 appliance with the command appliance_console_cli.

How reproducible:
Spin up 2 appliances unconfigured.
On the first one send:
appliance_console_cli -H cloudforms-db -r 99 -i -h localhost -U root -p smartvm
On the second one send:
appliance_console_cli -r 99 -H cloudforms-webui -h <CF DB IP> -U root -p smartvm -K <CF DB IP> -s root -a smartvm

Actual results:
--On a fresh install of CloudForms 4.1 Beta CFME 5.6.0 appliance:

appliance_console_cli -r 99 -H cloudforms-webui -h <CF DB IP> -U root -p smartvm -K <CF DB IP> -s root -a smartvm
fetch encryption key
configuring external database
Create region starting
Create region complete

Job for evmserverd.service failed because the control process exited with error code. See "systemctl status evmserverd.service" and "journalctl -xe" for details.

/opt/rh/cfme-gemset/gems/awesome_spawn-1.4.0/lib/awesome_spawn.rb:105:in `run!': /bin/systemctl exit code: 1 (AwesomeSpawn::CommandResultError)
	from /opt/rh/cfme-gemset/gems/linux_admin-0.16.0/lib/linux_admin/common.rb:24:in `run!'
	from /opt/rh/cfme-gemset/gems/linux_admin-0.16.0/lib/linux_admin/service/systemd_service.rb:21:in `start'
	from /var/www/miq/vmdb/gems/pending/appliance_console/database_configuration.rb:67:in `post_activation'
	from /var/www/miq/vmdb/gems/pending/appliance_console/cli.rb:193:in `set_external_db'
	from /var/www/miq/vmdb/gems/pending/appliance_console/cli.rb:153:in `set_db'
	from /var/www/miq/vmdb/gems/pending/appliance_console/cli.rb:136:in `run'
	from /var/www/miq/vmdb/gems/pending/appliance_console/cli.rb:269:in `parse'
	from /usr/bin/appliance_console_cli:16:in `<main>'

After which the status of the appliance shows:

Hostname:             cloudforms-wkr1
IP Address:           192.168.0.6
Netmask:              255.255.255.0
Gateway:              192.168.0.1
Primary DNS:          8.8.4.4
Secondary DNS:        8.8.8.8
Search Order:         openstacklocal
MAC Address:          fa:16:3e:09:6b:6b
Timezone:             America/New_York
Local Database:       not running
CFME Database:        postgres @ localhost
Database/Region:      vmdb_production / 0
External Auth:        not configured
CFME Version:         5.6.0.0-beta1
CFME Console:         https://192.168.0.6

As you can see the DB is still local and the region still 0.

Expected results:
On a fresh install of CloudForms 4.0 CFME 5.5.2 appliances, the same commands work correctly.

Comment 2 Dave Johnson 2016-05-03 20:08:38 UTC

Luke, can you reproduce and figure out the delta between what our automation is using.  I think there must be something more specific like one of the parameters.

Comment 5 luke couzens 2016-06-07 11:39:45 UTC

Looking at the two screenshots you can see that this is reproducible. On the left you can see the commands working for 5.5 and on the right not working for 5.6.0.8.

Dajo, Do we actually have 2 apps in 'external database setup' within are automation processes? I figured we only ran single appliance setups? or maybe Alex can help me with this?

Comment 6 Nick Carboni 2016-08-08 14:24:19 UTC

Closing as a duplicate.

The -r flag should only be passed if you intend to initialize a new region in a database.

*** This bug has been marked as a duplicate of bug 1347834 ***