Katello 3.17 to 3.18, cannot migrate to pulp3

caseybea · April 30, 2021, 4:14am

Centos8, yes. Centos8 STREAM, no.

gvde · April 30, 2021, 4:20am

Can you check in the Postgres database which distribution it is? Instructions are in the other thread.

ekohl · April 30, 2021, 1:28pm

Note that this creates the pulpcore database using the current locale. In the installer we enforce en_US.UTF-8 and UTF-8 encoding. If your OS locale is en_US.UTF-8 then it’ll be ok but this affects the results of sorting and can cause unexpected behavior.

For example:

$ echo -e "a\nb\nc\nd\nch\nh\ni" | LC_ALL=en_US.UTF-8 sort
a
b
c
ch
d
h
i
$ echo -e "a\nb\nc\nd\nch\nh\ni" | LC_ALL=cs_CZ.UTF-8 sort
a
b
c
d
h
ch
i

I’d recommend to be explicit

createdb -E UTF-8 -l en_US.UTF-8 pulpcore

iballou · April 30, 2021, 1:55pm

@caseybea @gvde since you’re both hitting the same error, mind if we take the remaining discussion over to [ContentMigration] Katello::Errors::Pulp3Error ? I’ll be looking for potentially-related Pulp 3 bugs.

caseybea · April 30, 2021, 2:07pm

@iballou @gvde Yes I was going to propose that but you beat me to it.

My original issue, the “content prepare” operationg getting just… STUCK— has been solved above. I’ll continue over in the other thread. Thank you much.

gvde · April 30, 2021, 2:10pm

Absolutely. Maybe you can change the subject of that topic? “Katello::Errors::Pulp3Error” is very generic and I cannot change the subject anymore.

iballou · April 30, 2021, 2:14pm

I can’t change it either, but hopefully searching for the error you’re both seeing will lead to the thread.