Closed
      
        Bug 1102627
          (b-2008-ix-0019)
      
      
        Opened 10 years ago
          Closed 10 years ago
      
        
    
  
b-2008-ix-0019 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
        Infrastructure & Operations Graveyard
          
        
        
      
        
    
        CIDuty
          
        
        
      
        
    
        
            x86_64
        
    
  
        
            Windows Server 2008
        
    
  
Tracking
(Not tracked)
        RESOLVED
        FIXED
        
    
  
People
(Reporter: philor, Unassigned)
References
Details
(Whiteboard: [buildduty][buildslaves][capacity])
      No description provided.
| Reporter | ||
| Updated•10 years ago
           | 
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
| Reporter | ||
| Comment 1•10 years ago
           | ||
On loan to an unknown person whose only trace was leaving the note "Reserved for testing ( do not enable or reboot!)" in slavealloc while disabling it on January 28th.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Comment 2•10 years ago
           | ||
After some archaeology, I linked bug 916765 in the slavealloc notes, which also links to bug 1122975.
| Reporter | ||
| Comment 3•10 years ago
           | ||
Ah, that explains the wrongness before the loan - a single instance of that known intermittent, during the time when we knew something was broken but didn't yet realize the problem was a set of slaves with only 4gb, so someone rage-disabled it with a useless slavealloc note and failed to reopen the tracking bug. 99.9% chance the slave is fine.
| Comment 4•10 years ago
           | ||
From Q via email on Feb 23:
"0019 was deemed "unusable" as being "too-slow" and was loaned to relops for AWS image  testing. The orginal note had a bug number not "( do not enable or reboot!)" . Don't know what happend there. I will copy the VHD capture information off that machine and hand it back over to see if it isn't "too slow" anymore"
Are we ready to put this slave back into production yet?
| Updated•10 years ago
           | 
Flags: needinfo?(q)
| Comment 6•10 years ago
           | ||
Re-enabled and returned to production.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
|   | ||
| Comment 7•10 years ago
           | ||
on loan for "Bug 989531 - Deploy NSIS 3.0b1 to buildslaves" work
| Comment 8•10 years ago
           | ||
Re-imaged and returned to production (try).
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
|   | ||
| Comment 9•10 years ago
           | ||
disabled to facilitate bug 1198317
|   | ||
| Updated•10 years ago
           | 
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
|   | ||
| Comment 10•10 years ago
           | ||
allocated to bug 1198317
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
|   | ||
| Comment 11•10 years ago
           | ||
deallocated from bug 1198317
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
| Updated•7 years ago
           | 
Product: Release Engineering → Infrastructure & Operations
| Updated•5 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
•