New deployments themselves are broken. I tried deploying cr-buildbucket-dev with some endpoints-related changes and I got:
Traceback (most recent call last):
File "appengine/runtime/wsgi.py", line 240, in Handle
handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
File "appengine/runtime/wsgi.py", line 299, in _LoadHandler
handler, path, err = LoadObject(self._handler)
File "appengine/runtime/wsgi.py", line 85, in LoadObject
obj = __import__(path[0])
File "apps.py", line 18, in <module>
html, endpoints, backend = main.initialize()
File "main.py", line 47, in initialize
return create_html_app(), create_endpoints_app(), create_backend_app()
File "main.py", line 22, in create_html_app
handlers.get_frontend_routes(), debug=utils.is_local_dev_server())
File "handlers.py", line 349, in get_frontend_routes
prpc_server.add_service(access.AccessServicer())
File "components/prpc/server.py", line 138, in add_service
self._discovery_service.add_service(servicer.DESCRIPTION)
File "components/prpc/discovery/service.py", line 53, in add_service
ensure_file(service_description['file'])
KeyError: 'file'
Note: this has brought down config validation for projects that have cr-buildbucket-dev.cfg file: on config changes, luci-config tries to access cr-buildbucket-dev's validation endpoint and fails. This results in:
CRITICAL: cr-buildbucket-dev.cfg: Error during external validation: Net error: Failed to call https://cr-buildbucket-dev.appspot.com/_ah/api/config/v1/validate after 4 attempts url: https://cr-buildbucket-dev.appspot.com/_ah/api/config/v1/validate config_set: projects/fuchsia path: cr-buildbucket-dev.cfg response: None
That blocks the config change.
I'll try to revert cr-buildbucket-dev to a working version.
API Explorer doesn't work in this version :-/ So I assume config validation will be broken too.
Switched to even older 15637-249eaa8 from May 22. API Explorer works...
Comment 1 by bugdroid1@chromium.org
, May 30 2018