Closed
Bug 1043753
Opened 10 years ago
Closed 10 years ago
Nodes marked "backoff" should not be selected for assignment
Categories
(Cloud Services Graveyard :: Server: Token, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rfkelly, Assigned: rfkelly, Mentored)
Details
(Whiteboard: [qa+][good first bug])
Attachments
(1 file)
1.40 KB,
patch
|
telliott
:
review+
|
Details | Diff | Splinter Review |
It's current possible for a new user to be assigned to a node that is marked as "backoff". In theory this means they would get an error as soon as they went to sync with their newly-allocated node, which seems silly. We should filter any of these out during node selection.
Updated•10 years ago
|
Whiteboard: [qa?]
Assignee | ||
Updated•10 years ago
|
Mentor: rfkelly
Whiteboard: [qa?] → [qa?][good first bug]
Assignee | ||
Comment 1•10 years ago
|
||
Assignee: nobody → rfkelly
Attachment #8504404 -
Flags: review?(telliott)
Updated•10 years ago
|
Attachment #8504404 -
Flags: review?(telliott) → review+
Assignee | ||
Comment 2•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 3•10 years ago
|
||
Awesome. Are we planning a TS deployment any time soon?
Perhaps after TS gets moved to the new Dev IAM?
Whiteboard: [qa?][good first bug] → [qa+][good first bug]
Assignee | ||
Comment 4•10 years ago
|
||
Yes, we'll need to do a deploy soon to get these out the door. Bob are handling TS stuff as well these days or should we still coordinate with Benson for TS deploys?
Flags: needinfo?(bobm)
Comment 5•10 years ago
|
||
(In reply to Ryan Kelly [:rfkelly] from comment #4)
> Yes, we'll need to do a deploy soon to get these out the door. Bob are
> handling TS stuff as well these days or should we still coordinate with
> Benson for TS deploys?
Benson's still the primary Op for TS, but given that TS and Sync 1.5 are basically inseparable, perhaps we should change that. We need to stand up a Sync 1.5 staging environment in the new development IAM- I wouldn't mind rolling out TS at the same time. In other words, I'll take the deployment ticket.
Flags: needinfo?(bobm)
Comment 6•10 years ago
|
||
I can open a TS+Verifier Stage deployment ticket, but do we have enough changes to warrant a deploy?
Anything besides this specific fix?
PS: Bob thanks for volunteering.
Flags: needinfo?(rfkelly)
Assignee | ||
Comment 7•10 years ago
|
||
> do we have enough changes to warrant a deploy?
I think we have enough changes to warrant a fresh deploy each of TS, sync, and the verifiers. I'll check my backlog for any other pending sync fixes we should get out, then prep some deployment tickets.
Flags: needinfo?(rfkelly)
Comment 8•10 years ago
|
||
:rfkelly thanks
We just deployed Sync Stage to the new Dev IAM: 1089945
but that was for specific testing
If you want to open a new one for Sync, along with new ones for TS+Verifier and Verifier, go for it
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•