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

Unable to sync repository with pulp (RH satellite) #19

Closed
kmittman opened this issue Jun 10, 2021 · 14 comments
Closed

Unable to sync repository with pulp (RH satellite) #19

kmittman opened this issue Jun 10, 2021 · 14 comments
Assignees

Comments

@kmittman
Copy link
Collaborator

Source: https://forums.developer.nvidia.com/t/error-syncing-rhel8-cuda-repo/176276

Multiple reports of unable to mirror/sync https://developer.download.nvidia.com/compute/cuda/repos/rhel8/x86_64/ repository with pulp since ~ 1 month ago.

"traceback"=>
     "Traceback (most recent call last):\n" +
     "  File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 367, in trace_task\n" +
     "    R = retval = fun(*args, **kwargs)\n" +
     "  File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line 688, in __call__\n" +
     "    return super(Task, self).__call__(*args, **kwargs)\n" +
     "  File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line 110, in __call__\n" +
     "    return super(PulpTask, self).__call__(*args, **kwargs)\n" +
     "  File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 622, in __protected_call__\n" +
     "    return self.run(*args, **kwargs)\n" +
     "  File \"/usr/lib/python2.7/site-packages/pulp/server/controllers/repository.py\", line 860, in sync\n" +
     "    raise pulp_exceptions.PulpExecutionException(_('Importer indicated a failed response'))\n" +
     "PulpExecutionException: Importer indicated a failed response\n",

modules.yaml document is valid UTF-8 but error suggests parsing failing at stream key-values.

        "distribution"=>
         {"items_total"=>0,
          "state"=>"FINISHED",
          "error_details"=>[],
          "items_left"=>0},
        "modules"=>
         {"state"=>"FAILED",
          "error"=>
           "strings in documents must be valid UTF-8: '\\x8c\\x01\\x00\\x00\\x04465-dkms\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04418-dkms\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04450\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04440\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04460\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04455\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04465\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04440-dkms\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04455-dkms\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04460-dkms\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04latest-dkms\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04450-dkms\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04418\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x04latest\\x00\\x14\\x00\\x00\\x00\\x020\\x00\\x08\\x00\\x00\\x00default\\x00\\x00\\x00'"},
        "errata"=>{"state"=>"NOT_STARTED"},
        "metadata"=>{"state"=>"FINISHED"}}},

Looking at another modularity-enabled repository, strings are enclosed in double-quotes ...

@kmittman kmittman self-assigned this Jun 10, 2021
@dralley
Copy link

dralley commented Jun 11, 2021

edit: disregard. I know what the problem is, it's not a problem with the metadata pre-se, its an edge case triggered by a specific arrangement of it.

@dralley
Copy link

dralley commented Jun 12, 2021

I can say confidently that this isn't an Nvidia repo issue.

@zvonkok
Copy link

zvonkok commented Jul 26, 2021

I think this can be closed.

@kmittman
Copy link
Collaborator Author

Pinging @dralley to comment.

@dralley
Copy link

dralley commented Jul 26, 2021

I agree - there is a fix deployed upstream that I believe is still trickling down into an actual release.

@kmittman
Copy link
Collaborator Author

Closing based on recommendation from Red Hat engineers.

@stuartcampbell
Copy link

I know this is closed, but just to comment that this is still an issue for the RHEL8/EL8 repos (works fine for the RHEL/EL7) - all other yum repos we sync also work fine, it's only this NVIDIA one that broke sometime in May.

I will open a support request with Red Hat to see what they say and comment here on any eta for the fix.

Thank you for looking into it anyway.

@mulderij
Copy link

mulderij commented Aug 25, 2021

I'll have to agree with @stuartcampbell
We experience the same issue on the RHEL8-repo. No issues with RHEL7-repo or any other repo in our Satellite.
BTW: we tried with Satellite 6.9.2 & 6.9.4

@stdweird
Copy link

@stuartcampbell @mulderij any luck so far getting a fix for this?
@dralley what is fix are you talking about? is it some satellite hotfix that customers can get their hands on?

@stdweird
Copy link

ok, found patch in https://forums.developer.nvidia.com/t/error-syncing-rhel8-cuda-repo/176276/16
i confirm that it works.

@mulderij
Copy link

@stdweird

@stuartcampbell @mulderij any luck so far getting a fix for this?

We did apply the workaround and that worked. Today we tried again on Satellite 6.9.5 without the workaround and that also appears to work.

@stdweird
Copy link

@mulderij thanks. i read the releasenotes yestderday, nothing jumped out as relevant so i tried the patch instead. good to see it confirmed !

@kmittman
Copy link
Collaborator Author

Thank you for confirming that RH Satellite now has the fix.

@dralley
Copy link

dralley commented Sep 23, 2021

Looks like the patch is targeted for Satellite 6.9.7.

Apologies it took so long, apparently because there was a needinfo flag, it didn't get included in the triage discussions for the previous release.

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

No branches or pull requests

6 participants