Actions
Bug #29649
closedThe system does not seem to be IPA-enrolled
Status:
Closed
Priority:
Low
Assignee:
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:
Description
Running the installer after the upgrade like I always do:
env TMP= TMPDIR= foreman-installer \ -v \ --foreman-proxy-log-level=DEBUG \ --enable-foreman-plugin-remote-execution \ --enable-foreman-proxy-plugin-remote-execution-ssh \ --enable-foreman-plugin-dhcp-browser \ --enable-foreman-plugin-remote-execution \ --enable-foreman-proxy-plugin-remote-execution-ssh \ --foreman-ipa-authentication=true \ --foreman-pam-service=foreman \ --foreman-http-keytab=/etc/http.keytab \ --no-enable-foreman-cli-ansible \ --no-enable-foreman-plugin-ansible \ --no-enable-foreman-proxy-plugin-ansible
After the upgrade to 2.0 I get
Evaluation Error: Error while evaluating a Function Call, theforeman: The system does not seem to be IPA-enrolled (file: /usr/share/foreman-installer/modules/foreman/manifests/config.pp, line: 101, column: 9) on node
Which reads:
unless 'ipa' in $facts and 'default_server' in $facts['ipa'] and 'default_realm' in $facts['ipa'] {
So it tests the output of facter ipa
. If I do that manually I get no output. digging a bit further this is the code in question: /etc/puppetlabs/code/modules/ipaclient/lib/facter/ipa_facts.rb
The important part would be:
if File.exist?('/etc/sssd/sssd.conf') && sssd = File.readlines('/etc/sssd/sssd.conf') sssd.each do |line| case line when /^ipa_domain/ Facter.add("ipa_domain") do has_weight 100 setcode do line.split("=")[1].strip end end when /^ipa_server/ Facter.add("ipa_server") do has_weight 100 setcode do line.split("=")[1].strip end end when /^auth_provider/ Facter.add("ipa_enrolled") do
Odd because:
root@theforeman ~ # ag '(ipa_domain|ipa_server|auth_provider)' /etc/sssd/sssd.conf |sed -e 's|mycompany.com|example.com|g' auth_provider = ipa ipa_domain = example.com ipa_server = _srv_, gandalf.example.com, olorin.example.com, mithrandir.example.com ipa_server_mode = false
Seems like I'm barking up the wrong tree, this must be a puppet problem. But please leave it for the moment because other may run into this problem as well.
Updated by The Foreman Bot almost 5 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ewoud Kohl van Wijngaarden
- Pull request https://github.com/theforeman/puppet-foreman/pull/839 added
Updated by Ewoud Kohl van Wijngaarden almost 5 years ago
- Category set to Foreman modules
- Target version set to 2.1.0
- Triaged changed from No to Yes
- Fixed in Releases deleted (
1.24.3)
Updated by Ewoud Kohl van Wijngaarden almost 5 years ago
- Status changed from Ready For Testing to Closed
Updated by Ewoud Kohl van Wijngaarden almost 5 years ago
- Fixed in Releases 2.1.0 added
- Fixed in Releases deleted (
2.2.0)
Updated by The Foreman Bot almost 5 years ago
- Pull request https://github.com/theforeman/puppet-foreman/pull/848 added
Updated by Ewoud Kohl van Wijngaarden over 4 years ago
- Status changed from Closed to New
- Target version changed from 2.0.1 to 2.1.2
Updated by The Foreman Bot about 4 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman/pull/935 added
Updated by The Foreman Bot almost 4 years ago
- Pull request https://github.com/theforeman/puppet-foreman/pull/888 added
Updated by Ewoud Kohl van Wijngaarden over 3 years ago
- Status changed from Ready For Testing to Closed
Updated by The Foreman Bot over 3 years ago
- Pull request https://github.com/theforeman/puppet-foreman/pull/960 added
Updated by Ewoud Kohl van Wijngaarden over 3 years ago
- Pull request deleted (
https://github.com/theforeman/puppet-foreman/pull/960)
Actions