Fix owner after smdba execution in the DB migration script (bsc#12147…

…46) (#7590) * Run chown after smdba to prevent permission issues * Add changelog entry
uyuni-project · Oct 2, 2023 · 7801b25 · 7801b25
1 parent b98e12f
commit 7801b25
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 1 deletion.
diff --git a/susemanager/bin/pg-migrate-x-to-y.sh b/susemanager/bin/pg-migrate-x-to-y.sh
@@ -194,11 +194,11 @@ fi
 
 cp /var/lib/pgsql/data-pg$OLD_VERSION/pg_hba.conf /var/lib/pgsql/data
 cp /var/lib/pgsql/data-pg${OLD_VERSION}/postgresql.conf /var/lib/pgsql/data/
-chown postgres:postgres /var/lib/pgsql/data/*
 
 echo "$(timestamp)   Tune new postgresql configuration..."
 smdba system-check autotuning
 if [ $? -eq 0 ]; then
+    chown postgres:postgres /var/lib/pgsql/data/*
     echo "$(timestamp)   Successfully tuned new postgresql configuration."
 else
     echo "$(timestamp)   Tuning of new postgresql configuration failed!"

diff --git a/susemanager/susemanager.changes.vzhestkov.fix-owner-after-smdba b/susemanager/susemanager.changes.vzhestkov.fix-owner-after-smdba
@@ -0,0 +1 @@
+- Fix possible permission issues with database migration script (bsc#1214746)