Foreman 2.2 rc3 with katello 3.16 on centos 7 recommended for prod?

masadrasheed · October 6, 2020, 8:08pm

I am thinking to use foreman 2.2 rc3 with katello 3.16 on centos 7 , is it recommended for prod ? also i find one issue in installation of postgres encoding , its known bug or it only come in some special condition ?

https://projects.theforeman.org/issues/30697

I try to change it to UTF8 but it break pulp worker and everything.

Tony_Coffman · October 6, 2020, 8:57pm

The tested version of Foreman for Katello 3.16 on CentOS7 is 2.1 per the installation documentation.

https://theforeman.org/plugins/katello/3.16/installation/index.html

masadrasheed · October 6, 2020, 9:02pm

thank you .

masadrasheed · October 7, 2020, 12:28pm

’ | RUBYLIB=/opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/…/…//modules: /opt/puppetlabs/bin/puppet apply --config=/tmp/kafo_installation20201007-15872-113zyr3/puppet.conf

[ERROR 2020-10-07T08:24:52 main] 2020-10-07 08:24:50.814428 WARN puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C

Warning: /etc/foreman-installer/custom-hiera.yaml: file does not contain a valid yaml hash

Error: Evaluation Error: Error while evaluating a Function Call, ‘upcase’ parameter ‘arg’ expects a value of type Numeric, String, Array, or Hash, got Undef (file: /usr/share/foreman-installer/modules/foreman_proxy/manifests/params.pp, line: 279, column: 29) on node fountain2

[ERROR 2020-10-07T08:24:52 main] Could not get default values, cannot continue

Is any of the foreman build working ?

masadrasheed · October 7, 2020, 12:32pm

Issue resolve : hostname should be set properly

masadrasheed · October 7, 2020, 1:47pm

Back to same situation katello 3.16 have bug as it create DB in SQL_ASCII instead of UTF 8

Katello::Errors::Pulp3Error: unsupported Unicode escape sequence
LINE 1: …“name”: “technical-writing”, “default”: false}]’, '{“as”: "…
^
DETAIL: Unicode escape values cannot be used for code point values above 007F when the server encoding is not UTF8.
CONTEXT: JSON data, line 1: {“as”:…

-bash-4.2$ psql pulpcore -c ‘SHOW SERVER_ENCODING’ -U postgres

server_encoding

SQL_ASCII

(1 row)

-bash-4.2$

masadrasheed · October 7, 2020, 1:48pm

This tested version is not working properly @Tony_Coffman

ekohl · October 7, 2020, 2:14pm

The database must use UTF-8 encoding. If you’re deploying it all on the same server, we guarantee that but if you’re using a pre-created external database that’s up to you.

masadrasheed · October 7, 2020, 3:12pm

deployed on same server and using standard installation document not separate DB or etc.

https://theforeman.org/plugins/katello/3.16/installation/index.html

this is the result

-bash-4.2$ psql pulpcore -c ‘SHOW SERVER_ENCODING’ -U postgres

server_encoding

SQL_ASCII

(1 row)

-bash-4.2$

I just tested again and same results ASCII DB created.

ekohl · October 7, 2020, 3:59pm

You’re right: we don’t enforce it for Pulpcore:

github.com

theforeman/puppet-pulpcore/blob/c9a96d8ca6cb9067e672f94b1022743e51f8535e/manifests/database.pp#L7-L11


postgresql::server::db { $pulpcore::postgresql_db_name:
  user     => $pulpcore::postgresql_db_user,
  password => postgresql::postgresql_password($pulpcore::user, $pulpcore::postgresql_db_password),
  before   => Pulpcore::Admin['migrate --noinput'],
}

We do for Foreman:

github.com

theforeman/puppet-foreman/blob/026d47434316b8ae318c5e42936edc12859ab475/manifests/database/postgresql.pp#L20-L26


postgresql::server::db { $dbname:
  user     => $foreman::db_username,
  password => $password,
  owner    => $foreman::db_username,
  encoding => 'utf8',
  locale   => 'en_US.utf8',
}

ekohl · October 7, 2020, 4:13pm

https://github.com/theforeman/puppet-pulpcore/pull/126

masadrasheed · October 7, 2020, 4:19pm

yes and the solution is

[root@foreman ~]# cat /etc/environment

LANG=en_US.utf-8

LC_ALL=en_US.utf-8

[root@foreman ~]#

Before Installation