(Note: marking as blocker for server-full based on discussion with Tarek. Feel free to change the Severity as best suits the bug) I was attempting to do a clone and build of server-full in the QA environment today (the Sync6 VM): sync6.mtv1.dev.svc.mozilla.com Performed the following basic steps (not using the channel option): hg clone https://hg.mozilla.org/services/server-full cd server-full make build bin/easy_install MySQL-Python Due to a separate known issue (https://bugzilla.mozilla.org/show_bug.cgi?id=686753), the "make build" step must be run twice. When I attempted to start the server, I started getting errors and trackback in STDOUT/STDERR: http://jbonacci.pastebin.mozilla.org/1357841 On the browser side, in the sync log, I started getting NS_ERROR_UNKNOWN_HOST errors and apparent 500: http://jbonacci.pastebin.mozilla.org/1357840 The issue appears to be that pinning is not working for Prod channel, so the WebOb version is wrong ls lib/python2.6/site-packages/ | grep WebOb Gives me WebOb-1.1.1-py2.6.egg-info or WebOb-1.2b2-py2.6.egg-info but not WebOb-1.0.7-py2.6.egg Workaround: bin/easy_install -U WebOb==1.0.7 I do a new clone and (double) build and run the WebOb install... After workaround: ls lib/python2.6/site-packages/ | grep WebOb Gives me WebOb-1.0.7-py2.6.egg WebOb-1.2b2-py2.6.egg-info IRC debug and discusson on #services: http://jbonacci.pastebin.mozilla.org/1357855
Right now the pastebins are set for 30 days. Let me know if you want them converted to text attachments.
Created attachment 571635 [details] [diff] [review] fixes the pinning
Assignee: nobody → tarek
Status: NEW → ASSIGNED
Attachment #571635 - Flags: review?(vng)
Comment on attachment 571635 [details] [diff] [review] fixes the pinning Review of attachment 571635 [details] [diff] [review]: ----------------------------------------------------------------- patch reviewed and tested on my local machine
Attachment #571635 - Flags: review?(vng) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Verified as fixed with the very latest pull from HG.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.