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

NR-238698: Issue fix - GcpMachinePoolMachine Status not populating correct ProvisioningState and LatestModelApplied fields #20

Conversation

sachin-shankar
Copy link

Refactored the way we populate the GcpMachinePoolMachine object status to ensure it reflects the correct Provisioning State and Image Model status.

@sachin-shankar sachin-shankar changed the base branch from nr-main to GCPMachinePools May 24, 2024 12:18
BrennenMM7 and others added 3 commits May 24, 2024 05:32
It was observed that the `GCPMachinePoolMachine` object wasn't updating the following fields correctly before:

`LatestModelApplied, ProvisioningState`

Fix - Use the raw GCP `instance` to update the same instead.
…PoolMachine` status.

- Create new type for VM provisioning state derived from GCP Instance status.
@sachin-shankar sachin-shankar force-pushed the update-gcpmachinepoolmachine-instanc-state branch from 99cc9ac to 97cc6ed Compare May 24, 2024 12:36
@sachin-shankar sachin-shankar changed the base branch from GCPMachinePools to nr-main May 24, 2024 19:55
@sachin-shankar sachin-shankar changed the base branch from nr-main to GCPMachinePools May 28, 2024 09:23
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