Foreman 1.6 to 1.7 upgrade issue

Support
1

After upgrading to 1.7 ( I had no problems from 1.4-1.6 this afternoon)
I got the following error when running

foreman-installer --noop --dont-save-answers --verbose

[ INFO 2014-12-11 17:00:29 main] Puppet has finished, bye!
[ INFO 2014-12-11 17:00:29 main] Executing hooks in group post
[DEBUG 2014-12-11 17:00:30 main] Hook
/usr/share/foreman-installer/hooks/post/10-post_install_message.rb
returned nil
[ INFO 2014-12-11 17:00:30 main] All hooks in group post finished
[DEBUG 2014-12-11 17:00:30 main] Exit with status code: 4 (signal was 4)
[ERROR 2014-12-11 17:00:30 main] Repeating errors encountered during run:*
[ERROR 2014-12-11 17:00:30 main]
/Stage[main]/Postgresql::Server::Config/Concat[/var/lib/pgsql/data/pg_ident.conf]/File[/var/lib/pgsql/data/pg_ident.conf]:
Could not evaluate: Could not retrieve information from environment
production source(s) file:/var/lib/puppet/concat/_var_lib_pgsql_data_pg_ident.conf/fragments.concat.out <file://var/lib/puppet/concat/_var_lib_pgsql_data_pg_ident.conf/fragments.concat.out>
[DEBUG 2014-12-11 17:00:30 main] Cleaning /tmp/d20141211-15597-1bhs5pb
[DEBUG 2014-12-11 17:00:30 main] Cleaning /tmp/default_values.yaml

The file in question does not in fact exist.

ls -l /var/lib/puppet/concat/_var_lib_pgsql_data_pg_ident.conf/fragments.concat.out

ls: cannot access /var/lib/puppet/concat/_var_lib_pgsql_data_pg_ident.conf/fragments.concat.out:
No such file or directory

ls -1 /var/lib/puppet/concat/_var_lib_pgsql_data_pg_hba.conf/fragments/

001_pg_hba_rule_local access as postgres user
002_pg_hba_rule_local access to database with same name
003_pg_hba_rule_allow localhost TCP access to postgresql user
004_pg_hba_rule_deny access to postgresql user
100_pg_hba_rule_allow access to all users
101_pg_hba_rule_allow access to ipv6 localhost

Foreman is running, I have not tried to install a node or anything, but
I would like to get the config to run.

Terrence

2

No ideas what is causing this error or how I might resolve it?

3

Errors with concat are to be expected when using --noop. To
illustrate, consider the following simple example

mkdir a
touch a/b

If this were executed in noop, a similar error would occur - 'b' could
not be touched, because 'a' has not been created. In the same way,
concat creates directories to store it's fragments, which are not
created in noop mode.

HTH,
Greg

··· On 12 December 2014 at 01:12, Terrence Martin wrote:

foreman-installer --noop --dont-save-answers --verbose

Could not evaluate: Could not retrieve information from environment
production source(s)
file:/var/lib/puppet/concat/_var_lib_pgsql_data_pg_ident.conf/fragments.concat.out*

4

Thanks, that makes sense, so basically this can be ignored then if it is
the only error I expect?

Terrence

··· On Tuesday, December 16, 2014 2:29:15 AM UTC-8, Greg Sutcliffe wrote: > > On 12 December 2014 at 01:12, Terrence Martin > wrote: > > > foreman-installer --noop --dont-save-answers --verbose > > > Could not evaluate: Could not retrieve information from environment > > production source(s) > > > file:/var/lib/puppet/concat/_var_lib_pgsql_data_pg_ident.conf/fragments.concat.out* > > > Errors with concat are to be expected when using --noop. To > illustrate, consider the following simple example > > mkdir a > touch a/b > > If this were executed in noop, a similar error would occur - 'b' could > not be touched, because 'a' has not been created. In the same way, > concat creates directories to store it's fragments, which are not > created in noop mode. > > HTH, > Greg >