[Spacewalk-list] Help setting up Ubuntu channel(s)

[Dimitri Yioulos]

It's more that I'm having problems getting the repos right.  For example, based on stuff I've read, I'm trying to use the following Ubuntu repo:  http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/.  But, when I run repo-sync, I get the following:

[root at spacewalk dyioulos]# /usr/bin/spacewalk-repo-sync --channel ubuntu-16.04-lts-main
15:28:27 ======================================
15:28:27 | Channel: ubuntu-16.04-lts-main
15:28:27 ======================================
15:28:27 Sync of channel started.
15:28:27 Repo URL: http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/
15:28:27 ERROR: Cannot retrieve repository metadata (repomd.xml) for repository: ubuntu_dists_xenial_main_binary-amd64_. Please verify its path and try again
15:28:27 Repo URL: http://de.archive.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/
15:28:28 ERROR: Cannot retrieve repository metadata (repomd.xml) for repository: ubuntu_dists_xenial-security_main_binary-amd64_. Please verify its path and try again
15:28:28 Sync of channel completed in 0:00:00.
15:28:28 Total time: 0:00:00

Note this - ERROR: Cannot retrieve repository metadata (repomd.xml).  Isn't repodm.xml yum-related?  Anyway, as I said above, I primarily need the help getting the repos set up.

Best,

Dimitri


-----Original Message-----
From: Paul-Andre Panon [mailto:paul-andre.panon at avigilon.com] 
Sent: Tuesday, August 08, 2017 2:19 PM
To: Dimitri Yioulos <dyioulos at netatlantic.com>
Cc: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Help setting up Ubuntu channel(s)

It's not as bad as it sounds because a fair amount of support has been baked into later Spacewalk releases. Creating Debian/Ubuntu channels and repos and getting them updated through standard Spacewalk scheduled updates is now part of stock Spacewalk functionality. I followed an approach similar to the example CentOS or Redhat channels /repos: a parent channel for the main repo for each release (14.04 LTS, 16.04 LTS) , and then child channels for backports, and security-specific  or general updates for those releases. You can also add custom child channels if you build custom client updates that include the secure apt patches. However downloading and updating Ubuntu errata is still a "third-party" add-on. Since Tomas indicated that 2.7 should be out this month, I would say wait until it's out, and then use my April 12 post, https://www.redhat.com/archives/spacewalk-list/2017-April/msg00050.html, as a supplement to the devops page.

For the error mentioned by https://www.redhat.com/archives/spacewalk-list/2017-April/msg00085.html, Vyas had those errors because the files listed are for our internal PKI CA. Instead use whatever CA certs were used to sign your Spacewalk cert (or the Spacewalk cert itself if it's a self-signed cert). Since then I have also updated Phil's patches for Secure Apt (see the comments in Phil's blog for links to the Spacewalk Bugzilla issue with the SecureApt patches).

Cheers,

Paul-Andre Panon
Senior systems administrator
 
Office: 604.629.5182 ext 2341 Mobile: 604.679.1617


Message: 2
Date: Mon, 7 Aug 2017 18:16:27 +0000
From: Dimitri Yioulos <dyioulos at netatlantic.com>
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] Help setting up Ubuntu channel(s)
Message-ID:
	<8A297512A160E4449EE365BF0A57A872018218CF at SBS1.NetAtlantic.local>
Content-Type: text/plain; charset="us-ascii"

Thanks, Paul-Andre.  I suspected it wasn't easy.  I may well wait for SW version 2.7.