Closed Bug 1270271 Opened 9 years ago Closed 9 years ago

Please deploy shavar 0.7 to STAGE

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Product:
Cloud Services
Component:
Operations: Deployment Requests - DEPRECATED
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: rpapa, Assigned: ckolos)

References

Details

Assignee: nobody → ckolos
Status: NEW → ASSIGNED
QA Contact: rpappalardo
Deployed to stage.

curl -k https://shavar.stage.mozaws.net/__version__
{"commit":"6b5ffd3a78da793e3830faf913a99293b07e0ea5","version":"0.7","source":"https://github.com/mozilla-services/shavar.git"}
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
QA Contact: rpappalardo → rbillings
================================
STACK-CHECK (STAGE)
================================

TEST ENVIRONMENT: stage

-----------------------------
DOWNLOAD LISTS
-----------------------------

STAGE - shavar.stage.mozaws.net

mozfull-track-digest256
mozfullstaging-track-digest256
mozplugin-block-digest256
mozplugin2-block-digest256
mozpub-track-digest256
mozstd-track-digest256
mozstd-trackwhite-digest256
mozstdstaging-track-digest256
mozstdstaging-trackwhite-digest256
moztestpub-track-digest256
moztestpub-trackwhite-digest256


-----------------------------
LIST: MOZPUB
-----------------------------

RESPONSE:

n:3600
i:mozpub-track-digest256
u:tracking-protection.stage.mozaws.net/mozpub-track-digest256/1458773165

EXAMPLE RESPONSE:

n:3600
i:mozpub-track-digest256
u:tracking-protection.stage.mozaws.net/mozpub-track-digest256/1442275596


-----------------------------
LIST: MOZSTD
-----------------------------

RESPONSE:

n:3600
i:mozstd-track-digest256
u:tracking-protection.stage.mozaws.net/mozstd-track-digest256/1458773165

EXAMPLE RESPONSE:

n:3600
i:mozstd-track-digest256
u:tracking-protection.stage.mozaws.net/mozstd-track-digest256/1442275596


-----------------------------
LIST: MOZSTDSTAGING
-----------------------------

RESPONSE:

n:3600
i:mozstdstaging-track-digest256
u:tracking-protection.stage.mozaws.net/mozstdstaging-track-digest256/1455641165

EXAMPLE RESPONSE:

n:3600
i:mozstdstaging-track-digest256
u:tracking-protection.stage.mozaws.net/mozstdstaging-track-digest256/1442275596


-----------------------------
LIST: MOZFULL
-----------------------------

RESPONSE:

n:3600
i:mozfull-track-digest256
u:tracking-protection.stage.mozaws.net/mozfull-track-digest256/1458773165

EXAMPLE RESPONSE:

n:3600
i:mozfull-track-digest256
u:tracking-protection.stage.mozaws.net/mozfull-track-digest256/1442275596


-----------------------------
LIST: MOZFULLSTAGING
-----------------------------

RESPONSE:

n:3600
i:mozfullstaging-track-digest256
u:tracking-protection.stage.mozaws.net/mozfullstaging-track-digest256/1455641165

EXAMPLE RESPONSE:

n:3600
i:mozfullstaging-track-digest256
u:tracking-protection.stage.mozaws.net/mozfullstaging-track-digest256/1442275596
Depends on: 1274685
working on issue blocking client-side verification:
Bug 1274685 - Unowned Safe Browsing tables break list updates

server-side tests seem to be OK so, we'll proceed with loadtesting this week.
(In reply to Richard Pappalardo [:rpapa][:rpappalardo] from comment #3)
> working on issue blocking client-side verification:
> Bug 1274685 - Unowned Safe Browsing tables break list updates
> 
> server-side tests seem to be OK so, we'll proceed with loadtesting this week.

:francois, is there anything else I can try or are we waiting on a fix before we can proceed?
Flags: needinfo?(francois)
(In reply to Richard Pappalardo [:rpapa][:rpappalardo] from comment #4)
> :francois, is there anything else I can try or are we waiting on a fix
> before we can proceed?

Now that we've identified the problem, we should be able to work around it and not have to wait for a fix.
Flags: needinfo?(francois)
(In reply to François Marier [:francois] from comment #5)
> (In reply to Richard Pappalardo [:rpapa][:rpappalardo] from comment #4)
> > :francois, is there anything else I can try or are we waiting on a fix
> > before we can proceed?
> 
> Now that we've identified the problem, we should be able to work around it
> and not have to wait for a fix.

:francois, ok great.  I assume this prob means changing the prefs a bit.  Let me know once you have an idea what I can try or, if it's easier, we can scheduling a working session to get it going.
:fmarier, it looks like with the new pref set you checked into services-test, I'm now able to successfully download (at least) the moz[test]pub files using both the STAGE and PROD shavar servers.   Though interestingly, on the very first try with Nightly on STAGE, the browser "hung" at the same step it was before and no moztestpub files were downloaded on that run.  
I wonder if there may be an intermittent race condition of some kind??
results here:
https://docs.google.com/spreadsheets/d/1UkmDo_fasNVwM5JQ0JkHvEMprTPlWnZqYIAr3-tnuDA/edit#gid=439592498

Anyway, I haven't yet tested the other pref sets (mozstd, mozstaging, etc.).  Should we go ahead and proceed with the rest of the client-side verification? or are there further things you'd like to investigate/change before we proceed?
Flags: needinfo?(francois)
(In reply to Richard Pappalardo [:rpapa][:rpappalardo] from comment #7)
> Anyway, I haven't yet tested the other pref sets (mozstd, mozstaging, etc.).
> Should we go ahead and proceed with the rest of the client-side
> verification? or are there further things you'd like to investigate/change
> before we proceed?

As discussed in person, the rest of the verification should proceed and a new bug should be filed against Toolkit::Safe Browsing with a copy of the profile that hung.
Flags: needinfo?(francois)
Will do.  thanks, :francois!

filed:
Bug 1277096 - Intermittent hang when registering with shavar server
Closing this out to deploy new stack w/ config changes

SEE:
Bug 1283570 - Please re-deploy shavar 0.7 to STAGE - CONFIG CHANGES
Resolution: FIXED → WONTFIX
You need to log in before you can comment on or make changes to this bug.