Bug 1142655
| Summary: | [RHSC] Host installation fails when the name of the host is edited while installation is in progress | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shruti Sampat <ssampat> | ||||
| Component: | rhsc | Assignee: | Sahina Bose <sabose> | ||||
| Status: | CLOSED CANTFIX | QA Contact: | RHS-C QE <rhsc-qe-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rhgs-3.0 | CC: | nlevinki, rhs-bugs, rhsc-qe-bugs | ||||
| Target Milestone: | --- | Keywords: | ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-01-29 15:13:08 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: |
|
||||||
Created attachment 938367 [details]
host-deploy logs
Thank you for your report. This bug is filed against a component for which no further new development is being undertaken |
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.