Bug 720044 - New tickets should not be opened upon power failure on a system marked "broken"
Summary: New tickets should not be opened upon power failure on a system marked "broken"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Steven Lawrance
QA Contact:
URL:
Whiteboard:
: 720672 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-08 20:12 UTC by Sean Waite
Modified: 2019-05-22 13:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-28 23:50:12 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Sean Waite 2011-07-08 20:12:58 UTC 
Description of problem:
If power fails on a broken system, a new ticket is opened. Since systems are automatically marked broken after power fails, and testing the power function is a step in fixing a system that fails to power cycle. This creates a lot of unnecessary tickets.

Version-Release number of selected component (if applicable):
Most recent

How reproducible:
100%

Steps to Reproduce:
1. Find system with broken power, that is marked broken
2. Power Cycle

  
Actual results:
New ticket created each time

Expected results:
The original ticket is sufficient

Additional info:
This is probably a regression.
Comment 1 Bill Peck 2011-07-08 20:27:40 UTC 
Some additional info here:

We used to only do this logic when a power command failed from the scheduler.  Now we do it for manual interaction as well.  Thats good, but we should pay attention to the current status and only move the system to broken once and not email the owner again.
Comment 2 Steven Lawrance 2011-07-18 03:38:15 UTC 
*** Bug 720672 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.