| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
GCE instance tags can be used for various purposes, such as applying
network firewall rules or filtering VMs for scheduling onto specific
hosts.
To support these use cases, syzkaller needs the ability to set
instance tags during VM creation.
This patch introduces a new tags field to the gce VM configuration that
allows users to specify a list of tags to be attached to GCE instances
created by syz-manager.
|
| |
|
|
|
| |
It simplifies the dependency tree and fixes a build error for the
send-test-email container.
|
| |
|
|
|
|
| |
Google Cloud cannot automatically infer it from our images, so we need
to explicitly set it. The flag is required to create a GVNIC-based GCE
instance (the only type for C4A machines).
|
| |
|
|
| |
It must be more than 10GB.
|
| |
|
|
| |
Bonus: add error processing.
|
| |
|
|
|
| |
Add a method for querying the current project name.
Add a method for querying the latest secret version.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
It's now the recommended approach.
Co-authored-by: Alex Tyler <alextyler@google.com>
Co-authored-by: Aleksandr Nogikh <nogikh@google.com>
|
| |
|
|
|
|
|
| |
We seem to be getting more of ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS
errors rather than ZONE_RESOURCE_POOL_EXHAUSTED.
Let's support both.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Since this can be enabled on per-image basis, we don't need to
specifically add this to the creation RPC.
This is basically a revert of https://github.com/google/syzkaller/pull/3328.
|
| |
|
|
|
|
| |
This is needed for Cuttlefish-on-GCE. It adds the field 'nested_virt' to
the config file and then passes it through to the relevant field in the
call to gce.CreateInstance().
|
| |
|
|
|
| |
At the moment syzkaller can only use the zone where it's running. Make it a
configurable option instead (with the old behavior as a fallback).
|
| |
|
|
| |
Now we always enable it, make this configurable for GCE instances.
|
| |
|
|
| |
Adds the function to read GCP Secrets.
|
| |
|
|
|
| |
Enabling DisplayDevice can give us some more coverage.
Requires switching to v1 API which is a good idea anyway.
|
| |
|
|
|
|
|
|
|
|
| |
0. Remove aetest build tag. We don't need it anymore, go test should work.
1. IsDevAppServer does not return true in tests anymore, so don't use it
2. Use a different mechanism to register test/prod config.
We don't have aetest tag anymore, so we need something even more dynamic.
3. Fix new golangci-lint warnings: all test files are checked now.
Update #1461
|
| | |
|
| |
|
|
|
|
| |
We are hitting quotas for operation completion polling.
Not surprising since we create/delete instances all the time.
Slightly decrease rate of polling.
|
| |
|
|
|
|
|
|
|
| |
We are seeing some flakes during bisection and image testing.
Hard to tell what's the root cause because they are episodic.
But using non-preemptible VMs for bisection and image testing
looks good on all fronts.
Update #501
|
| |
|
|
|
|
|
| |
The part that we want from gofmt is simplify (-s).
Fix all code that needs fixing.
Update #538
|
| |
|
|
|
|
| |
Sometimes we see rate limiting errors.
This is especially bad for e.g. patch testing requests.
Increase default API delay and add backoff logic.
|
| | |
|
| |
|
|
| |
The current instance is not necessary in the default network.
|
| | |
|
| |
|
|
|
|
| |
Turns out GetSerialPortOutput API does not work if instance has
serial port connections enabled (which we always have).
Get output from serial port relay service instead.
|
| |
|
|
| |
"can't ssh into the instance" is not a very useful error.
|
| |
|
|
|
|
| |
google.golang.org/api/compute/v0.beta again changed public interfaces
which causes breakages in other build environments.
Update everything to HEAD.
|
| |
|