-
Notifications
You must be signed in to change notification settings - Fork 79
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
'NoneType' object has no attribute 'artifact_set_sha256' when syncing a recently updated deb remote #719
Comments
@paralllax
If that fixes the issue, please try syncing again once more using optimize mode:
If this second sync now works (immediately after the other sync, it should be very quick), then this was likely a one time effect due to a previous sync that was corrected by the next successful sync. If you are consistently getting the error when using
|
Hi @quba42, My apologies, I somehow missed the notification for your update! After about a week or so, the issue went away, I assume because something changed on the endpoint. However it came back a couple days ago once more. It looks like that directive may not be available in our version:
I tried with the following:
I did a normal sync after which worked. Thank you for sharing the work around! Since it's come up a couple times for the same set of 3 repos (microsoft repos for bionic, focal, & jammy), in case it's still relevant, here is the version output for bionic before I used your work around.
|
Apart from that, you have given us just about all the information you can for us to keep digging for the root cause. |
Version
Installed and setup via ansible (
pulp_installer
)Describe the bug
It looks like there is an issue comparing the indices for a remote when syncing a repository after the remote has updated. When running a sync job, it returns with this error:
The stack trace for the error is:
To Reproduce
It may be difficult to reproduce. This is only happening on the microsoft repositories. We are syncing arch amd64 for jammy, focal, and bionic. In order to reproduce it you need to have a previous version of the repository/release. If you setup a brand new remote and repository, it doesn't encounter this issue when syncing, since it has nothing to compare from.
These are the basic settings
Expected behavior
The repository should sync and pull in the new updates without any issues.
Additional context
The remote microsoft repos we're mirror'ing were updated several days ago. The day they were updated is when our sync's started to fail. It's only for those repos. I am uncertain if they configured something incorrectly in their release, or it's simply a bug with the plugin. The timing is odd nonetheless. These are the URLs:
if it's of any relevance, here is the remote config for one of the above. They're identical aside from name and URL
The text was updated successfully, but these errors were encountered: