Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test ticket for Initiating Fleet setup on boot #120726

Closed
dikshachauhan-qasource opened this issue Dec 8, 2021 · 4 comments
Closed

Test ticket for Initiating Fleet setup on boot #120726

dikshachauhan-qasource opened this issue Dec 8, 2021 · 4 comments
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team triage_needed

Comments

@dikshachauhan-qasource
Copy link

dikshachauhan-qasource commented Dec 8, 2021

This is the testing ticket request to validate Initiation of Fleet setup on boot process.

Testing steps are shared at : #111858 (comment)

Assigned to @dikshachauhan-qasource

@dikshachauhan-qasource dikshachauhan-qasource added the bug Fixes for quality problems that affect the customer experience label Dec 8, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 8, 2021
@dikshachauhan-qasource
Copy link
Author

Hi @EricDavisX

We have validated this ticket and found it working fine.

Steps performed:

  • Created a self managed 7.15.2 environment.
  • Accessed the fleet UI and Checked out the default installed integrations[Elastic Agent, system, Fleet-server].
  • Installed few other supported integrations : APM, Elastic synthesis and Endpoint security.
  • And recorded the versions of each integrations
Integration Version
APM 0.4.0
Elastic Agent 1.2.1
Endpoint 1.1.1
Fleet Server 1.0.1
Synthetics 0.3.0
System 1.6.4
  • Now, took a snapshot on Kibana. > By Creating a repository and snapshot policy.
  • Upgraded Elasticsearch and Kibana to 7.16.0
  • Checked out packages versions and upgraded them under settings tab to below available versions.
Integration Version
APM 7.16.0
Elastic Agent 1.3.0
Endpoint 1.2.2
Fleet Server 1.1.0
Synthetics 0.5.0
System 1.6.4
  • Now Rolled back with following steps.
  1. Stopped Kibana Instance.
  2. Performed DELETE /.kibana* API request to your Elasticsearch instance
  3. Restored previous 7.15 data using the Elasticsearch API
# You may need to do this first to allow wildcard deletes
PUT _cluster/settings
{
  "persistent" : {
    "action.destructive_requires_name" : false
  }
}

# Actual delete command
POST _snapshot/my-repository/[timestamp]_snapshot/_restore
{
  "indices": ".kibana*"
}
  1. Started 7.15 Kibana instance.

Observations:
Kibana rolled out successfully and earlier package versions were also available.

Screenshots:
image

image

Further, Please let us know is more testing is required around packages version and upgrades here.

Thanks
QAS

@kpollich
Copy link
Member

kpollich commented Dec 8, 2021

@dikshachauhan-qasource thanks so much for this! Very happy to see this process went well with the QA team 🎉

@azasypkin azasypkin added Team:Fleet Team label for Observability Data Collection Fleet team triage_needed labels Dec 16, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@jen-huang
Copy link
Contributor

This looks to be done, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team triage_needed
Projects
None yet
Development

No branches or pull requests

5 participants