[uyuni-users] Update Uyuni 4.0.2 to current version
Hi, I tried to update my Uyuni installation from 4.0.2 to 2020.03 (the current version). I did " spacewalk-service stop", changed the repo and made a zypper update. After that I startet the postgresql database and tried the schema upgrade. But the upgrade didn't finished succesfully: Schema upgrade: [susemanager-schema-4.0.13-400.3.1.uyunimaster] -> [susemanager-schema-4.1.5-1.1.uyuni] Searching for upgrade path to: [susemanager-schema-4.1.5-1] Searching for upgrade path to: [susemanager-schema-4.1.5] Searching for start path: [susemanager-schema-4.0.13-400] Searching for start path: [susemanager-schema-4.0.13] The path: [susemanager-schema-4.0.13] -> [susemanager-schema-4.0.14] -> [susemanager-schema-4.1.0] -> [susemanager-schema-4.1.1] -> [susemanager-schema-4.1.2] -> [susemanager-schema-4.1.3] -> [susemanager-schema-4.1.4] -> [susemanager-schema-4.1.5] Planning to run schema upgrade with dir '/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721' Hit Enter to continue or Ctrl+C to interrupt: Executing spacewalk-sql, the log is in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log]. (22/26) apply upgrade [susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql] sql.postgresql] Upgrade failed, please see log [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log]. You can fix the failed migration in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721] and run spacewalk-schema-upgrade again The last element in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log shows: ?column? ------------------------------------------------------------------------------------------------ susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql (1 row) psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun". ================== started: 2020-03-27 13:40:57 ================== SQL> select 'susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql' from dual; DELETE FROM rhnTaskoTemplate WHERE bunch_id = (SELECT id FROM rhnTaskoBunch WHERE name='mgr-register-bunch') AND task_id = (SELECT id FROM rhnTaskoTask WHERE name='mgr-register'); DELETE FROM rhnTaskoTask WHERE name = 'mgr-register'; DELETE FROM rhnTaskoSchedule WHERE job_label = 'mgr-register-default'; DELETE FROM rhnTaskoBunch WHERE name = 'mgr-register-bunch'; commit; ?column? ------------------------------------------------------------------------------------------------ susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql (1 row) psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun". Did I made a mistake or is there a solution for the problem? Greets Torsten -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Hi exactly the same thing happens here. 4.0.2 should also be updated to 2020.03 However, the correct repository was set before zypper update. Do I / we do something wrong? Is there a kind of "how do I update" for stupid? Regards Thomas
Am 27.03.2020 um 14:34 schrieb Haupt, Torsten <Torsten.Haupt@lhw.mlu.sachsen-anhalt.de>:
Hi,
I tried to update my Uyuni installation from 4.0.2 to 2020.03 (the current version). I did " spacewalk-service stop", changed the repo and made a zypper update. After that I startet the postgresql database and tried the schema upgrade. But the upgrade didn't finished succesfully:
Schema upgrade: [susemanager-schema-4.0.13-400.3.1.uyunimaster] -> [susemanager-schema-4.1.5-1.1.uyuni] Searching for upgrade path to: [susemanager-schema-4.1.5-1] Searching for upgrade path to: [susemanager-schema-4.1.5] Searching for start path: [susemanager-schema-4.0.13-400] Searching for start path: [susemanager-schema-4.0.13] The path: [susemanager-schema-4.0.13] -> [susemanager-schema-4.0.14] -> [susemanager-schema-4.1.0] -> [susemanager-schema-4.1.1] -> [susemanager-schema-4.1.2] -> [susemanager-schema-4.1.3] -> [susemanager-schema-4.1.4] -> [susemanager-schema-4.1.5] Planning to run schema upgrade with dir '/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721' Hit Enter to continue or Ctrl+C to interrupt: Executing spacewalk-sql, the log is in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log]. (22/26) apply upgrade [susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql] sql.postgresql] Upgrade failed, please see log [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log]. You can fix the failed migration in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721] and run spacewalk-schema-upgrade again
The last element in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log shows: ?column? ------------------------------------------------------------------------------------------------ susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql (1 row)
psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun". ================== started: 2020-03-27 13:40:57 ================== SQL> select 'susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql' from dual; DELETE FROM rhnTaskoTemplate WHERE bunch_id = (SELECT id FROM rhnTaskoBunch WHERE name='mgr-register-bunch') AND task_id = (SELECT id FROM rhnTaskoTask WHERE name='mgr-register'); DELETE FROM rhnTaskoTask WHERE name = 'mgr-register'; DELETE FROM rhnTaskoSchedule WHERE job_label = 'mgr-register-default'; DELETE FROM rhnTaskoBunch WHERE name = 'mgr-register-bunch'; commit;
?column? ------------------------------------------------------------------------------------------------ susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql (1 row)
psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun".
Did I made a mistake or is there a solution for the problem?
Greets Torsten -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Make sure, that postgres is up and running. Normally it will be stopped when you do a spacewalk-service stop. So do a "systemctl start postgres" and try again. Robert sent from my mobile device -------- Originale Nachricht -------- Von: "Haupt, Torsten" <torsten.haupt@lhw.mlu.sachsen-anhalt.de> Gesendet: Fri Mar 27 14:34:32 GMT+01:00 2020 An: "uyuni-users@opensuse.org" <uyuni-users@opensuse.org> Betreff: [uyuni-users] Update Uyuni 4.0.2 to current version Hi, I tried to update my Uyuni installation from 4.0.2 to 2020.03 (the current version). I did " spacewalk-service stop", changed the repo and made a zypper update. After that I startet the postgresql database and tried the schema upgrade. But the upgrade didn't finished succesfully: Schema upgrade: [susemanager-schema-4.0.13-400.3.1.uyunimaster] -> [susemanager-schema-4.1.5-1.1.uyuni] Searching for upgrade path to: [susemanager-schema-4.1.5-1] Searching for upgrade path to: [susemanager-schema-4.1.5] Searching for start path: [susemanager-schema-4.0.13-400] Searching for start path: [susemanager-schema-4.0.13] The path: [susemanager-schema-4.0.13] -> [susemanager-schema-4.0.14] -> [susemanager-schema-4.1.0] -> [susemanager-schema-4.1.1] -> [susemanager-schema-4.1.2] -> [susemanager-schema-4.1.3] -> [susemanager-schema-4.1.4] -> [susemanager-schema-4.1.5] Planning to run schema upgrade with dir '/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721' Hit Enter to continue or Ctrl+C to interrupt: Executing spacewalk-sql, the log is in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log]. (22/26) apply upgrade [susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql] sql.postgresql] Upgrade failed, please see log [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log]. You can fix the failed migration in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721] and run spacewalk-schema-upgrade again The last element in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log shows: ?column? ------------------------------------------------------------------------------------------------ susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql (1 row) psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun". ================== started: 2020-03-27 13:40:57 ================== SQL> select 'susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql' from dual; DELETE FROM rhnTaskoTemplate WHERE bunch_id = (SELECT id FROM rhnTaskoBunch WHERE name='mgr-register-bunch') AND task_id = (SELECT id FROM rhnTaskoTask WHERE name='mgr-register'); DELETE FROM rhnTaskoTask WHERE name = 'mgr-register'; DELETE FROM rhnTaskoSchedule WHERE job_label = 'mgr-register-default'; DELETE FROM rhnTaskoBunch WHERE name = 'mgr-register-bunch'; commit; ?column? ------------------------------------------------------------------------------------------------ susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql (1 row) psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun". Did I made a mistake or is there a solution for the problem? Greets Torsten -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Oh sorry... Just saw, that it stopped in the middle... sent from my mobile device -------- Originale Nachricht -------- Von: "Haupt, Torsten" <torsten.haupt@lhw.mlu.sachsen-anhalt.de> Gesendet: Fri Mar 27 14:34:32 GMT+01:00 2020 An: "uyuni-users@opensuse.org" <uyuni-users@opensuse.org> Betreff: [uyuni-users] Update Uyuni 4.0.2 to current version Hi, I tried to update my Uyuni installation from 4.0.2 to 2020.03 (the current version). I did " spacewalk-service stop", changed the repo and made a zypper update. After that I startet the postgresql database and tried the schema upgrade. But the upgrade didn't finished succesfully: Schema upgrade: [susemanager-schema-4.0.13-400.3.1.uyunimaster] -> [susemanager-schema-4.1.5-1.1.uyuni] Searching for upgrade path to: [susemanager-schema-4.1.5-1] Searching for upgrade path to: [susemanager-schema-4.1.5] Searching for start path: [susemanager-schema-4.0.13-400] Searching for start path: [susemanager-schema-4.0.13] The path: [susemanager-schema-4.0.13] -> [susemanager-schema-4.0.14] -> [susemanager-schema-4.1.0] -> [susemanager-schema-4.1.1] -> [susemanager-schema-4.1.2] -> [susemanager-schema-4.1.3] -> [susemanager-schema-4.1.4] -> [susemanager-schema-4.1.5] Planning to run schema upgrade with dir '/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721' Hit Enter to continue or Ctrl+C to interrupt: Executing spacewalk-sql, the log is in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log]. (22/26) apply upgrade [susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql] sql.postgresql] Upgrade failed, please see log [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log]. You can fix the failed migration in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721] and run spacewalk-schema-upgrade again The last element in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log shows: ?column? ------------------------------------------------------------------------------------------------ susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql (1 row) psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun". ================== started: 2020-03-27 13:40:57 ================== SQL> select 'susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql' from dual; DELETE FROM rhnTaskoTemplate WHERE bunch_id = (SELECT id FROM rhnTaskoBunch WHERE name='mgr-register-bunch') AND task_id = (SELECT id FROM rhnTaskoTask WHERE name='mgr-register'); DELETE FROM rhnTaskoTask WHERE name = 'mgr-register'; DELETE FROM rhnTaskoSchedule WHERE job_label = 'mgr-register-default'; DELETE FROM rhnTaskoBunch WHERE name = 'mgr-register-bunch'; commit; ?column? ------------------------------------------------------------------------------------------------ susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql (1 row) psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun". Did I made a mistake or is there a solution for the problem? Greets Torsten -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Hello, In may case I had to truncate the table "rhntaskorun" (clean all lines) and schema-update worked. Yes a lose tasks history but is OK for me. Cristian Gherman On 3/27/20 4:03 PM, Robert Paschedag wrote:
Oh sorry... Just saw, that it stopped in the middle...
sent from my mobile device
-------- Originale Nachricht -------- Von: "Haupt, Torsten" <torsten.haupt@lhw.mlu.sachsen-anhalt.de> Gesendet: Fri Mar 27 14:34:32 GMT+01:00 2020 An: "uyuni-users@opensuse.org" <uyuni-users@opensuse.org> Betreff: [uyuni-users] Update Uyuni 4.0.2 to current version
Hi,
I tried to update my Uyuni installation from 4.0.2 to 2020.03 (the current version). I did " spacewalk-service stop", changed the repo and made a zypper update. After that I startet the postgresql database and tried the schema upgrade. But the upgrade didn't finished succesfully:
Schema upgrade: [susemanager-schema-4.0.13-400.3.1.uyunimaster] -> [susemanager-schema-4.1.5-1.1.uyuni] Searching for upgrade path to: [susemanager-schema-4.1.5-1] Searching for upgrade path to: [susemanager-schema-4.1.5] Searching for start path: [susemanager-schema-4.0.13-400] Searching for start path: [susemanager-schema-4.0.13] The path: [susemanager-schema-4.0.13] -> [susemanager-schema-4.0.14] -> [susemanager-schema-4.1.0] -> [susemanager-schema-4.1.1] -> [susemanager-schema-4.1.2] -> [susemanager-schema-4.1.3] -> [susemanager-schema-4.1.4] -> [susemanager-schema-4.1.5] Planning to run schema upgrade with dir '/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721' Hit Enter to continue or Ctrl+C to interrupt: Executing spacewalk-sql, the log is in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log]. (22/26) apply upgrade [susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql] sql.postgresql] Upgrade failed, please see log [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log]. You can fix the failed migration in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721] and run spacewalk-schema-upgrade again
The last element in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanager-schema-4.1.5.log shows: ?column? ------------------------------------------------------------------------------------------------ susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql (1 row)
psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun". ================== started: 2020-03-27 13:40:57 ================== SQL> select 'susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql' from dual; DELETE FROM rhnTaskoTemplate WHERE bunch_id = (SELECT id FROM rhnTaskoBunch WHERE name='mgr-register-bunch') AND task_id = (SELECT id FROM rhnTaskoTask WHERE name='mgr-register'); DELETE FROM rhnTaskoTask WHERE name = 'mgr-register'; DELETE FROM rhnTaskoSchedule WHERE job_label = 'mgr-register-default'; DELETE FROM rhnTaskoBunch WHERE name = 'mgr-register-bunch'; commit;
?column? ------------------------------------------------------------------------------------------------ susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register-task.sql.postgresql (1 row)
psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun".
Did I made a mistake or is there a solution for the problem?
Greets Torsten -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Hi Am Freitag, 27. März 2020, 14:34:32 CET schrieb Haupt, Torsten:
Hi,
I tried to update my Uyuni installation from 4.0.2 to 2020.03 (the current version). I did " spacewalk-service stop", changed the repo and made a zypper update. After that I startet the postgresql database and tried the schema upgrade. But the upgrade didn't finished succesfully:
[...]
The last element in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to-susemanag er-schema-4.1.5.log shows: ?column? ---------------------------------------------------------------------------- -------------------- susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register- task.sql.postgresql (1 row)
psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun". ================== started: 2020-03-27 13:40:57 ================== SQL> select 'susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr-register -task.sql.postgresql' from dual; DELETE FROM rhnTaskoTemplate WHERE bunch_id = (SELECT id FROM rhnTaskoBunch WHERE name='mgr-register-bunch') AND task_id = (SELECT id FROM rhnTaskoTask WHERE name='mgr-register'); DELETE FROM rhnTaskoTask WHERE name = 'mgr-register'; DELETE FROM rhnTaskoSchedule WHERE job_label = 'mgr-register-default'; DELETE FROM rhnTaskoBunch WHERE name = 'mgr-register-bunch'; commit;
Hmm, seems we forgot to cleanup a table. Thanks for reporting. I made a PR which should fix it for others in future: https://github.com/uyuni-project/uyuni/pull/2071 If your server is still at this point, you can download the new version of that file (Files -> View File -> RAW) and copy it on your server at /etc/sysconfig/rhn/schema-upgrade/susemanager-schema-4.1.3-to-susemanager- schema-4.1.4/004-drop-mgr-register-task.sql.postgresql After this call "spacewalk-schema-upgrade" again and it should continue with the upgrade. -- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Hi, and thanks to all. The new scripts works. Greets Torsten
-----Original Message----- From: Michael Calmer [mailto:mc@suse.de] Sent: Saturday, March 28, 2020 2:37 PM To: uyuni-users@opensuse.org Subject: [EXTERN] Re: [uyuni-users] Update Uyuni 4.0.2 to current version
Hi
Am Freitag, 27. März 2020, 14:34:32 CET schrieb Haupt, Torsten:
Hi,
I tried to update my Uyuni installation from 4.0.2 to 2020.03 (the current version). I did " spacewalk-service stop", changed the repo and made a zypper update. After that I startet the postgresql database and tried the schema upgrade. But the upgrade didn't finished succesfully:
[...]
The last element in [/var/log/spacewalk/schema-upgrade/schema-from-20200327-142721-to- suse manag er-schema-4.1.5.log shows: ?column? ---------------------------------------------------------------------- ------ -------------------- susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr- regi ster- task.sql.postgresql (1 row)
psql:<stdin>:4: ERROR: update or delete on table "rhntaskotemplate" violates foreign key constraint "rhn_tasko_run_template_fk" on table "rhntaskorun" DETAIL: Key (id)=(18) is still referenced from table "rhntaskorun". ================== started: 2020-03-27 13:40:57 ================== SQL> select 'susemanager-schema-4.1.3-to-susemanager-schema-4.1.4/004-drop-mgr- reg ister -task.sql.postgresql' from dual; DELETE FROM rhnTaskoTemplate WHERE bunch_id = (SELECT id FROM rhnTaskoBunch WHERE name='mgr-register-bunch') AND task_id = (SELECT id FROM rhnTaskoTask WHERE name='mgr-register'); DELETE FROM rhnTaskoTask WHERE name = 'mgr-register'; DELETE FROM rhnTaskoSchedule WHERE job_label = 'mgr-register-default'; DELETE FROM rhnTaskoBunch WHERE name = 'mgr- register-bunch'; commit;
Hmm, seems we forgot to cleanup a table. Thanks for reporting.
I made a PR which should fix it for others in future:
https://github.com/uyuni-project/uyuni/pull/2071
If your server is still at this point, you can download the new version of that file (Files -> View File -> RAW) and copy it on your server at
/etc/sysconfig/rhn/schema-upgrade/susemanager-schema-4.1.3-to- susemanager- schema-4.1.4/004-drop-mgr-register-task.sql.postgresql
After this call "spacewalk-schema-upgrade" again and it should continue with the upgrade.
-- Regards
Michael Calmer
-------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
-- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
participants (5)
-
Cristian Gherman -
Haupt, Torsten -
Michael Calmer -
Robert Paschedag -
Thomas Weis