#1506 AltImage Images failling with odd error
Closed: Fixed with Explanation by arrfab. Opened by tdawson.

I am trying to do this quarters Alternative Images images, but the image builds are failing with a strange error:
"FAILED: GenericError: multiple matches for file extension: "
where is either sha256, packages, verified, or changes.xz ... the most common is sha256
This is happening after, what appears to be a successful image build.

Here are some examples.
* https://cbs.centos.org/koji/taskinfo?taskID=4240542
* https://cbs.centos.org/koji/taskinfo?taskID=4240519
* https://cbs.centos.org/koji/taskinfo?taskID=4240520
* https://cbs.centos.org/koji/taskinfo?taskID=4240524
* https://cbs.centos.org/koji/taskinfo?taskID=4240525


@tkopecek : any idea ? worth knowing that koji was updated to 1.34 (from 1.31) recently .
I read the koji release notes and saw that there were fixes for kiwi but no introduced breaking change.
Do you have an idea ? Do you prefer a ticket on koji issue tracker ?

Metadata Update from @arrfab:
- Issue priority set to: Waiting on External (was: Needs Review)
- Issue tagged with: blocked, cbs, centos-build-pipeline, high-gain, investigation, medium-trouble

@tkopecek : it seems one migration script created some duplicates :

From the archivetypes tables (just last entries):

 55 | kiwi-checksum    | Kiwi package list checksum                                         | sha256                                      | 
 56 | kiwi-changes     | Kiwi changes file                                                  | changes.xz changes                          | 
 57 | kiwi-packages    | Kiwi packages listing                                              | packages                                    | 
 58 | kiwi-verified    | Kiwi verified package list                                         | verified                                    | 
 51 | vhdx-compressed  | Compressed VHDx image                                              | vhdx.gz vhdx.xz                             | 
 59 | checksum         | Checksum file                                                      | sha256                                      | 
 60 | changes          | Kiwi changes file                                                  | changes.xz changes                          | 
 61 | packages         | Kiwi packages listing                                              | packages                                    | 
 62 | verified         | Kiwi verified package list                                         | verified                                    | 

So it seems we had to enter initially the missing entries for kiwi to work on 1.31 but the https://pagure.io/koji/blob/master/f/schemas/schema-upgrade-1.32-1.33.sql was then adding new one with different name but same description/extension

I guess it's safe to just remove the previous ones ?

Metadata Update from @arrfab:
- Issue assigned to arrfab

I just wanted to eventually remove duplicates but it doesn't work :

koji=> delete from archivetypes where name='kiwi-checksum';
ERROR:  update or delete on table "archivetypes" violates foreign key constraint "archiveinfo_type_id_fkey" on table "archiveinfo"
DETAIL:  Key (id)=(55) is still referenced from table "archiveinfo".

@tkopecek we'd probably need your help for this one

I see the relationship in the archiveinfo table so can't delete the existing type_id , so instead I just removed id 59,60,61 and 62 from the archivetypes.

@tdawson : can you give it another try now ?

@tdawson : fwiw, I just resubmitted your first build and it worked :
https://cbs.centos.org/koji/taskinfo?taskID=4241647

but as I resubmitted as service user cbs-koji it has able to build but not tag it to your altimages9s-images-live-candidate tag. You can do that yourself now and also resubmit your other builds, but clearly it now works .

I have verified that the builds are working, and are being properly tagged when I build them.
This can be closed.
Thank you for everyone's work on getting this fixed so quickly.

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

It is already closed, so just confirming that deleting new ones was the right thing to do.

Log in to comment on this ticket.

Metadata