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

[NEXMANAGE-899] Fix dispatcher not recording state file and causing snapshot failure #583

Merged
merged 6 commits into from
Oct 24, 2024

Conversation

yengliong93
Copy link
Contributor

@yengliong93 yengliong93 commented Oct 22, 2024

PULL DESCRIPTION

The dispatcher agent raises an exception when it fails to retrieve the state value from the state file. This results in the dispatcher not recording the restart_reason and snapshot_num, which are important for the rollback scenario.
This PR removes the exception that occurs when the dispatcher agent is unable to retrieve the state value from the state file. In cases where the state is None, the dispatcher will still record the restart_reason and snapshot_num.

Impact Analysis

Info Please fill out this column
Root Cause Dispatcher not records the restart_reason and snapshot_num.
Jira ticket NEXMANAGE-899

CODE MAINTAINABILITY

  • Added required new tests relevant to the changes
  • Updated Documentation as relevant to the changes
  • PR change contains code related to security
  • PR introduces changes that break compatibility with other modules/services (If YES, please provide description)
  • Run go fmt or format-python.sh as applicable
  • Update Changelog
  • Integration tests are passing
  • If Cloudadapter changes, check Azure connectivity manually

Code must act as a teacher for future developers

…napshot failure

The dispatcher agent raises an exception when it fails to retrieve the
state value from the state file. This results in the dispatcher not
recording the restart_reason and snapshot_num, which are important for
the rollback scenario.
This PR removes the exception that occurs when the dispatcher agent is
unable to retrieve the state value from the state file. In cases where
the state is None, the dispatcher will still record the restart_reason and
snapshot_num.

Signed-off-by: yengliong <[email protected]>
@gblewis1
Copy link
Contributor

Would like to see integration test passing -- will try triggering it later (Jenkins is down now).

@gblewis1
Copy link
Contributor

@yengliong93 this looks good but I would like to run it through integration test first.

@gblewis1
Copy link
Contributor

Both build and integration tests are blocked by Penang power outage.

@yengliong93
Copy link
Contributor Author

IT is failing. Checking it...

@yengliong93
Copy link
Contributor Author

Unit tests fix and IT pass.

@yengliong93 yengliong93 merged commit 74476aa into develop Oct 24, 2024
15 checks passed
@yengliong93 yengliong93 deleted the fix-snapshot-not-record branch October 24, 2024 07:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants