Bug 2276019 - koji rpm 1.34 contains sql schema upgrade for 1.35
Summary: koji rpm 1.34 contains sql schema upgrade for 1.35
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: koji
Version: epel9
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Mike McLean
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-19 01:57 UTC by opencodesystems
Modified: 2024-10-08 01:48 UTC (History)
3 users (show)

Fixed In Version: koji-1.35.0-1.fc41 koji-1.35.0-1.fc40 koji-1.35.0-1.el9 koji-1.35.0-1.el8 koji-1.35.0-1.fc39
Clone Of:
Environment:
Last Closed: 2024-09-24 00:16:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description opencodesystems 2024-04-19 01:57:35 UTC
Description of problem: 
koji 1.34 rpm contains schema upgrade sql 1.34-1.35


Version-Release number of selected component (if applicable):
koji-1.34.0-3.fc38.noarch

How reproducible:
install/upgrade koji to 1.34.0-3



Actual results:
# ls -la /usr/share/koji/schema-upgrade-1.34-1.35.sql
-rw-r--r-- 1 root root 214 Mar 22 02:00 /usr/share/koji/schema-upgrade-1.34-1.35.sql

# rpm -qf /usr/share/koji/schema-upgrade-1.34-1.35.sql
koji-1.34.0-3.fc38.noarch

# cat /usr/share/koji/schema-upgrade-1.34-1.35.sql
-- upgrade script to migrate the Koji database schema
-- from version 1.33 to 1.34

BEGIN;

CREATE INDEX CONCURRENTLY IF NOT EXISTS rpminfo_nvra
    ON rpminfo(name,version,release,arch,external_repo_id);

COMMIT;


Expected results:
There should be no such sql , or its content should be added in schema-upgrade-1.33-1.34 and fixed to be actually working.


Additional info:
I have tried to apply it, but it fails:
# psql koji koji < /usr/share/koji/schema-upgrade-1.34-1.35.sql
BEGIN
ERROR:  CREATE INDEX CONCURRENTLY cannot run inside a transaction block
ROLLBACK

Comment 1 Fedora Update System 2024-09-22 17:16:29 UTC
FEDORA-2024-97bb089724 (koji-1.35.0-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-97bb089724

Comment 2 Fedora Update System 2024-09-22 17:16:30 UTC
FEDORA-2024-dad2d56011 (koji-1.35.0-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-dad2d56011

Comment 3 Fedora Update System 2024-09-22 17:16:31 UTC
FEDORA-EPEL-2024-812b8e317f (koji-1.35.0-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-812b8e317f

Comment 4 Fedora Update System 2024-09-22 17:16:32 UTC
FEDORA-2024-89201f2d14 (koji-1.35.0-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-89201f2d14

Comment 5 Fedora Update System 2024-09-23 01:46:00 UTC
FEDORA-2024-97bb089724 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-97bb089724`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-97bb089724

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-09-23 01:57:29 UTC
FEDORA-EPEL-2024-310a77c93b has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-310a77c93b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2024-09-23 02:03:44 UTC
FEDORA-EPEL-2024-812b8e317f has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-812b8e317f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2024-09-23 02:08:45 UTC
FEDORA-2024-89201f2d14 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-89201f2d14`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-89201f2d14

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2024-09-23 02:49:32 UTC
FEDORA-2024-dad2d56011 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-dad2d56011`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-dad2d56011

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2024-09-24 00:16:31 UTC
FEDORA-2024-89201f2d14 (koji-1.35.0-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2024-09-24 01:31:34 UTC
FEDORA-2024-dad2d56011 (koji-1.35.0-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2024-10-01 02:17:15 UTC
FEDORA-EPEL-2024-310a77c93b (koji-1.35.0-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2024-10-01 02:40:58 UTC
FEDORA-EPEL-2024-812b8e317f (koji-1.35.0-1.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2024-10-08 01:48:33 UTC
FEDORA-2024-97bb089724 (koji-1.35.0-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.