Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1140172

Summary: deploy selected is visible and functioning for already installed storage node
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: Storage Node, UIAssignee: Michael Burman <miburman>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.3.0CC: mfoley, miburman
Target Milestone: ER05   
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-09 12:07:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
deploy_already_deployed_storage_node none

Description Armine Hovsepyan 2014-09-10 12:18:37 UTC 
Created attachment 936120 [details]
deploy_already_deployed_storage_node

Description of problem:
deploy selected is visible and functioning for already installed storage node

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

How reproducible:
2 out of 2

Steps to Reproduce:
1. install server with agent and storage on IP1
2. install storage and agent on IP2 and connect to IP1
3. As soon as add-to-maintenance starts, stop storage on IP1

after step3. storage cluster becomes down

4. restart storage node in IP1
5. navigate to storage nodes administration page
6. select storage node in IP2 and click Deploy Selected
7. During the add-to-maintenance, stop storage on IP1

After step7. storage cluster becomes down and immediately come back ON as visible in server.log attached in comment #5

8. Navigate to storage nodes administration page 
9. Select storage node in IP2 (the only running currently) and click Deploy Selected

Actual results:
After step8. Deploy Selected is active and functioning

Expected results:
After step8. Deploy Selected should be grey and inactive

Additional info:
Comment 2 John Sanda 2014-09-22 16:28:21 UTC 
Reassigning to Jirka since he has handled UI related changes.
Comment 3 Simeon Pinder 2014-09-29 08:12:55 UTC 
Moving into ER05 as didn't make the ER04 cut.
Comment 4 Armine Hovsepyan 2014-10-09 12:07:31 UTC 
unable to reproduce the issue - closing as not a bug. Will reopen in case it's visible .