Learn more about these different git repos.
Other Git URLs
Apr 08 17:43:08 koji kojira[3783067]: 2022-04-08 17:43:08,383 [WARNING] {3783067} koji.repo.regen:734 Tag name/id mismatch: directory: privatecloud-el8-build, name: tools-kernel-el7-build, id: 45 Apr 08 17:43:08 koji kojira[3783067]: 2022-04-08 17:43:08,392 [WARNING] {3783067} koji.repo.regen:734 Tag name/id mismatch: directory: openstack-victoria-el8-build, name: openstack-train-el7-build, id: 48 Apr 08 17:43:08 koji kojira[3783067]: 2022-04-08 17:43:08,403 [WARNING] {3783067} koji.repo.regen:734 Tag name/id mismatch: directory: openstack-victoria-el8-build, name: tools-kernel-el8-build-side-37, id: 48 Apr 08 17:43:08 koji kojira[3783067]: 2022-04-08 17:43:08,413 [WARNING] {3783067} koji.repo.regen:734 Tag name/id mismatch: directory: privatecloud-c8s-build, name: tools-kernel-el8-build, id: 51 Apr 08 17:43:08 koji kojira[3783067]: 2022-04-08 17:43:08,421 [WARNING] {3783067} koji.repo.regen:734 Tag name/id mismatch: directory: privatecloud-c8s-build, name: tools-kernel-el7, id: 51
I don't think I have done anything special to get this one but our logs are full of this =(
Koji: 1.28.0
So, these repos were not renamed? Warning basically says, that repo path is different from what is written in that repo.json file.
Metadata Update from @tkopecek: - Custom field Size adjusted to None
@tkopecek tbh I don't know which ones it is talking about. I don't think I ever manually mocked with any repo.json's - merely just changing names of external repos or their URLs, but my guess is that it would not care about some 3+month old ones.
/mnt/koji/repos/privatecloud-el8-build vs contents of /mnt/koji/repos/privatecloud-el8-build/<repo>/repo.json
/mnt/koji/repos/privatecloud-el8-build
/mnt/koji/repos/privatecloud-el8-build/<repo>/repo.json
Manual change is not the source here. There is some problem that repo was historically created for different tag. It would be good to go through repos in /mnt/koji/repos/privatecloud-el8-build and check when the name of the tag changed to current one or if they are all the same.
ping @ignatenkobrain ?
Metadata Update from @tkopecek: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.