Fix post_activation exception when setting up internal database

[agrare]

Once both database and messaging have been configured by the CLI, start evmserverd.service. This will work if you pass both database and messaging config in the same invocation or if you configure them separately.

Example command: appliance_console_cli --internal --username='root' --password='smartvm' --region=1 --dbdisk=/dev/vdb --message-server-config --message-keystore-password="smartvm" --server=start

Fixes:

  config.post_activation
        ^^^^^^^^^^^^^^^^
from /opt/manageiq/manageiq-gemset/gems/manageiq-appliance_console-9.0.1/lib/manageiq/appliance_console/cli.rb:297:in `set_db'
from /opt/manageiq/manageiq-gemset/gems/manageiq-appliance_console-9.0.1/lib/manageiq/appliance_console/cli.rb:261:in `run'
from /opt/manageiq/manageiq-gemset/gems/manageiq-appliance_console-9.0.1/lib/manageiq/appliance_console/cli.rb:544:in `parse'
from /opt/manageiq/manageiq-gemset/gems/manageiq-appliance_console-9.0.1/bin/appliance_console_cli:7:in `<top (required)>'
from /opt/manageiq/manageiq-gemset/bin/appliance_console_cli:25:in `load'
from /opt/manageiq/manageiq-gemset/bin/appliance_console_cli:25:in `<main>'

Introduced by #195

Follow-up:

• Add documentation for appliance_console_cli messaging config manageiq-documentation#1789

[agrare]

We already have an explicit --server=start option, thinking we just reuse that either by setting options[:server] ||= "start" or just documenting that when you run appliance_console_cli you pass that so the full command would be:

appliance_console_cli --internal --username='root' --password='smartvm' --region=1 --dbdisk=/dev/vdb \
  --message-server-config --message-keystore-password="smartvm" \
  --server=start

Or split up into individual steps:

appliance_console_cli --internal --username='root' --password='smartvm' --region=1 --dbdisk=/dev/vdb
appliance_console_cli --message-server-config --message-keystore-password="smartvm" 
appliance_console_cli --server=start

[Fryguy]

I like the single step version and we can take care of the dependencies internally. So, yeah, seems we can just document that.

[agrare]

Working on adding documentation for the messaging config since it seems that wasn't added, I'll add the --server=start to the examples so people should copy&paste the right thing

[agrare]

Okay I'm going to take this out of WIP since this is functional and the only issues left aren't related to this fix (specifically #245)

Example: appliance_console_cli --internal --username='root' --password='smartvm' --region=1 --dbdisk=/dev/vdb --message-server-config --message-keystore-password="smartvm" --server=start