| Issue 1554: | New projects aren't cloneable on slave servers | |
| 3 people starred this issue and may be notified of changes. | Back to list |
************************************************************ ***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW ***** ***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL ***** ***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC. ***** ***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS! ***** ************************************************************ Affected Version: 2.4.2 What steps will reproduce the problem? 0. Stop Gerrit slave, then restart it 1. Create a new project in Gerrit 2. Watch it replicate to a slave. Verify the project is on the slave's disk. 3. Try to clone the project from the slave. 4. Project does not clone, even after the project_list cache timeout has expired. What is the expected output? What do you see instead? I see an error indicating that "project" is not a Gerrit project. Please provide any additional information below. When the project_list cache on a slave has not been populated, a Gerrit slave never learns about new projects that are replicated to it. In order for a slave to learn about new projects, the project_list cache must have data. When it does, then it obeys the project_list cache timeout. Take a running slave, and run this: ssh -p 29418 slave gerrit flush-caches --cache project_list The project_list cache is now empty. Now create a new project on the master, have it replicate to the slave, and it won't be available even after the project_list cache timeout has expired on the slave. It is necessary to do an "ls-projects" to make the slave aware of the project.
Sep 28, 2012
(No comment was entered for this change.)
Status:
Submitted
Sep 28, 2012
(No comment was entered for this change.)
Labels:
FixedIn-2.5
Oct 31, 2012
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |
Owner: gustaf.l...@sonyericsson.com