Closed
Bug 1412209
Opened 8 years ago
Closed 8 years ago
Determine why production flipped to using BMO staging
Categories
(Conduit :: Phabricator, defect, P1)
Conduit
Phabricator
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: zalun, Assigned: ckolos)
Details
Changed just the description of the D157.
On [Save changes] Phabricator displayed an error:
Bugzilla Bug ID: Bugzilla did not provide an expected response (28).
| Reporter | ||
Updated•8 years ago
|
Summary: Unable to update revision → Unable to edit revision
| Reporter | ||
Comment 1•8 years ago
|
||
Same error on `arc diff`:
[2017-10-27 10:31:26] EXCEPTION: (ArcanistDifferentialCommitMessageParserException) Invalid or missing field "Bug #": Bugzilla Bug ID: Bugzilla did not provide an expected response (28). at [<arcanist>/src/differential/ArcanistDifferentialCommitMessage.php:54]
arcanist(), phutil()
I can't replicate it locally.
| Reporter | ||
Comment 2•8 years ago
|
||
Moving the bug to the Bugzilla API component.
I believe the error is coming from `/rest/phabbugz/check_bug/` endpoint.
Component: Phabricator Extensions → API
Product: Conduit → bugzilla.mozilla.org
Version: unspecified → Production
| Reporter | ||
Updated•8 years ago
|
Summary: Unable to edit revision → Unable to get data from /rest/phabbugz/check_bug/ endpoint
Updated•8 years ago
|
Component: API → Extensions: PhabBugz
| Reporter | ||
Comment 3•8 years ago
|
||
Phabricator was canfigured to use dev Bugzilla servers.
Component: Extensions: PhabBugz → Phabricator Extensions
Product: bugzilla.mozilla.org → Conduit
Version: Production → unspecified
Comment 4•8 years ago
|
||
Staging, technically.
Comment 6•8 years ago
|
||
We're not sure what happened, though.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Unable to get data from /rest/phabbugz/check_bug/ endpoint → Determine why production flipped to using BMO staging
Updated•8 years ago
|
Assignee: nobody → ckolos
Status: REOPENED → ASSIGNED
Comment 7•8 years ago
|
||
Some extra info to help with debugging:
Phabricator code was changed while back to default to https://bugzilla.allizom.org for the bugzilla.url config value. So if Phab is installed and puppet or an ENV var used by entrypoint.sh is not used to change the config value, that is what will be used. So in the recent deployment of production Phab, somehow the setting was not updated properly and the default remained.
| Assignee | ||
Comment 8•8 years ago
|
||
Which ENV var should be passed to the container to configure this setting?
Comment 9•8 years ago
|
||
(In reply to Chris Kolosiwsky [:ckolos] from comment #8)
> Which ENV var should be passed to the container to configure this setting?
Fom mozphabs entrypoint.sh:
test -n "${BUGZILLA_URL}" \
&& ./bin/config set bugzilla.url "${BUGZILLA_URL}"
| Assignee | ||
Comment 10•8 years ago
|
||
Updated in our puppet code for deployment.
Updated•8 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•