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

QA test: State Store migrations #4962

Closed
AndersonQ opened this issue Jun 19, 2024 · 4 comments
Closed

QA test: State Store migrations #4962

AndersonQ opened this issue Jun 19, 2024 · 4 comments
Assignees
Labels
QA:Validated Validated by the QA Team Testing

Comments

@AndersonQ
Copy link
Member

Test scenarios:

  • Action store -> JSON state store
  • State Store (YAML) -> JSON state store

Action store -> JSON state store

  • Install and enroll a 7.17 Elastic Agent
  • upgrade to s build containing Fix and refactor the state store #4441
  • ensure the agent is healthy, connected to fleet and with a valid configuration
    • use the agent status command to check it's healthy and connected to fleet
    • check on fleetUI the agent is healthy
    • use the inspect command to ensure the agent's local copy of the policy is correct

State Store (YAML) -> JSON state store

  • Install and enroll the latest released Elastic Agent
  • upgrade to s build containing Fix and refactor the state store #4441
  • ensure the agent is healthy, connected to fleet and with a valid configuration
    • use the agent status command to check it's healthy and connected to fleet
    • check on fleetUI the agent is healthy
    • use the inspect command to ensure the agent's local copy of the policy is correct
@AndersonQ
Copy link
Member Author

@amolnater-qasource if you have any question, let me know or ping me on slack.

@amolnater-qasource
Copy link

Hi @AndersonQ

We have revalidated this issue on latest 8.15.0-SNAPSHOT kibana and had below observations:

Observations:

  • On upgrading 7.17.22 and 8.14.1 running Agent status command- All the components remain in Running state.
  • Post upgrade agents remain Healthy.
  • On running Inspect command, agent policy is correct.

Steps followed:

  1. Install 7.17.22 and 8.14.1 agent.
  2. Upgrade both the agents to latest 8.15.0 SNAPSHOT : https://snapshots.elastic.co/8.15.0-f2f3669f/downloads/.
  3. Run sudo elastic-agent status.
  4. Observe agent status under Fleet>Agents tab.
  5. Run sudo elastic-agent inspect.

7.17.22 status and inspect command before upgrade:
beforeUpgrade717.txt

7.17.22 status and inspect command after upgrade:
afterUpgrade717.txt

8.14.1 status and inspect command before upgrade:
beforeUpgrade8141.txt

8.14.1 status and inspect command after upgrade:
afterUpgrade8141.txt

Build details:
VERSION: 8.15.0 SNAPSHOT
BUILD: 75836
COMMIT: 28cad8dff93db87cc8045c5871d77a7936a8b0d2
Artifact Link: https://snapshots.elastic.co/8.15.0-f2f3669f/downloads/beats/elastic-agent/elastic-agent-8.15.0-SNAPSHOT-linux-x86_64.tar.gz

Please let us know if we are missing anything here.

Thanks!

@jlind23
Copy link
Contributor

jlind23 commented Jul 1, 2024

Thanks @amolnater-qasource! Closing this issue as done then.

@jlind23 jlind23 closed this as completed Jul 1, 2024
@amolnater-qasource
Copy link

Thank you for confirming! @jlind23

@amolnater-qasource amolnater-qasource added QA:Validated Validated by the QA Team and removed QA:Needs Validation Needs validation by the QA Team labels Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA:Validated Validated by the QA Team Testing
Projects
None yet
Development

No branches or pull requests

3 participants