cluster-api-provider-azure: capz-periodic-e2e-full-main CI job failing
/kind bug
What steps did you take and what happened:
In testgrid, the capz-periodic-e2e-full-main job began failing after the custom VM extensions PR got merged. Here is the log that seems to implicate new custom VM code somehow:
capz-e2e: Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node expand_less | 21m9s
-- | --
{ Failure /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:670 Unexpected error: <autorest.DetailedError>: { Original: <*azure.RequestError \| 0xc000f6a6c0>{ DetailedError: { Original: nil, PackageType: "", Method: "", StatusCode: <int>404, Message: "", ServiceError: nil, Response: { Status: "404 Not Found", StatusCode: 404, Proto: "HTTP/2.0", ProtoMajor: 2, ProtoMinor: 0, Header: { "X-Ms-Failure-Cause": ["gateway"], "X-Ms-Correlation-Request-Id": [ "fa92e7e4-30c2-4a30-9670-2aacda76b2e8", ], "Date": [ "Mon, 03 Oct 2022 17:27:42 GMT", ], "Content-Length": ["110"], "Content-Type": [ "application/json; charset=utf-8", ], "Expires": ["-1"], "X-Ms-Request-Id": [ "fa92e7e4-30c2-4a30-9670-2aacda76b2e8", ], "X-Ms-Routing-Request-Id": [ "CENTRALUS:20221003T172742Z:fa92e7e4-30c2-4a30-9670-2aacda76b2e8", ], "Strict-Transport-Security": [ "max-age=31536000; includeSubDomains", ], "X-Content-Type-Options": ["nosniff"], "Cache-Control": ["no-cache"], "Pragma": ["no-cache"], }, Body: <io.nopCloser>{ Reader: <*bytes.Buffer \| 0xc001d539e0>{ buf: "{\"error\":{\"code\":\"ResourceGroupNotFound\",\"message\":\"Resource group 'capz-e2e-2tk088-cc' could not be found.\"}}", off: 0, lastRead: 0, }, }, ContentLength: 110, TransferEncoding: nil, Close: false, Uncompressed: false, Trailer: nil, Request: { Method: "GET", URL: { Scheme: "https", Opaque: "", User: nil, Host: "management.azure.com", Path: "/subscriptions/===REDACTED===/resourceGroups/capz-e2e-2tk088-cc/providers/Microsoft.Compute/virtualMachines", RawPath: "", ForceQuery: false, RawQuery: "api-version=2021-11-01", Fragment: "", RawFragment: "", }, Proto: "", ProtoMajor: 0, ProtoMinor: 0, Header: { "User-Agent": [ "Go/go1.18.6 (amd64-linux) go-autorest/v14.2.1 Azure-SDK-For-Go/v63.4.0 compute/2021-11-01", ], "Authorization": [ "Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6IjJaUXBKM1VwYmpBWVhZR2FYRUpsOGxWMFRPSSIsImtpZCI6IjJaUXBKM1VwYmpBWVhZR2FYRUpsOGxWMFRPSSJ9.eyJhdWQiOiJodHRwczovL21hbmFnZW1lbnQuYXp1cmUuY29tLyIsImlzcyI6Imh0dHBzOi8vc3RzLndpbmRvd3MubmV0LzA5N2Y4OWEwLTkyODYtNDNkMi05YTFhLTA4ZjFkNDliMWFmOC8iLCJpYXQiOjE2NjQ4MTc3NjIsIm5iZiI6MTY2NDgxNzc2MiwiZXhwIjoxNjY0ODIxNjYyLCJhaW8iOiJFMlpnWVBnWFdQZzQ1RTFRc1lTL2gzNmR3TU1JQUE9PSIsImFwcGlkIjoi===REDACTED===IiwiYXBwaWRhY3IiOiIxIiwiaWRwIjoiaHR0cHM6Ly9zdHMud2luZG93cy5uZXQvM... Gomega truncated this representation as it exceeds 'format.MaxLength'. Consider having the object provide a custom 'GomegaStringer' representation or adjust the parameters in Gomega's 'format' package. Learn more here: https://onsi.github.io/gomega/#adjusting-output compute.VirtualMachinesClient#List: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceGroupNotFound" Message="Resource group 'capz-e2e-2tk088-cc' could not be found." occurred /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_vmextensions.go:97}
What did you expect to happen:
Anything else you would like to add:
Environment:
- cluster-api-provider-azure version:
- Kubernetes version: (use
kubectl version): - OS (e.g. from
/etc/os-release):
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (16 by maintainers)
The clusterclass test spec in this job passed (unrelated tests failed unfortunately) Nice work @willie-yao!
I updated #2698 to get the resource group name correctly, instead of using the clusterName as the resource group name. This should solve the problem.
@willie-yao let’s remove it for now and file an issue that we need to backfill test coverage of vm extensions for clusterclass E2E scenarios
@mboersma: GitHub didn’t allow me to assign the following users: willie-yao.
Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.