Project

General

Profile

Actions

action #17666

closed

[tools]Failed to create needle - no areas defined

Added by mlin7442 over 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
-
Start date:
2017-03-10
Due date:
% Done:

0%

Estimated time:

Description

observation

Trying to save a needle not based on any existing needle and not taking matches from other needles but with a matching area defined yields an error that "no areas are defined" while the json preview also shows correct content.

steps to reproduce

1) open needle editor
2) select Needle based on to None
3) unchecked "Take matches"
Now json is in a fresh state.
4) create matching area
5) add a tag
6) now the json preview shows proper tag and areas, saving needle
RED WARNING show up - Unable to save needle : no areas defined

problem

H1. needle editor broken

suggestion

  • Debug assets/javascripts/needleeditor.js

workaround

probably it helps to take any needle as template and/or select 'take matches' and then save.

further details

screenshot attached


Files

no_area.png (76.1 KB) no_area.png mlin7442, 2017-03-10 14:13
Actions #1

Updated by mlin7442 over 7 years ago

  • Category set to Regressions/Crashes
Actions #2

Updated by mlin7442 over 7 years ago

additional information:

$ rpm -qi openQA
Name : openQA
Version : 4.4.1487185841.20f2a62
Release : 75.1
Architecture: noarch
Install Date: Thu 16 Feb 2017 05:37:45 PM CST
Group : Development/Tools/Other
Size : 5728636
License : GPL-2.0+
Signature : RSA/SHA256, Thu 16 Feb 2017 03:17:03 AM CST, Key ID 5b121667cbdf5e8f
Source RPM : openQA-4.4.1487185841.20f2a62-75.1.src.rpm
Build Date : Thu 16 Feb 2017 03:16:51 AM CST
Build Host : lamb20
Relocations : (not relocatable)
Vendor : obs://build.opensuse.org/devel:openQA
URL : http://os-autoinst.github.io/openQA/
Summary : The openQA web-frontend, scheduler and tools
Description :
The openQA framework consists of two parts, which are tracked in
separate git repos. The OS-autoinst test engine and the front-end
with web-interface, test-scheduler and other high-level logic, which
is part of this repo.
Distribution: devel:openQA / openSUSE_Leap_42.2

Actions #3

Updated by oholecek over 7 years ago

I tried to revert https://github.com/os-autoinst/openQA/pull/1244 and it started to work

Actions #4

Updated by oholecek over 7 years ago

  • Assignee set to mkittler
Actions #5

Updated by mkittler over 7 years ago

  • Status changed from New to In Progress

I'll have a look at it. Seems like our tests are insufficient.

Actions #6

Updated by okurz over 7 years ago

  • Description updated (diff)

could also reproduce, reworked description

Actions #8

Updated by RBrownSUSE over 7 years ago

  • Subject changed from Failed to create needle - no areas defined to [tools]Failed to create needle - no areas defined
Actions #9

Updated by oholecek over 7 years ago

  • Status changed from In Progress to Resolved
  • Target version set to Milestone 6

Merged and I confirm I can save needle as described in repro steps now.

Actions #10

Updated by qkzhu about 7 years ago

I met this issue again on o.s.d

I want to select the 'Advanced' button for https://openqa.suse.de/tests/1054018#step/onetime_vncsession_xvnc_java/16

Actions #11

Updated by mgriessmeier about 7 years ago

same issue for me, when trying to create a needle it shows the error
though the json looks valid to me with proper areas defined

Actions #12

Updated by mgriessmeier about 7 years ago

edit: Workaround works perfectly though

Actions #13

Updated by qkzhu about 7 years ago

  • Status changed from Resolved to Feedback
  • Target version deleted (Milestone 6)
Actions #14

Updated by mkittler about 7 years ago

  • Status changed from Feedback to In Progress
Actions #15

Updated by mkittler almost 7 years ago

  • Status changed from In Progress to Feedback

Does it work on production a server (not sure whether the fix is already deployed)?

Actions #16

Updated by okurz almost 7 years ago

  • Status changed from Feedback to Resolved

worked for me on production

Actions

Also available in: Atom PDF