Skip to content

drpc: log enhancements#2366

Open
raghavendra-talur wants to merge 3 commits intoRamenDR:mainfrom
raghavendra-talur:rtalur-log-enhancement-drpc
Open

drpc: log enhancements#2366
raghavendra-talur wants to merge 3 commits intoRamenDR:mainfrom
raghavendra-talur:rtalur-log-enhancement-drpc

Conversation

@raghavendra-talur
Copy link
Member

These are some simple log enhancements in the drpc reconcile workflow.

Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com>
Copy link
Member

@ELENAGER ELENAGER left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, only lint error must be fixed

This helps the log reader to understand that the next log line failure
to get the placementRule is not a critical error.

Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com>
Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com>
@raghavendra-talur raghavendra-talur force-pushed the rtalur-log-enhancement-drpc branch from e2b3c47 to 2c47e50 Compare December 17, 2025 20:20
Copy link
Member

@asn1809 asn1809 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

return nil, err
}

placementType = "PlacementRule"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the placementType assignments are swapped. This should be "Placement", since we're in the error block where PlacementRule wasn't found.

"can't proceed. PlacementRule and Placement CR with the same name exist on the same namespace")
}

placementType = "Placement"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be "PlacementRule"

@raaizik
Copy link
Member

raaizik commented Jan 1, 2026

I already have an open PR for this purpose @raghavendra-talur #2045

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.

6 participants