-
Notifications
You must be signed in to change notification settings - Fork 227
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
porch: packagevariant creating extra revisions #3877
Comments
Controller log. Seeing this a lot:
|
This is so weird. I deleted all the packagevariantsets; all the packagevariants were deleted (see though #3878). I manually deleted all the lingering branches for "edge-02" (see #3882). I used
|
More info:
|
From the logs, I see this over and over:
This is from the line:
So, @natasha41575, we are not setting newPR.Name when contructing the PackageRevision. Is this intentional? Is the idea that Porch will create a name for us? That's fine - but for some reason, just with this package, even though there doesn't seem to be an error, we keep creating new PRs. |
Ok, so this may be part of the issue. The PackageRevision is not created with the ownerRef. Look at these two PRs, one is for "edge-02" and one is not:
The one that is working has the ownerRef set, the other doesn't. I have no idea how that is happening, though, since it is set here: |
Actually, one of the few dozen entries for edge-02 does have an ownerRef. Huh. |
Hmm. That's the most recent one. |
I'm trying to understand why this is happening just with Also, could you share what your |
I don't think so. I am confused as well. |
No on that repo, because of the other bug. I am using http://github.com/nephio-test |
I am Repos are setup like this the yamls here, using the repos.sh script in there (see, they no longer point to the directories): https://github.com/johnbelamaric/nephio-testorg-deploy |
Oddly I am not seeing the same behavior when I run the controller locally. |
The other weird thing as I mentioned before is that the UI does not show the bogus package revisions, only the CLI and of course looking directly at the repo. |
So, after restarting the porch-controllers and the porch-server having restarted itself:
This makes me think that somehow the porch-server state got confused due to all the previous errors, and perhaps this is the source of the issue. I still can't explain it. But I will watch to see if there are more issues. |
So as I said offline, since this is (hopefully) an uncommon issue that will be difficult to repro, I think we can put it in the backlog for now. It's possible that porch was confused by all the previous errors, but I'm still not sure how that would affect the PackageVariant's ownerrefs and detection of existing packages. If we see any similar issues, we should investigate further. |
Expected behavior
PackageVariant will create a single downstream.
Actual behavior
Usually it works. But I have this weirdness:
Repositories
PackageVariant resources (created by PackageVariantSet controller):
Those both look fine. But, here are my rpkgs:
The
us-central1-edge-02
variant has gone crazy!This is in the logs a lot:
Information
Steps to reproduce the behavior
I'll work on a cleaner repro.
The text was updated successfully, but these errors were encountered: