New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 855288 link

Starred by 0 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jul 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Create/delete devservers

Project Member Reported by mjayapal@chromium.org, Jun 22 2018

Issue description

Comment 1 by jkop@chromium.org, Jun 22 2018

Status: Assigned (was: Untriaged)

Comment 2 by jkop@chromium.org, Jun 22 2018

Owner: mjayapal@chromium.org
Status: Started (was: Assigned)
Deletion was almost done by crrev.com/i/643796, but they were left commented out.

Creation is done.
please add the new devservers into prod

thanks.
Cc: harpreet@chromium.org dsunk...@chromium.org
Hi Jacob,

Thanks for adding devserver 6 - 9

I have compared devserver1 and the newly created devserver and found two changes can you please change that.


Hostname     : chromeos15-infra-devserver1.cros.corp.google.com
Status       : primary
Roles        : devserver
Attributes   : {u'restricted_subnet': u'100.115.124.0/22', u'port': u'8082'}
Date Created : 2017-11-01 15:26:18
Date Modified: 2017-11-01 15:26:18
Note         : None

Hostname     : chromeos15-infra-devserver6.cros.crop.google.com
Status       : invalid
Roles        : devserver
Attributes   : {}
Date Created : None
Date Modified: 2018-06-22 14:29:19
Note         : None

Can you please modify with the attributes ' {u'restricted_subnet': u'100.115.124.0/22', u'port': u'8082'} ' in devserver 6-9 & change the status to 'primary'

Please let me know if I have to modify/configure in devservers 6-9.

Thanks,
Mani

Labels: -Pri-3 Pri-2
Hi Jacob,

Just verified given you a wrong FQDN. Its my fault.

chromeos15-infra-devserver6.cros.corp.google.com
chromeos15-infra-devserver7.cros.corp.google.com
chromeos15-infra-devserver8.cros.corp.google.com
chromeos15-infra-devserver9.cros.corp.google.com

Can you plz delete and recreate with the attributes.

Thanks,
Mani

Comment 6 by jkop@chromium.org, Jun 27 2018

...that's the exact same set of FQDNs as before. I have no idea what you want here.

Comment 7 by jkop@chromium.org, Jun 27 2018

Cc: xixuan@chromium.org
Contact the current deputy for anything further you need done. But first make sure you understand the problem, because what you've said makes no sense taken as a whole.
output of 'atest server list' for the above 4 devservers

Hostname     : chromeos15-infra-devserver7.cros.crop.google.com
Status       : invalid
Roles        : devserver
Attributes   : {}
Date Created : None
Date Modified: 2018-06-22 14:19:18
Note         : None

Hostname     : chromeos15-infra-devserver6.cros.crop.google.com
Status       : invalid
Roles        : devserver
Attributes   : {}
Date Created : None
Date Modified: 2018-06-22 14:29:19
Note         : None

Hostname     : chromeos15-infra-devserver8.cros.crop.google.com
Status       : invalid
Roles        : devserver
Attributes   : {}
Date Created : None
Date Modified: 2018-06-22 14:34:20
Note         : None

Hostname     : chromeos15-infra-devserver9.cros.crop.google.com
Status       : invalid
Roles        : devserver
Attributes   : {}
Date Created : None
Date Modified: 2018-06-22 14:39:21
Note         : None

It was created cros.crop.google.com  instead of cros.corp.google.com

So can you recreate with the below servers

chromeos15-infra-devserver6.cros.corp.google.com
chromeos15-infra-devserver7.cros.corp.google.com
chromeos15-infra-devserver8.cros.corp.google.com
chromeos15-infra-devserver9.cros.corp.google.com

Thanks,
Mani
Please create with the attributes 

Attributes   : {u'restricted_subnet': u'100.115.124.0/22', u'port': u'8082'}


Thanks,
Mani
Owner: xixuan@chromium.org
Project Member

Comment 11 by bugdroid1@chromium.org, Jun 27 2018

Please use 'atest server list -r devserver --skylab' to check since we migrate server_db to skylab:

....
hostname: "chromeos15-infra-devserver6.cros.corp.google.com"
environment: ENVIRONMENT_PROD
status: STATUS_PRIMARY
roles: ROLE_DEVSERVER
attributes {
  devserver_restricted_subnet: "100.115.124.0/22"
  devserver_port: 8082
}

hostname: "chromeos15-infra-devserver7.cros.corp.google.com"
environment: ENVIRONMENT_PROD
status: STATUS_PRIMARY
roles: ROLE_DEVSERVER
attributes {
  devserver_restricted_subnet: "100.115.124.0/22"
  devserver_port: 8082
}

hostname: "chromeos15-infra-devserver8.cros.corp.google.com"
environment: ENVIRONMENT_PROD
status: STATUS_PRIMARY
roles: ROLE_DEVSERVER
attributes {
  devserver_restricted_subnet: "100.115.124.0/22"
  devserver_port: 8082
}

hostname: "chromeos15-infra-devserver9.cros.corp.google.com"
environment: ENVIRONMENT_PROD
status: STATUS_PRIMARY
roles: ROLE_DEVSERVER
attributes {
  devserver_restricted_subnet: "100.115.124.0/22"
  devserver_port: 8082
}
....
Status: Fixed (was: Started)
feel free to reopen it if these devservers don't properly perform in prod.
Owner: mjayapal@chromium.org
Status: Assigned (was: Fixed)
chromeos15-infra-devserver6.cros.corp.google.com is not pingable and sshable. Could you check and make it up?
new Devservers is turned ON.

As discussed please update the devservers.

Thanks
Status: Fixed (was: Assigned)
Able to ping all the devservers.

Closing this bug for now.

Sign in to add a comment