Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-14312

Yum proxy of mirrors.centos.org fails with encoding error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.5.1
    • Fix Version/s: 3.6.0
    • Component/s: Yum
    • Labels:
    • Story Points:
      0.5

      Description

      Reproduce steps...

      1. Create a yum proxy repository in Nexus with remote set to http://mirror.centos.org/centos/7/os/x86_64
      2. Configure yum in CentOS 7.3 to use it

      This fails with an error complaining that the encoding has not been set in the primary.xml file.

      Sure enough, if you check the file from RedHat it has:

      <?xml version="1.0" encoding="UTF-8"?>
      

      Our generated XML is missing the encoding:

      <?xml version="1.0"?>
      

      Full error log is below:

      (process:18863): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
      This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
      The overwriting error message was: Parsing primary.xml error: Specification mandate value for attribute e
      
      
      (process:18863): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
      This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
      The overwriting error message was: Parsing primary.xml error: attributes construct error
      
      
      (process:18863): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
      This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
      The overwriting error message was: Parsing primary.xml error: Couldn't find end of Start Tag rpm:entry line 481849
      
      
      (process:18863): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
      This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
      The overwriting error message was: Parsing primary.xml error: Premature end of data in tag rpm:provides line 481846
      
      
      (process:18863): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
      This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
      The overwriting error message was: Parsing primary.xml error: Premature end of data in tag format line 481839
      
      
      (process:18863): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
      This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
      The overwriting error message was: Parsing primary.xml error: Premature end of data in tag package line 481820
      
      
      (process:18863): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
      This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
      The overwriting error message was: Parsing primary.xml error: Premature end of data in tag metadata line 1
      
      
      
       One of the configured repositories failed (Unknown),
       and yum doesn't have enough cached data to continue. At this point the only
       safe thing yum can do is fail. There are a few ways to work "fix" this:
      
           1. Contact the upstream for the repository and get them to fix the problem.
      
           2. Reconfigure the baseurl/etc. for the repository, to point to a working
              upstream. This is most often useful if you are using a newer
              distribution release than is supported by the repository (and the
              packages for the previous distribution release still work).
      
           3. Run the command with the repository temporarily disabled
                  yum --disablerepo=<repoid> ...
      
           4. Disable the repository permanently, so yum won't use it by default. Yum
              will then just ignore the repository until you permanently enable it
              again or use --enablerepo for temporary usage:
      
                  yum-config-manager --disable <repoid>
              or
                  subscription-manager repos --disable=<repoid>
      
           5. Configure the failing repository to be skipped, if it is unavailable.
              Note that yum will try to contact the repo. when it runs most commands,
              so will have to try and fail each time (and thus. yum will be be much
              slower). If it is a very temporary problem though, this is often a nice
              compromise:
      
                  yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
      
      Parsing primary.xml error: Input is not proper UTF-8, indicate encoding !
      Bytes: 0x92 0x73 0x20 0x64
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              moncef Moncef Ben-Soula
              Reporter:
              rseddon Rich Seddon
              Last Updated By:
              Peter Lynch
              Team:
              Nexus - Formats
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title