Closed Bug 1695940 (bmo-release-20210302.1) Opened 5 years ago Closed 5 years ago

push updated bugzilla.mozilla.org live: mozillabteam/bmo:release-20210302.1

Categories

(bugzilla.mozilla.org :: Infrastructure, task)

Product:
bugzilla.mozilla.org
Component:
Infrastructure
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
bmo-push accept production

People

(Reporter: dkl, Assigned: bobm)

Details

changes

revisions: 45e4047be - d102cc3c7
bug 1693171 : "See Also" field to link to pocket issues
bug 1693908 : [WEBHOOKS] Align field names and data structure with that of the REST API where currently not aligned
bug 1693860 : [WEBHOOKS] The Webhook push connector needs to return more details when an error occurs instead of just the code
bug 1694806 : [WEBHOOKS] Bugzilla Webhook Setup: Appears to add Space to end of URL
bug 1694803 : [WEBHOOKS] Bugzilla Webhook Documentation: Requests/Schema Update
bug 1695739 : "Team Name" search doesn't work

version.json

{
   "build" : "https://circleci.com/gh/mozilla-bteam/bmo/31107",
   "commit" : "7adb94323bab34a5bd59a8d45fd58a3c16b78199",
   "source" : "https://github.com/mozilla-bteam/bmo",
   "version" : "20210302.1"
}
Assignee: nobody → bobm
Status: NEW → ASSIGNED
status-bmo-push: --- → development
tracking-bmo-push: --- → verify?
Flags: needinfo?(dkl)

Now getting the following in dev:

Mar 03 16:00:35 ip-172-31-46-113 docker-bugzilla[18214]: /usr/bin/docker: Error response from daemon: failed to initialize logging driver: dial tcp 127.0.0.1:24224: connect: connection refused.
Mar 03 16:00:35  docker-bugzilla[18214]: time="2021-03-03T16:00:35Z" level=error msg="error waiting for container: context canceled"
Mar 03 16:00:35  systemd[1]: docker-bugzilla.service: main process exited, code=exited, status=125/n/a
Mar 03 16:00:35  docker-bugzilla[18323]: bugzilla
Mar 03 16:00:36  docker-bugzilla[18335]: bugzilla
Mar 03 16:00:36  systemd[1]: Unit docker-bugzilla.service entered failed state.
Mar 03 16:00:36  systemd[1]: docker-bugzilla.service failed.

Because fluentd hadn't started. After starting it, it was able to load. This seems like a fluke, but will add something to make sure fluentd is running before starting the service container.

There also appears to be a problem promoting a new stack over a broken stack in dev. I've manually promoted a working one.

Ok dev has passed QA. We are ready for move to stage.

Flags: needinfo?(dkl) → needinfo?(bobm)
status-bmo-push: development → staging
tracking-bmo-push: accept → verify?
Flags: needinfo?(bobm) → needinfo?(dkl)

Stage is good. On to prod.

tracking-bmo-push: verify? → accept
Flags: needinfo?(dkl) → needinfo?(bobm)

Production deployment complete.

status-bmo-push: staging → production
tracking-bmo-push: accept → verify?
Flags: needinfo?(bobm) → needinfo?(dkl)

All done.

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
tracking-bmo-push: verify? → accept
Flags: needinfo?(dkl)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.