← Back to team overview

jiocloud-devops team mailing list archive

[Bug 1448945] [NEW] [VirtualEnv] haproxy and gcp1 node in "failed" state in Virtual Env. #1096

 

Mayank Kapoor (mayankkapoor) has assigned this bug to you for Jio:

himanshu@bootstrap1-testjenkins-puppet-rjil-gate-1096:~$ date
Mon Apr 27 09:23:20 UTC 2015
himanshu@bootstrap1-testjenkins-puppet-rjil-gate-1096:~$ consul members
Node                                            Address         Status  Type    Build  Protocol
stmonleader1-testjenkins-puppet-rjil-gate-1096  10.0.0.90:8301  alive   client  0.4.0  2
stmon1-testjenkins-puppet-rjil-gate-1096        10.0.0.93:8301  alive   client  0.4.0  2
stmon2-testjenkins-puppet-rjil-gate-1096        10.0.0.94:8301  alive   client  0.4.0  2
bootstrap1-testjenkins-puppet-rjil-gate-1096    10.0.0.88:8301  alive   server  0.4.0  2
ocdb1-testjenkins-puppet-rjil-gate-1096         10.0.0.87:8301  alive   server  0.4.0  2
st1-testjenkins-puppet-rjil-gate-1096           10.0.0.91:8301  alive   client  0.4.0  2
ct1-testjenkins-puppet-rjil-gate-1096           10.0.0.97:8301  alive   client  0.4.0  2
oc1-testjenkins-puppet-rjil-gate-1096           10.0.0.89:8301  alive   server  0.4.0  2

haproxy1-testjenkins-puppet-rjil-gate-1096      10.0.0.86:8301  failed  client  0.4.0  2
gcp1-testjenkins-puppet-rjil-gate-1096          10.0.0.92:8301  failed  client  0.4.0  2

cp2-testjenkins-puppet-rjil-gate-1096           10.0.0.96:8301  alive   client  0.4.0  2
cp1-testjenkins-puppet-rjil-gate-1096           10.0.0.95:8301  alive   client  0.4.0  2
himanshu@bootstrap1-testjenkins-puppet-rjil-gate-1096:~$ 
himanshu@bootstrap1-testjenkins-puppet-rjil-gate-1096:~$ date
Mon Apr 27 09:23:32 UTC 2015
himanshu@bootstrap1-testjenkins-puppet-rjil-gate-1096:~$

** Affects: jio
     Importance: High
     Assignee: Reliance Jio DevOps Team (jiocloud-devops)
         Status: Fix Released


** Tags: operational-issue
-- 
[VirtualEnv] haproxy and gcp1 node in "failed" state in Virtual Env. #1096
https://bugs.launchpad.net/bugs/1448945
You received this bug notification because you are a member of Reliance Jio DevOps Team, which is a bug assignee.