systemtest: use Fleet Server #5085
Conversation
axw
force-pushed
the
systemtest-fleet-server
branch
from
28d8638 to
8cfe40c
Compare
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
axw
force-pushed
the
systemtest-fleet-server
branch
2 times, most recently
from
5096b94 to
51c8c7e
Compare
Codecov Report
@@ Coverage Diff @@
## master #5085 +/- ##
==========================================
+ Coverage 77.30% 77.35% +0.04%
==========================================
Files 179 179
Lines 10540 10540
==========================================
+ Hits 8148 8153 +5
+ Misses 2392 2387 -5
|
|
test seems to be flaky, bringing back into draft while I debug... |
axw
force-pushed
the
systemtest-fleet-server
branch
from
e1e572e to
1bbef5b
Compare
| if c.FleetEnrollmentToken != "" { | ||
| if c.FleetServer { | ||
| c.request.Env["FLEET_SERVER_ENABLE"] = "1" | ||
| c.request.Env["FLEET_SERVER_HOST"] = "0.0.0.0" |
There was a problem hiding this comment.
Shouldn't be necessary anymore afaik.
There was a problem hiding this comment.
I just tried removing FLEET_SERVER_HOST and FLEET_SERVER_PORT (and tried just removing each individually), and the server never became accessible. In the elastic-agent log I see "State changed to CONFIG: Re-configuring". Maybe a bug masked by overriding the host/port?
There was a problem hiding this comment.
I'm going to merge as it is and come back to this, so we can get our system tests running again
There was a problem hiding this comment.
Yes sure; thanks for trying it out.
* systemtest: use Fleet Server * systemtest: fix bulk unenrolment (cherry picked from commit 139ce53)
3 participants
Motivation/summary
In the Fleet integration system test, bootstrap Fleet Server and then run the APM integration on a separate Elastci Agent that enrolls with the Fleet Server.
Related issues
Closes #5075