= phenomenon =
During the recent mass branch, not all packages got a F12 branch
= reason =
Unclear
= recommendation =
Further investigation needed but for now I'm going to do each package individually excluding the dead packages.
Packages that are active but not branched. nobranch.txt
Looks like this is the result of the bug where running against the app servers causes some database commits to appear to work but not actually save information into the db. Running against bapp1 instead of admin.fp.o makes this go away.
Mass branch SOP updated with a note to point pkgdb-client at bapp1 for mas branching: https://fedoraproject.org/wiki/Mass_Branching_SOP#Notes_on_Optimization
Also wrote a section on how to use find-unbranched to check whether mass branching looks correct after mass branching is performed. Packages cleaned up.
this doesn't resolve the root cause (finding the bug in TG1/CherryPy-2/SQLAlchemy/PackageDb that's causing this race condition but it does clear up the mass branch situation for this cycle.
Login to comment on this ticket.