Re: [Spacewalk-list] Ubuntu 18.04 package management in Spacewalk 2.8

2018-12-11 Thread Paul-Andre Panon 
After clearing the unwanted entries in the rhnServerNeededCache table, I
verified that the incorrect packages had been cleared from the package
list for the servers. I then ran rhn_check on one of the clients that had
been cleared and after some delay (due to queuing a taskomatic task to
update the server's package list?) the incorrect packages came back.
Hopefully that can help someone else figure out the last few steps of
which task is incorrectly updating rhnServerNeededCache, why it's doing
it, and fix the bug.

-Original Message-
From: Paul-Andre Panon 
Sent: Monday, December 10, 2018 6:06 PM
To: 'spacewalk-list@redhat.com' ;
'spacewalk-list@redhat.com' 
Subject: RE: Ubuntu 18.04 package management in Spacewalk 2.8

It looks like there aren't too many things that insert into the
rhnServerNeededCache.
./java/code/src/com/redhat/rhn/manager/errata/cache/ErrataCacheManager.jav
a calls some queries directly to insert into the table, and the
update_needed_cache stored procedure could also be a cause.

I've cleared out the table rows for some server/package combos in our
environment that I know are invalid, and I'll see if the entries get
repopulated for those combos during the next sync or at other times. That
will hopefully help narrow down the possibilities. Most of those table
inserts appear to have to do with the errata cache management so maybe
there's something in there that was missed during the PR500 fixes.

-Original Message-
From: Paul-Andre Panon 
Sent: Monday, December 10, 2018 4:51 PM
To: 'spacewalk-list@redhat.com' ;
'spacewalk-list@redhat.com' 
Subject: RE: Ubuntu 18.04 package management in Spacewalk 2.8

Earlier today I wrote about the changes in PR500. That parsing actually
seems to be OK after all because the EVR entries in the database are OK.

That said, it looks like the spurious package entries are due to spurious
entries in the rhnServerNeededCache table. So the question is what is
populating the rhnServerNeededCache table incorrectly, and why?

___
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-11 Thread Graeme Fowler 
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 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  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]
metadata_expire = 86400
sslclientcert = /etc/pki/entitlement/3922910052842520258.pem
baseurl = 
https://cdn.redhat.com/content/dist/rhel/server/6/$releasever/$basearch/os
ui_repoid_vars = releasever basearch
sslverify = 1
name = Red Hat Enterprise Linux 6 Server (RPMs)
sslclientkey = /etc/pki/entitlement/3922910052842520258-key.pem
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
enabled = 1
sslcacert = /etc/rhsm/ca/redhat-uep.pem
gpgcheck = 1

Spacewalk pulling from mirror (above)
[rhel-6-server-rpms]
name = Red Hat Enterprise Linux 6 Server (RPMs)
baseurl = https://xxx.xxx.xxx.xxx/rhel-6-server-rpms/
enabled = 1
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release


RHEL 7

[rhel-7-server-rpms]
metadata_expire = 86400
sslclientcert = /etc/pki/entitlement/redhat.pem
baseurl = 
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os
ui_repoid_vars = releasever basearch
sslverify = 1
name = Red Hat Enterprise Linux 7 Server (RPMs)
sslclientkey = /etc/pki/entitlement/redhat-key.pem
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
enabled = 1
sslcacert = /etc/rhsm/ca/redhat-uep.pem
gpgcheck = 1



​





From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of p.cook...@bham.ac.uk 
mailto:p.cook...@bham.ac.uk>>
Sent: Tuesday, November 27, 2018 4:16 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Jeffrey

Thanks for your reply. It seems I would have been better off by starting with 
installing Spacewalk on a RHEL 7 server rather than an OL 7 server then? Can 
you just clarify/confirm what URL’s you’ve configured for the RHEL 6/7 
repositories please (obviously, for the RHEL 6 local, just take out any 
sensitive information)?

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of 
jeffrey.ir...@rivertechllc.com
Sent: 26 November 2018 19:58
To:

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

2018-12-11 Thread p.cook...@bham.ac.uk 
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  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]
metadata_expire = 86400
sslclientcert = /etc/pki/entitlement/3922910052842520258.pem
baseurl = 
https://cdn.redhat.com/content/dist/rhel/server/6/$releasever/$basearch/os
ui_repoid_vars = releasever basearch
sslverify = 1
name = Red Hat Enterprise Linux 6 Server (RPMs)
sslclientkey = /etc/pki/entitlement/3922910052842520258-key.pem
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
enabled = 1
sslcacert = /etc/rhsm/ca/redhat-uep.pem
gpgcheck = 1

Spacewalk pulling from mirror (above)
[rhel-6-server-rpms]
name = Red Hat Enterprise Linux 6 Server (RPMs)
baseurl = https://xxx.xxx.xxx.xxx/rhel-6-server-rpms/
enabled = 1
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release


RHEL 7

[rhel-7-server-rpms]
metadata_expire = 86400
sslclientcert = /etc/pki/entitlement/redhat.pem
baseurl = 
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os
ui_repoid_vars = releasever basearch
sslverify = 1
name = Red Hat Enterprise Linux 7 Server (RPMs)
sslclientkey = /etc/pki/entitlement/redhat-key.pem
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
enabled = 1
sslcacert = /etc/rhsm/ca/redhat-uep.pem
gpgcheck = 1



​





From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of p.cook...@bham.ac.uk 
mailto:p.cook...@bham.ac.uk>>
Sent: Tuesday, November 27, 2018 4:16 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Jeffrey

Thanks for your reply. It seems I would have been better off by starting with 
installing Spacewalk on a RHEL 7 server rather than an OL 7 server then? Can 
you just clarify/confirm what URL’s you’ve configured for the RHEL 6/7 
repositories please (obviously, for the RHEL 6 local, just take out any 
sensitive information)?

Regards
Phil

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


I have been able to do this by building a rhel 6 server and creating a local 
repo mirror.  I then created a rhel 7 and installed spacewalk.  That way i have 
the entitlements for rhel 6 and 7 covered.  From there, I set up the channels 
and pointed the rhel 7 to the redhat network, and the rhel 6 was pointed to my 
local repo server.  I can now get all the rhel 6 and 7 patches into spacewalk.


From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of

[Spacewalk-list] Internal Server Error - Snapshot Rollback

2018-12-11 Thread p.cook...@bham.ac.uk 
Hi all

I have Spacewalk 2.8 installed on an Oracle Linux 7.6 system using the integral 
PostgreSQL database.

Today I created a Snapshot Tag, prior to patching a small amount of packages, 
on an Oracle 6 system. When I tried to Rollback to this Snapshot Tag, from the 
Web UI, I received an "Internal Server Error" and no Rollback occurred. The 
Rollback worked fine, yesterday, when I patched just one of these packages 
though. Any ideas?

Regards

Philip Cookson
Linux Administrator (Contractor)
IT Services
ERI Building
Edgbaston
Birmingham
B15 2TT

Tel: 0121 414 4731
Email: p.cook...@bham.ac.uk

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list