Re: [Spacewalk-list] remove package in spacewalk repo

2018-12-13 Thread Dennis Pittman
To add to the last response you may have to remove the package if it's still 
listed in a softwarechannel

spacecmd package_detail libmspack-0.7 # list the details about the package
spacecmd package_remove libmspack-0.7  # remove the package.  This will work 
when the remove_orphan does not, If the package is not orphaned

Dennis J. Pittman
(e)  djpit...@outlook.com
(m)919-426-8907
(a) 310 Acorn Hollow Pl., Durham, NC 27703

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of William Hongach
Sent: Thursday, December 13, 2018 2:20 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] remove package in spacewalk repo

Hello,

To clarify, are you referring to packages that have been downloaded locally and 
pushed to Spacewalk?  If so, an unwanted package that is no longer part of a 
software channel can be listed and removed as follows:

spacecmd package_listorphans
spacecmd package_removeorphans

This will check for dependencies and remove it from both the Spacewalk database 
as well as the filesystem.  You can also check the filesystem against the 
database and vice versa as follows:

spacewalk-data-fsck -f
spacewalk-data-fsck -d

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Jérôme Meyer
Sent: Thursday, December 13, 2018 11:16 AM
To: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Subject: [Spacewalk-list] remove package in spacewalk repo

Hi,

It is possible to remove unwanted package in spacewalk repository?
In my dev-epel channel there's a package that is no longer available 
(libmspack-0.7).

Could I delete it? Can it result a dependency problem?...and how to do that?

Thank in advance
Regards,
J.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] remove package in spacewalk repo

2018-12-13 Thread William Hongach
Hello,

To clarify, are you referring to packages that have been downloaded locally and 
pushed to Spacewalk?  If so, an unwanted package that is no longer part of a 
software channel can be listed and removed as follows:

spacecmd package_listorphans
spacecmd package_removeorphans

This will check for dependencies and remove it from both the Spacewalk database 
as well as the filesystem.  You can also check the filesystem against the 
database and vice versa as follows:

spacewalk-data-fsck -f
spacewalk-data-fsck -d

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Jérôme Meyer
Sent: Thursday, December 13, 2018 11:16 AM
To: 'spacewalk-list@redhat.com' 
Subject: [Spacewalk-list] remove package in spacewalk repo

Hi,

It is possible to remove unwanted package in spacewalk repository?
In my dev-epel channel there's a package that is no longer available 
(libmspack-0.7).

Could I delete it? Can it result a dependency problem?...and how to do that?

Thank in advance
Regards,
J.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] remove package in spacewalk repo

2018-12-13 Thread Jérôme Meyer
Hi,

It is possible to remove unwanted package in spacewalk repository?
In my dev-epel channel there's a package that is no longer available 
(libmspack-0.7).

Could I delete it? Can it result a dependency problem?...and how to do that?

Thank in advance
Regards,
J.


smime.p7s
Description: S/MIME cryptographic signature
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 Servers

2018-12-13 Thread p.cook...@bham.ac.uk
Hi Ray

Yes, as I’ve said below, I’ve managed to directly sync both RHEL6 and RHEL7 
packages to our Spacewalk server now. After struggling for 2-3 weeks, off and 
on, I’ve learnt I sort of only needed 2 lots of information really (both from 
the lists).


1.  Add Red Hat Subscription Manager (RHSM) SSL Certificate to the trusted 
certificates database on the Spacewalk server.

# cp -p /etc/rhsm/ca/redhat-uep.pem /usr/share/pki/ca-trust-source/anchors/
# update-ca-trust


2.  Follow Robert's instructions, from list, here: 
https://www.redhat.com/archives/spacewalk-list/2016-January/msg00014.html

Note, I’ve installed Spacewalk 2.8 on a RHEL 7 server. Therefore, I sourced the 
/etc/yum.repos.d/redhat.repo info from that server. I’d also built a RHEL 6 
client test system, so I sourced the equivalent information from that system.

If you need any further help just let me know, though, as I know how 
frustrating this was to sort out! I’ve only patched a single RHEL 6/7 system, 
subsequently, but it’s looking encouraging.

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of raymond.setchfi...@gmail.com
Sent: 13 December 2018 11:43
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Phil

I would be very interested in knowing if you got this working, as this is 
something which I have been attempting to do.

I resolved this issue which you are experiencing by doing the following;

copy the redhat-uep.pem to your spacewalk server to the following location
#> /usr/share/pki/ca-trust-source/anchors/redhat-uep.pem
run
#> update-ca-trust

But from there I ran into authentication issues.

If you get further than I please let me know

Ray

On Thu, Dec 13, 2018 at 11:22 AM 
p.cook...@bham.ac.uk 
mailto:p.cook...@bham.ac.uk>> wrote:
Hi Graeme

Thanks for your response. I could see it was a certificate issue; just not so 
sure how to resolve it.

After installing Spacewalk 2.8 on a RHEL 7 server I encountered the following 3 
errors when trying to sync a RHEL 7 repository. I found all the resolutions in 
the lists so thought I’d group them together, here, for quick reference.

Subsequently, I’ve synced the RHEL 7 repository to the Spacewalk server and 
successfully patched a RHEL 7 client system from it too☺

1st SYNC ERROR - [Errno 14] curl#60 - "Peer's certificate issuer has been 
marked as not trusted by the user."
Resolution:
# cp -p /etc/rhsm/ca/redhat-uep.pem /usr/share/pki/ca-trust-source/anchors/
# update-ca-trust

2nd SYNC ERROR - [Errno 14] HTTPS Error 403 – Forbidden
Resolution:
Add Red Hat SSL Certificate details to relevant repository configuration page 
in Spacewalk Web UI.
See Robert's instructions, from list, here: 
https://www.redhat.com/archives/spacewalk-list/2016-January/msg00014.html

3rd SYNC ERROR - 
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os/repodata/repomd.xml:
 [Errno 14] HTTPS Error 404 - Not Found
Resolution:
Amend Repository URL
From 
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os
To   https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os

Note, if I’d followed Robert’s instructions, more diligently, I wouldn’t have 
seen this last error!

I’ve also used a similar configuration for RHEL 6, too, and directly synced a 
RHEL 6 repository then successfully patched a RHEL 6 client system from it.

Hope this is useful to others.

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Graeme Fowler
Sent: 11 December 2018 16:52
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Phil

The answer is staring you in the face in red: the RHEL repos use a certificate 
which your system doesn’t trust. You’ll need to fetch a copy of the cert and 
install it into your appropriate PKI tools on the Spacewalk server (part of the 
OS, not Spacewalk) to allow it to trust the certificate.

You’re very much not the only person to have raised this on this mailing list – 
a check of the archives might help you!

Graeme


From: 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of "p.cook...@bham.ac.uk" 
mailto:p.cook...@bham.ac.uk>>
Reply-To: "spacewalk-list@redhat.com" 
mailto:spacewalk-list@redhat.com>>
Date: Tuesday, 11 December 2018 at 16:39
To: "spacewalk-list@redhat.com" 
mailto:spacewalk-list@redhat.com>>
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Jeffrey

I haven’t had much success patching RHEL systems with my original proof of 
concept (PoC) environment that had Spacewalk 2.8 installed on an OEL 7 server.

I’ve therefore, created a 2nd PoC environment with 

Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 Servers

2018-12-13 Thread Raymond Setchfield
Hi Phil

I would be very interested in knowing if you got this working, as this is
something which I have been attempting to do.

I resolved this issue which you are experiencing by doing the following;

copy the redhat-uep.pem to your spacewalk server to the following location

#> /usr/share/pki/ca-trust-source/anchors/redhat-uep.pem

run

#> update-ca-trust


But from there I ran into authentication issues.


If you get further than I please let me know


Ray

On Thu, Dec 13, 2018 at 11:22 AM p.cook...@bham.ac.uk 
wrote:

> Hi Graeme
>
>
>
> Thanks for your response. I could see it was a certificate issue; just not
> so sure how to resolve it.
>
>
>
> After installing Spacewalk 2.8 on a RHEL 7 server I encountered the
> following 3 errors when trying to sync a RHEL 7 repository. I found all the
> resolutions in the lists so thought I’d group them together, here, for
> quick reference.
>
>
>
> Subsequently, I’ve synced the RHEL 7 repository to the Spacewalk server
> and successfully patched a RHEL 7 client system from it tooJ
>
>
>
> *1st SYNC ERROR* - [Errno 14] curl#60 - "Peer's certificate issuer has
> been marked as not trusted by the user."
>
> *Resolution*:
>
> # cp -p /etc/rhsm/ca/redhat-uep.pem /usr/share/pki/ca-trust-source/anchors/
>
> # update-ca-trust
>
>
>
> *2nd SYNC ERROR* - [Errno 14] HTTPS Error 403 – Forbidden
>
> *Resolution*:
>
> Add Red Hat SSL Certificate details to relevant repository configuration
> page in Spacewalk Web UI.
>
> See Robert's instructions, from list, here:
> https://www.redhat.com/archives/spacewalk-list/2016-January/msg00014.html
>
>
>
> *3rd SYNC ERROR* -
> https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os/repodata/repomd.xml:
> [Errno 14] HTTPS Error 404 - Not Found
>
> *Resolution*:
>
> Amend Repository URL
>
> From
> https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os
>
> To   https://cdn.redhat.com/content/dist/rhel/server/7/7*S*
> erver/x86_64/os
> 
>
>
>
> Note, if I’d followed Robert’s instructions, more diligently, I wouldn’t
> have seen this last error!
>
>
>
> I’ve also used a similar configuration for RHEL 6, too, and directly
> synced a RHEL 6 repository then successfully patched a RHEL 6 client system
> from it.
>
>
>
> Hope this is useful to others.
>
>
>
> Regards
>
> Phil
>
>
>
> *From:* spacewalk-list-boun...@redhat.com <
> spacewalk-list-boun...@redhat.com> *On Behalf Of *Graeme Fowler
> *Sent:* 11 December 2018 16:52
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL
> 6/7 Servers
>
>
>
> Hi Phil
>
>
>
> The answer is staring you in the face in red: the RHEL repos use a
> certificate which your system doesn’t trust. You’ll need to fetch a copy of
> the cert and install it into your appropriate PKI tools on the Spacewalk
> server (part of the OS, not Spacewalk) to allow it to trust the certificate.
>
>
>
> You’re very much not the only person to have raised this on this mailing
> list – a check of the archives might help you!
>
>
>
> Graeme
>
>
>
>
>
> *From: * on behalf of "
> p.cook...@bham.ac.uk" 
> *Reply-To: *"spacewalk-list@redhat.com" 
> *Date: *Tuesday, 11 December 2018 at 16:39
> *To: *"spacewalk-list@redhat.com" 
> *Subject: *Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL
> 6/7 Servers
>
>
>
> Hi Jeffrey
>
>
>
> I haven’t had much success patching RHEL systems with my original proof of
> concept (PoC) environment that had Spacewalk 2.8 installed on an *OEL* 7
> server.
>
>
>
> I’ve therefore, created a 2nd PoC environment with Spacewalk 2.8
> installed on a *RHEL* 7 server, as you’ve described. I’ve left the RHEL 7
> server repo (rhel-7-server-rpms) with its default configuration, as you
> have below, but when I try and sync I see the following error:
>
>
>
> [root@ yum.repos.d]# *cat
> /var/log/rhn/reposync/rhel7_x86_64.log*
>
> 2018/12/11 15:50:42 +01:00 Command: ['/usr/bin/spacewalk-repo-sync',
> '--channel', 'rhel7_x86_64', '--type', 'yum']
>
> 2018/12/11 15:50:42 +01:00 Sync of channel started.
>
> 2018/12/11 15:50:42 +01:00
>
> 2018/12/11 15:50:42 +01:00   Processing repository with URL:
> https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os
>
> 2018/12/11 15:50:43 +01:00 ERROR: failure: repodata/repomd.xml from
> rhel7_x86_64: [Errno 256] No more mirrors to try.
>
>
> https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os/repodata/repomd.xml:
> [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not
> trusted by the user."
>
> 2018/12/11 15:50:43 +01:00 ERROR: failure: repodata/repomd.xml from
> rhel7_x86_64: [Errno 256] No more mirrors to try.
>
>
> https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os/repodata/repomd.xml:
> [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not
> trusted by the user."
>
> 2018/12/11 15:50:43 +01:00 Sync of 

Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 Servers

2018-12-13 Thread p.cook...@bham.ac.uk
Hi Graeme

Thanks for your response. I could see it was a certificate issue; just not so 
sure how to resolve it.

After installing Spacewalk 2.8 on a RHEL 7 server I encountered the following 3 
errors when trying to sync a RHEL 7 repository. I found all the resolutions in 
the lists so thought I’d group them together, here, for quick reference.

Subsequently, I’ve synced the RHEL 7 repository to the Spacewalk server and 
successfully patched a RHEL 7 client system from it too☺

1st SYNC ERROR - [Errno 14] curl#60 - "Peer's certificate issuer has been 
marked as not trusted by the user."
Resolution:
# cp -p /etc/rhsm/ca/redhat-uep.pem /usr/share/pki/ca-trust-source/anchors/
# update-ca-trust

2nd SYNC ERROR - [Errno 14] HTTPS Error 403 – Forbidden
Resolution:
Add Red Hat SSL Certificate details to relevant repository configuration page 
in Spacewalk Web UI.
See Robert's instructions, from list, here: 
https://www.redhat.com/archives/spacewalk-list/2016-January/msg00014.html

3rd SYNC ERROR - 
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os/repodata/repomd.xml:
 [Errno 14] HTTPS Error 404 - Not Found
Resolution:
Amend Repository URL
From 
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os
To   https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os

Note, if I’d followed Robert’s instructions, more diligently, I wouldn’t have 
seen this last error!

I’ve also used a similar configuration for RHEL 6, too, and directly synced a 
RHEL 6 repository then successfully patched a RHEL 6 client system from it.

Hope this is useful to others.

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Graeme Fowler
Sent: 11 December 2018 16:52
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Phil

The answer is staring you in the face in red: the RHEL repos use a certificate 
which your system doesn’t trust. You’ll need to fetch a copy of the cert and 
install it into your appropriate PKI tools on the Spacewalk server (part of the 
OS, not Spacewalk) to allow it to trust the certificate.

You’re very much not the only person to have raised this on this mailing list – 
a check of the archives might help you!

Graeme


From: 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of "p.cook...@bham.ac.uk" 
mailto:p.cook...@bham.ac.uk>>
Reply-To: "spacewalk-list@redhat.com" 
mailto:spacewalk-list@redhat.com>>
Date: Tuesday, 11 December 2018 at 16:39
To: "spacewalk-list@redhat.com" 
mailto:spacewalk-list@redhat.com>>
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Jeffrey

I haven’t had much success patching RHEL systems with my original proof of 
concept (PoC) environment that had Spacewalk 2.8 installed on an OEL 7 server.

I’ve therefore, created a 2nd PoC environment with Spacewalk 2.8 installed on a 
RHEL 7 server, as you’ve described. I’ve left the RHEL 7 server repo 
(rhel-7-server-rpms) with its default configuration, as you have below, but 
when I try and sync I see the following error:

[root@ yum.repos.d]# cat /var/log/rhn/reposync/rhel7_x86_64.log
2018/12/11 15:50:42 +01:00 Command: ['/usr/bin/spacewalk-repo-sync', 
'--channel', 'rhel7_x86_64', '--type', 'yum']
2018/12/11 15:50:42 +01:00 Sync of channel started.
2018/12/11 15:50:42 +01:00
2018/12/11 15:50:42 +01:00   Processing repository with URL: 
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os
2018/12/11 15:50:43 +01:00 ERROR: failure: repodata/repomd.xml from 
rhel7_x86_64: [Errno 256] No more mirrors to try.
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os/repodata/repomd.xml:
 [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not trusted 
by the user."
2018/12/11 15:50:43 +01:00 ERROR: failure: repodata/repomd.xml from 
rhel7_x86_64: [Errno 256] No more mirrors to try.
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os/repodata/repomd.xml:
 [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not trusted 
by the user."
2018/12/11 15:50:43 +01:00 Sync of channel completed in 0:00:00.
[root@yum.repos.d]#

Did you perform some additional configuration perhaps/any ideas? Might be 
useful if you could forward a screen dump of your channel/repo setup screen for 
RHEL 7, from the Web UI, too?

Regards
Phil



From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of 
jeffrey.ir...@rivertechllc.com
Sent: 27 November 2018 14:21
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers


RHEL 6 (my mirror repo) pulling from RH


[rhel-6-server-rpms]