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

Missing Metadata for ProjectList in project.openshift.io/v1 #2064

Closed
Mangaal opened this issue Oct 16, 2024 · 2 comments
Closed

Missing Metadata for ProjectList in project.openshift.io/v1 #2064

Mangaal opened this issue Oct 16, 2024 · 2 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@Mangaal
Copy link

Mangaal commented Oct 16, 2024

Description:
It appears that the metadata field, specifically resourceVersion, is missing in the ProjectList object

Questions:
Is the absence of resourceVersion in the ProjectList metadata for project.openshift.io/v1 by design, or is this a bug?
If this is by design, could you please clarify the reasoning behind it?

This caused issues when handling watch events in the Argo CD gitops-engine. After printing out the API resource details during troubleshooting, I confirmed that the resourceVersion is missing for ProjectList.

Here is the relevant log output:

&{map[apiVersion:project.openshift.io/v1 kind:ProjectList metadata:map[]] 
&{map[apiVersion:apps/v1 kind:StatefulSetList metadata:map[resourceVersion:50313]]
&{map[apiVersion:operator.openshift.io/v1 kind:KubeControllerManagerList metadata:map[continue: resourceVersion:50313]]
&{map[apiVersion:operator.openshift.io/v1 kind:KubeControllerManagerList metadata:map[continue: resourceVersion:50313]]
&{map[apiVersion:argoproj.io/v1alpha1 kind:AppProjectList metadata:map[continue: resourceVersion:72951]]
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 15, 2025
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 15, 2025
@Mangaal Mangaal closed this as completed Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

2 participants