Description of problem: It seems that lately, bugzilla numbers for new bugzillas are generated with increment of 10, not increment of 1. Version-Release number of selected component (if applicable): 2.18 (the current one). How reproducible: Looking at the bugzillas create in October 2007. Steps to Reproduce: 1. https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&version=&component=&target_milestone=&query_format=advanced&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&fixed_in_type=allwordssubstr&fixed_in=&qa_whiteboard_type=allwordssubstr&qa_whiteboard=&devel_whiteboard_type=allwordssubstr&devel_whiteboard=&keywords_type=allwords&keywords=&cust_facing=&cust_facing_type=substring&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-10-01&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Actual results: All bugzilla numbers end with 1. Expected results: I'd expect us not to waste the bugzilla numbers so much. Additional info:
With our new move to a replicated MySQL server environment, we had to change the increment value to 20. This allows future growth when dealing with master to master server replication. So this would explain what you are seeing.