Hide Forgot
Created attachment 1209653 [details] deployment.ear Description of problem: The status for SubDeployments in list of deployments page or in summary page is displayed as "Unknown". Version-Release number of selected component (if applicable): 5.7.0.4-alpha1.20161005153002_cfc8a23 How reproducible: always Steps to Reproduce: 1. Deploy an EAR file which contains JAR and WAR into EAP7. 2. List Deployments for that EAP7 server. Those SubDeployment JAR and WAR files statuses will be shown "Unknown". Actual results: "Unknown" status for SubDeployments. Expected results: TBD by PM. Suggestion: SubDeployments can have status of parent EAR deployment. Attached EAP file which was used. But it happens for "hawkular-alerter-metrics.war" and another hawkular sub-deployments as well.
I just ran a WildFly 10 with the ear (the one attached to this BZ). I ran jboss-cli.sh and looked at the EAR's information using this query: ./jboss-cli.sh --connect '--command=/deployment=cfme_test_ear_middleware.ear/:read-resource(recursive=true,include-runtime=true)' And I notice that the subdeployments do NOT have a status attribute (only the main parent deployment does). Without a way for WildFly to tell us what the status is, it doesn't surprise me that subdeployments show "unknown" - there *is* no WildFly status for subdeployments! { "outcome" => "success", "result" => { "content" => [{"hash" => bytes { 0xce, 0xd0, 0xb3, 0x9c, 0xe5, 0xb4, 0xa6, 0x59, 0x13, 0x14, 0x3f, 0xfc, 0x1b, 0x67, 0xdc, 0x7b, 0x41, 0xf2, 0x5e, 0xaa }}], "disabled-time" => undefined, "disabled-timestamp" => undefined, "enabled" => true, "enabled-time" => 1476800253680L, "enabled-timestamp" => "2016-10-18 10:17:33,680 EDT", "name" => "cfme_test_ear_middleware.ear", "owner" => [ ("subsystem" => "deployment-scanner"), ("scanner" => "default") ], "persistent" => false, "runtime-name" => "cfme_test_ear_middleware.ear", "status" => "OK", "subdeployment" => {"cfme_test_nested_war_middleware.war" => {"subsystem" => { "undertow" => { "active-sessions" => 0, "context-root" => "/cfme_test_nested_war_middleware", "expired-sessions" => 0, "max-active-sessions" => -1, "rejected-sessions" => 0, "server" => "default-server", "session-avg-alive-time" => 0, "session-max-alive-time" => 0, "sessions-created" => 0, "virtual-host" => "default-host", "servlet" => undefined, "websocket" => undefined }, "logging" => {"configuration" => {"default" => { "error-manager" => undefined, "filter" => undefined, "formatter" => { "PATTERN" => { "class-name" => "org.jboss.logmanager.formatters.PatternFormatter", "module" => undefined, "properties" => {"pattern" => "%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"} }, "COLOR-PATTERN" => { "class-name" => "org.jboss.logmanager.formatters.PatternFormatter", "module" => undefined, "properties" => {"pattern" => "%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"} } }, "handler" => { "CONSOLE" => { "class-name" => "org.jboss.logmanager.handlers.ConsoleHandler", "encoding" => undefined, "error-manager" => undefined, "filter" => undefined, "formatter" => "COLOR-PATTERN", "handlers" => [], "level" => "INFO", "module" => undefined, "properties" => { "autoFlush" => "true", "target" => "SYSTEM_OUT", "enabled" => "true" } }, "FILE" => { "class-name" => "org.jboss.logmanager.handlers.PeriodicRotatingFileHandler", "encoding" => undefined, "error-manager" => undefined, "filter" => undefined, "formatter" => "PATTERN", "handlers" => [], "level" => "ALL", "module" => undefined, "properties" => { "append" => "true", "autoFlush" => "true", "enabled" => "true", "suffix" => ".yyyy-MM-dd", "fileName" => "/home/mazz/bin/wildfly/wildfly-10.0.0.Final/standalone/log/server.log" } } }, "logger" => { "ROOT" => { "filter" => undefined, "handlers" => [ "FILE", "CONSOLE" ], "level" => "INFO", "use-parent-handlers" => undefined }, "sun.rmi" => { "filter" => undefined, "handlers" => [], "level" => "WARN", "use-parent-handlers" => true }, "org.jboss.as.config" => { "filter" => undefined, "handlers" => [], "level" => "DEBUG", "use-parent-handlers" => true }, "com.arjuna" => { "filter" => undefined, "handlers" => [], "level" => "WARN", "use-parent-handlers" => true } }, "pojo" => undefined }}} }}}, "subsystem" => {"logging" => {"configuration" => {"default" => { "error-manager" => undefined, "filter" => undefined, "formatter" => { "PATTERN" => { "class-name" => "org.jboss.logmanager.formatters.PatternFormatter", "module" => undefined, "properties" => {"pattern" => "%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"} }, "COLOR-PATTERN" => { "class-name" => "org.jboss.logmanager.formatters.PatternFormatter", "module" => undefined, "properties" => {"pattern" => "%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"} } }, "handler" => { "CONSOLE" => { "class-name" => "org.jboss.logmanager.handlers.ConsoleHandler", "encoding" => undefined, "error-manager" => undefined, "filter" => undefined, "formatter" => "COLOR-PATTERN", "handlers" => [], "level" => "INFO", "module" => undefined, "properties" => { "autoFlush" => "true", "target" => "SYSTEM_OUT", "enabled" => "true" } }, "FILE" => { "class-name" => "org.jboss.logmanager.handlers.PeriodicRotatingFileHandler", "encoding" => undefined, "error-manager" => undefined, "filter" => undefined, "formatter" => "PATTERN", "handlers" => [], "level" => "ALL", "module" => undefined, "properties" => { "append" => "true", "autoFlush" => "true", "enabled" => "true", "suffix" => ".yyyy-MM-dd", "fileName" => "/home/mazz/bin/wildfly/wildfly-10.0.0.Final/standalone/log/server.log" } } }, "logger" => { "ROOT" => { "filter" => undefined, "handlers" => [ "FILE", "CONSOLE" ], "level" => "INFO", "use-parent-handlers" => undefined }, "sun.rmi" => { "filter" => undefined, "handlers" => [], "level" => "WARN", "use-parent-handlers" => true }, "org.jboss.as.config" => { "filter" => undefined, "handlers" => [], "level" => "DEBUG", "use-parent-handlers" => true }, "com.arjuna" => { "filter" => undefined, "handlers" => [], "level" => "WARN", "use-parent-handlers" => true } }, "pojo" => undefined }}}} } }
So with Mazz' comment it is clear that the agent can't deliver that data. So in MiQ we need to either not display any status info for subdeployments at all. Or just take the value from the outer parent deployment.
https://github.com/ManageIQ/manageiq/pull/12040
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/e7890c72f52154791dd14ad5ab4047f635adf9ef commit e7890c72f52154791dd14ad5ab4047f635adf9ef Author: Josejulio Martínez <jmartine> AuthorDate: Tue Oct 18 16:44:05 2016 -0500 Commit: Josejulio Martínez <jmartine> CommitDate: Wed Oct 19 13:16:10 2016 -0500 Uses parent deployment status for subdeployments. https://bugzilla.redhat.com/show_bug.cgi?id=1384118 .../providers/hawkular/middleware_manager.rb | 4 +- .../hawkular/middleware_manager/refresh_parser.rb | 24 ++++++++-- .../middleware_manager/refresh_parser_spec.rb | 53 ++++++++++++---------- 3 files changed, 50 insertions(+), 31 deletions(-)
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/54014708b2ca20e1490e982ea5a20cc57f29bf9d commit 54014708b2ca20e1490e982ea5a20cc57f29bf9d Author: Greg Blomquist <blomquisg> AuthorDate: Mon Oct 24 14:59:25 2016 -0400 Commit: Oleg Barenboim <chessbyte> CommitDate: Mon Oct 24 22:03:12 2016 +0200 Merge pull request #12040 from josejulio/fix_subdeployment_status Uses parent deployment status for subdeployments. (cherry picked from commit 7a9cb9148824efcbba6b05b47f5f6a0bbf1cb0a2) https://bugzilla.redhat.com/show_bug.cgi?id=1384118 .../providers/hawkular/middleware_manager.rb | 4 +- .../hawkular/middleware_manager/refresh_parser.rb | 24 ++++++++-- .../middleware_manager/refresh_parser_spec.rb | 53 ++++++++++++---------- 3 files changed, 50 insertions(+), 31 deletions(-)