Bug 1445233

Summary: Able to initiate stop operation on already stopped server
Product: Red Hat CloudForms Management Engine Reporter: Prachi <pyadav>
Component: ProvidersAssignee: Tomas Coufal <tcoufal>
Status: CLOSED WONTFIX QA Contact: Prachi <pyadav>
Severity: medium Docs Contact:
Priority: high    
Version: 5.8.0CC: abonas, jfrey, jhardy, mmahoney, obarenbo
Target Milestone: GAKeywords: Triaged
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-04 15:35:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Middleware Target Upstream Version:
Embargoed:
Attachments:
Description Flags
STop opeartion on already stopped opeartion none

Description Prachi 2017-04-25 10:15:15 UTC
Created attachment 1273865 [details]
STop opeartion on already stopped opeartion

Description of problem: Able to initiate stop operation on already stopped server. It will show operation initiated on UI


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

5.8.0.11-beta2.20170418170914_a53d2a7 

How reproducible: 


Steps to Reproduce:
1. Stop the EAP server
2. login to CFME
3. Navigate to stopped server
4. initiate the stop operation on already stopped server
5. Select ok to start operation

Actual results:
 Operation will be initiated with a message.

Expected results: Operation should not be initiated as server was already stopped.


Additional info:

CFME logs are generating Error logs for opeartion roll back as well as EAP is showing error.


CFE error:

*****************************
[----] I, [2017-04-24T08:29:43.420028 #2944:10d1398]  INFO -- : MIQ(ManageIQ::Providers::Hawkular::MiddlewareManager#with_provider_connection) Connecting through ManageIQ::Providers::Hawkular::MiddlewareManager: [hawkular-EAP-Test]

[----] E, [2017-04-24T08:29:46.144001 #2944:7527b94] ERROR -- : MIQ(ManageIQ::Providers::Hawkular::MiddlewareManager#run_operation) error callback was called, reason: Performed [Stop] on a [DMR Node] given by Inventory path [/t;hawkular/f;master.Unnamed%20Domain/r;Local~~/r;Local~%2Fhost%3Dmaster/r;Local~%2Fhost%3Dmaster%2Fserver-config%3Dserver-one]

***************************** 


EAP error:

*****************************
ERROR [org.hawkular.agent.monitor.protocol.EndpointService] (Hawkular-WildFly-Agent-Scheduler-Metrics-2) HAWKMONITOR010049: Could not access resources of endpoint [DMREndpointService[Endpoint[Local]:[null]]]: org.hawkular.agent.monitor.protocol.ProtocolException: Unsuccessful fetching DMR attribute [/host=master/server=server-one/core-service=platform-mbean/type=memory] [heap-memory-usage]
[Host Controller] 	at org.hawkular.agent.monitor.protocol.dmr.DMRDriver.fetchAttribute(DMRDriver.java:159)
[Host Controller] 	at org.hawkular.agent.monitor.protocol.EndpointService.measureMetrics(EndpointService.java:476)
[Host Controller] 	at org.hawkular.agent.monitor.scheduler.MetricsCollector.run(MetricsCollector.java:60)
[Host Controller] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[Host Controller] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[Host Controller] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[Host Controller] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[Host Controller] 	at java.lang.Thread.run(Thread.java:745)
[Host Controller] 	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
[Host Controller] Caused by: org.hawkular.dmr.api.OperationFailureException: Could not perform operation [read-attribute]: WFLYCTL0030: No resource definition is registered for address [
[Host Controller]     ("host" => "master"),
[Host Controller]     ("server" => "server-one"),
[Host Controller]     ("core-service" => "platform-mbean"),
[Host Controller]     ("type" => "memory")

*****************************

Comment 2 Alissa 2017-04-25 11:49:19 UTC
I'm reducing severity as this has no severe implication on the system.
I agree it would be nice to be fixed from user's perspective.
The available operations on a server should be "sensitive" to server's status, so irrelevant operations should be greyed out in the UI.

Comment 3 Alissa 2017-11-28 14:34:43 UTC
seems related to https://bugzilla.redhat.com/show_bug.cgi?id=1513038