Red Hat Bugzilla – Bug 1325939
SSH provisioning fails when sql logging level is set to 'error'
Last modified: 2018-02-21 12:29:40 EST
Current logger calls return `true`|`false` depending whether the current level allows the logging message or not. In the orchestration, we happened to have the logger call as the last call of the orchestration method (https://github.com/theforeman/foreman/blob/1.10.1/app/models/concerns/orchestration/ssh_provision.rb#L66). When the method returns non-true value, it's considered as failure and the whole thing tries to get rollbacked.
Created from redmine issue http://projects.theforeman.org/issues/13769
Upstream bug assigned to inecas@redhat.com
Moving 6.2 bugs out to sat-backlog.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/13769 has been resolved.
~]# cat /etc/foreman/settings.yaml | grep -A 10 "Log settings" # Log settings for the current environment can be adjusted by adding them # here. For example, if you want to increase the log level. :logging: :level: error # Individual logging types can be toggled on/off here :loggers: :ldap: :enabled: true Tried to Provision a VM on AWS/EC2 via Finish template and was able to successfully provision one and also get the VM to do the SSH configuration on it. VERIFIED with sat63-snap24 Will attach few screenshots shortly
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. https://access.redhat.com/errata/RHSA-2018:0336