Bug 845511 - [as7] signal reload/restart-required to user for Managed Server
[as7] signal reload/restart-required to user for Managed Server
Status: NEW
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
4.4
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-03 05:30 EDT by Libor Zoubek
Modified: 2015-11-01 19:45 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Libor Zoubek 2012-08-03 05:30:31 EDT
Description of problem: Signaling server reload/restart required does not work for managed servers. Now, when we can configure managed servers (Bug 828656) we should also singal user that he actualy needs to restart the server, so his changes take effect. In this case (for example changing server-group) it is probably obvious, but you never know.



Version-Release number of selected component (if applicable):
JON 3.1.1.ER1, RHQ 4.5.0-master

How reproducible:always


Steps to Reproduce:
1.have AS7 domain controller imported
2.edit configuration of a managed server (better to be running)
3.check that user is notified that server needs to be restarted (refresh current configuration for managed server)
  
Actual results: no notification is given to user. 

In AS7 cli

/host=master/server=server-one:read-resource()

returns 

"response-headers" => {"process-state" => "restart-required"}

Expected results: user gets notified as it is for AS7 Standalone & Domain configurations. Message should say, that we're talking about particular managed server so user does not get confused and does not try restart HC or DC.


Additional info:

Note You need to log in before you can comment on or make changes to this bug.