Closed
Bug 1497291
Opened 7 years ago
Closed 7 years ago
Assign reboot failure bugs to RelOps not DCOps
Categories
(Infrastructure & Operations Graveyard :: RelOps: Roller, task)
Infrastructure & Operations Graveyard
RelOps: Roller
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dhouse, Assigned: dhouse)
Details
Attachments
(2 files)
|
74 bytes,
text/x-github-pull-request
|
dhouse
:
checked-in+
|
Details | Review |
|
55 bytes,
text/x-github-pull-request
|
dhouse
:
checked-in+
|
Details | Review |
Re: https://bugzilla.mozilla.org/show_bug.cgi?id=1495250#c4
We have started seeing more problems that break reboot/startup but are not issues for DCOps to work on.
We can change roller to assign the "reboot failed" bugs to RelOps instead of DCOps. Then RelOps can redirect the bug to DCOps if there is a problem we cannot resolve and need physical/DC assistance.
Comment 1•7 years ago
|
||
Could we set this up to automatically cc me on the bug?
(In reply to Mark Cornmesser [:markco] from comment #1)
> Could we set this up to automatically cc me on the bug?
If the bugs get assigned to "Relops: Hardware", would watching that component be enough? If not, I'll add a list into puppet to set who gets a cc on the bugs.
Flags: needinfo?(mcornmesser)
Attachment #9030320 -
Attachment description: GitHub Pull Request → roller code changes
Attachment #9030320 -
Flags: checked-in+
I confirmed the "host unreachable" bugs are being assigned to the RelOps: Hardware component now instead of DCOps. (https://bugzilla.mozilla.org/show_bug.cgi?id=1513579)
Attachment #9030484 -
Flags: checked-in+
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•