Bug 762405 (GLUSTER-673) - First server can be shutdown by refreshing the machine connected to it
Summary: First server can be shutdown by refreshing the machine connected to it
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-673
Product: GlusterSP
Classification: Retired
Component: core
Version: 3.0.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: 3.0.4
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-23 06:09 UTC by Raghavendra Bhat
Modified: 2010-03-25 18:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Raghavendra Bhat 2010-02-23 06:09:11 UTC
Connect to the first server(i.e the management server) from a remote machine through browser(ex:http://192.168.1.35 connects to 192.168.1.35 which is the management server).We will get the webUI in the remote machine. If we click reboot then the mangement server reboots. Immedietly after clicking reboot, if we click shutdown it will ask wherther we want to shutdown. Clicking "ok", then waiting till the management server boots and immedietly after it reboots when we are about to get the login screen, refreshing in the remote machine will shutdown the management server(since we had clicked shutdown immedietly after clicking reboot). Not only shutdown, immedietly after clicking reboot  whatever we had clicked that thing will be activated when we refresh in the remote machine after the management server reboots.

Comment 1 Harshavardhana 2010-03-10 10:33:15 UTC
Until distributed management comes slave node installation will have "httpd" switched off, fixed upstream in 3.0.4 branch

Comment 2 Harshavardhana 2010-03-24 00:46:43 UTC
Raghavendra are you still able to reproduce this?


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