Bug 1142655 - [RHSC] Host installation fails when the name of the host is edited while installation is in progress
Summary: [RHSC] Host installation fails when the name of the host is edited while inst...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: RHS-C QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-17 07:29 UTC by Shruti Sampat
Modified: 2018-01-29 15:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-29 15:13:08 UTC
Embargoed:


Attachments (Terms of Use)
host-deploy logs (193.70 KB, text/plain)
2014-09-17 07:31 UTC, Shruti Sampat
no flags Details

Description Shruti Sampat 2014-09-17 07:29:48 UTC
Description of problem:
------------------------

When the "Name" of a host was edited while installation was in progress, the host ended up in Install Failed state instead of coming up. The following is from events log -

------------------------------------------------------------------------------

Host host3 installation failed. CallableStatementCallback; SQL [{call updatevdsstatic(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}]; ERROR: duplicate key value violates unique constraint "vds_static_vds_name_unique"
  Where: SQL statement "UPDATE vds_static SET host_name =  $1 , free_text_comment =  $2 , ip =  $3 ,vds_unique_id =  $4 , port =  $5 , vds_group_id =  $6 ,vds_name =  $7 ,server_SSL_enabled =  $8 , vds_type =  $9 , _update_date = LOCALTIMESTAMP,vds_strength =  $10 , pm_type =  $11 ,pm_user =  $12 ,pm_password =  $13 , pm_port =  $14 ,pm_options =  $15 ,pm_enabled =  $16 , pm_proxy_preferences =  $17 , pm_secondary_ip =  $18 , pm_secondary_type =  $19 , pm_secondary_user =  $20 , pm_secondary_password =  $21 , pm_secondary_port =  $22 , pm_secondary_options =  $23 , pm_secondary_concurrent =  $24 , otp_validity =  $25 , vds_spm_priority =  $26 , sshKeyFingerprint =  $27 , console_address =  $28 , ssh_port =  $29 , ssh_username =  $30 , disable_auto_pm =  $31  WHERE vds_id =  $32 "
PL/pgSQL function "updatevdsstatic" line 4 at SQL statement; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "vds_static_vds_name_unique"
  Where: SQL statement "UPDATE vds_static SET host_name =  $1 , free_text_comment =  $2 , ip =  $3 ,vds_unique_id =  $4 , port =  $5 , vds_group_id =  $6 ,vds_name =  $7 ,server_SSL_enabled =  $8 , vds_type =  $9 , _update_date = LOCALTIMESTAMP,vds_strength =  $10 , pm_type =  $11 ,pm_user =  $12 ,pm_password =  $13 , pm_port =  $14 ,pm_options =  $15 ,pm_enabled =  $16 , pm_proxy_preferences =  $17 , pm_secondary_ip =  $18 , pm_secondary_type =  $19 , pm_secondary_user =  $20 , pm_secondary_password =  $21 , pm_secondary_port =  $22 , pm_secondary_options =  $23 , pm_secondary_concurrent =  $24 , otp_validity =  $25 , vds_spm_priority =  $26 , sshKeyFingerprint =  $27 , console_address =  $28 , ssh_port =  $29 , ssh_username =  $30 , disable_auto_pm =  $31  WHERE vds_id =  $32 "
PL/pgSQL function "updatevdsstatic" line 4 at SQL statement.

-------------------------------------------------------------------------------

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
Red Hat Storage Console Version: 3.0.0-0.14.el6rhs 

How reproducible:
-----------------
Consistently.

Steps to Reproduce:
-------------------

1. Create a 4-node RHS cluster and import the cluster using the Console.
2. While the hosts are being installed, edit the names of all nodes except one.
3. After a few moments all the nodes except the one whose name was not edited, will end up in Install Failed state. The node that was not edited comes up.

Actual results:
----------------
Nodes whose name was edited while installation was in progress, fail to install.

Expected results:
------------------
Node is expected to come up.

Additional info:
-----------------

When the cluster was imported without editing the names while installation was in progress, the nodes came up as expected. Find host-deploy logs from one of the nodes attached.

Comment 1 Shruti Sampat 2014-09-17 07:31:15 UTC
Created attachment 938367 [details]
host-deploy logs

Comment 3 Sahina Bose 2018-01-29 15:13:08 UTC
Thank you for your report. This bug is filed against a component for which no further new development is being undertaken


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