fix: use valid version for 7.17

[mdelapenya]

What does this PR do?

Uses 7.17 version for fleet-server

Why is it important?

The current value was added by a backport, so it's wrong

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have run the Unit tests (make unit-test), and they are passing locally
• I have run the End-2-End tests for the suite I'm working on, and they are passing locally
• I have noticed new Go dependencies (run make notice in the proper directory)

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Caused by [7.17](backport #2064) fix: update stack deployment to follow Users&Roles best practices #2102

[elasticmachine]

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-02-09T11:52:50.739+0000

• Duration: 63 min 42 sec

Test stats 🧪

Test	Results
Failed	6
Passed	243
Skipped	0
Total	249

Test errors

Expand to view the tests failures

Initializing / End-To-End Tests / fleet_sles15_integrations / Adding an Integration to a Policy #1 – Integrations

Expand to view the error details

 Step the "Elastic APM" datasource is shown in the policy as added 

• no stacktrace

Initializing / End-To-End Tests / fleet_debian_amd64_integrations / Adding an Integration to a Policy #1 – Integrations

Expand to view the error details

 Step the "Elastic APM" datasource is shown in the policy as added 

• no stacktrace

Initializing / End-To-End Tests / fleet_debian_arm64_integrations / Adding an Integration to a Policy #1 – Integrations

Expand to view the error details

 Step the "Elastic APM" datasource is shown in the policy as added 

• no stacktrace

Initializing / End-To-End Tests / fleet_debian_amd64_apm_server / Deploying a default stand-alone agent with the Elastic APM integration – APM Integration

Expand to view the error details

 Step the "apm-server" process is in the "started" state on the host 

• no stacktrace

Initializing / End-To-End Tests / fleet_debian_amd64_apm_server / Deploying a ubi8 stand-alone agent with the Elastic APM integration – APM Integration

Expand to view the error details

 Step the "apm-server" process is in the "started" state on the host 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / [empty] – TEST-x86_64-kubernetes-autodiscover-5bb79de7-2022-02-09-12:23:05.xml

• no error details
Expand to view the stacktrace

 Test report file /var/lib/jenkins/workspace/PR-2120-1-4ef4f600-7346-451d-8f86-9da4b6286a4f/outputs/3.131.93.198/TEST-x86_64-kubernetes-autodiscover-5bb79de7-2022-02-09-12:23:05.xml was length 0 

Steps errors

Expand to view the steps failures

Shell Script

• Took 11 min 6 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2120-1-d13ceddc-021c-4f11-8763-e01aa8f64958/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "integrations && ~@nightly && ~@skip:arm64" '

Archive the artifacts

• Took 0 min 0 sec . View more details here
• Description: [2022-02-09T12:36:34.692Z] Archiving artifacts script returned exit code 2

Shell Script

• Took 10 min 6 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2120-1-63a9b68a-9a47-4fff-94c6-9f64134e38ce/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "integrations && ~@nightly && ~@skip:amd64" '

Archive the artifacts

• Took 0 min 0 sec . View more details here
• Description: [2022-02-09T12:35:06.692Z] Archiving artifacts script returned exit code 2

Shell Script

• Took 10 min 4 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2120-1-c505035a-ea5d-41bf-bfce-4bd1fe4d5798/e2essh [email protected] -- 'sudo bash /home/ec2-user/e2e-testing/.ci/scripts/functional-test.sh "integrations && ~@nightly && ~@skip:amd64" '

Archive the artifacts

• Took 0 min 0 sec . View more details here
• Description: [2022-02-09T12:34:10.367Z] Archiving artifacts script returned exit code 2

Shell Script

• Took 18 min 40 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2120-1-82818963-6a2e-47c7-96f0-3c84a7bae277/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "apm_server && ~@nightly && ~@skip:amd64" '

Archive the artifacts

• Took 0 min 0 sec . View more details here
• Description: [2022-02-09T12:41:49.992Z] Archiving artifacts script returned exit code 2

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

• Name: Initializing / End-To-End Tests / fleet_sles15_integrations / Adding an Integration to a Policy #1 – Integrations
• Name: Initializing / End-To-End Tests / fleet_debian_amd64_integrations / Adding an Integration to a Policy #1 – Integrations
• Name: Initializing / End-To-End Tests / fleet_debian_arm64_integrations / Adding an Integration to a Policy #1 – Integrations
• Name: Initializing / End-To-End Tests / fleet_debian_amd64_apm_server / Deploying a default stand-alone agent with the Elastic APM integration – APM Integration
• Name: Initializing / End-To-End Tests / fleet_debian_amd64_apm_server / Deploying a ubi8 stand-alone agent with the Elastic APM integration – APM Integration
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / [empty] – TEST-x86_64-kubernetes-autodiscover-5bb79de7-2022-02-09-12:23:05.xml

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.