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

porch: git access parameters do not follow changes in the porch Repository object #532

Closed
kispaljr opened this issue Feb 21, 2024 · 5 comments
Assignees
Labels
area/package-management SIG Automation Package Management Subproject area/platform area/porch Porch related issues bug Something isn't working triaged
Milestone

Comments

@kispaljr
Copy link
Contributor

I encountered the following issue that seems to be a bug in the git client handling in porch:

  1. Repository.config.porch.kpt.dev object created with missing secretRef field
  2. kpt alpha rpkg init ... command fails with message: Error: Internal error occurred: authentication required
  3. Correct secretRef info is patched into the Repository (with kubectl apply)
  4. kpt alpha rpkg init ... command fails with the same message: Error: Internal error occurred: authentication required
  5. Repository object is deleted and the recreated with the same contents
  6. kpt alpha rpkg init ... command succeeds
@kispaljr kispaljr added the area/package-management SIG Automation Package Management Subproject label Feb 21, 2024
@tliron tliron added the area/porch Porch related issues label Feb 26, 2024
@kispaljr
Copy link
Contributor Author

kispaljr commented Mar 1, 2024

This seems to be a duplicate of kptdev/kpt#4088
Sorry.
Should I leave the issue open anyway, considering that eventually we want to track porch issues under Nephio, not under kpt?

@liamfallon
Copy link
Member

I think we should probably move any issues that still exist (probably most of them) across to here. Maybe we can check with @johnbelamaric about what's the best thing to do.

@johnbelamaric
Copy link
Member

Yeah, we should move them here. Moving issues from one org to a different org is not something that is natively supported by GitHub. But it looks like there are some workarounds in the comments here (I have not tried any of these): https://github.com/orgs/community/discussions/5766

@gvbalaji gvbalaji added this to R4 Apr 3, 2024
@gvbalaji gvbalaji moved this to Todo in R4 Apr 3, 2024
@gvbalaji gvbalaji added this to the R3 milestone Apr 3, 2024
@liamfallon liamfallon added the bug Something isn't working label May 17, 2024
@liamfallon
Copy link
Member

Triaged

@kushnaidu kushnaidu self-assigned this Jun 12, 2024
@kushnaidu kushnaidu moved this from Todo to In Progress in R4 Jun 14, 2024
@kushnaidu
Copy link
Contributor

kushnaidu commented Jun 20, 2024

I cannot reproduce the issue any more and won't create a PR for this issue.
My findings are as follows,

Repository created without secretref -
created repo with no credentials

porchctl command throws error with auth failed -
error with init command

Update repo and init again with porchctl -
patch repo and init
The command succeeds without any issue.

Same tried with kpt alpha and without any issue -
kpt

As soon as we change the repository, we can see in the logs that porch can recognize the change and updates the cache.

Closing the ticket.

@github-project-automation github-project-automation bot moved this from In Progress to Done in R4 Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/package-management SIG Automation Package Management Subproject area/platform area/porch Porch related issues bug Something isn't working triaged
Projects
Status: Done
Development

No branches or pull requests

6 participants