Results 1 to 6 of 6

Thread: ZYPPER REF

  1. #1

    ZYPPER REF

    SMT SLES12 SP2 running as guest on KVM LPAR.
    Trying to refresh the repositories and receive the following:
    Repository 'SLES12-SP2-12.2-0' is up to date.
    Retrieving repository 'SLES12-SP2-Pool' metadata .................................................. .................................................. ....[error]
    Repository 'SLES12-SP2-Pool' is invalid.
    [SMT-http_lrtp9050_fmr_com:SLES12-SP2-Pool|http://lrtp9050.fmr.com/repo/SUSE/Pr...p9050_fmr_com] Valid metadata not found at specified URL
    Please check if the URIs defined for this repository are pointing to a valid repository.
    Skipping repository 'SLES12-SP2-Pool' because of the above error.
    Retrieving repository 'SLES12-SP2-Updates' metadata .................................................. .................................................. .[error]
    Repository 'SLES12-SP2-Updates' is invalid.
    [SMT-http_lrtp9050_fmr_com:SLES12-SP2-Updates|http://lrtp9050.fmr.com/repo/SUSE/Up...p9050_fmr_com] Valid metadata not found at specified URL
    Please check if the URIs defined for this repository are pointing to a valid repository.
    Skipping repository 'SLES12-SP2-Updates' because of the above error.
    Some of the repositories have not been refreshed because of an error.

    Sync with SCC is working with no problems.
    Repositories were added with YAST

  2. #2

    Re: ZYPPER REF

    Just a few things to refine this a bit:

    Is it safe to assume that the LPAR is also SLES 12 SP2, not just the SMT
    software on top of it? That is probably implied, but I do not know it for
    sure so figured i would ask.

    Has this ever worked before from this box, or are these both newly-added
    repositories (vs. ones that worked and today do not work)?

    Have you tried loading those URIs in a web browser to see if they show
    anything valid at all?

    Do you have other SMT systems with which you could compare? Not being an
    SMT guru I do no know if the URI should go all of the way to the 'product'
    directory or stop at the OS level, or whatever.

    If no helpful responses show up in the next few days, you may have better
    luck getting SMT help in the forum for applications, or installation, or
    configuration, or something. I do not think SMT has its own, but more
    people frequent those areas than the System X area, and I would guess this
    is not an issue specific to System Z as much as SMT.


    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.

  3. Re: ZYPPER REF

    Hi and welcome to the Forum
    Is the system running btrfs filesystem, if so, have a look at this TID;
    https://www.suse.com/support/kb/doc/?id=7017376
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  4. #4

    Re: ZYPPER REF

    Host server running on LPAR is SLES12 SP2
    We have SMT working on a different environment (z/VM v6.3 with SLES11 SP4 guests) and that particular set of repositories works with no problem.
    The SLES11 server still points to NCC rather than SCC.

  5. #5

    Re: ZYPPER REF

    We found our problem. We changed the default location of the downloaded mirrored files in smt.conf.
    needed to add a symbolic link in /srv/www/htcdocs/repo pointing to the new location

    Thanks to everyone who replied.

  6. #6

    Re: ZYPPER REF

    On 06/27/2017 08:44 AM, fidlinux wrote:
    >
    > We found our problem. We changed the default location of the downloaded
    > mirrored files in smt.conf.
    > needed to add a symbolic link in /srv/www/htcdocs/repo pointing to the
    > new location


    Great explanation; thank-you for providing the resolution as it will
    probably help others in the future.


    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •