Description of problem:configuring external auth crashes appliance console 220.127.116.11
Version-Release number of selected component (if applicable):18.104.22.168
Steps to Reproduce:
3.select option 14
4.follow prompts to configure
Actual results:appliance console crashes when restarting sssd and httpd
Expected results:appliance console does not crash while finishing setup
Although appliance_console crashes it seems external auth is actually setup
Configuring IPA (may take a minute) ...
Configuring the IPA Client ...
Configuring pam ...
Configuring sssd ...
Configuring IPA HTTP Service and Keytab ...
Configuring httpd ...
Configuring SELinux ...
Restarting sssd and httpd ...
/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.19.0/lib/linux_admin/common.rb:24:in `run!'
from /opt/rh/cfme-gemset/gems/linux_admin-0.19.0/lib/linux_admin/service/systemd_service.rb:21:in `start'
from /opt/rh/cfme-gemset/gems/linux_admin-0.19.0/lib/linux_admin/service/systemd_service.rb:40:in `restart'
from /var/www/miq/vmdb/gems/pending/appliance_console/external_httpd_authentication.rb:83:in `block in post_activation'
from /var/www/miq/vmdb/gems/pending/appliance_console/external_httpd_authentication.rb:83:in `each'
from /var/www/miq/vmdb/gems/pending/appliance_console/external_httpd_authentication.rb:83:in `post_activation'
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:278:in `block in <module:ApplianceConsole>'
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:109:in `loop'
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:109:in `<module:ApplianceConsole>'
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:95:in `<main>'
I suspect your appliance my not be correctly configured.
Can you please confirm your appliance is running with the command:
systemctl status evmserverd
When you configured your database with the appliance_console did you happen
to answer "yes" to the prompt:
`Configure this server as a dedicated database instance? (Y/N): `
You need to answer "no" to that.
So I think you are correct, I can only reproduce this on an unconfigured appliance. On that note though should we really see an appliance console crash, regardless if evm is started or not?
New commit detected on ManageIQ/manageiq-gems-pending/master:
Author: Joe VLcek <firstname.lastname@example.org>
AuthorDate: Tue Jan 17 20:13:04 2017 -0500
Commit: Joe VLcek <email@example.com>
CommitDate: Thu Jan 19 13:44:45 2017 -0500
Restart httpd only if it is running.
.../appliance_console/external_httpd_authentication.rb | 9 +++++----
.../external_httpd_authentication_spec.rb | 17 +++++++++++++++++
2 files changed, 22 insertions(+), 4 deletions(-)
Verified in 22.214.171.124
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.