[Flaky Test]: Multiple tests failing with "unable to create policy: Package at top-level directory must contain a top-level manifest.yml file." #4102

cmacknz · 2024-01-18T19:05:01Z

https://buildkite.com/elastic/elastic-agent/builds/6362

Observed for both TestFQDN and TestInstallAndUnenrollWithEndpointSecurity/unprotected so far.
Edit 2024-02-08: Also observed on TestEndpointSecurityUnprivileged on this build.

=== RUN   TestFQDN
    fqdn_test.go:66: Set FQDN on host to exnykc.baz.io
    fqdn_test.go:70: Enroll agent in Fleet with a test policy
    fqdn_test.go:91: 
        	Error Trace:	/home/ubuntu/agent/testing/integration/fqdn_test.go:91
        	Error:      	Received unexpected error:
        	            	unable to create policy: Package at top-level directory  must contain a top-level manifest.yml file.
        	Test:       	TestFQDN
--- FAIL: TestFQDN (2.07s)

=== RUN   TestInstallAndUnenrollWithEndpointSecurity/unprotected
    endpoint_security_test.go:227: Enrolling the agent in Fleet
    endpoint_security_test.go:251: 
        	Error Trace:	/home/ubuntu/agent/testing/integration/endpoint_security_test.go:251
        	            				/home/ubuntu/agent/testing/integration/endpoint_security_test.go:114
        	Error:      	Received unexpected error:
        	            	unable to create policy: Package at top-level directory  must contain a top-level manifest.yml file.
        	Test:       	TestInstallAndUnenrollWithEndpointSecurity/unprotected
--- FAIL: TestInstallAndUnenrollWithEndpointSecurity/unprotected (1.94s)

This error originates from Fleet, not the agent. This is a returned error from the /api/fleet/agent_policies" API. The failing line is:

elastic-agent/pkg/testing/tools/tools.go

Lines 38 to 52 in 84a2d5c

    
           // InstallAgentWithPolicy creates the given policy, enrolls the given agent 
        
           // fixture in Fleet using the default Fleet Server, waits for the agent to be 
        
           // online, and returns the created policy. 
        
           func InstallAgentWithPolicy(ctx context.Context, t *testing.T, 
        
           	installOpts atesting.InstallOpts, 
        
           	agentFixture *atesting.Fixture, 
        
           	kibClient *kibana.Client, 
        
           	createPolicyReq kibana.AgentPolicy) (kibana.PolicyResponse, error) { 
        
           	t.Helper() 
        
           	// Create policy 
        
           	policy, err := kibClient.CreatePolicy(ctx, createPolicyReq) 
        
           	if err != nil { 
        
           		return policy, fmt.Errorf("unable to create policy: %w", err) 
        
           	}

The error in Fleet seems to originate from https://github.com/elastic/kibana/blob/a7ee92712608755a163a7da6547ce2ba1c31c7f8/x-pack/plugins/fleet/server/services/epm/archive/parse.ts#L217-L225

  // The package must contain a manifest file ...
  const manifestFile = path.posix.join(toplevelDir, MANIFEST_NAME);
  const manifestBuffer = assetsMap[manifestFile];
  logger.debug(`Verifying archive - checking manifest file and manifest buffer`);
  if (!paths.includes(manifestFile) || !manifestBuffer) {
    throw new PackageInvalidArchiveError(
      `Package at top-level directory ${toplevelDir} must contain a top-level ${MANIFEST_NAME} file.`
    );
  }

The text was updated successfully, but these errors were encountered:

elasticmachine · 2024-01-18T19:05:03Z

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

elasticmachine · 2024-01-18T19:05:40Z

Pinging @elastic/fleet (Team:Fleet)

cmacknz · 2024-01-18T19:07:35Z

Example of a failing request causing this failure:

elastic-agent/testing/integration/fqdn_test.go

Lines 71 to 85 in 84a2d5c

    
           createPolicyReq := kibana.AgentPolicy{ 
        
           	Name:        "test-policy-fqdn-" + strings.ReplaceAll(fqdn, ".", "-"), 
        
           	Namespace:   info.Namespace, 
        
           	Description: fmt.Sprintf("Test policy for FQDN E2E test (%s)", fqdn), 
        
           	MonitoringEnabled: []kibana.MonitoringEnabledOption{ 
        
           		kibana.MonitoringEnabledLogs, 
        
           		kibana.MonitoringEnabledMetrics, 
        
           	}, 
        
           	AgentFeatures: []map[string]interface{}{ 
        
           		{ 
        
           			"name":    "fqdn", 
        
           			"enabled": false, 
        
           		}, 
        
           	}, 
        
           }

nchaulet · 2024-01-18T21:32:29Z

The issue seems to happen when trying to install elastic_agent, (not sure why yet maybe they was an issue with the bundled package, I am not able to reproduce it on the latest SNAPSHOT)

cmacknz · 2024-01-18T21:35:07Z

Will keep an eye out for this, if it goes away we can just close this. Our tests do this a lot so if the bug is still there I think it will show itself quickly.

rdner · 2024-02-02T16:04:27Z

The same issue is happening again in

elastic-agent/testing/integration/container_cmd_test.go

Lines 60 to 63 in 2555088

    
           policy, err := info.KibanaClient.CreatePolicy(ctx, createPolicyReq) 
        
           if err != nil { 
        
           	t.Fatalf("could not create Agent Policy: %s", err) 
        
           }

TestContainerCMD
    container_cmd_test.go:62: could not create Agent Policy: Package at top-level directory  must contain a top-level manifest.yml file.

The build sample https://buildkite.com/elastic/elastic-agent/builds/6741#018d6a53-dfe4-4946-8dd6-7776c95e1c73

rdner · 2024-02-02T20:27:56Z

Another failure like this in TestFQDN https://buildkite.com/elastic/elastic-agent/builds/6741#018d6ad7-dc9c-492a-a9bd-53ef8bd44087

cmacknz · 2024-02-05T16:41:59Z

=== RUN   TestFQDN
    fqdn_test.go:66: Set FQDN on host to hkbgjg.baz.io
    fqdn_test.go:70: Enroll agent in Fleet with a test policy
    fqdn_test.go:91: 
        	Error Trace:	/home/ubuntu/agent/testing/integration/fqdn_test.go:91
        	Error:      	Received unexpected error:
        	            	unable to create policy: Package at top-level directory  must contain a top-level manifest.yml file.
        	Test:       	TestFQDN
--- FAIL: TestFQDN (2.51s)

@nchaulet @kpollich this continues to happen, any ideas on what might be causing this on the Fleet side or what we could do to resolve it? Would retrying help?

kpollich · 2024-02-06T20:03:20Z

The root cause here is that the Elastic Agent package archive available in the Kibana instance used for these tests is corrupt in some fashion. One thing that might be helpful is checking the Kibana logs while the tests are running to see if there's any kind of installation error reported there. In general, the elastic_agent package is bundled with the Kibana distributable so it should be valid and installable no matter what.

Is the Kibana instance that's available during these test runs a cloud instance in a particular environment/region? Maybe we can try reproducing the issue by manually provisioning a Kibana instance the same way these tests do.

cmacknz · 2024-02-06T20:11:50Z

We use the CFT region for these tests.

cmacknz · 2024-02-06T20:18:13Z

Oddly all of the failures use the linux-arm64-ubuntu runner, but I wouldn't expect that to affect the stack deployment.

juliaElastic · 2024-02-07T15:56:42Z

What is the best way to reproduce this? Triggering a new build on main?
I was thinking to login to the kibana of the deployment to check what is in the problematic elastic_agent bundled package, is there a way to find out the kibana credentials from the build?

cmacknz · 2024-02-07T16:01:30Z

We log the deployment ID in the test runs if you look in the console output you should see something like the following.

>>> Created cloud stack 8.13.0-SNAPSHOT [stack_id: 8130-SNAPSHOT, deployment_id: <REDACTED>]
--
  | 2024-02-02 17:33:30 UTC | >>> Waiting for cloud stack 8.13.0-SNAPSHOT to be ready [stack_id: 8130-SNAPSHOT, deployment_id: <REDACTED>]

The deployments are eventually cleaned up so I'm not sure if they'll be kept running long enough to catch this.

If I look at the simplest test that reproduced this, it is just creating a simple policy:

elastic-agent/testing/integration/fqdn_test.go

Lines 70 to 91 in b6c24c1

    
           t.Log("Enroll agent in Fleet with a test policy") 
        
           createPolicyReq := kibana.AgentPolicy{ 
        
           	Name:        "test-policy-fqdn-" + strings.ReplaceAll(fqdn, ".", "-"), 
        
           	Namespace:   info.Namespace, 
        
           	Description: fmt.Sprintf("Test policy for FQDN E2E test (%s)", fqdn), 
        
           	MonitoringEnabled: []kibana.MonitoringEnabledOption{ 
        
           		kibana.MonitoringEnabledLogs, 
        
           		kibana.MonitoringEnabledMetrics, 
        
           	}, 
        
           	AgentFeatures: []map[string]interface{}{ 
        
           		{ 
        
           			"name":    "fqdn", 
        
           			"enabled": false, 
        
           		}, 
        
           	}, 
        
           } 
        
           installOpts := atesting.InstallOpts{ 
        
           	NonInteractive: true, 
        
           	Force:          true, 
        
           } 
        
           policy, err := tools.InstallAgentWithPolicy(ctx, t, installOpts, agentFixture, kibClient, createPolicyReq) 
        
           require.NoError(t, err)

So you could attempt to call that function repeatedly with a randomly varying name.

Effectively what our tests are doing is creating lots of different policies in rapid succession, possibly concurrently, because the various test runners for each tested agent architecture run in parallel.

cmacknz · 2024-02-07T16:02:09Z

The error we get is from the last line in the block I linked above:

=== RUN   TestFQDN
    fqdn_test.go:66: Set FQDN on host to hkbgjg.baz.io
    fqdn_test.go:70: Enroll agent in Fleet with a test policy
    fqdn_test.go:91: 
        	Error Trace:	/home/ubuntu/agent/testing/integration/fqdn_test.go:91
        	Error:      	Received unexpected error:
        	            	unable to create policy: Package at top-level directory  must contain a top-level manifest.yml file.
        	Test:       	TestFQDN
--- FAIL: TestFQDN (2.51s)

cmacknz · 2024-02-07T16:04:54Z

So you could attempt to call that function repeatedly with a randomly varying name.

To be clear, I think you can probably just create your own deployment in the CFT region and use something like the code I linked to create policies rapidly and concurrently without depending on our test framework at all.

I don't think there is anything special in the test framework here, besides the pattern of our API calls, which you should be able to replicate outside of the framework.

juliaElastic · 2024-02-07T16:30:56Z

Ok I'll give it a go with a new deployment to reproduce, thanks.

AndersonQ · 2024-02-08T09:43:38Z

just for the record, another instance of it: TestEndpointSecurityUnprivileged: https://buildkite.com/elastic/elastic-agent/builds/6892#018d876e-3454-4372-865c-14ce199ba51c

juliaElastic · 2024-02-08T10:15:50Z

create your own deployment in the CFT region

Could you clarify how to select CFT region? I don't seem to have access to manually create a deployment in production.
The test created a deployment in this region: GCP - Los Angeles (us-west2)
In staging I only see GCP - Iowa (us-central1)

I've tested with a script in this staging instance to create agent policies with agent monitoring concurrently, but couldn't reproduce the issue.
I think the error log could be improved to log more details, is it possible to run these tests with a custom kibana image?
I created a pr cloud deployment which uses the same GCP us-west2 zone, but still can't reproduce the issue.

Another question, are these integration tests being run concurrently?

rdner · 2024-02-08T16:31:25Z

This suddenly escalated in the recent build https://buildkite.com/elastic/elastic-agent/builds/6936#018d8947-2e57-43fe-8b01-e1543bd867f2

45 tests failed, seems like in all of them there was some kind of issue communicating to the fleet server, particularly enrolment.

Error: fail to enroll: fail to execute request to fleet-server: status code: 0, fleet-server returned an error: , message: Unknown resource.

nchaulet · 2024-02-08T16:48:01Z

I am able to reproduce it locally it seems an issue with concurrent install of package, trying to figure what will be the right fix here https://elastic.slack.com/archives/C02BPSXUSKF/p1707410812298429?thread_ts=1707311534.367209&cid=C02BPSXUSKF

How to reproduce the bug I introduce an artificial delay in the package install process

--- a/x-pack/plugins/fleet/server/services/epm/packages/_install_package.ts
+++ b/x-pack/plugins/fleet/server/services/epm/packages/_install_package.ts
@@ -150,6 +150,7 @@ export async function _installPackage({
         spaceId,
         verificationResult,
       });
+      await new Promise((resolve) => setTimeout(resolve, 30 * 1000));
     }
     logger.debug(`Package install - Installing Kibana assets`);
     const kibanaAssetPromise = withPackageSpan('Install Kibana assets', () =>

Than doing two concurrent request to create an agent policy

repro.mov

cmacknz · 2024-02-08T19:10:49Z

Could you clarify how to select CFT region? I don't seem to have access to manually create a deployment in production.
The test created a deployment in this region: GCP - Los Angeles (us-west2)
In staging I only see GCP - Iowa (us-central1)

The CFT region is a production region, not staging. Will DM you details since the links are private.

rdner · 2024-02-12T09:28:27Z

Another occurrence in a recent build (2024-02-10T00:01:30.609Z) on next day after the fix was merged (2024-02-09T13:43:26Z). This time the error message changed:

https://buildkite.com/elastic/elastic-agent/builds/6993#018d9052-86fa-49d4-8986-b2fd55437893

=== RUN   TestFQDN
    fqdn_test.go:66: Set FQDN on host to dnyskp.baz.io
    fqdn_test.go:70: Enroll agent in Fleet with a test policy
    fqdn_test.go:91: 
        	Error Trace:	/home/ubuntu/agent/testing/integration/fqdn_test.go:91
        	Error:      	Received unexpected error:
        	            	unable to create policy: Manifest file manifest.yml not found in paths.
        	Test:       	TestFQDN
--- FAIL: TestFQDN (2.26s)
=== RUN   TestEndpointSecurityUnprivileged
    endpoint_security_test.go:592: Enrolling the agent in Fleet
    endpoint_security_test.go:609: 
        	Error Trace:	/home/ubuntu/agent/testing/integration/endpoint_security_test.go:609
        	Error:      	Received unexpected error:
        	            	unable to create policy: Manifest file manifest.yml not found in paths.
        	Test:       	TestEndpointSecurityUnprivileged
        	Messages:   	Policy Response was: {{    []     0 0 [] false} 0001-01-01 00:00:00 +0000 UTC  0 false []}
--- FAIL: TestEndpointSecurityUnprivileged (1.73s)

There is a chance that a new snapshot was not used for this run but sine the error message changed it tells me it might be something else.

juliaElastic · 2024-02-12T12:00:56Z

@rdner The error message changed by a recent pr, it is coming from the same code path. From what I found, the snapshot during the saturday night build is from friday night, which didn't contain the fix yet.
Let's see if the error occurs again in the builds this week, hopefully not.

rdner · 2024-02-14T17:57:40Z

No failures in the last 2 days. Closing for now.

rdner · 2024-03-14T08:54:15Z

It appears to be back in https://buildkite.com/elastic/elastic-agent/builds/7776#018e3a44-b483-40fd-8255-c68a28340465

=== RUN   TestLogIngestionFleetManaged/Normal_logs_with_flattened_data_stream_are_shipped
    logs_ingestion_test.go:378: received a non 200-OK when adding package to policy. Status code: 400
    logs_ingestion_test.go:385: ================================================================================
    logs_ingestion_test.go:386: Kibana error response:
    logs_ingestion_test.go:387: HTTP/1.1 400 Bad Request
        Content-Length: 99
        Cache-Control: private, no-cache, no-store, must-revalidate
        Content-Security-Policy: script-src 'report-sample' 'self'; worker-src 'report-sample' 'self' blob:; style-src 'report-sample' 'self' 'unsafe-inline'; report-to violations-endpoint
        Content-Type: application/json; charset=utf-8
        Cross-Origin-Opener-Policy: same-origin
        Date: Thu, 14 Mar 2024 00:41:15 GMT
        Elastic-Api-Version: 2023-10-31
        Kbn-License-Sig: aae020e5403c04f90cee724f1b0e9d9bf953cfbd825ce1b7a661696fc918d7c8
        Kbn-Name: instance-0000000000
        Permissions-Policy: camera=(), display-capture=(), fullscreen=(self), geolocation=(), microphone=(), web-share=()
        Referrer-Policy: strict-origin-when-cross-origin
        Reporting-Endpoints: violations-endpoint="https://at-ingest-ci-8140-snapshot.kb.us-west2.gcp.elastic-cloud.com:9243/internal/security/analytics/_record_violations"
        X-Cloud-Request-Id: jpqhTfvBR6q3EiCurZEHMg
        X-Content-Type-Options: nosniff
        X-Found-Handling-Cluster: 766134025f594be89bcc257a84173981
        X-Found-Handling-Instance: instance-0000000000
        
        {"statusCode":400,"error":"Bad Request","message":"Manifest file manifest.yml not found in paths."}
    logs_ingestion_test.go:388: ================================================================================
    logs_ingestion_test.go:389: Rendered policy:
    logs_ingestion_test.go:390: 
        {
          "policy_id": "b84f0de3-e6a8-41fb-9c14-efe9b83e34d4",
          "package": {
            "name": "log",
            "version": "2.3.0"
          },
          "name": "Log-Input-TestLogIngestionFleetManaged/Normal_logs_with_flattened_data_stream_are_shipped-2024-03-14T00:41:15Z",
          "namespace": "testlogingestionfleetmanagednormallogswithflatteneddatastreamareshippednamespace17172997543648347858",
          "inputs": {
            "logs-logfile": {
              "enabled": true,
              "streams": {
                "log.logs": {
                  "enabled": true,
                  "vars": {
                    "paths": [
                      "/tmp/fleet-ingest-1774416147/log.log" 
                    ],
                    "data_stream.dataset": "testlogingestionfleetmanagednormallogswithflatteneddatastreamareshippeddataset"
                  }
                }
              }
            }
          }
        }
    logs_ingestion_test.go:391: ================================================================================
--- FAIL: TestLogIngestionFleetManaged/Normal_logs_with_flattened_data_stream_are_shipped (0.08s)

Is it the same issue or a new one?

rdner · 2024-03-19T12:42:59Z

@juliaElastic may I ask to have a look at #4102 (comment) ?

juliaElastic · 2024-03-19T13:41:49Z

@nchaulet Any idea if this is the same issue as before?
It does look similar, I tested manually adding a Custom log integration, and didn't get the issue. So it seems there still might be a concurrency issue with the package installation somewhere.

nchaulet · 2024-03-19T17:18:01Z

Something seems weird @rdner it is possible that the test try to do concurrent request to POST /package_policies from the log the request kind of match the error

I was able to get a repro and working on a fix for that elastic/kibana#178993

rdner · 2024-03-20T09:38:57Z

Something seems weird @rdner it is possible that the test try to do concurrent request to POST /package_policies from the log the request kind of match the error

@nchaulet I checked the code, this test does not do requests concurrently but it does 2 POST /api/fleet/agent_policies requests which are quite close to each other, as you can see in the logs you mentioned.

First request is coming from here:

elastic-agent/testing/integration/logs_ingestion_test.go

Lines 82 to 88 in ddd832b

    
           policy, err := tools.InstallAgentWithPolicy( 
        
           	ctx, 
        
           	t, 
        
           	installOpts, 
        
           	agentFixture, 
        
           	info.KibanaClient, 
        
           	createPolicyReq)

which comes to this function eventually:

elastic-agent/pkg/testing/tools/tools.go

Lines 41 to 75 in ddd832b

    
           func InstallAgentWithPolicy(ctx context.Context, t *testing.T, 
        
           	installOpts atesting.InstallOpts, 
        
           	agentFixture *atesting.Fixture, 
        
           	kibClient *kibana.Client, 
        
           	createPolicyReq kibana.AgentPolicy) (kibana.PolicyResponse, error) { 
        
           	t.Helper() 
        
           	// Create policy 
        
           	policy, err := kibClient.CreatePolicy(ctx, createPolicyReq) 
        
           	if err != nil { 
        
           		return policy, fmt.Errorf("unable to create policy: %w", err) 
        
           	} 
        
           	if createPolicyReq.IsProtected { 
        
           		// If protected fetch uninstall token and set it for the fixture 
        
           		resp, err := kibClient.GetPolicyUninstallTokens(ctx, policy.ID) 
        
           		if err != nil { 
        
           			return policy, fmt.Errorf("failed to fetch uninstal tokens: %w", err) 
        
           		} 
        
           		if len(resp.Items) == 0 { 
        
           			return policy, fmt.Errorf("expected non-zero number of tokens: %w", err) 
        
           		} 
        
           		if len(resp.Items[0].Token) == 0 { 
        
           			return policy, fmt.Errorf("expected non-empty token: %w", err) 
        
           		} 
        
           		uninstallToken := resp.Items[0].Token 
        
           		t.Logf("Protected with uninstall token: %v", uninstallToken) 
        
           		agentFixture.SetUninstallToken(uninstallToken) 
        
           	} 
        
           	err = InstallAgentForPolicy(ctx, t, installOpts, agentFixture, kibClient, policy.ID) 
        
           	return policy, err 
        
           }

It creates a new policy and enrolls the currently running agent:

elastic-agent/pkg/testing/tools/tools.go

Line 49 in ddd832b

policy, err := kibClient.CreatePolicy(ctx, createPolicyReq)

elastic-agent/pkg/testing/tools/tools.go

Line 73 in ddd832b

    
           err = InstallAgentForPolicy(ctx, t, installOpts, agentFixture, kibClient, policy.ID)

But there is a sub-test case that also creates a policy here:

elastic-agent/testing/integration/logs_ingestion_test.go

Lines 97 to 99 in ddd832b

    
           t.Run("Normal logs with flattened data_stream are shipped", func(t *testing.T) { 
        
           	testFlattenedDatastreamFleetPolicy(t, ctx, info, policy) 
        
           })

elastic-agent/testing/integration/logs_ingestion_test.go

Lines 365 to 375 in ddd832b

    
           // 2. Call Kibana to create the policy. 
        
           // Docs: https://www.elastic.co/guide/en/fleet/current/fleet-api-docs.html#create-integration-policy-api 
        
           resp, err := info.KibanaClient.Connection.Send( 
        
           	http.MethodPost, 
        
           	"/api/fleet/package_policies", 
        
           	nil, 
        
           	nil, 
        
           	bytes.NewBufferString(agentPolicy)) 
        
           if err != nil { 
        
           	t.Fatalf("could not execute request to Kibana/Fleet: %s", err) 
        
           }

@belimawr since you worked on this test, could you give us more context why we create 2 policies here?

belimawr · 2024-03-20T11:55:13Z

@belimawr since you worked on this test, could you give us more context why we create 2 policies here?

The test TestLogIngestionFleetManaged creates a single policy

elastic-agent/testing/integration/logs_ingestion_test.go

Lines 82 to 88 in 0159e54

    
           policy, err := tools.InstallAgentWithPolicy( 
        
           	ctx, 
        
           	t, 
        
           	installOpts, 
        
           	agentFixture, 
        
           	info.KibanaClient, 
        
           	createPolicyReq)

then it adds a package to the policy on

elastic-agent/testing/integration/logs_ingestion_test.go

Line 318 in 0159e54

func testFlattenedDatastreamFleetPolicy(

If you look at the template it contains the exiting policy ID

elastic-agent/testing/integration/logs_ingestion_test.go

Lines 493 to 518 in 0159e54

    
           var policyJSON = ` 
        
           { 
        
             "policy_id": "{{.PolicyID}}", 
        
             "package": { 
        
               "name": "log", 
        
               "version": "2.3.0" 
        
             }, 
        
             "name": "{{.Name}}", 
        
             "namespace": "{{.Namespace}}", 
        
             "inputs": { 
        
               "logs-logfile": { 
        
                 "enabled": true, 
        
                 "streams": { 
        
                   "log.logs": { 
        
                     "enabled": true, 
        
                     "vars": { 
        
                       "paths": [ 
        
                         "{{.LogFilePath | js}}" {{/* we need to escape windows paths */}} 
        
                       ], 
        
                       "data_stream.dataset": "{{.Dataset}}" 
        
                     } 
        
                   } 
        
                 } 
        
               } 
        
             } 
        
           }`

My understanding when I wrote this test is that the call to /api/fleet/package_policies only adds packages to the policy.

rdner · 2024-03-20T16:25:42Z

@belimawr I just expected method PUT or PATCH for updating a policy, my bad.

cmacknz added Team:Elastic-Agent Label for the Agent team flaky-test Unstable or unreliable test cases. labels Jan 18, 2024

cmacknz added the Team:Fleet Label for the Fleet team label Jan 18, 2024

cmacknz closed this as completed Jan 29, 2024

rdner reopened this Feb 2, 2024

rdner assigned cmacknz Feb 5, 2024

nchaulet mentioned this issue Feb 8, 2024

[Fleet] Fix isPackageVersionOrLaterInstalled to check for installed package elastic/kibana#176532

Merged

2 tasks

cmacknz mentioned this issue Feb 8, 2024

[Flaky Test]: TestInstallWithEndpointSecurityAndRemoveEndpointIntegration – Error installing fleet package: Error installing endpoint 8.11.0: runtime_exception #4158

Closed

nchaulet closed this as completed in elastic/kibana#176532 Feb 9, 2024

rdner reopened this Feb 12, 2024

rdner closed this as completed Feb 14, 2024

rdner reopened this Mar 14, 2024

nchaulet mentioned this issue Mar 19, 2024

[Fleet] Fix concurent package policies create elastic/kibana#178993

Merged

2 tasks

nchaulet closed this as completed in elastic/kibana#178993 Mar 20, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Flaky Test]: Multiple tests failing with "unable to create policy: Package at top-level directory must contain a top-level manifest.yml file." #4102

[Flaky Test]: Multiple tests failing with "unable to create policy: Package at top-level directory must contain a top-level manifest.yml file." #4102

cmacknz commented Jan 18, 2024 •

edited by AndersonQ

Loading

elasticmachine commented Jan 18, 2024

elasticmachine commented Jan 18, 2024

cmacknz commented Jan 18, 2024

nchaulet commented Jan 18, 2024

cmacknz commented Jan 18, 2024

rdner commented Feb 2, 2024 •

edited

Loading

rdner commented Feb 2, 2024

cmacknz commented Feb 5, 2024

kpollich commented Feb 6, 2024 •

edited

Loading

cmacknz commented Feb 6, 2024

cmacknz commented Feb 6, 2024

juliaElastic commented Feb 7, 2024

cmacknz commented Feb 7, 2024

cmacknz commented Feb 7, 2024

cmacknz commented Feb 7, 2024 •

edited

Loading

juliaElastic commented Feb 7, 2024

AndersonQ commented Feb 8, 2024

juliaElastic commented Feb 8, 2024 •

edited

Loading

rdner commented Feb 8, 2024 •

edited

Loading

nchaulet commented Feb 8, 2024 •

edited

Loading

cmacknz commented Feb 8, 2024 •

edited

Loading

rdner commented Feb 12, 2024

juliaElastic commented Feb 12, 2024 •

edited

Loading

rdner commented Feb 14, 2024

rdner commented Mar 14, 2024

rdner commented Mar 19, 2024

juliaElastic commented Mar 19, 2024 •

edited

Loading

nchaulet commented Mar 19, 2024 •

edited

Loading

rdner commented Mar 20, 2024

belimawr commented Mar 20, 2024

rdner commented Mar 20, 2024

[Flaky Test]: Multiple tests failing with "unable to create policy: Package at top-level directory must contain a top-level manifest.yml file." #4102

[Flaky Test]: Multiple tests failing with "unable to create policy: Package at top-level directory must contain a top-level manifest.yml file." #4102

Comments

cmacknz commented Jan 18, 2024 • edited by AndersonQ Loading

elasticmachine commented Jan 18, 2024

elasticmachine commented Jan 18, 2024

cmacknz commented Jan 18, 2024

nchaulet commented Jan 18, 2024

cmacknz commented Jan 18, 2024

rdner commented Feb 2, 2024 • edited Loading

rdner commented Feb 2, 2024

cmacknz commented Feb 5, 2024

kpollich commented Feb 6, 2024 • edited Loading

cmacknz commented Feb 6, 2024

cmacknz commented Feb 6, 2024

juliaElastic commented Feb 7, 2024

cmacknz commented Feb 7, 2024

cmacknz commented Feb 7, 2024

cmacknz commented Feb 7, 2024 • edited Loading

juliaElastic commented Feb 7, 2024

AndersonQ commented Feb 8, 2024

juliaElastic commented Feb 8, 2024 • edited Loading

rdner commented Feb 8, 2024 • edited Loading

nchaulet commented Feb 8, 2024 • edited Loading

cmacknz commented Feb 8, 2024 • edited Loading

rdner commented Feb 12, 2024

juliaElastic commented Feb 12, 2024 • edited Loading

rdner commented Feb 14, 2024

rdner commented Mar 14, 2024

rdner commented Mar 19, 2024

juliaElastic commented Mar 19, 2024 • edited Loading

nchaulet commented Mar 19, 2024 • edited Loading

rdner commented Mar 20, 2024

belimawr commented Mar 20, 2024

rdner commented Mar 20, 2024

cmacknz commented Jan 18, 2024 •

edited by AndersonQ

Loading

rdner commented Feb 2, 2024 •

edited

Loading

kpollich commented Feb 6, 2024 •

edited

Loading

cmacknz commented Feb 7, 2024 •

edited

Loading

juliaElastic commented Feb 8, 2024 •

edited

Loading

rdner commented Feb 8, 2024 •

edited

Loading

nchaulet commented Feb 8, 2024 •

edited

Loading

cmacknz commented Feb 8, 2024 •

edited

Loading

juliaElastic commented Feb 12, 2024 •

edited

Loading

juliaElastic commented Mar 19, 2024 •

edited

Loading

nchaulet commented Mar 19, 2024 •

edited

Loading