Description of problem: If I create a scalable application I get a result of HAProxy being started with severity "result". This rather strange/not consistent since the appliation itself is reported via severity "info". [ { "exit_code" => big integer 0, "field" => undefined, "severity" => "info", "text" => "Application scalable was created." }, { "exit_code" => big integer 0, "field" => undefined, "severity" => "debug", "text" => "The cartridge jbossas deployed a template application" }, { "exit_code" => big integer 0, "field" => undefined, "severity" => "result", "text" => "HAProxy instance is started " } ] Furthermore the basic logic we were told to follow is to show the user whatever is reported as "field": "result" or "severity":"result". Thus if a user of the Eclipse tooling is creating a scalable applicaiton he'll get a dialog about HAProxy being started which is weird usabilitywise. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create a scalable application 2. 3. Actual results: Expected results: HAProxy being started should get reported with severity "info" or "debug" Additional info:
This might be a duplicate of bug 980928 https://bugzilla.redhat.com/show_bug.cgi?id=980928
*** This bug has been marked as a duplicate of bug 980928 ***
Is duplicate with https://bugzilla.redhat.com/show_bug.cgi?id=980928 in terms of code? To me as a user this doesn't look duplicate, the issue here is a "bad" severity ("result" where it should be "info") and not a compatibility issue like #980928
This was closed as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=980928. On INT, where I see https://bugzilla.redhat.com/show_bug.cgi?id=980928 fixed since I get messages with field "result", I still experience this. I thus reopen this issue an ask you to please clarify: * If this is expected: please re-close as "NOT A BUG" * If this is not expected: please keep this opened until the message severity/field is changed to "info".
Sorry Andre I misunderstood your comments. The broker sets the messages returned from node as CLIENT_RESULT to severity=result. I agree with you that this message "HAProxy instance is started" should be debug. This fix needs to happen in HAProxy cartridge. I'm assigning the bug to node/runtime team for a fix.
https://github.com/openshift/origin-server/pull/3207 Have changed code to use client_message instead of client_result.
Checked on devenv_3580, the message severity level show warning this time. "messages": [ { "exit_code": 0, "field": null, "severity": "info", "text": "Application app3s was created." }, { "exit_code": 0, "field": null, "severity": "warning", "text": "HAProxy instance is started\n" @Andre Dietisheim Not sure if the current result is acceptable. Can you please help move the bug to verified if it is ok.
According commnet#4, assign the bug back.
@Meng Bo: As soon as severity/field are not RESULT we wont show it in the Eclipse tooling which is what a user is imho expecting. We have a generic logic in the tooling where we only show messages that are either RESULT in severity or in field. I cant say if DEBUG or WARNING are the right severities for you guys though.
According to comment#9, please move the bug back to ON_QA, and QE will verify it.
@Meng Bo: I apparently cannot set this status (ON_QA). The only choices I have in status are assigned or closed. What do I miss?
Move it back to ON_QA according to comment 7 and comment 9
Move bug to verified.