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-1284] Timed out waiting for INBM Dispatcher response after trigger first run for power heuristic operation #649

Conversation

gblewis1
Copy link
Contributor

@gblewis1 gblewis1 commented Mar 5, 2025

PULL DESCRIPTION

This bug is the result of a coding mistake which tries to look up schedule info when responding to a request with a request ID. Scheduling info is only relevant when sending a result WITHOUT a request ID.

Impact Analysis

Info Please fill out this column
Root Cause reusing same method for different tasks
Jira ticket NEXMANAGE-1284

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

… trigger first run for power heuristic operation

This bug is the result of a coding mistake which tries to look up
schedule info when responding to a request with a request ID.
Scheduling info is only relevant when sending a result WITHOUT
a request ID.
@gblewis1 gblewis1 marked this pull request as ready for review March 5, 2025 03:24
@gblewis1 gblewis1 requested a review from nmgaston as a code owner March 5, 2025 03:24
@gblewis1 gblewis1 merged commit 65fb545 into develop Mar 5, 2025
7 of 8 checks passed
@gblewis1 gblewis1 deleted the gblewis1/NEXMANAGE-1284/timed_out_waiting_for_inbm_dispatcher_response branch March 5, 2025 05:09
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