[socorro-crashstats] Remove BZAPI_BASE_URL in settings/local.py on stage and prod

RESOLVED FIXED

Status

RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: peterbe, Assigned: cturra)

Tracking

Details

(Whiteboard: [push interrupt])

(Reporter)

Description

5 years ago
Change::

  BZAPI_BASE_URL = 'https://api-dev.bugzilla.mozilla.org/1.1'

To::

  BZAPI_BASE_URL = 'https://api-dev.bugzilla.mozilla.org/1.3'

in settings/local.py

I've already done it for dev.
(Reporter)

Updated

5 years ago
Blocks: 867603
(Assignee)

Comment 1

5 years ago
i have pushed this change to stage. let me know when you're ready for this to go to prod.
Assignee: server-ops-webops → cturra
Flags: needinfo?(peterbe)
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [push interrupt]
(Reporter)

Comment 2

5 years ago
I changed the title of the bug.

From now on, BZAPI_BASE_URL is set in settings/base.py so we need to remove it from settings/local.py on stage and prod.


Please do NOT restart apache after you have removed this from settings/local.py because the relevant change just landed in master https://github.com/mozilla/socorro-crashstats/commit/4afdc152bbf92cf751a46a577752005fa1ee0b48 and we have no way to upgrade stage and prod. 
So, once we do an upgrade to stage or prod we will have this change in place and then it's safe to kick apache.
Flags: needinfo?(peterbe)
Summary: [socorro-crashstats] Change BZAPI_BASE_URL in settings/local.py on stage and prod → [socorro-crashstats] Remove BZAPI_BASE_URL in settings/local.py on stage and prod
(Assignee)

Comment 3

5 years ago
i have removed the BZAPI_BASE_URL from the local.py file in stage, but am hesitant to land this change in prod until we're ready with the code. there are any number of reasons why apache /could/ be restarted and i don't want to chance that in production.
(Reporter)

Comment 4

5 years ago
(In reply to Chris Turra [:cturra] from comment #3)
> i have removed the BZAPI_BASE_URL from the local.py file in stage, but am
> hesitant to land this change in prod until we're ready with the code. there
> are any number of reasons why apache /could/ be restarted and i don't want
> to chance that in production.

Good thinking. I know it hurts but I suspect we're going to have to leave this open like this until we get a neat way of upgrading socorro-crashstats.
(Assignee)

Comment 5

5 years ago
:peterbe - any updates on this?
Flags: needinfo?(peterbe)
(Reporter)

Comment 6

5 years ago
I was away on paternity leave. I think stage and prod have been upgraded since. Is it possible to check when they were upgraded?

Most likely you can proceed with this change on prod. The code landed in master many weeks ago now.
Flags: needinfo?(peterbe)
(Assignee)

Comment 7

5 years ago
thnx for the update :peterbe. i have completed this in production.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.