[Spacewalk-list] Error: Cannot retrieve repository metadata (repomd.xml) for

Wed Jan 8 16:12:53 UTC 2020

Hi Laurence,

I've been having a similar issue on Spacewalk 2.10. Spacewalk "Seems" to be syncing repositories just fine, but obviously isn't as newly added packages don't get listed in spacewalk after syncing. It just seems to retain an older list of packages.

I'm interested in any solution that comes your way so I'll be watching :)

Jody McIvor
Sr. Systems Administrator, Integration
Les Services D'intégration
[TEL] (250) 852-5202

jmcivor at bclc.com
BCLC.com

-----Original Message-----
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> On Behalf Of spacewalk-list-request at redhat.com
Sent: January 8, 2020 4:54 AM
To: spacewalk-list at redhat.com
Subject: Spacewalk-list Digest, Vol 140, Issue 4

Send Spacewalk-list mailing list submissions to
spacewalk-list at redhat.com

To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/spacewalk-list
or, via email, send a message with subject or body 'help' to
spacewalk-list-request at redhat.com

You can reach the person managing the list at
spacewalk-list-owner at redhat.com

When replying, please edit your Subject line so it is more specific than "Re: Contents of Spacewalk-list digest..."

Today's Topics:

   1. Missing Fedora 31 client repositories forSpacewalk 2.9
      (Neal Gompa)
   2. Error: Cannot retrieve repository metadata(repomd.xml) for
      repository (Laurence Rosen)
   3. Re: Missing Fedora 31 client repositories for Spacewalk 2.9
      (Michael Mraka)
   4. Re: Missing Fedora 31 client repositories for Spacewalk 2.9
      (Brian Long)
   5. Spacewalk client not checking in on CentOS 7 (Len Ewen)

----------------------------------------------------------------------

Message: 1
Date: Tue, 7 Jan 2020 16:26:41 -0500
From: Neal Gompa <ngompa13 at gmail.com>
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Missing Fedora 31 client repositories for
Spacewalk 2.9
Message-ID:
<CAEg-Je-wsvoBvH3ekyfJakWsMOFzemOtKYYx_FCkmRhkrgnhWA at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Hey all,

It seems we don't have client repositories for Fedora 31 for Spacewalk 2.9. Can someone please build the client packages for Fedora 31 and make them available?

Thanks in advance.

--
?????????/ Always, there's only one truth!

------------------------------

Message: 2
Date: Tue, 7 Jan 2020 20:33:34 -0500
From: Laurence Rosen <lrosen at interactions.com>
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Error: Cannot retrieve repository metadata
(repomd.xml) for repository
Message-ID:
<CAOwbKjhAQY2p+bxXquODpjNjBgqn2NsSnuOF6qUOz-8Ae=_+7w at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Yeah, I don't get it!  The system registered ok.
yum repolist works for the other repos.  I even installed a package.

--

Larry Rosen

TechOps - Systems Administrator

[image: Interactions: Simply Better Understanding]

Indy Heritage Park - 5th Floor

o: 317.810.2848

lrosen at interactions.com

www.interactions.com

--

*******************************************************************************

This e-mail and any of its attachments may contain
Interactions LLC
proprietary information, which is privileged,
confidential, or subject to
copyright belonging to the Interactions
LLC. This e-mail is intended solely
for the use of the individual or
entity to which it is addressed. If you
are not the intended recipient of this
e-mail, you are hereby notified that
any dissemination, distribution, copying,
or action taken in relation to
the contents of and attachments to this e-mail
is strictly prohibited and
may be unlawful. If you have received this e-mail in
error, please notify
the sender immediately and permanently delete the original
and any copy of
this e-mail and any printout. Thank You.?

*******************************************************************************?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20200107/fb89cf38/attachment.html>

------------------------------

Message: 3
Date: Wed, 8 Jan 2020 09:29:26 +0100
From: Michael Mraka <michael.mraka at redhat.com>
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Missing Fedora 31 client repositories
for Spacewalk 2.9
Message-ID: <20200108082926.GA3836 at magni.redhat.com>
Content-Type: text/plain; charset=utf-8

Neal Gompa:
> Hey all,
>
> It seems we don't have client repositories for Fedora 31 for Spacewalk
> 2.9. Can someone please build the client packages for Fedora 31 and
> make them available?

Fedora 31 had not been around when Spacewalk 2.9 was released therefore there
are no client repositories.
You can use Fedora 31 client from nightly repos.
https://copr.fedorainfracloud.org/coprs/g/spacewalkproject/nightly-client/

Regards,

--
Michael Mr?ka
System Management Engineering, Red Hat

------------------------------

Message: 4
Date: Wed, 8 Jan 2020 07:44:33 -0500
From: Brian Long <briandlong at gmail.com>
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Missing Fedora 31 client repositories
for Spacewalk 2.9
Message-ID:
<CANzVr1Y5J+LwMsti8x7mKhy70+pj_1eg_O3wGG81dTxxe88ibw at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Considering Spacewalk 2.9 was released in January 2019, what is the
plan for 2.10?  Has Red Hat-sponsored Spacewalk development diminished
since Red Hat Satellite 6.x is based on TheForeman and Red Hat
Satellite 5.x is EOL in May 2020?

https://access.redhat.com/support/policy/updates/satellite

/Brian/

On Wed, Jan 8, 2020 at 3:30 AM Michael Mraka <michael.mraka at redhat.com> wrote:
>
> Neal Gompa:
> > Hey all,
> >
> > It seems we don't have client repositories for Fedora 31 for Spacewalk
> > 2.9. Can someone please build the client packages for Fedora 31 and
> > make them available?
>
> Fedora 31 had not been around when Spacewalk 2.9 was released therefore there
> are no client repositories.
> You can use Fedora 31 client from nightly repos.
> https://copr.fedorainfracloud.org/coprs/g/spacewalkproject/nightly-client/
>
> Regards,
>
> --
> Michael Mr?ka
> System Management Engineering, Red Hat
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list

------------------------------

Message: 5
Date: Wed, 8 Jan 2020 07:54:06 -0500
From: Len Ewen <ewenf at uindy.edu>
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Spacewalk client not checking in on CentOS 7
Message-ID:
<CANwEa2j-r_XUDpLn9_pB8SqFdcr5i6BiKMAWr=mMWgUDVhb01w at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I know this a stupid noob question but I have a problem.  I've got a clean
built, fresh out of the box spacewalk 2.9 server and a 2.9 client.  The
client checked in once, but hasn't checked again for the last 16 hours.  16
hours seems like a long time for a check in to happen, but I am not sure
what is going on.  What am I missing?  Do I need to set up a cron job to
update or something?

---------------

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362

[image: UIndyIT.jpg]

Confidentiality Notice: This communication and/or its content are for the
sole use of the intended recipient, and may be privileged, confidential, or
otherwise protected from disclosure by law. If you are not the intended
recipient, please notify the sender and then delete all copies of it.
Unless you are the intended recipient, your use or dissemination of the
information contained in this communication may be illegal.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20200108/0f3100d1/attachment.html>

------------------------------

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

End of Spacewalk-list Digest, Vol 140, Issue 4
**********************************************

________________________________
This email is intended only for the addressee. It may contain confidential or proprietary information that cannot be disclosed without BCLC's permission. If you have received this email in error, please notify the sender immediately and delete the email.