Create/delete devservers |
|||||||||
Issue descriptionMoved devservers from chromeos9 to chromeos15, Need to delete the old devserver host entry and create new host entry. List of Old devserver hosts entry to be deleted. chromeos9-infra-devserver4.cros.crop.google.com chromeos9-infra-devserver5.cros.crop.google.com chromeos9-infra-devserver6.cros.crop.google.com chromeos9-infra-devserver7.cros.crop.google.com List of New devserver hosts entry to be created. chromeos15-infra-devserver6.cros.crop.google.com chromeos15-infra-devserver7.cros.crop.google.com chromeos15-infra-devserver8.cros.crop.google.com chromeos15-infra-devserver9.cros.crop.google.com Thanks, Mani
,
Jun 22 2018
Deletion was almost done by crrev.com/i/643796, but they were left commented out. Creation is done.
,
Jun 22 2018
please add the new devservers into prod thanks.
,
Jun 26 2018
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
,
Jun 26 2018
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
,
Jun 27 2018
...that's the exact same set of FQDNs as before. I have no idea what you want here.
,
Jun 27 2018
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.
,
Jun 27 2018
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
,
Jun 27 2018
Please create with the attributes
Attributes : {u'restricted_subnet': u'100.115.124.0/22', u'port': u'8082'}
Thanks,
Mani
,
Jun 27 2018
,
Jun 27 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/infra_internal/skylab_inventory/+/0c718cb86f0d4ba24055e1f93352e4e982823178 commit 0c718cb86f0d4ba24055e1f93352e4e982823178 Author: Xixuan Wu <xixuan@chromium.org> Date: Wed Jun 27 19:43:08 2018
,
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 } ....
,
Jun 27 2018
,
Jun 27 2018
feel free to reopen it if these devservers don't properly perform in prod.
,
Jun 28 2018
chromeos15-infra-devserver6.cros.corp.google.com is not pingable and sshable. Could you check and make it up?
,
Jun 28 2018
new Devservers is turned ON. As discussed please update the devservers. Thanks
,
Jul 13
Able to ping all the devservers. Closing this bug for now. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by jkop@chromium.org
, Jun 22 2018