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

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.

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

thank you .

’ | 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 ?

Issue resolve : hostname should be set properly

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$

This tested version is not working properly @Tony_Coffman

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.

1 Like

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.

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

We do for Foreman:

1 Like
2 Likes

yes and the solution is :slight_smile:

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

LANG=en_US.utf-8

LC_ALL=en_US.utf-8

[root@foreman ~]#

Before Installation

2 Likes