Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

[p.cook...@bham.ac.uk]

Hi Jérôme

Thanks for your feedback. I've read that "spacewalk-clone-by-date" gives some 
unexpected results, really doesn't sound very reliable or therefore, of much 
interest to me!

I've started some testing of "spacewalk-manage-channel-lifecycle" and, 
initially, that seems to be giving more consistent results. As the name 
suggests, maybe it's more likely to manage a dev/test/prod lifecycle/workflow 
better? It seems to just capture the state of the source channel as opposed to 
copying every package, from the related repo, in to new repo's each time. This 
makes me think that you'd have to ensure the source repo's were retained while 
dev/test/prod clones were still referencing it but far less disk space is 
required. I'm waiting to see what happens when the source is re-synced and more 
packages are added to it, as I wouldn't want the clone repo's to get any 
updated packages as well!

Regards
Phil


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of jerome.me...@lcsystems.ch
Sent: 16 January 2019 12:13
To: 'spacewalk-list@redhat.com' 
Subject: Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi Phil,

I'm using the spacewalk-clone-by-date command and there's my point of view and 
experience.
I've created three channels: dev,test and prod with spacewalk-clone-by-date. 
Each month in a specific date I resync these three channels with the same 
commands. In this process errata will be synchronized with their dependencies.
All was perfect until I notice that not all packages will be added. By example 
new package version but not an errata will not be updated. At the end, the 
channels hasn't the same packages number has it's parents.
I'll perhaps make some test with other commands but if you do any more tests on 
your side, I'll be interested in your results.
Unfortunately I didn't any more informations on web regarding this problematic.

Regards,
Jérôme

From: 
spacewalk-list-boun...@redhat.com<mailto: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: Dienstag, 15. Januar 2019 14:01
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi all

I've recently built a SW 2.8 environment, added Channels/Repositories for 
RHEL/Oracle Linux 6/7 and successfully patched relevant client systems. I now 
want to know how people are managing their patching workflow - at this point in 
time I just want to ensure the same group of patches are applied to Dev, Test 
and Production after sufficient testing has been performed. If I never re-sync 
these repositories obviously they'll remain static and could be used for the 
whole workflow. However, other service areas may want their environments 
patched at different times with additional patches. I guess I could just create 
similar Channels/Repositories, at a later time, but that would be time 
consuming and need more disk space. I've seen references to cloning using 
WebUI, spacecmd -- softwarechannel_clone, spacewalk-clone-by-date or 
spacewalk-manage-channel-lifecycle and can research these further but just 
wondering what people have found to be the easiest and most reliable solution 
really?

Regards
Phil

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

Re: [Spacewalk-list] Spacewalk - Patching Log Files

[p.cook...@bham.ac.uk]

Thanks for your feedback Matt, that’s helpful.

Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mattma...@gmail.com
Sent: 11 January 2019 21:18
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk - Patching Log Files

Logging on the client isn't enabled by default, but I believe you can get that 
information by enabling it in the /etc/sysconfig/rhn/up2date config file.

writeChangesToLog[comment]=Log to /var/log/up2date which packages has been 
added and removed
writeChangesToLog=1

Otherwise you can query the API to get all the events for a particular system.

On Wed, Jan 9, 2019 at 5:24 AM 
p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> 
mailto:p.cook...@bham.ac.uk>> wrote:
Good morning all

I’ve found that /var/log/yum.log, on client systems, isn’t updated when 
patching RHEL 6/7 systems from a Spacewalk server (v2.8). I know details of 
patching activities can be found in the Schedule > Completed Actions or yum 
history, after the event, but is there any log on client or server that can be 
monitored from the command line actually during patching? It’s just to monitor 
the patching activity, really, rather than a need to trace a problem or 
similar. If not, I presume that’s because the details you see in Schedule > 
Actions are actually being directly written to the embedded PostgreSQL database?

Regards

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

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

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

[Spacewalk-list] Managing Channels/Repositories - Patching Workflow

[p.cook...@bham.ac.uk]

Hi all

I've recently built a SW 2.8 environment, added Channels/Repositories for 
RHEL/Oracle Linux 6/7 and successfully patched relevant client systems. I now 
want to know how people are managing their patching workflow - at this point in 
time I just want to ensure the same group of patches are applied to Dev, Test 
and Production after sufficient testing has been performed. If I never re-sync 
these repositories obviously they'll remain static and could be used for the 
whole workflow. However, other service areas may want their environments 
patched at different times with additional patches. I guess I could just create 
similar Channels/Repositories, at a later time, but that would be time 
consuming and need more disk space. I've seen references to cloning using 
WebUI, spacecmd -- softwarechannel_clone, spacewalk-clone-by-date or 
spacewalk-manage-channel-lifecycle and can research these further but just 
wondering what people have found to be the easiest and most reliable solution 
really?

Regards
Phil

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

[Spacewalk-list] Spacewalk Provisioning

[p.cook...@bham.ac.uk]

Hi all

I've recently built a SW 2.8 environment on a RHEL 7 server, added 
Channels/Repositories for RHEL/Oracle Linux 6/7 and successfully patched 
relevant client systems. I now want to look at provisioning RHEL/Oracle Linux 
6/7
systems - I won't be using a DHCP server. Can anyone supply simple instructions 
for doing this as I can't seem to get a proper angle on it? I was envisaging 
using the newly created repositories created for patching but when I look in 
Systems > Kickstart > Create Kickstart Profile I see this:

Base Channel: No Kickstartable Channels found.
Kickstartable Tree: No trees were found for the selected channel

I learnt that this was because I need to "enable" the repositories to be 
kickstartable by re-syncing with relevant option but this give message 
"Kickstartable tree not detected (no valid treeinfo file)" for bot Red Hat and 
Oracle Linux channels (see below). Do I need to sync from different base 
channels perhaps?

[root@ ~]# spacewalk-repo-sync -c rhel7_x86_64 --sync-kickstart
12:23:10 ==
12:23:10 | Channel: rhel7_x86_64
12:23:10 ==
12:23:10 Sync of channel started.
12:23:10
12:23:10   Processing repository with URL: 
https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os
Repository group_spacewalkproject-java-packages is listed more than once in the 
configuration
12:23:13
12:23:13   Importing comps file 
fef86aafcac04474fa71d40322b4b81bab738f67-comps.xml.
12:23:22 Packages in repo: 23382
12:24:06 No new packages to sync.
12:24:07
12:24:07   Errata in repo: 3449.
12:24:07 No new errata to sync.
12:24:07
12:24:07   Importing kickstarts.
12:24:10 Kickstartable tree not detected (no valid treeinfo file)
12:24:10 Sync of channel completed in 0:01:00.
12:24:10 Total time: 0:01:00
[root@ ~]#

[root@ ~]# spacewalk-repo-sync -c ol7_x86_64 --sync-kickstart
12:56:10 ==
12:56:10 | Channel: ol7_x86_64
12:56:10 ==
12:56:10 Sync of channel started.
12:56:11
12:56:11   Processing repository with URL: 
http://public-yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/
Repository group_spacewalkproject-java-packages is listed more than once in the 
configuration
12:56:12
12:56:12   Importing comps file comps.xml.
12:56:18 Packages in repo: 11799
12:56:36 No new packages to sync.
12:56:36
12:56:36   Errata in repo: 1360.
12:56:37 No new errata to sync.
12:56:37
12:56:37   Importing kickstarts.
12:56:39 Kickstartable tree not detected (no valid treeinfo file)
12:56:40 Sync of channel completed in 0:00:28.
12:56:40 Total time: 0:00:28
[root@ ~]#

Regards
Phil

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

Re: [Spacewalk-list] issue with new channel

[p.cook...@bham.ac.uk]

Hi Yang

After creating several cloned repo’s I started to see 
“java.lang.OutOfMemoryError: Java heap space” messages in 
“/var/log/rhn/rhn_taskomatic_daemon.log” In addition, the generation of repo 
metadata, for some of the larger repo’s, wasn’t completing. There are lots of 
hits about this both in the lists and from Google! After increasing max memory 
for Java, from 512Mb to 4096Mb, I don’t seem to be having any more problems 
though☺ See this link for further background info:


https://docs.oracle.com/cd/E92593_01/E90695/html/swk24-issues-memory.html

Regards
Phil
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Yang Li
Sent: 16 January 2019 20:52
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] issue with new channel

I have new channel setup in our spacewalk server. the repo sync looks fine. on 
client side, it yum repolist looks fine, but when I do yum update, it will 
break out with following error:

# yum update  --nogpgcheck
Loaded plugins: rhnplugin
This system is receiving updates from RHN Classic or Red Hat Satellite.


One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
yum --disablerepo= ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable 
or
subscription-manager repos --disable=

 5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=.skip_if_unavailable=true

failed to retrieve repodata/repomd.xml from ius_rhel7_x86_64
error was [Errno 14] HTTPS Error 404 - Not Found

this is what I see in repo sync log:

# cat ius_rhel7_x86_64.log
2019/01/11 10:45:00 -04:00 Command: ['/usr/bin/spacewalk-repo-sync', 
'--channel', 'ius_rhel7_x86_64', '--type', 'yum']
2019/01/11 10:45:00 -04:00 Sync of channel started.
2019/01/11 10:45:00 -04:00 Repo URL: 
http://archive.linux.duke.edu/ius/stable/Redhat/7/x86_64/
2019/01/11 10:45:01 -04:00 Packages in repo:   737
2019/01/11 10:45:02 -04:00 Packages already synced:  0
2019/01/11 10:45:02 -04:00 Packages to sync:   737
2019/01/11 10:45:02 -04:00 1/737 : apcu-panel56u-4.0.11-2.ius.el7-0.noarch
2019/01/11 10:45:03 -04:00 2/737 : apr15u-1.5.2-2.ius.el7-0.x86_64
2019/01/11 10:45:05 -04:00 3/737 : apr15u-debuginfo-1.5.2-2.ius.el7-0.x86_64
...

2019/01/11 10:58:30 -04:00 731/737 : 
uwsgi-plugin-python35u-debuginfo-2.0.16-1.ius.el7-0.x86_64
2019/01/11 10:58:31 -04:00 732/737 : 
uwsgi-plugin-python35u-debuginfo-2.0.17.1-1.ius.el7-0.x86_64
2019/01/11 10:58:32 -04:00 733/737 : 
uwsgi-plugin-python36u-2.0.16-1.ius.el7-0.x86_64
2019/01/11 10:58:32 -04:00 734/737 : 
uwsgi-plugin-python36u-2.0.17.1-1.ius.el7-0.x86_64
2019/01/11 10:58:33 -04:00 735/737 : 
uwsgi-plugin-python36u-debuginfo-2.0.17.1-1.ius.el7-0.x86_64
2019/01/11 10:58:33 -04:00 736/737 : 
uwsgi-plugin-python36u-debuginfo-2.0.16-1.ius.el7-0.x86_64
2019/01/11 10:58:34 -04:00 737/737 : yum-plugin-replace-0.2.7-1.ius.el7-0.noarch
2019/01/11 10:58:35 -04:00 Linking packages to channel.
2019/01/11 10:58:42 -04:00 Repo 
http://archive.linux.duke.edu/ius/stable/Redhat/7/x86_64/ has 0 errata.
2019/01/11 10:58:42 -04:00 Sync of channel completed in 0:13:41.

What could be the issue?

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

Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

[p.cook...@bham.ac.uk]

Hi Jérôme

Bit of an update.

Firstly, you have to install the "spacewalk-utils" package to get the 
"spacewalk-manage-channel-lifecycle" utility. This is sourced from the 
"spacewalk" repository. Once this is done, you don't seem to get a "man" page 
but the following command provides help and clearly states at least all the 
basic things you need to know:

# spacewalk-manage-channel-lifecycle -h

Initially, it really does seem to accommodate cloning Dev, Test and Prod repo's 
really well, although further testing is required.

Note: After using the utility to create several cloned repo's I started to see 
"java.lang.OutOfMemoryError: Java heap space" messages in 
"/var/log/rhn/rhn_taskomatic_daemon.log" In addition, the generation of repo 
metadata, for some of the larger repo's, wasn't completing. There are lots of 
hits about this both in the lists and from Google! After increasing max memory 
for Java, from 512Mb to 4096Mb, I don't seem to be having any more problems 
though:) See this link for further background info:


https://docs.oracle.com/cd/E92593_01/E90695/html/swk24-issues-memory.html

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of jerome.me...@lcsystems.ch
Sent: 17 January 2019 13:50
To: 'spacewalk-list@redhat.com' 
Subject: Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi Phil,

Thank you for sharing your information about your test...
"Spacewalk-manage-channel-lifecycle" sounds very interesting. I'll also do some 
tests and give you feedback.
I'm very interested in the results of the re-sync because that is actually the 
most important thing.

Best regards,
Jérôme



From: 
spacewalk-list-boun...@redhat.com<mailto: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: Mittwoch, 16. Januar 2019 14:38
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi Jérôme

Thanks for your feedback. I've read that "spacewalk-clone-by-date" gives some 
unexpected results, really doesn't sound very reliable or therefore, of much 
interest to me!

I've started some testing of "spacewalk-manage-channel-lifecycle" and, 
initially, that seems to be giving more consistent results. As the name 
suggests, maybe it's more likely to manage a dev/test/prod lifecycle/workflow 
better? It seems to just capture the state of the source channel as opposed to 
copying every package, from the related repo, in to new repo's each time. This 
makes me think that you'd have to ensure the source repo's were retained while 
dev/test/prod clones were still referencing it but far less disk space is 
required. I'm waiting to see what happens when the source is re-synced and more 
packages are added to it, as I wouldn't want the clone repo's to get any 
updated packages as well!

Regards
Phil


From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of jerome.me...@lcsystems.ch<mailto:jerome.me...@lcsystems.ch>
Sent: 16 January 2019 12:13
To: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Subject: Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi Phil,

I'm using the spacewalk-clone-by-date command and there's my point of view and 
experience.
I've created three channels: dev,test and prod with spacewalk-clone-by-date. 
Each month in a specific date I resync these three channels with the same 
commands. In this process errata will be synchronized with their dependencies.
All was perfect until I notice that not all packages will be added. By example 
new package version but not an errata will not be updated. At the end, the 
channels hasn't the same packages number has it's parents.
I'll perhaps make some test with other commands but if you do any more tests on 
your side, I'll be interested in your results.
Unfortunately I didn't any more informations on web regarding this problematic.

Regards,
Jérôme

From: 
spacewalk-list-boun...@redhat.com<mailto: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: Dienstag, 15. Januar 2019 14:01
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi all

I've recently built a SW 2.8 environment, added Channels/Repositories for 
RHEL/Oracle Linux 6/7 and successfully patched relevant client systems. I now 
want to know how people are managing their patching workflow - at this point in 
time I just want to ensure the same group of patches are applied to Dev, Test

Re: [Spacewalk-list] package install fail

[p.cook...@bham.ac.uk]

Hi

Personally, I’ve only been using Spacewalk for patching, rather than 
provisioning, although that is my next objective. However, it would seem it 
can’t find the package and therefore, you’re not pointing to the right area or 
there’s sort of configuration issue. May be the following link will help or you 
could search for similar?

https://unix.stackexchange.com/questions/284251/centos-kickstart-packages

Good luck
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of rui.a.z...@nokia-sbell.com
Sent: 16 January 2019 02:40
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] FW: package install fail



From: Zhou, Rui A. (NSB - CN/Shanghai)
Sent: 2019年1月16日 10:28
To: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Cc: Zhu, Ting (NSB - CN/Shanghai) 
mailto:ting@nokia-sbell.com>>
Subject: package install fail

Hi: dears
   I had install the spacewalk2.8,  it all works fine, client can register to 
server and spacewalk can send cmd etc…
But when I use the spacewalk to install os, it always appears the following 
tips, of course the five packages wrote in the KS.
I understand it will find the configured tree path(/var/ftp/pub/CentOS7) to 
install needed packages, but it not work.
So I try to config cobbler repo(rndmirrors), It doesn't seem to work either.  
It's been bothering me for a long time.
Am I missing any configuration? Hope to be helped! Thank you!


[root@splunk-server repo_mirror]# ls -la /var/www/cobbler/repo_mirror/rndmirrors
total 368
drwxr-xr-x  4 root   root   54 Jan 15 23:35 .
drwxr-xr-x  3 apache apache 24 Jan 15 19:12 ..
-rw-r--r--  1 root   root   373476 Jan 15 23:35 comps.xml
drwxr-xr-x  2 root   root   29 Jan 15 19:12 .origin
drwxr-xr-x 33 root   root  285 Jan 15 23:35 Packages


[cid:image001.png@01D4AD76.B0D82B10]
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] FW: Managing Channels/Repositories - Patching Workflow

[p.cook...@bham.ac.uk]

Forgot to add.

The source repo has been updated, with additional packages, but the cloned 
repo's have remained static, as you might expect:)

Regards
Phil

From: Philip Cookson (IT Services)
Sent: 17 January 2019 15:24
To: 'spacewalk-list@redhat.com' 
Subject: RE: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi Jérôme

Bit of an update.

Firstly, you have to install the "spacewalk-utils" package to get the 
"spacewalk-manage-channel-lifecycle" utility. This is sourced from the 
"spacewalk" repository. Once this is done, you don't seem to get a "man" page 
but the following command provides help and clearly states at least all the 
basic things you need to know:

# spacewalk-manage-channel-lifecycle -h

Initially, it really does seem to accommodate cloning Dev, Test and Prod repo's 
really well, although further testing is required.

Note: After using the utility to create several cloned repo's I started to see 
"java.lang.OutOfMemoryError: Java heap space" messages in 
"/var/log/rhn/rhn_taskomatic_daemon.log" In addition, the generation of repo 
metadata, for some of the larger repo's, wasn't completing. There are lots of 
hits about this both in the lists and from Google! After increasing max memory 
for Java, from 512Mb to 4096Mb, I don't seem to be having any more problems 
though:) See this link for further background info:


https://docs.oracle.com/cd/E92593_01/E90695/html/swk24-issues-memory.html

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of jerome.me...@lcsystems.ch<mailto:jerome.me...@lcsystems.ch>
Sent: 17 January 2019 13:50
To: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Subject: Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi Phil,

Thank you for sharing your information about your test...
"Spacewalk-manage-channel-lifecycle" sounds very interesting. I'll also do some 
tests and give you feedback.
I'm very interested in the results of the re-sync because that is actually the 
most important thing.

Best regards,
Jérôme



From: 
spacewalk-list-boun...@redhat.com<mailto: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: Mittwoch, 16. Januar 2019 14:38
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi Jérôme

Thanks for your feedback. I've read that "spacewalk-clone-by-date" gives some 
unexpected results, really doesn't sound very reliable or therefore, of much 
interest to me!

I've started some testing of "spacewalk-manage-channel-lifecycle" and, 
initially, that seems to be giving more consistent results. As the name 
suggests, maybe it's more likely to manage a dev/test/prod lifecycle/workflow 
better? It seems to just capture the state of the source channel as opposed to 
copying every package, from the related repo, in to new repo's each time. This 
makes me think that you'd have to ensure the source repo's were retained while 
dev/test/prod clones were still referencing it but far less disk space is 
required. I'm waiting to see what happens when the source is re-synced and more 
packages are added to it, as I wouldn't want the clone repo's to get any 
updated packages as well!

Regards
Phil


From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of jerome.me...@lcsystems.ch<mailto:jerome.me...@lcsystems.ch>
Sent: 16 January 2019 12:13
To: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Subject: Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi Phil,

I'm using the spacewalk-clone-by-date command and there's my point of view and 
experience.
I've created three channels: dev,test and prod with spacewalk-clone-by-date. 
Each month in a specific date I resync these three channels with the same 
commands. In this process errata will be synchronized with their dependencies.
All was perfect until I notice that not all packages will be added. By example 
new package version but not an errata will not be updated. At the end, the 
channels hasn't the same packages number has it's parents.
I'll perhaps make some test with other commands but if you do any more tests on 
your side, I'll be interested in your results.
Unfortunately I didn't any more informations on web regarding this problematic.

Regards,
Jérôme

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of 
p.cook...@bham.ac.uk<mailto:p.cook...@bham.

Re: [Spacewalk-list] Repo question...

[p.cook...@bham.ac.uk]

Initially, browse here:

http://mirror.centos.org/centos/6/

You can then drill down to every repo you may need. You'll probably want at 
least os (base) and updates:

http://mirror.centos.org/centos/6/os/x86_64/
http://mirror.centos.org/centos/6/updates/x86_64/
http://mirror.centos.org/centos/6/extras/x86_64/

Once all the repo's have been synced up to date you should get everything you 
need.

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of dyiou...@netatlantic.com
Sent: 17 January 2019 22:17
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Repo question...

Also, when was the last time you sync'd your CentOS 6 repo?  Run 
"spacewalk-repo-sync --channel  --type yum"?

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Dimitri Yioulos
Sent: Thursday, January 17, 2019 5:13 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Repo question...

6 should work.  I believe that by using 6, instead of e.g. 6.10, when the 
distro is upgraded (e.g. 6.9 -> 6.10), you pick up the upgrade.  My Spacewalk 
repo for CentOS 6 is http://mirror.centos.org/centos/6/updates/x86_64/.

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Dave Thoms
Sent: Thursday, January 17, 2019 5:06 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Repo question...


I did check /etc/yum.repos.d and did a "dry run" of yum on the machine.  There 
are more updates using a local yum update from the command line than from 
Spacewalk.  The one that caught my eye, and concern, was a new kernel.



So.  Do I use the specific version directory when setting up the Spacewalk repo 
(6.10) or do I use 6.





Thanks,

Dave T.


From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Dimitri Yioulos 
mailto:dyiou...@netatlantic.com>>
Sent: Thursday, January 17, 2019 2:48:14 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Repo question...

[ALERT]


Might you have packages installed from repos which are not accounted for in 
Spacewalk?  You might want to look in /etc/yum.repos.d, as well as to run yum 
update on one of your machines (without actually installing the updates), and 
check those against what Spacewalk would update.



Dimitri



From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Dave Thoms
Sent: Thursday, January 17, 2019 4:41 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Repo question...



I am using Spacewalk 2.8 on CentOS 7.  I still have lingering CentOS 6 
(technically 6.10) machines that need updates. I noticed that the amount of 
update that updates available for my 6.10 machines under a local yum update are 
different that what Spacewalk offers.  So I did some digging via browser in 
http://mirror.chpc.utah.edu/pub/centos (a physically near mirror) and found 
very specific directories like 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 
6.9, and 6.10.  I current have the repo for my CentOS 6 machines set to use "6" 
in Spacewalk, but my CentOS machines are really "6.10".  What directory should 
I be using?  I thought "6" covered all the 6's.  But, maybe not.





Why is it so hard to find this info online?





Thanks in advance,

Dave T.

The information in this e-mail (including attachments, if any) is considered 
confidential and is intended only for the recipient(s) listed above. Any 
review, use, disclosure, distribution or copying of this e-mail is prohibited 
except by or on behalf of the intended recipient. If you have received this 
email in error, please notify me immediately by reply e-mail, delete this 
e-mail, and do not disclose its contents to anyone. Any opinions expressed in 
this e-mail are those of the individual and not necessarily the TruHearing 
group. Thank you.

[External Email] This email originated outside TruHearing. Please exercise 
caution with links and attachments. For assistance, please contact HelpDesk
--IT Ops Team

The information in this e-mail (including attachments, if any) is considered 
confidential and is intended only for the recipient(s) listed above. Any 
review, use, disclosure, distribution or copying of this e-mail is prohibited 
except by or on behalf of the intended recipient. If you have received this 
email in error, please notify me immediately by reply e-mail, delete this 
e-mail, and do not disclose its contents to anyone. Any opinions expressed in 
this e-mail are those of the individual and not necessarily the TruHearing 
group. Thank you.
___

Re: [Spacewalk-list] Any chance to get "Schedule"-Jobs running on SW-Server?

[p.cook...@bham.ac.uk]

Hi Matthias

I’m not entirely sure what you’re asking but you can schedule scripts from the 
Spacewalk Web UI in the following way:

Systems > Click on system name > Remote Command - Add script details then click 
on Schedule

Click on Schedule top menu item to see progress of Action

Note, by default, the rhnsd daemon on a client system connects to the Spacewalk 
server every 4 hours (see /etc/sysconfig/rhn/rhnsd) and performs any updates or 
actions that you have scheduled. However, if you install the Open Source 
Architecture Daemon (OSAD), on the client system, updates and actions should be 
picked up almost immediately from the Spacewalk server.

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mgru...@metzler.com
Sent: 23 January 2019 09:56
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Any chance to get "Schedule"-Jobs running on 
SW-Server?

Hi!

Is there any chance to Schedule-Jobs via "system_runscript" working on a 
SpaceWalk-Server like it works on any Client?
I know taskomatic is the "scheduler" within SpaceWalk, but that is not 
configurable.

At the moment I use at to schedule dynamic processes, but thats a bit "tricky"

Perhaps someone has a better solution, and not using something like obsidian or 
Automic?

cheers
Matthias


METZLER
Informationstechnologie

Matthias Gruber
IT-Infrastruktur & -Betrieb

B. Metzler seel. Sohn & Co.
Kommanditgesellschaft auf Aktien
Untermainanlage 1
60329 Frankfurt am Main
Telefon (0 69) 21 04 - 43 30
Telefax (0 69) 21 04 - 40 40
mgru...@metzler.com
www.metzler.com


Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich von 
Metzler, Emmerich Müller, Gerhard Wiesheu
Vorsitzender des Aufsichtsrats: Dr. Christoph Schücking
Sitz der Gesellschaft: Frankfurt am Main, Handelsregister-Nr. HRB 27 515

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfänger 
sein, so bitten wir Sie höflich, dies unverzüglich dem Absender mitzuteilen und 
die Nachricht zu löschen. Es ist unzulässig, die Nachricht unbefugt 
weiterzuleiten oder zu kopieren. Da wir nicht die Echtheit oder Vollständigkeit 
der in dieser Nachricht enthaltenen Informationen garantieren oder zusichern 
können, sind die vorstehenden Ausführungen rechtlich nicht bindend. Eine 
Haftung hierfür wird ausgeschlossen.
This message is confidential. If you are not the intended recipient, we kindly 
ask you to inform the sender and delete the information. Any unauthorised 
dissemination or copying hereof is prohibited. As we cannot guarantee or assure 
the genuineness or completeness of the information contained in this message, 
the statements set forth above are not legally binding. Accordingly we cannot 
accept any liability for their contents.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] FW: Spacewalk Provisioning

[p.cook...@bham.ac.uk]

I know it hasn't been too long, but does anyone have any information for me 
please, as I really do want to get started with provisioning?

Many thanks
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of p.cook...@bham.ac.uk
Sent: 22 January 2019 13:30
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk Provisioning

Hi all

I've recently built a SW 2.8 environment on a RHEL 7 server, added 
Channels/Repositories for RHEL/Oracle Linux 6/7 and successfully patched 
relevant client systems. I now want to look at provisioning RHEL/Oracle Linux 
6/7
systems - I won't be using a DHCP server. Can anyone supply simple instructions 
for doing this as I can't seem to get a proper angle on it? I was envisaging 
using the newly created repositories created for patching but when I look in 
Systems > Kickstart > Create Kickstart Profile I see this:

Base Channel: No Kickstartable Channels found.
Kickstartable Tree: No trees were found for the selected channel

I learnt that this was because I need to "enable" the repositories to be 
kickstartable by re-syncing with relevant option but this give message 
"Kickstartable tree not detected (no valid treeinfo file)" for bot Red Hat and 
Oracle Linux channels (see below). Do I need to sync from different base 
channels perhaps?

[root@ ~]# spacewalk-repo-sync -c rhel7_x86_64 --sync-kickstart
12:23:10 ==
12:23:10 | Channel: rhel7_x86_64
12:23:10 ==
12:23:10 Sync of channel started.
12:23:10
12:23:10   Processing repository with URL: 
https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os
Repository group_spacewalkproject-java-packages is listed more than once in the 
configuration
12:23:13
12:23:13   Importing comps file 
fef86aafcac04474fa71d40322b4b81bab738f67-comps.xml.
12:23:22 Packages in repo: 23382
12:24:06 No new packages to sync.
12:24:07
12:24:07   Errata in repo: 3449.
12:24:07 No new errata to sync.
12:24:07
12:24:07   Importing kickstarts.
12:24:10 Kickstartable tree not detected (no valid treeinfo file)
12:24:10 Sync of channel completed in 0:01:00.
12:24:10 Total time: 0:01:00
[root@ ~]#

[root@ ~]# spacewalk-repo-sync -c ol7_x86_64 --sync-kickstart
12:56:10 ==
12:56:10 | Channel: ol7_x86_64
12:56:10 ==
12:56:10 Sync of channel started.
12:56:11
12:56:11   Processing repository with URL: 
http://public-yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/
Repository group_spacewalkproject-java-packages is listed more than once in the 
configuration
12:56:12
12:56:12   Importing comps file comps.xml.
12:56:18 Packages in repo: 11799
12:56:36 No new packages to sync.
12:56:36
12:56:36   Errata in repo: 1360.
12:56:37 No new errata to sync.
12:56:37
12:56:37   Importing kickstarts.
12:56:39 Kickstartable tree not detected (no valid treeinfo file)
12:56:40 Sync of channel completed in 0:00:28.
12:56:40 Total time: 0:00:28
[root@ ~]#

Regards
Phil

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

Re: [Spacewalk-list] Antwort: Re: Any chance to get "Schedule"-Jobs running on SW-Server?

[p.cook...@bham.ac.uk]

Hi Matthias

No problem, I have NO ability to write as much as you have in a foreign 
language so you’re still doing far better than me☺

When Spacewalk is installed on the server osa-dispatcher will be running 
automatically. Scheduled tasks (including scripts initiated from Remote 
Command) will only be picked up every 4 hours, as mentioned below. You could 
possibly reduce this to minutes, rather than hours, by amending the setting in 
/etc/sysconfig/rhn/rhnsd. Alternatively, you can install OSAD on registered 
client systems and then scheduled tasks should be picked up almost immediately.

If you want to install OSAD my notes, below, may help?

osa-dispatcher
Server-side service written in Python that determines when an osad client 
instance needs to be pinged or run rhn_check and sends a message telling them 
to do so.

Open Source Architecture Daemon (OSAD)
Client-side service written in Python that responds to pings and runs rhn_check 
when told to by osa-dispatcher.

Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client

Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all

Spacewalk Actions Control - Show Status
# rhn-actions-control --report

Start OSAD
# systemctl start osad.service OR service osad start

Enable OSAD
# systemctl enable osad.service OR chkconfig osad on

OSAD Log File
/var/log/osad

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mgru...@metzler.com
Sent: 23 January 2019 11:21
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Antwort: Re: Any chance to get "Schedule"-Jobs 
running on SW-Server?

Hi Phil,

thanks for your explanation, sorry, as non native english person, I had some 
trouble to formulate it correct

Yes thats the way, as you describe with client systems, the way I also do it or 
via spacecmd, but I would like to schedule this way on my SpaceWalk-Server, not 
the client.
As far as I noticed there is the osa-dispatcher running but not an osad 
(client) therefore he (my spacewalk-server) doesnt pick the job

This was my question... (still have trouble to put it in propper english 
sentences ;->)

cheers
Matthias



METZLER
Informationstechnologie

Matthias Gruber
IT-Infrastruktur & -Betrieb

B. Metzler seel. Sohn & Co.
Kommanditgesellschaft auf Aktien
Untermainanlage 1
60329 Frankfurt am Main
Telefon (0 69) 21 04 - 43 30
Telefax (0 69) 21 04 - 40 40
mgru...@metzler.com<mailto:mgru...@metzler.com>
www.metzler.com



Von:    "p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>" 
mailto:p.cook...@bham.ac.uk>>
An:"spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>" 
mailto:spacewalk-list@redhat.com>>
Datum:23.01.2019 11:43
Betreff:Re: [Spacewalk-list] Any chance to get "Schedule"-Jobs running  
  onSW-Server?
Gesendet von:
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>




Hi Matthias

I’m not entirely sure what you’re asking but you can schedule scripts from the 
Spacewalk Web UI in the following way:

Systems > Click on system name > Remote Command - Add script details then click 
on Schedule

Click on Schedule top menu item to see progress of Action

Note, by default, the rhnsd daemon on a client system connects to the Spacewalk 
server every 4 hours (see /etc/sysconfig/rhn/rhnsd) and performs any updates or 
actions that you have scheduled. However, if you install the Open Source 
Architecture Daemon (OSAD), on the client system, updates and actions should be 
picked up almost immediately from the Spacewalk server.

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of mgru...@metzler.com<mailto:mgru...@metzler.com>
Sent: 23 January 2019 09:56
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Any chance to get "Schedule"-Jobs running on 
SW-Server?

Hi!

Is there any chance to Schedule-Jobs via "system_runscript" working on a 
SpaceWalk-Server like it works on any Client?
I know taskomatic is the "scheduler" within SpaceWalk, but that is not 
configurable.

At the moment I use at to schedule dynamic processes, but thats a bit "tricky"

Perhaps someone has a better solution, and not using something like obsidian or 
Automic?

cheers
Matthias


METZLER
Informationstechnologie

Matthias Gruber
IT-Infrastruktur & -Betrieb

B. Metzler seel. Sohn & Co.
Kommanditgesellschaft auf Aktien
Untermainanlage 1
60329 Frankfurt am Main
Telefon (0 69) 21 04 - 43 30
Telefax (0 69) 2

Re: [Spacewalk-list] Antwort: Re: Antwort: Re: Any chance to get "Schedule"-Jobs running on SW-Server?

[p.cook...@bham.ac.uk]

Yes, I’ve registered my Spacewalk server with itself, to get updates etc, and 
installed OSAD on it.

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mgru...@metzler.com
Sent: 23 January 2019 12:46
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Antwort: Re: Antwort: Re: Any chance to get 
"Schedule"-Jobs running on SW-Server?

Hi Phil

Ohh.. thanks a lot for your notices, they are quite helpfull, but :-)

can I install an osad on the spacewalk-server, so that he can schedules tasks 
on "himself"?

I tried the following, on the SW-Web-Gui:

Systems -> Seeking my Spacewalk-Server (swmain) -> Details -> Remote Command
As skript just a "ls" or something like that and schedule in 5 mins.

Got a "Remote Command has been scheduled 
successfully<https://spacewalk.metzler.com/rhn/systems/details/history/Event.do?sid=110014=17093>
 at 1/23/19 1:34:00 PM CET. "

A look into Schedule tells me "Pending", afai understand, and I will see it 
tomorrow, in max 4h he will/should execute my simple ls, and now the part I am 
seeking for...
Again thats not scheduled on any client, but on the Spacewalk-Server, where 
Spacewalk is running solely, pgsql, the webgui, osa-dispatcher and all the 
stuff..

As I learned, the osa-dispatcher -> osad communication does the trick to 
schedule it and run it at the designated time, not the 4h cycle, since the osad 
runs on SW-clients, there is no trouble, (well sometimes with the communication 
of osad, but thats a different topic), now the question, could I riskfree 
install a osad on my swmain, there would be running osa-dispatcher and osad on 
the same machine, and would he (swmain) pick the job correctly?

Thanks again for your time
cheers
Matthias


METZLER
Informationstechnologie

Matthias Gruber
IT-Infrastruktur & -Betrieb

B. Metzler seel. Sohn & Co.
Kommanditgesellschaft auf Aktien
Untermainanlage 1
60329 Frankfurt am Main
Telefon (0 69) 21 04 - 43 30
Telefax (0 69) 21 04 - 40 40
mgru...@metzler.com<mailto:mgru...@metzler.com>
www.metzler.com



Von:"p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>" 
mailto:p.cook...@bham.ac.uk>>
An:"spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>" 
mailto:spacewalk-list@redhat.com>>
Datum:23.01.2019 13:03
Betreff:Re: [Spacewalk-list] Antwort: Re: Any chance to get
"Schedule"-JobsrunningonSW-Server?
Gesendet von:
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>




Hi Matthias

No problem, I have NO ability to write as much as you have in a foreign 
language so you’re still doing far better than me☺

When Spacewalk is installed on the server osa-dispatcher will be running 
automatically. Scheduled tasks (including scripts initiated from Remote 
Command) will only be picked up every 4 hours, as mentioned below. You could 
possibly reduce this to minutes, rather than hours, by amending the setting in 
/etc/sysconfig/rhn/rhnsd. Alternatively, you can install OSAD on registered 
client systems and then scheduled tasks should be picked up almost immediately.

If you want to install OSAD my notes, below, may help?

osa-dispatcher
Server-side service written in Python that determines when an osad client 
instance needs to be pinged or run rhn_check and sends a message telling them 
to do so.

Open Source Architecture Daemon (OSAD)
Client-side service written in Python that responds to pings and runs rhn_check 
when told to by osa-dispatcher.

Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client

Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all

Spacewalk Actions Control - Show Status
# rhn-actions-control --report

Start OSAD
# systemctl start osad.service OR service osad start

Enable OSAD
# systemctl enable osad.service OR chkconfig osad on

OSAD Log File
/var/log/osad

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of mgru...@metzler.com<mailto:mgru...@metzler.com>
Sent: 23 January 2019 11:21
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Antwort: Re: Any chance to get "Schedule"-Jobs 
running on SW-Server?

Hi Phil,

thanks for your explanation, sorry, as non native english person, I had some 
trouble to formulate it correct

Yes thats the way, as you describe with client systems, the way I also do it or 
via spacecmd, but I would like to schedule this way on my SpaceWalk-Server, not 
the client.
As far as I noticed there is the osa-dispatcher running but not an 

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

[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> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> 
mailto:p.cook...@bham.ac.uk>>
Sent: Tuesday, November 27, 2018 4:16 AM
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

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> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of 
jeffrey.ir...@rivertechllc.com<mailto:jeffrey.ir...@rivertechllc.com>
Sent: 26 November 2018 19:58
To: spacewalk-list@redhat.com<mailto: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...

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

[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>" 
mailto:p.cook...@bham.ac.uk>>
Reply-To: "spacewalk-list@redhat.com<mailto: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>" 
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> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of 
jeffrey.ir...@rivertechllc.com<mailto:jeffrey.ir...@rivertechllc.com>
Sent: 27 November 2018 14:21
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewa

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

[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> 
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> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Graeme Fowler
Sent: 11 December 2018 16:52
To: spacewalk-list@redhat.com<mailto: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>" 
mailto:p.cook...@bham.ac.uk>>
Reply-To: "spacewalk-list@redhat.com<mailto: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>" 
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

[Spacewalk-list] spacewalk-report missing

[p.cook...@bham.ac.uk]

Hi all

Does anyone know why I wouldn't have "spacewalk-report" immediately available 
after installing Spacewalk 2.8 - it appears it should be bundled with the main 
app? Subsequently, I thought it might have to be installed separately, perhaps, 
but it isn't available in the Spacewalk repo and I haven't been able to 
identify where else it may be sourced from.

Regards
Phil

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

[Spacewalk-list] FW: spacewalk-report missing

[p.cook...@bham.ac.uk]

Hello again all

Please ignore this query. I've discovered that the "spacewalk-reports" (plural 
"s" on end) package needs to be installed, to obtain the "spacewalk-report" 
utility, and that this is actually available from the Spacewalk repository.

Regards
Phil

From: Philip Cookson (IT Services)
Sent: 18 December 2018 12:32
To: spacewalk-list@redhat.com
Subject: spacewalk-report missing

Hi all

Does anyone know why I wouldn't have "spacewalk-report" immediately available 
after installing Spacewalk 2.8 - it appears it should be bundled with the main 
app? Subsequently, I thought it might have to be installed separately, perhaps, 
but it isn't available in the Spacewalk repo and I haven't been able to 
identify where else it may be sourced from.

Regards
Phil

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

[Spacewalk-list] Internal Server Error - Snapshot Rollback

[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

[Spacewalk-list] Rollback to Snapshot - Internal Server Error

[p.cook...@bham.ac.uk]

Hi all

I have a new environment with Spacewalk 2.8 installed on RHEL 7. Also, I appear 
to have successfully synced RHEL 6/7 repositories and patched client systems 
from them. However, subsequently, I've tagged a Snapshot but if I try and 
Rollback to this Snapshot I get an "Internal Server Error" and nothing happens. 
I've seen some reference, in the lists, to issues with rollback but no 
solutions yet. Does anyone know why I might be experiencing this?

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

Re: [Spacewalk-list] osa-dispatcher installation on spacewalk proxy

[p.cook...@bham.ac.uk]

Hi

I suspect not - just follow official documentation for installing Spacewalk, 
Spacewalk Proxy and OSAD on to client systems. Hopefully, following links will 
help:

https://github.com/spacewalkproject/spacewalk/wiki/HowToInstall

https://github.com/spacewalkproject/spacewalk/wiki/HowToInstallProxy

https://github.com/spacewalkproject/spacewalk/wiki/OSADSetup

Regards
Phil


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of ssaam...@hotmail.com
Sent: 12 December 2018 12:04
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher installation on spacewalk proxy

I highly appreciate if any one can help me out =)

From: SAM O mailto:ssaam...@hotmail.com>>
Sent: Monday, December 3, 2018 10:05 AM
To: SAM O; spacewalk-list@redhat.com
Subject: Re: osa-dispatcher installation on spacewalk proxy

If anyone can please advise about how to make OSA works with spacewalk proxy, 
just a piece of info: I use 3rd part SSL certifications.


From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of SAM O mailto:ssaam...@hotmail.com>>
Sent: Friday, November 30, 2018 5:23 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] osa-dispatcher installation on spacewalk proxy

Hello All,

Do you install usaully osa-dispatcher on Spacewalk proxy ?

I have clients registered to Spacewalk proxy:

OSA Status:

offline as of unknown



Thanks

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

Re: [Spacewalk-list] Patch notifications and logs

[p.cook...@bham.ac.uk]

Hi Anand

Are you only relying on rhn_check to pickup the patching request or have you 
installed Open Source Architecture Daemon (OSAD) on the client? The latter 
should be quicker. You may find the following link useful:

https://github.com/spacewalkproject/spacewalk/wiki/OsadHowTo

You could also monitor /var/log/yum.log, on the client, too?

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of William Hongach
Sent: 10 December 2018 14:18
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Patch notifications and logs

Hello,

Have you checked to see if this is an selinux issue?  If you have selinux set 
to enforcing, you can look for messages relating to rhnsd and rhn_check in 
/var/log/audit/audit.log.

The context for rhnsd should be rhnsd_exec_t and rhn_check should be rpm_exec_t.

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Ventrapragada, Anand
Sent: Monday, December 10, 2018 8:52 AM
To: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Subject: [Spacewalk-list] Patch notifications and logs

Hello spacewalk Team-

When I am patching RHEL 7 nodes using  spacewalk UI , patch process is getting 
into pending state for a longer time.

-   Is there any way to find out the insights, what exactly is happening 
during the process(Im looking for somewhere we can  find logs for this)

-   Is there any way we can initiate  automatic mail alerts before patching 
process to start and after the completion of patching process(success/Failure )

Thanks
Anand vamsi.






DISCLAIMER: This e-mail message and any attachments are intended solely for the 
use of the individual or entity to which it is addressed and may contain 
information that is confidential or legally privileged. If you are not the 
intended recipient, you are hereby notified that any dissemination, 
distribution, copying or other use of this message or its attachments is 
strictly prohibited. If you have received this message in error, please notify 
the sender immediately and permanently delete this message and any attachments.

___
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

[p.cook...@bham.ac.uk]

Yes, it’s certainly given me something to think about.

Thanks everyone.

Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of waldi...@gmail.com
Sent: 27 November 2018 14:40
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Yay

A lot of great information to you! :-)

I believe now you are good to go.

__
Best
Waldirio
Skype: waldirio
Site: www.waldirio.com.br<http://www.waldirio.com.br>
LinkedIn: https://www.linkedin.com/in/waldirio


On Tue, Nov 27, 2018 at 6:28 AM William Hongach 
mailto:william.hong...@marist.edu>> wrote:
Hi Jeff,

Yes, it is a two-step process but it is a workaround to the Spacewalk server 
not having the subscription to other distributions (or even major releases).  
For example, if your Spacewalk server is RHEL 7, and you want to download/push 
RHEL 6 packages using a local machine you can script the following:

Download:
Create a local directory
reposync –n –repoid=rhel-6-server-rpms
reposync –n –repod=rhel-6-server-optional-rpms

Push:
rhnpush –v –channel=$CHANNEL –server=http://$SERVER/APP –dir=./local-dir

My cron job runs this monthly since that is the anticipated patch frequencey 
for our test and dev servers.  While our software channels are created ahead of 
time, you can script creation of these channels before the push as well, using 
the “spacecmd softwarechannel_create” command.

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Irwin, Jeffrey
Sent: Tuesday, November 27, 2018 9:09 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers


​HTH,

That sounds better than my solution by far.  Well, same solution but more 
streamlined.  So you do a reposync using a script, then use rhnpush to push to 
satellite?  Is that right?



Jeff




From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of William Hongach 
mailto:william.hong...@marist.edu>>
Sent: Tuesday, November 27, 2018 9:03 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hi Phil,

I use Spacewalk to centrally manage multiple distributions and different major 
releases within each distribution, as you are seeking to accomplish.  
Understanding that the Linux server running Spacewalk would not have access to 
all of the different proprietary subscriptions, this was achieved by setting up 
repository download servers for each distribution/release that required a 
separate subscription.  Updates are downloaded by a scripted cron job on each 
local repo server and pushed to the central Spacewalk server using rhnpush.

To script update downloads on a local repo server, the reposync command can be 
used for RHEL, the smt-mirror command can be used for SUSE, etc.  With this 
method, you do not need to worry about URLs.  You can download repositories by 
their ID/name.

HTH.

From: 
spacewalk-list-boun...@redhat.com<mailto: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:17 AM
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

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> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of 
jeffrey.ir...@rivertechllc.com<mailto:jeffrey.ir...@rivertechllc.com>
Sent: 26 November 2018 19:58
To: spacewalk-list@redhat.com<mailto: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> 
mailto:spacewalk-list-boun...@redhat.com&g

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

[p.cook...@bham.ac.uk]

Good afternoon

I'm currently looking in to options for introducing a single centralised 
patching solution for both Oracle Linux 6/7 and RHEL 6/7 systems. There are 
about 100 Oracle Linux servers and 50 RHEL servers. I'm starting with the 
Spacewalk product and therefore, built a proof of concept environment by 
installing Spacewalk 2.8 on an Oracle 7 system. Subsequently, I've added 
channels/repositories for Oracle 6/7 and successfully patched a number of test 
client systems.
However, I can't seem to obtain clear instructions for how to patch RHEL 6/7 
systems using Spacewalk. I believe the functionality of Red Hat Satellite and 
Spacewalk is basically the same but the ability to connect directly to RHN to 
synchronize software repositories and errata's has been disabled. I've seen 
some tentative clues that this can be circumvented as well as some reference to 
using "mrepo" but the latter just seems over complicated really.

Alternatively, if Red Hat Satellite is purchased to patch the RHEL 6/7 servers, 
has anyone had success with using it to patch Oracle 6/7 servers?

In addition to patching, I also need to investigate their provisioning 
capabilities too.

Regards
Phil

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

Re: [Spacewalk-list] Patching notifcation - status & alerts

[p.cook...@bham.ac.uk]

Hi Sethu

I've raised a separate query, today, asking how to configure patching of RHEL 
6/7 servers with Spacewalk. As it seems that you're already patching RHEL 7 
servers, can you let me know how you've managed this please?

Sorry for hijacking your "patching notification" thread!

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of sethumadhav@point72.com
Sent: 26 November 2018 13:21
To: 'Robert Paschedag' 
Cc: 'spacewalk-list@redhat.com' 
Subject: Re: [Spacewalk-list] Patching notifcation - status & alerts

Robert-

-> Yes, But I am looking for patch notification alerts (mails), when patch 
starts is it possible to notify via mail?
-> When Patch is under progress how I can check the status (logs) from 
-> CLI a least?. I know from Web interface, but it shows only in progress (how 
can we check current status of the patch here) for a long time How can I get 
notification  mail/alert if patch is failed/success with error/success(list of 
patches applied) after completion of patch?

I appreciate if you can help me on above 

Regards
Sethu

-Original Message-
From: Robert Paschedag [mailto:robert.pasche...@web.de]
Sent: Monday, November 26, 2018 4:07 PM
To: spacewalk-list@redhat.com; Ede, Sethu Madhav; 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list] Patching notifcation - status & alerts

Am 26. November 2018 11:04:14 MEZ schrieb "Ede, Sethu Madhav" 
:
>Hi spacewalk community-
>
>
>
>I am new to community
>
>
>
>When I am patching host with RHEL 7 errata from spacewalk, patch is in 
>pending state for a long time and I don't see any logs from GUI/CLI.
>Don't  know how to check the logs/status from GUI/CLI and also not 
>receiving  any alerts/mails after completion of patching
>
>Is there any way that we can check the status of the patching from 
>GUI/CLI and whether patched node can notify(via email) regarding the 
>status of patching either success or failures.
>
>Regards,
>Sethu

Hi Sethu,

you only see the status of the Patch "process", if you scheduled the patches 
from the Web interface onto the clients.

You can then see the status within Web interface on the client at "system" -> 
events -> pending or history.

If you just run "yum upgrade" on the client, you won't see anything within Web 
interface. You'll only notice, that the package list has updated and there 
should not be any package to be upgraded anymore.

Hope that helped.


Robert
>
>
>
>
>
>DISCLAIMER: This e-mail message and any attachments are intended solely 
>for the use of the individual or entity to which it is addressed and 
>may contain information that is confidential or legally privileged. If 
>you are not the intended recipient, you are hereby notified that any 
>dissemination, distribution, copying or other use of this message or 
>its attachments is strictly prohibited. If you have received this 
>message in error, please notify the sender immediately and permanently 
>delete this message and any attachments.


--
sent from my mobile device





DISCLAIMER: This e-mail message and any attachments are intended solely for the 
use of the individual or entity to which it is addressed and may contain 
information that is confidential or legally privileged. If you are not the 
intended recipient, you are hereby notified that any dissemination, 
distribution, copying or other use of this message or its attachments is 
strictly prohibited. If you have received this message in error, please notify 
the sender immediately and permanently delete this message and any attachments.




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

___
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

[p.cook...@bham.ac.uk]

Hi Waldirio

Thanks for your response and I’ll take a look at those links. I didn’t think 
there would be any problem patching  RHEL servers with Satellite, as that was 
exactly what it was designed to do, but have you had any success with using the 
same system to patch Oracle 6/7 systems as well – as I’m trying to establish a 
single centralised system capable of doing both? I’m thinking that it probably 
can but Red Hat just wouldn’t support that element?

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of waldi...@gmail.com
Sent: 27 November 2018 01:18
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [EXTERNAL] Spacewalk 2.8 - Patching RHEL 6/7 
Servers

Hello Phil

Yeap, this is the diff between the Product (Red Hat Satellite) and Upstream 
(Spacewalk), basically, on Satellite everything will be automatically and will 
sync packages and erratas. When using SW you have to do this work manually 
*implementing some way to download/push to your SW server*.

There are diff ways to do this implementation, and I really recommend you to 
take a look in the list archives [1]. I wrote this book [2] with all SW 
workflow, unfortunately, I didn't add a way to sync Red Hat repos.

Hope this helps.
__
Best
Waldirio
Skype: waldirio
Site: www.waldirio.com.br<http://www.waldirio.com.br>
LinkedIn: https://www.linkedin.com/in/waldirio

[1]. https://www.redhat.com/archives/spacewalk-list/
[2]. 
https://www.amazon.com/Spacewalk-Satellite-Project-solution-management-ebook/dp/B071DDQ4W2

On Mon, Nov 26, 2018 at 11:58 AM Irwin, Jeffrey 
mailto:jeffrey.ir...@rivertechllc.com>> wrote:

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> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> 
mailto:p.cook...@bham.ac.uk>>
Sent: Monday, November 26, 2018 7:20 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [EXTERNAL] [Spacewalk-list] Spacewalk 2.8 - Patching RHEL 6/7 Servers

Good afternoon

I’m currently looking in to options for introducing a single centralised 
patching solution for both Oracle Linux 6/7 and RHEL 6/7 systems. There are 
about 100 Oracle Linux servers and 50 RHEL servers. I’m starting with the 
Spacewalk product and therefore, built a proof of concept environment by 
installing Spacewalk 2.8 on an Oracle 7 system. Subsequently, I’ve added 
channels/repositories for Oracle 6/7 and successfully patched a number of test 
client systems.
However, I can’t seem to obtain clear instructions for how to patch RHEL 6/7 
systems using Spacewalk. I believe the functionality of Red Hat Satellite and 
Spacewalk is basically the same but the ability to connect directly to RHN to 
synchronize software repositories and errata's has been disabled. I’ve seen 
some tentative clues that this can be circumvented as well as some reference to 
using “mrepo” but the latter just seems over complicated really.

Alternatively, if Red Hat Satellite is purchased to patch the RHEL 6/7 servers, 
has anyone had success with using it to patch Oracle 6/7 servers?

In addition to patching, I also need to investigate their provisioning 
capabilities too.

Regards
Phil

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list
___
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

[p.cook...@bham.ac.uk]

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  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> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> 
mailto:p.cook...@bham.ac.uk>>
Sent: Monday, November 26, 2018 7:20 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [EXTERNAL] [Spacewalk-list] Spacewalk 2.8 - Patching RHEL 6/7 Servers

Good afternoon

I'm currently looking in to options for introducing a single centralised 
patching solution for both Oracle Linux 6/7 and RHEL 6/7 systems. There are 
about 100 Oracle Linux servers and 50 RHEL servers. I'm starting with the 
Spacewalk product and therefore, built a proof of concept environment by 
installing Spacewalk 2.8 on an Oracle 7 system. Subsequently, I've added 
channels/repositories for Oracle 6/7 and successfully patched a number of test 
client systems.
However, I can't seem to obtain clear instructions for how to patch RHEL 6/7 
systems using Spacewalk. I believe the functionality of Red Hat Satellite and 
Spacewalk is basically the same but the ability to connect directly to RHN to 
synchronize software repositories and errata's has been disabled. I've seen 
some tentative clues that this can be circumvented as well as some reference to 
using "mrepo" but the latter just seems over complicated really.

Alternatively, if Red Hat Satellite is purchased to patch the RHEL 6/7 servers, 
has anyone had success with using it to patch Oracle 6/7 servers?

In addition to patching, I also need to investigate their provisioning 
capabilities too.

Regards
Phil

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

[Spacewalk-list] Spacewalk - Patching Log Files

[p.cook...@bham.ac.uk]

Good morning all

I've found that /var/log/yum.log, on client systems, isn't updated when 
patching RHEL 6/7 systems from a Spacewalk server (v2.8). I know details of 
patching activities can be found in the Schedule > Completed Actions or yum 
history, after the event, but is there any log on client or server that can be 
monitored from the command line actually during patching? It's just to monitor 
the patching activity, really, rather than a need to trace a problem or 
similar. If not, I presume that's because the details you see in Schedule > 
Actions are actually being directly written to the embedded PostgreSQL database?

Regards

Philip Cookson
Linux Administrator
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

Re: [Spacewalk-list] Redhat channel on spacewalk

[p.cook...@bham.ac.uk]

No problem, I'm glad I (well Robert really) could be of help:)

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of debayan.mukher...@accenture.com
Sent: 02 April 2019 16:28
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Redhat channel on spacewalk

Hi Phil,

Roberts instructions were really useful.
It is like a backdoor, I have fixed it.
Thanks for the enlightenment, really appreciate your help.


Thanks!

Regards,
Debayan Mukherjee

From: 
spacewalk-list-boun...@redhat.com<mailto: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: Thursday, March 21, 2019 3:06 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [External] Re: [Spacewalk-list] Redhat channel on spacewalk

This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links 
and attachments.


Hi Debayan

I found Robert's instructions, from the list, useful - see link below:

https://www.redhat.com/archives/spacewalk-list/2016-January/msg00014.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_archives_spacewalk-2Dlist_2016-2DJanuary_msg00014.html=DwMFAg=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU=kjYgKXRvPKJ-1Spwl9FaKBV5WMz2rUyGBr-Fiqe550E=XMZhp9gAYZZaZ-CIW1JEA3rEAHCz0vnx1xI7qkH4-r0=llDGurKlaPtQ5yQsQMD7W-U8fGHfKt2Paqbft6AZM68=>

Note, I believe this is un-supported by Red Hat if you go down this route 
though.

Regards
Phil


From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of 
debayan.mukher...@accenture.com<mailto:debayan.mukher...@accenture.com>
Sent: 20 March 2019 15:18
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Redhat channel on spacewalk

Hello,

Recently I have built spacewalk on a redhat 7.0 server.
Configured channels for ubuntu and centos, which is working fine and clients 
are also registered properly.

Does anyone have any idea of creating repository for Redhat servers? Is redhat 
satellite is the only option for creating repository on spacewalk? (I have 
heard that Redhat is going to stop their support on Redhat 5).


Thank you for your help!
Debayan Mukherjee




This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy. Your privacy is important to us. Accenture uses your personal data only 
in compliance with data protection laws. For further information on how 
Accenture processes your personal data, please see our privacy statement at 
https://www.accenture.com/us-en/privacy-policy.
__

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

Re: [Spacewalk-list] Redhat channel on spacewalk

[p.cook...@bham.ac.uk]

Hi Debayan

I found Robert's instructions, from the list, useful - see link below:

https://www.redhat.com/archives/spacewalk-list/2016-January/msg00014.html

Note, I believe this is un-supported by Red Hat if you go down this route 
though.

Regards
Phil


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of debayan.mukher...@accenture.com
Sent: 20 March 2019 15:18
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Redhat channel on spacewalk

Hello,

Recently I have built spacewalk on a redhat 7.0 server.
Configured channels for ubuntu and centos, which is working fine and clients 
are also registered properly.

Does anyone have any idea of creating repository for Redhat servers? Is redhat 
satellite is the only option for creating repository on spacewalk? (I have 
heard that Redhat is going to stop their support on Redhat 5).


Thank you for your help!
Debayan Mukherjee




This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy. Your privacy is important to us. Accenture uses your personal data only 
in compliance with data protection laws. For further information on how 
Accenture processes your personal data, please see our privacy statement at 
https://www.accenture.com/us-en/privacy-policy.
__

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

[Spacewalk-list] spacewalk-report enhancement

[p.cook...@bham.ac.uk]

Good morning

I really like the "spacewalk-report system-currency" report as it gives a 
really good idea of the patch status of each registered system. However, is 
there any way of getting a "System Groups" column added to this? We use System 
Groups to group systems by service and so this would help us produce a regular 
report that could be sent to each service Manager. Currently, we have to do 
this manually after running the report and putting the output in to Excel.

Only the "spacewalk-report inventory" report seems to have a Groups column but 
it lacks the patch type details of the "spacewalk-report system-currency" 
report.

Equally, if anyone knows of an alternative way of doing this, then that would 
be good too.

Regards

Philip Cookson
Linux Administrator
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

Re: [Spacewalk-list] spacewalk-report enhancement

[p.cook...@bham.ac.uk]

Hi Michael

Thanks for your quick response, this looks encouraging. I really don't know 
SQL, though, so can you highlight exactly how to amend the report definition 
please? Also, how can you list available attribute names, like for System 
Group, as I need?

# cat /usr/share/spacewalk/reports/data/system-currency

synopsis:

System currency list

description:

Prints list of numbers of available erratas for each registered system

columns:

system_id Server ID
org_id  Organization ID which is server registered to
nameName of the server
criticalNumber of critical security updates available
important Number of important security updates available
moderateNumber of moderate importance security updates available
low Number of low importance security updates available
bug Number of bug fixes available
enhancement Number of enhancements available
score Total system score

params:

p_crit  java.sc_crit
p_imp   java.sc_imp
p_mod   java.sc_mod
p_low   java.sc_low
p_bug   java.sc_bug
p_enh   java.sc_enh

sql:

select system_id, org_id, name, critical, important, moderate, low, 
bug, enhancement,
((critical * :p_crit) + (important *  :p_imp) + (moderate * 
:p_mod) + (low * :p_low) + (bug * :p_bug) + (enhancement * :p_enh)) as score
from (
select S.id as system_id,
S.org_id as org_id,
S.name as name,
sum(case when (substr(E.synopsis, 1, 1) = 'C' and 
E.advisory_type = 'Security Advisory') then 1 else 0 end) as critical,
sum(case when (substr(E.synopsis, 1, 1) = 'I' and 
E.advisory_type = 'Security Advisory') then 1 else 0 end) as important,
sum(case when (substr(E.synopsis, 1, 1) = 'M' and 
E.advisory_type = 'Security Advisory') then 1 else 0 end) as moderate,
sum(case when (substr(E.synopsis, 1, 1) = 'L' and 
E.advisory_type = 'Security Advisory') then 1 else 0 end) as low,
sum(case when E.advisory_type = 'Bug Fix Advisory' then 1 else 
0 end) as bug,
sum(case when E.advisory_type = 'Product Enhancement Advisory' 
then 1 else 0 end) as enhancement
from rhnServer S left join
(select distinct err.id, snc.server_id, err.synopsis, 
err.advisory_type from rhnErrata err join
rhnServerNeededCache SNC on err.id=SNC.errata_id) E on 
S.id=E.server_id
group by S.id, S.org_id, name
) X
-- where placeholder
order by org_id, system_id

#

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of michael.mr...@redhat.com
Sent: 04 April 2019 10:28
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] spacewalk-report enhancement

p.cook...@bham.ac.uk:
> Good morning
> 
> I really like the "spacewalk-report system-currency" report as it gives a 
> really good idea of the patch status of each registered system. However, is 
> there any way of getting a "System Groups" column added to this? We use 
> System Groups to group systems by service and so this would help us produce a 
> regular report that could be sent to each service Manager. Currently, we have 
> to do this manually after running the report and putting the output in to 
> Excel.
> 
> Only the "spacewalk-report inventory" report seems to have a Groups column 
> but it lacks the patch type details of the "spacewalk-report system-currency" 
> report.
> 
> Equally, if anyone knows of an alternative way of doing this, then that would 
> be good too.

Hello Philip,

See definition of system-currency report in  
/usr/share/spacewalk/reports/data/system-currency
and create your own modification.

> Regards
> 
> Philip Cookson

Regards,

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

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

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

Re: [Spacewalk-list] Clients not Updating / Missing Python Files

[p.cook...@bham.ac.uk]

Merphis

You need to install Spacewalk's CA certificate on the client to enable SSL 
communication:

# rpm -Uvh http:///pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm

Add certificate to database:

# certutil -d sql:/etc/pki/nssdb -An RHN-ORG-TRUSTED-SSL-CERT -t C,, 
-ai /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

Test SSL communication works before attempting to register/re-register:

# curl -v https://


Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of merphis.el...@us.idemia.com
Sent: 04 April 2019 12:09
To: Robert Paschedag ; spacewalk-list@redhat.com
Cc: Patel, Nainesh 
Subject: Re: [Spacewalk-list] Clients not Updating / Missing Python Files

I am still getting the certificate error:

[Thu Apr  4 07:00:55 2019] up2date D: logininfo:{'X-RHN-Server-Id': 110009, 
'X-RHN-Auth-Server-Time': '1554375655.77', 'X-RHN-Auth': 
'kqGoAs+CkN0wXkEpWS0o+BEy2nvxD3MDrtrx16T6gBA=', 'X-RHN-Auth-Channels': 
[['centos_7_zabbix_4_0', '2019040406', '1', '1']], 'X-RHN-Auth-User-Id': 
'', 'X-RHN-Auth-Expire-Offset': '3600.0'} [Thu Apr  4 07:00:56 2019] up2date 
Traceback (most recent call last):
  File "/usr/sbin/rhn_check", line 382, in __run_action
(status, message, data) = CheckCli.__do_call(method, params, kwargs)
  File "/usr/sbin/rhn_check", line 374, in __do_call
method = getMethod.getMethod(method, "/usr/share/rhn/", "actions")
  File "/usr/share/rhn/up2date_client/getMethod.py", line 83, in getMethod
actions = __import__(modulename)
  File "/usr/share/rhn/actions/packages.py", line 295, in 
yum_base = YumAction()
  File "/usr/share/rhn/actions/packages.py", line 69, in __init__
self.doSackSetup()
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 741, in 
doSackSetup
return self._getSacks(archlist=archlist, thisrepo=thisrepo)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in 
_getSacks
self.repos.populateSack(which=repos)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 386, in 
populateSack
sack.populate(repo, mdtype, callback, cacheonly)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 227, in populate
if self._check_db_version(repo, mydbtype):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 319, in 
_check_db_version
return repo._check_db_version(mdtype)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1515, in 
_check_db_version
repoXML = self.repoXML
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1701, in 
repoXML = property(fget=lambda self: self._getRepoXML(),
  File "/usr/share/yum-plugins/rhnplugin.py", line 567, in _getRepoXML
return YumRepository._getRepoXML(self)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1697, in 
_getRepoXML
self._loadRepoXML(text=self.ui_id)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1688, in 
_loadRepoXML
return self._groupLoadRepoXML(text, self._mdpolicy2mdtypes())
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1662, in 
_groupLoadRepoXML
if self._commonLoadRepoXML(text):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1482, in 
_commonLoadRepoXML
result = self._getFileRepoXML(local, text)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1259, in 
_getFileRepoXML
size=102400) # setting max size as 100K
  File "/usr/share/yum-plugins/rhnplugin.py", line 382, in _getFile
start, end, copy_local, checkfunc, text, reget, cache, size)
  File "/usr/share/yum-plugins/rhnplugin.py", line 486, in 
_noExceptionWrappingGet
raise urlException
: failed to retrieve repodata/repomd.xml from 
centos_7_zabbix_4_0 error was [Errno 14] curl#51 - "Unable to communicate 
securely with peer: requested domain name does not match the server's 
certificate."

[Thu Apr  4 07:00:56 2019] up2date D: local action status: ((6,), 'Fatal error 
in Python code occurred', {}) [Thu Apr  4 07:00:56 2019] up2date D: rpcServer: 
Calling XMLRPC registration.welcome_message

-Original Message-
From: Robert Paschedag 
Sent: Thursday, April 04, 2019 6:46 AM
To: Ellis, Merphis ; spacewalk-list@redhat.com
Cc: Patel, Nainesh 
Subject: RE: RE: [Spacewalk-list] Clients not Updating / Missing Python Files

Am 4. April 2019 12:40:07 MESZ schrieb "Ellis, Merphis" 
:
>When I run the rhn_check it does now pull a list of required updates 
>and then I see it try to go out to the internet to get the packages.
>Is there a way to have it pull them from the spacewalk server?  This is 
>a problem with our proxy in that it does not work very well when we try 
>to connect to the public repos using https (port 443).
>
>We have always worked around this by only connecting using http 
>(port80).

Just disable all non spacewalk repos and try again.
Robert

>
>-Original Message-
>From: Robert Paschedag 
>Sent: Thursday, April 04, 2019 2:53 AM
>To: Ellis, Merphis ; 
>spacewalk-list@redhat.com

Re: [Spacewalk-list] [External] Re: Need to know about spacewalk internal architecture and why spacewalk is taking time to deploy scheduled actions

[p.cook...@bham.ac.uk]

Debayan

OSAD and the related packages come from the spacewalk repo, not the RHEL repo. 
The details below may help:

By default, the rhnsd daemon on a client system connects to the Spacewalk 
server every four hours (see /etc/sysconfig/rhn/rhnsd) and performs any updates 
or actions that have been scheduled. If you install the OSA daemon, you can 
apply updates and actions to client systems immediately from the Spacewalk 
server.

osa-dispatcher
Server-side service written in Python that determines when an osad client 
instance needs to be pinged or run rhn_check and sends a message telling them 
to do so.

Open Source Architecture Daemon (OSAD)
Client-side service written in Python that responds to pings and runs rhn_check 
when told to by osa-dispatcher.


Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client

Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all

Start OSAD
# systemctl start osad.service

Enable OSAD
# systemctl enable osad.service

OSAD Log File
/var/log/osad

See official documentation, at the following link, for more details:

https://github.com/spacewalkproject/spacewalk/wiki/OSADSetup


Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of debayan.mukher...@accenture.com
Sent: 03 April 2019 12:32
To: spacewalk-list@redhat.com
Cc: Lingayya, Shanker 
Subject: Re: [Spacewalk-list] [External] Re: Need to know about spacewalk 
internal architecture and why spacewalk is taking time to deploy scheduled 
actions

Hi James and others,


  1.  Tried installing OSAD, but it seems OSAD package is not present in RHEL 
7.4 repo. (it has been discontinued).
  2.  Tried decreasing the value in /etc/sysconfig/rhn/rhnsd and it is not 
permitted to go below 60minutes. (https://access.redhat.com/solutions/92343).

Is there any other solution to decrease the value (for syncing the scheduled 
actions in spacewalk)?


Thanks!

Regards,
Debayan Mukherjee

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of James Hibberd
Sent: Tuesday, April 2, 2019 8:27 PM
To: spacewalk-list@redhat.com
Cc: Lingayya, Shanker 
mailto:shanker.linga...@accenture.com>>
Subject: [External] Re: [Spacewalk-list] Need to know about spacewalk internal 
architecture and why spacewalk is taking time to deploy scheduled actions

This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links 
and attachments.


For Question 3 – I think this might be what you are looking for

On the client side you can change the check in times – Standard config is 240 
minutes , so every 2 hours the client will check into the server.

On the clients change the value inside

/etc/syscon/rhn/rhnsd

To something like 15 minutes, I have my clients checking in every 40 minutes 
instead of the 240 minutes


Hopefully that helps

Thanks

James Hibberd​

 •

Proact IT UK


Technical Support Consultant



m: +447 808 611 011


jhibb...@proact.co.uk

  |

www.proact.eu



Grayson House • Venture Way • Chesterfield • S41 8NE • United Kingdom




‑ Delivering Business Agility ‑


[SIEM 
PoC]

This email and its attachments may be confidential and are intended solely for 
the use of the individual to whom it is addressed. Any views or opinions 
expressed are solely those of the author and do not necessarily represent those 
of Proact IT UK. If you have received this message in error, please notify us 
immediately by replying to the message and deleting it from your computer. We 
do not accept responsibility for any errors or omissions that are present in 
this message, or any attachment, that have arisen as a result of email 
transmission. Proact processes personal information you may provide via email 
or otherwise in accordance with its privacy 
notice.




From: 

Re: [Spacewalk-list] [External] Re: Need to know about spacewalk internal architecture and why spacewalk is taking time to deploy scheduled actions

[p.cook...@bham.ac.uk]

No problem, well done Debayan.

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of debayan.mukher...@accenture.com
Sent: 08 April 2019 11:37
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] [External] Re: Need to know about spacewalk 
internal architecture and why spacewalk is taking time to deploy scheduled 
actions

Hi Phil,

Thanks for all your help!
I have fixed it and it worked well.

Thanks!

Regards,
Debayan Mukherjee

From: 
spacewalk-list-boun...@redhat.com<mailto: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: Wednesday, April 3, 2019 6:23 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] [External] Re: Need to know about spacewalk 
internal architecture and why spacewalk is taking time to deploy scheduled 
actions

Debayan

OSAD and the related packages come from the spacewalk repo, not the RHEL repo. 
The details below may help:

By default, the rhnsd daemon on a client system connects to the Spacewalk 
server every four hours (see /etc/sysconfig/rhn/rhnsd) and performs any updates 
or actions that have been scheduled. If you install the OSA daemon, you can 
apply updates and actions to client systems immediately from the Spacewalk 
server.

osa-dispatcher
Server-side service written in Python that determines when an osad client 
instance needs to be pinged or run rhn_check and sends a message telling them 
to do so.

Open Source Architecture Daemon (OSAD)
Client-side service written in Python that responds to pings and runs rhn_check 
when told to by osa-dispatcher.


Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client

Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all

Start OSAD
# systemctl start osad.service

Enable OSAD
# systemctl enable osad.service

OSAD Log File
/var/log/osad

See official documentation, at the following link, for more details:

https://github.com/spacewalkproject/spacewalk/wiki/OSADSetup<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spacewalkproject_spacewalk_wiki_OSADSetup=DwMGaQ=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU=kjYgKXRvPKJ-1Spwl9FaKBV5WMz2rUyGBr-Fiqe550E=-TL-kq4qG5iFUVvfvFQGfpaXSDo1naG2nprNhjTTL20=SC8K1YYIIGMyipQ65DVZd3D0YYYuVu4CKVUZjGBvY38=>


Regards
Phil

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of 
debayan.mukher...@accenture.com<mailto:debayan.mukher...@accenture.com>
Sent: 03 April 2019 12:32
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Cc: Lingayya, Shanker 
mailto:shanker.linga...@accenture.com>>
Subject: Re: [Spacewalk-list] [External] Re: Need to know about spacewalk 
internal architecture and why spacewalk is taking time to deploy scheduled 
actions

Hi James and others,


  1.  Tried installing OSAD, but it seems OSAD package is not present in RHEL 
7.4 repo. (it has been discontinued).
  2.  Tried decreasing the value in /etc/sysconfig/rhn/rhnsd and it is not 
permitted to go below 60minutes. 
(https://access.redhat.com/solutions/92343<https://urldefense.proofpoint.com/v2/url?u=https-3A__access.redhat.com_solutions_92343=DwMGaQ=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU=kjYgKXRvPKJ-1Spwl9FaKBV5WMz2rUyGBr-Fiqe550E=-TL-kq4qG5iFUVvfvFQGfpaXSDo1naG2nprNhjTTL20=KQjrGE0W2C0RI_UeoEGNrzmhN6u-nhLRKsYYrUQGHW0=>).

Is there any other solution to decrease the value (for syncing the scheduled 
actions in spacewalk)?


Thanks!

Regards,
Debayan Mukherjee

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of James Hibberd
Sent: Tuesday, April 2, 2019 8:27 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Cc: Lingayya, Shanker 
mailto:shanker.linga...@accenture.com>>
Subject: [External] Re: [Spacewalk-list] Need to know about spacewalk internal 
architecture and why spacewalk is taking time to deploy scheduled actions

This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links 
and attachments.


For Question 3 – I think this might be what you are looking for

On the client side you can change the check in times – Standard config is 240 
minutes , so every 2 hours the client will check into the server.

On the clients change the value inside

/etc/syscon/rhn/rhnsd

To something like 15 minutes, I have my clients checking in every 40 minutes 
instead of the 240 minutes


Hopefully that helps

Thanks

James Hibberd​

 •

Proact IT UK


Technical Support Consultant



m: +447 808 611 011


jhibb...@proact.co.uk<mailto:jhibb...@proact.co.uk>

  |

www.proact.eu<https://urldefense.proofpoint.com/v2/url?u=http-3A__w

Re: [Spacewalk-list] FW: Disable downloading stock repos in CentOS

[p.cook...@bham.ac.uk]

You can disable a repo as described below – if done correctly then it shouldn’t 
show up with “yum repolist enabled” any longer. If you mean stop syncing a 
repository, though, that can be done from the WebUI as below:

Channels -> Manage Software Channels -> Click Channel Name -> Repositories -> 
Sync -> Disable Schedule

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of jerome.me...@lcsystems.ch
Sent: 26 February 2019 15:33
To: 'Paul Deveau' 
Cc: spacewalk-list@redhat.com
Subject: [Spacewalk-list] FW: Disable downloading stock repos in CentOS

Dear Paul,

Do you have found a solution to your repo?
From my side I’ve moved all my repos to an old directory but spacewalk will be 
re-create them.
Before creating a crontab job to removing of these files automatically, I 
wanted to know if another solution exists.

Best regards,
Jérôme

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of William H. ten Bensel
Sent: Samstag, 23. Februar 2019 00:02
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] Disable downloading stock repos in CentOS

There is another option mentioned in the archive, about updating /etc/yum.conf 
with a new reposdir=.  This avoids updating/creating the repositories when the 
CentOS release rpm is updated with the next kernel release.   Oracle and Redhat 
do not include the repository information in the primary release rpm, but 
provide optional rpms or methods to install the repositories.  By separating 
the functionality of the rpm, this avoids these issues.  I wish CentOS would 
follow the same process as well.

https://www.redhat.com/archives/spacewalk-list/2018-February/msg00033.html

# rpm -ql centos-release-7-5.1804.5.el7.centos.x86_64 |grep repo

/etc/yum.repos.d/CentOS-Base.repo
/etc/yum.repos.d/CentOS-CR.repo
/etc/yum.repos.d/CentOS-Debuginfo.repo
/etc/yum.repos.d/CentOS-Media.repo
/etc/yum.repos.d/CentOS-Sources.repo
/etc/yum.repos.d/CentOS-Vault.repo
/etc/yum.repos.d/CentOS-fasttrack.repo

# rpm -ql oraclelinux-release-7.5-1.0.5.el7.x86_64 |grep repo
#

- Thanks and good luck



From:    "p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>" 
mailto:p.cook...@bham.ac.uk>>
To:"spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>" 
mailto:spacewalk-list@redhat.com>>
Date:02/22/2019 07:39 AM
Subject:Re: [Spacewalk-list] Disable downloading stock repos in CentOS
Sent by:
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>




This email originated from outside of the company. Please use discretion if 
opening attachments or clicking on links.


Hi Paul

There are a few options to disable existing repo’s really:

1.   Move existing related repo files to a different location (like you’ve 
described).

mkdir /root/Original_Repos
mv /etc/yum.repos.d/* /root/Original_Repos/
yum clean all and/orrm -rf /var/cache/yum

2.   Temporarily disable during update.

yum --disablerepo= update

3.   Permanently disable.

Change the value of “enabled=” from 1 to 0 in /etc/yum.repos.d/

Regards
Phil



From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of pdev...@uottawa.ca<mailto:pdev...@uottawa.ca>
Sent: 22 February 2019 12:52
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Disable downloading stock repos in CentOS

Hello,

I would like to disable the downloading of the stock repos like 
Centos-Base.repo and the rest They get in the way when I perform upgrades 
(unless I'm doing something wrong?) I usually move the repos to a different 
directory so that yum does not see them.

Thank you,

--
Paul Deveau
Analyste de systèmes principal|Senior Systems Analyst
Technologies de l’information|Information Technology
Université d’Ottawa|University of 
Ottawa___
Spacewalk-list mailing list
Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list




**



This email and any attachments may contain information that is confidential 
and/or privileged for the sole use of the intended recipient. Any use, review, 
disclosure, copying, distribution or reliance by others, and any forwarding of 
this email or its contents, without the express permission of the sender is 
strictly prohibited by law. If you are not the intended recipient, please 
contact the sender immediately, delete the e-mail and destroy all copies.

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

Re: [Spacewalk-list] Registration to the new server via rhnreg_ks returns an SSL error

[p.cook...@bham.ac.uk]

Obviously, that will work but you won’t be using the secure layer or addressing 
the underlying problem!

If you’re getting the same problem with a new client system I can see how you 
may think it’s a server related issue. However, the Spacewalk certificate is 
generated during installation so it would be un-usual, I would have thought?

Did you add the certificate to the database (certutil -d sql:/etc/pki/nssdb -An 
RHN-ORG-TRUSTED-SSL-CERT -t C,, -ai /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT), 
too, as you only mention getting the rpm (rpm -Uvh 
http://spacewalk-server/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm)?

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of rui.a.z...@nokia-sbell.com
Sent: 28 February 2019 09:51
To: spacewalk-list@redhat.com
Cc: Zhu, Ting (NSB - CN/Shanghai) 
Subject: Re: [Spacewalk-list] Registration to the new server via rhnreg_ks 
returns an SSL error


I think this may not the problem of the client, when I try to add new client 
server it also has the error: The SSL certificate failed verification.
I find this help, change the --serverUrl=https://spacewalk-server/XMLRPC to
--serverUrl=http://spacewalk-server/XMLRPC.  The system can be registerd,
 The reason maybe:

  *   System did not have the correct SSL certificate.(I check, server and 
client have the same sslCACert)
  *   SSL certificate was corrupted.(how to explain this?)


From: 
spacewalk-list-boun...@redhat.com<mailto: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: 2019年2月28日 17:35
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] Registration to the new server via rhnreg_ks 
returns an SSL error

Hi

It’s a little more involved than that! I produced these notes, for myself, when 
un-registering a system from a Dev Spacewalk Server and registering it with a 
Test Spacewalk Server. It’s effectively the same thing that you need to do 
though.


Spacewalk does not provide an option to un-register a client system (similar to 
registering - “rhnreg_ks”) - the only option is to remove the client system’s 
profile from the Spacewalk server.

To remove a client’s profile from the Spacewalk server perform these steps:


  1.  Log in to the Spacewalk Console.
  2.  Click on the Systems tab in the top navigation bar and then click on the 
name of the system which you want to remove from the Systems List.
  3.  Click the Delete System link in the top-right corner of the page.
  4.  Confirm system profile deletion by clicking the Delete Profile button.
  5.  Now go to the client system and execute below command to remove the 
associated System ID file:

# rm /etc/sysconfig/rhn/systemid

In addition, remove Spacewalk certificate for Development and add certificate 
for Test. Then register client system with Test Spacewalk server:

# certutil -d sql:/etc/pki/nssdb -Dn RHN-ORG-TRUSTED-SSL-CERT -t C,, -ai 
/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
# rpm -ev rhn-org-trusted-ssl-cert-1.0-1.noarch
# rpm -Uvh https://https://%3cTest> 
Server>/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
# certutil -d sql:/etc/pki/nssdb -An RHN-ORG-TRUSTED-SSL-CERT -t C,, -ai 
/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
# rhnreg_ks --serverUrl=https:///XMLRPC 
--sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=[ACTIVATION 
KEY]


Note, if you’re using OSAD, the service may have stopped during this process 
and therefore, will need to be re-started. I’ve also found that, even if it’s 
still running, I’ve had to restart it before actions were automatically picked 
up again:

# systemctl start osad OR service osad start


Hope this is of help?

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of rui.a.z...@nokia-sbell.com<mailto:rui.a.z...@nokia-sbell.com>
Sent: 28 February 2019 08:57
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Cc: Zhu, Ting (NSB - CN/Shanghai) 
mailto:ting@nokia-sbell.com>>
Subject: [Spacewalk-list] Registration to the new server via rhnreg_ks returns 
an SSL error

I re-installed the spacewalk server, and the client can not register to the new 
installed server.

[root@FNSHB109 rhn]# rpm -e rhn-org-trusted-ssl-cert-1.0-1.noarch

[root@FNSHB109 rhn]# rpm -Uvh 
http://spacewalk-server/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
Retrieving http://spacewalk-server/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
Preparing...  # [100%]
Updating / installing...
   1:rhn-org-trusted-ssl-cert-1.0-1   # [100%]

[root@FNSHB109 rhn]# rhnreg_ks --serverUrl=https://spacewalk-server/XMLRPC 
--sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=1-cen

Re: [Spacewalk-list] Antwort: FW: List of patched/to patched systems by commandline

[p.cook...@bham.ac.uk]

This screen in WebUI may be of interest too:

Systems (top menu) -> Systems (left menu) -> System Currency (left option)
nb Option to "Download CSV" (bottom right) too

Subsequently, if you just wanted to apply security updates, perhaps, navigate 
to here:

Systems -> Tick Systems -> Manage -> Errata -> Set Show to "Security Advisory" 
-> Select All -> Apply Errata


Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mgru...@metzler.com
Sent: 18 February 2019 15:40
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Antwort: FW: List of patched/to patched systems by 
commandline

Hi!

Oh... thats sound good... I am back in that stuff tomorrow
Thanks a lot

Matthias



METZLER
Informationstechnologie

Matthias Gruber
IT-Infrastruktur & -Betrieb

B. Metzler seel. Sohn & Co.
Kommanditgesellschaft auf Aktien
Untermainanlage 1
60329 Frankfurt am Main
Telefon (0 69) 21 04 - 43 30
Telefax (0 69) 21 04 - 40 40
mgru...@metzler.com<mailto:mgru...@metzler.com>
www.metzler.com



Von:"p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>" 
mailto:p.cook...@bham.ac.uk>>
An:"spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>" 
mailto:spacewalk-list@redhat.com>>
Datum:18.02.2019 16:32
Betreff:[Spacewalk-list] FW: List of patched/to patched systems by 
commandline
Gesendet von:
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>




Hi Matthias

I’ve come across a “spacecmd” report called “report_outofdatesystems” which may 
be of interest to you as it produces a very simple list of systems with the 
number of outstanding patches?

spacecmd {SSM:0}> report_outofdatesystems
System   Packages
--
server 19
server 22
server 3590
server 4592
spacecmd {SSM:0}>

Regards
Phil

From: Philip Cookson (IT Services)
Sent: 12 February 2019 15:27
To: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Subject: RE: [Spacewalk-list] List of patched/to patched systems by commandline

Hi Matthias

Have you looked at the standard Spacewalk reports or “spacecmd” command at all?

The “spacewalk-report” tool outputs information in a CSV format.

The related package needs to be installed from the Spacewalk repository:

# yum -y install spacewalk-reports

The man page for spacewalk-report is in the usual format and there is also an 
option "--list-fields-info" that is helpful:

# spacewalk-report --list-fields

See report descriptions below – the “system-currency” report might be useful 
for what you’re after?
• channel-packages - Packages in channels
• channels - Channel report
• custom-info - Display system custom info
• entitlements - Entitlement and channel list and usage
• errata-channels - List of errata in channels
• errata-list - Errata information based upon compliance checks against 
systems
• errata-list-all - List of all erratas
• errata-systems - Listing of each errata applicable to each affected 
system
• inactive-systems - Inactive systems in Satellite
• inventory - Inventory report
• kickstartable-trees - List of kickstartable trees
• packages-updates-all - List of packages that can be upgraded
• packages-updates-newest - List of packages that can be upgraded
• scap-scan - Results of OpenSCAP xccdf evaluation
• scap-scan-results - Results of OpenSCAP xccdf evaluation
• system-crash-count - Crash count for systems
• system-crash-details - Crash details for systems
• system-currency - System currency list
• system-groups - System groups in Satellite
• system-groups-keys - Activation keys for system groups
• system-groups-systems - Systems in system groups
• system-groups-users - System groups users report
• system-history - System event history
• system-history-channels - Channel event history
• system-history-configuration - Configuration event history
• system-history-entitlements - System entitlement event history
• system-history-errata - Errata event history
• system-history-kickstart - Kickstart event history
• system-history-packages - Package event history
• system-history-scap - OpenSCAP event history
• system-packages-installed - Packages installed on systems
• users - Users in the system
• users-systems - Systems administered by individual users

The output could be piped through awk to get just the

Re: [Spacewalk-list] Registration to the new server via rhnreg_ks returns an SSL error

[p.cook...@bham.ac.uk]

You're only showing the top of the files there. Is the rest of the information 
the same too, particularly the server name and actual key? All the responses 
from "spacewalk-setup" should be in there really.

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of rui.a.z...@nokia-sbell.com
Sent: 01 March 2019 11:02
To: spacewalk-list@redhat.com; robert.pasche...@web.de
Cc: Zhu, Ting (NSB - CN/Shanghai) 
Subject: Re: [Spacewalk-list] Registration to the new server via rhnreg_ks 
returns an SSL error

Very sad to say, they are the same, I think if the file in hosts has some 
impacts? I find I have not write the configuration before. I will try and tell 
the result later.
[root@spacewalk-server pxelinux.cfg]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
135.251.206.139 spacewalk-server

Client:
[root@FNSHA172 yum.repos.d]# cat /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
91:88:95:56:dd:6c:6d:0d

Server:
[root@spacewalk-server ~]# cat /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
91:88:95:56:dd:6c:6d:0d

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of p.cook...@bham.ac.uk
Sent: 2019年3月1日 17:09
To: robert.pasche...@web.de; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Registration to the new server via rhnreg_ks 
returns an SSL error

Whether you re-installed the Spacewalk application on the same server or a 
different one, a new certificate should have been produced after running 
"spacewalk-setup."

Subsequently, the certificate can be viewed on the server:

cat /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT

OR

WebUI -> Systems (Top Menu) -> Kickstart (Left Menu) -> GPG and SSL Keys -> 
RHN-ORG-TRUSTED-SSL-CERT -> Key contents

If everything has been done correctly, to register the client, the certificate 
can be viewed on there too:

cat /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

If they don't match, you'll have a problem!

Like Robert says, it seems to be "just" a SSL issue really but, obviously, the 
certificate is being generated by the Spacewalk application installation.

Regards
Phil

-Original Message-
From: robert.pasche...@web.de 
Sent: 28 February 2019 16:47
To: spacewalk-list@redhat.com; Philip Cookson (IT Services) 
; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Registration to the new server via rhnreg_ks 
returns an SSL error

Am 28. Februar 2019 11:10:57 MEZ schrieb "p.cook...@bham.ac.uk" 
:
>Obviously, that will work but you won’t be using the secure layer or 
>addressing the underlying problem!
>
>If you’re getting the same problem with a new client system I can see 
>how you may think it’s a server related issue. However, the Spacewalk 
>certificate is generated during installation so it would be un-usual, I 
>would have thought?
>
>Did you add the certificate to the database (certutil -d 
>sql:/etc/pki/nssdb -An RHN-ORG-TRUSTED-SSL-CERT -t C,, -ai 
>/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT), too, as you only mention 
>getting the rpm (rpm -Uvh 
>http://spacewalk-server/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm)?
>
>Regards
>Phil
>
>From: spacewalk-list-boun...@redhat.com 
> On Behalf Of 
>rui.a.z...@nokia-sbell.com
>Sent: 28 February 2019 09:51
>To: spacewalk-list@redhat.com
>Cc: Zhu, Ting (NSB - CN/Shanghai) 
>Subject: Re: [Spacewalk-list] Registration to the new server via 
>rhnreg_ks returns an SSL error
>
>
>I think this may not the problem of the client, when I try to add new 
>client server it also has the error: The SSL certificate failed 
>verification.
>I find this help, change the
>--serverUrl=https://spacewalk-server/XMLRPC to 
>--serverUrl=http://spacewalk-server/XMLRPC.  The system can be 
>registerd,  The reason maybe:
>
>*   System did not have the correct SSL certificate.(I check, server
>and client have the same sslCACert)
>  *   SSL certificate was corrupted.(how to explain this?)

This is just a standard SSL issue. Nothing special with spacewalk.

If you're connecting to https://spacewalk-server/, "spacewalk-server" has to be 
included within the SSL certificate. And if that is missing, the certificate 
may be valid but you still get the verification error .

Robert

>
>
>From:
>spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-bounces@redhat.
>com> [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of
>p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>
>Sent: 2019年2月28日 17:35
>To: spacewalk-list@redhat.com<mailto:spacewalk-lis

Re: [Spacewalk-list] xmlrpclib.ProtocolError issue with spacewalk-manage-channel-lifecycle

[p.cook...@bham.ac.uk]

Hi Jérôme

If you've never modified the default Java memory settings, for Taskomatic, or 
Tomcat memory settings it's possibly running out of memory and task is 
crashing. This is a known issue, particularly when you sync large repos etc. 
See following link for more info:

https://docs.oracle.com/cd/E92593_01/E90695/html/swk24-issues-memory.html


You can see what Taskomatic is currently using by checking status:

# systemctl status taskomatic.service

● taskomatic.service - Taskomatic
   Loaded: loaded (/usr/lib/systemd/system/taskomatic.service; enabled; vendor 
preset: disabled)
   Active: active (running) since Wed 2019-02-20 14:18:56 GMT; 1 day 23h ago
  Process: 46068 ExecStop=/usr/sbin/taskomatic stop (code=exited, 
status=0/SUCCESS)
  Process: 49351 ExecStart=/usr/sbin/taskomatic start (code=exited, 
status=0/SUCCESS)
 Main PID: 49377 (taskomaticd)
   CGroup: /system.slice/taskomatic.service
   ├─49377 /usr/bin/taskomaticd 
/usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf 
wrapper.pidfile=/var/run//taskomatic.pid wrapper.daemonize=TRUE
   └─49383 /usr/bin/java -Dibm.dst.compatibility=true 
-Dfile.encoding=UTF-8 -Xms256m -Xmx1024m 
-Djava.library.path=/usr/lib:/usr/lib64:/usr/lib/oracle/11.2/client64/lib:/usr/lib/oracle/11.2/client/lib
 -classpath /usr/share/jav...

Feb 20 14:18:56  systemd[1]: Starting Taskomatic...
Feb 20 14:18:56  taskomatic[49351]: Starting RHN Taskomatic...
Feb 20 14:18:56  wrapper[49377]: --> Wrapper Started as Daemon
Feb 20 14:18:56  wrapper[49377]: Launching a JVM...
Feb 20 14:18:56  systemd[1]: Started Taskomatic.
#

After changing the memory size you'll need to re-start Taskomatic.

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of jerome.me...@lcsystems.ch
Sent: 20 February 2019 10:20
To: 'Robert Paschedag' ; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] xmlrpclib.ProtocolError issue with 
spacewalk-manage-channel-lifecycle

Hi Robert,

Thanks for your quick reply.
It is good to know that isn't a application's issue ;) Do you know if there's a 
possibility to tune the DB to avoid this problem? Actually I've the SW 2.8

Best regards,
Jérôme




-Original Message-
From: Robert Paschedag [mailto:robert.pasche...@web.de]
Sent: Dienstag, 19. Februar 2019 18:31
To: spacewalk-list@redhat.com; Jérôme Meyer; 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list] xmlrpclib.ProtocolError issue with 
spacewalk-manage-channel-lifecycle

Am 19. Februar 2019 16:44:24 MEZ schrieb "Jérôme Meyer" 
:
>Hi Everyone,
>
>I'm using the spacewalk-manage-channel-lifecycle to manage my 
>spacewalk's channel.
>
>Sometimes when I run this command, I've received this following error 
>on epel channel but not on any other channel.
>At the end I've runned with channel exclusion (-x
>dev-epel7-centos7-x86_64) and all was fine but it isn't the solution...
>
>
>1)  In this case I just started the command a second time. This is the 
>reason why there is no package.
>
>2)  The only difference I see between the epel channel and the others 
>is that there are a lot of packets to transfert.
>
>
># spacewalk-manage-channel-lifecycle -c dev-centos7-x86_64 --promote
>INFO: Merging packages from dev-centos7-x86_64 into test-centos7-x86_64
>INFO: Added 0 packages
>INFO: Merging errata into test-centos7-x86_64
>INFO: Added 0 errata
>
>INFO: Merging packages from dev-centos7-x86_64-centosplus into 
>test-centos7-x86_64-centosplus
>INFO: Added 0 packages
>INFO: Merging errata into test-centos7-x86_64-centosplus
>INFO: Added 0 errata
>
>INFO: Merging packages from dev-centos7-x86_64-extras into 
>test-centos7-x86_64-extras
>INFO: Added 0 packages
>INFO: Merging errata into test-centos7-x86_64-extras
>INFO: Added 0 errata
>
>[...]
>
>INFO: Merging packages from dev-epel7-centos7-x86_64 into
>test-epel7-centos7-x86_64
>Traceback (most recent call last):
>  File "/bin/spacewalk-manage-channel-lifecycle", line 575, in 
>merge_channels(child_source, child_dest) File 
>"/bin/spacewalk-manage-channel-lifecycle", line 213, in merge_channels
>dest_label)
>  File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__
>return self.__send(self.__name, args)
>  File "/usr/lib64/python2.7/xmlrpclib.py", line 1591, in __request
>verbose=self.__verbose
>  File "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request
>return self.single_request(host, handler, request_body, verbose) 
>File "/usr/lib64/python2.7/xmlrpclib.py", line 1321, in single_request
>response.msg,
>xmlrpclib.ProtocolError: chlxintmgmtp01.weforum.local/rpc/api: 500 Internal Server Error>

What I could think of, is that there are too many transaction going onto the 
database and it just takes too long so you get that 500 error.

Had this when I was to clean (and archive) finished actions. Had to do this in 
steps Otherwise I got an 500 error. But that was somewhere in SW 2.7 I think.

Robert

>
>
>Has anyone ever had this problem before?
>A 

Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

[p.cook...@bham.ac.uk]

Hi Harald

I have Spacewalk 2.8 installed on a RHEL 7 server. I only need to register RHEL 
6/7 and Oracle Linux 6/7 systems, rather than Centos, so this may possibly be 
why I’m not seeing your issue?

However, if rhnsd has been installed, correctly, it should start automatically 
and /etc/sysconfig/rhn/rhnsd should be present too - /etc/sysconfig/rhn/rhnsd 
comes from the rhnsd package:

# rpm -qf /etc/sysconfig/rhn/rhnsd
rhnsd-5.0.37-1.el7.centos.x86_64
#

Therefore, it may be wise to check the steps you took to register the client 
systems and/or verify the package:

[root@its-n-swcli-01 ~]# rpm -V rhnsd
[root@its-n-swcli-01 ~]#

Regards
Phil



From: spacewalk-list-boun...@redhat.com  On 
Behalf Of harald.wacha...@akm.at
Sent: 19 February 2019 08:32
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Phil,

Still a problem with the offline clients.
It looks like that the rhn daemon stops working after some time.

Redirecting to /bin/systemctl status  rhnsd.service
● rhnsd.service - Spacewalk Server daemon
   Loaded: loaded (/usr/lib/systemd/system/rhnsd.service; static; vendor 
preset: disabled)
   Active: inactive (dead)



And some more:

I have no /etc/sysconfig/rhn/rhnsd

[root@vie-srv-XXX log]# cd /etc/sysconfig/rhn/
[root@vie-srv-XXX rhn]# ls -la
total 24
drwxr-xr-x. 4 root root 4096 Feb 19 09:18 .
drwxr-xr-x. 7 root root 4096 Jan 23 16:48 ..
drwxr-xr-x. 4 root root   37 Jan 23 16:48 allowed-actions
drwxr-xr-x. 2 root root   37 Feb 14 12:19 clientCaps.d
-rw---. 1 root root  129 Jan 29 16:48 osad-auth.conf.rpmsave
-rw-r--r--. 1 root root 1446 Nov 26 21:50 rhncfg-client.conf
-rw---. 1 root root 1321 Jan 23 16:51 systemid
-rw-r--r--. 1 root root 1948 Jan 23 16:51 up2date

In the rhncfg-client.conf I can find a log directory: script_log_file = 
/var/log/rhn/rhncfg-action-output.log

But even this log file does not exist……


Warm regards,

Harald


Von: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>
Gesendet: Donnerstag, 14. Februar 2019 14:46
An: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

No problem Harald. If you want to continue using rhnsd you can still reduce the 
check-in time in /etc/sysconfig/rhn/rhnsd if you want though (default is 240 
mins):

# cat /etc/sysconfig/rhn/rhnsd
INTERVAL=240
#

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of harald.wacha...@akm.at<mailto:harald.wacha...@akm.at>
Sent: 14 February 2019 11:18
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi Phil,

Thanks for your reply.
It looks like it was a rookie mistake.
I am new at Spacewalk and I followed the instructions here to register a client.

https://github.com/spacewalkproject/spacewalk/wiki/RegisteringClients

Unfortunately there was no hint that you have to start the rhnsd service.
So I have started the service now and configured it to start automatically.
And I need no osad at the moment. Every 4 hours check in is fine for me.

Thanks again,

Warm regards,

Harald






Von: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>
Gesendet: Donnerstag, 14. Februar 2019 10:01
An: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi Harald

Were they ok originally, and stopped working properly, or are you just trying 
to setup OSAD for the first time? Either way if you work through my personal 
notes (for OSAD), below, it may help to identify your problem. If everything 
has been done correctly it may be an infrastructure problem though ie 
un-reliable network connection or NTP?

By default, the rhnsd daemon on a client system connects to the Spacewalk 
server every four hours (see /etc/sysconfig/rhn/rhnsd) and performs any updates 
or actions that have been scheduled. If you install the OSA daemon, you can 
apply updates and actions to client systems immediately from the Spacewalk 
server.

osa-dispatcher
Server-side service that determines when an osad client instance needs to be 
pinged or run rhn_check and sends a message telling them to do so. This is 
installed when Spacewalk is installed.

Open Source Architecture Daemon (OSAD)
Client-side service that responds to pings and runs rhn_check when told to by 
osa-dispatcher.

See official documentation, at the following link, for more details:

https://github.com/spacewalkproject/spacewalk/wiki/OSADSetup

Install OSAD and related RHN/Spac

Re: [Spacewalk-list] Disable downloading stock repos in CentOS

[p.cook...@bham.ac.uk]

Hi Paul

There are a few options to disable existing repo's really:


1.   Move existing related repo files to a different location (like you've 
described).

mkdir /root/Original_Repos
mv /etc/yum.repos.d/* /root/Original_Repos/
yum clean all and/or rm -rf /var/cache/yum


2.   Temporarily disable during update.

yum --disablerepo= update


3.   Permanently disable.

Change the value of "enabled=" from 1 to 0 in /etc/yum.repos.d/

Regards
Phil



From: spacewalk-list-boun...@redhat.com  On 
Behalf Of pdev...@uottawa.ca
Sent: 22 February 2019 12:52
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Disable downloading stock repos in CentOS

Hello,

I would like to disable the downloading of the stock repos like 
Centos-Base.repo and the rest They get in the way when I perform upgrades 
(unless I'm doing something wrong?) I usually move the repos to a different 
directory so that yum does not see them.

Thank you,

--
Paul Deveau
Analyste de systèmes principal|Senior Systems Analyst
Technologies de l'information|Information Technology
Université d'Ottawa|University of Ottawa
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

[p.cook...@bham.ac.uk]

If /etc/sysconfig/rhn/rhnsd isn’t there then either rhnsd hasn’t installed 
correctly or, like you say, someone or something has removed it afterwards. If 
that’s the case may be other related files could be missing too? Either way if 
you verify the package (rpm -V rhnsd) it should give you some indication of 
this. If it does find errors then yes, initially, just try re-installing it.

Might be wise to check the other packages, that were installed for client 
registration, too:

rhn-client-tools
rhn-check
rhn-setup
m2crypto
yum-rhn-plugin

Regards
Phil


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of whten...@up.com
Sent: 21 February 2019 00:22
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

If /etc/sysconfig/rhn/rhnsd is not there, then need to investigate the package 
rhnsd. I would try and reinstall the rpm, and check to see if the file is there.

If the file is not there:
What version of rhnsd is installed on the clients?
What files are being provided by the rpm?  rpm -ql rhnsd

If the file is there:
Wait. If it is no longer there after some time.
A mis-configured chef/puppet/automated action could be deleting the 
file vs creating or updating the file.


If it is still there, some other items to look at:
Someone could have accidentally deleted the file (oops).
There could a custom RPM that is being installed on the impacted 
systems that has a script which is deleting the file.

Thanks




From:Wachauer Harald 
mailto:harald.wacha...@akm.at>>
To:"spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>" 
mailto:spacewalk-list@redhat.com>>
Date:02/19/2019 02:33 AM
Subject:Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Sent by:
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>




This email originated from outside of the company. Please use discretion if 
opening attachments or clicking on links.


Phil,

Still a problem with the offline clients.
It looks like that the rhn daemon stops working after some time.

Redirecting to /bin/systemctl status  rhnsd.service
● rhnsd.service - Spacewalk Server daemon
   Loaded: loaded (/usr/lib/systemd/system/rhnsd.service; static; vendor 
preset: disabled)
   Active: inactive (dead)



And some more:

I have no /etc/sysconfig/rhn/rhnsd

[root@vie-srv-XXX log]# cd /etc/sysconfig/rhn/
[root@vie-srv-XXX rhn]# ls -la
total 24
drwxr-xr-x. 4 root root 4096 Feb 19 09:18 .
drwxr-xr-x. 7 root root 4096 Jan 23 16:48 ..
drwxr-xr-x. 4 root root   37 Jan 23 16:48 allowed-actions
drwxr-xr-x. 2 root root   37 Feb 14 12:19 clientCaps.d
-rw---. 1 root root  129 Jan 29 16:48 osad-auth.conf.rpmsave
-rw-r--r--. 1 root root 1446 Nov 26 21:50 rhncfg-client.conf
-rw---. 1 root root 1321 Jan 23 16:51 systemid
-rw-r--r--. 1 root root 1948 Jan 23 16:51 up2date

In the rhncfg-client.conf I can find a log directory: script_log_file = 
/var/log/rhn/rhncfg-action-output.log

But even this log file does not exist……


Warm regards,

Harald


Von: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>
Gesendet: Donnerstag, 14. Februar 2019 14:46
An: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

No problem Harald. If you want to continue using rhnsd you can still reduce the 
check-in time in /etc/sysconfig/rhn/rhnsd if you want though (default is 240 
mins):

# cat /etc/sysconfig/rhn/rhnsd
INTERVAL=240
#

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>mailto:spacewalk-list-boun...@redhat.com>>
 On Behalf Of harald.wacha...@akm.at<mailto:harald.wacha...@akm.at>
Sent: 14 February 2019 11:18
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi Phil,

Thanks for your reply.
It looks like it was a rookie mistake.
I am new at Spacewalk and I followed the instructions here to register a client.

https://github.com/spacewalkproject/spacewalk/wiki/RegisteringClients

Unfortunately there was no hint that you have to start the rhnsd service.
So I have started the service now and configured it to start automatically.
And I need no osad at the moment. Every 4 hours check in is fine for me.

Thanks again,

Warm regards,

Harald






Von: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>mailto:spacewalk-list-boun...@redhat.com>>
 Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>
Gesendet: Donnerstag, 14. Februar 2019 10:01
An: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Betreff: Re: [Spacewalk-list] Spa

Re: [Spacewalk-list] centos mirror and setup in spacewalk

[p.cook...@bham.ac.uk]

Hi Vyas

Not sure which versions you're using but you could try the following:

CentOS7-base:  http://mirror.centos.org/centos/7/os/x86_64/
CentOS7-updates:   http://mirror.centos.org/centos/7/updates/x86_64/
CentOS7-extras:   http://mirror.centos.org/centos/7/extras/x86_64/

CentOS6-base:  http://mirror.centos.org/centos/6/os/x86_64/
CentOS6-updates:   http://mirror.centos.org/centos/6/updates/x86_64/
CentOS6-extras:   http://mirror.centos.org/centos/6/extras/x86_64/

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of vyas.devagu...@inova.org
Sent: 21 February 2019 19:44
To: spacewalk-list@redhat.com
Cc: spacewalk-list-boun...@redhat.com
Subject: [Spacewalk-list] centos mirror and setup in spacewalk

HI ,

Do any one have the centos mirror list to setup In spacewalk server .



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

Re: [Spacewalk-list] Registration to the new server via rhnreg_ks returns an SSL error

[p.cook...@bham.ac.uk]

Whether you re-installed the Spacewalk application on the same server or a 
different one, a new certificate should have been produced after running 
"spacewalk-setup."

Subsequently, the certificate can be viewed on the server:

cat /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT

OR

WebUI -> Systems (Top Menu) -> Kickstart (Left Menu) -> GPG and SSL Keys -> 
RHN-ORG-TRUSTED-SSL-CERT -> Key contents

If everything has been done correctly, to register the client, the certificate 
can be viewed on there too:

cat /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

If they don't match, you'll have a problem!

Like Robert says, it seems to be "just" a SSL issue really but, obviously, the 
certificate is being generated by the Spacewalk application installation.

Regards
Phil

-Original Message-
From: robert.pasche...@web.de  
Sent: 28 February 2019 16:47
To: spacewalk-list@redhat.com; Philip Cookson (IT Services) 
; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Registration to the new server via rhnreg_ks 
returns an SSL error

Am 28. Februar 2019 11:10:57 MEZ schrieb "p.cook...@bham.ac.uk" 
:
>Obviously, that will work but you won’t be using the secure layer or 
>addressing the underlying problem!
>
>If you’re getting the same problem with a new client system I can see 
>how you may think it’s a server related issue. However, the Spacewalk 
>certificate is generated during installation so it would be un-usual, I 
>would have thought?
>
>Did you add the certificate to the database (certutil -d 
>sql:/etc/pki/nssdb -An RHN-ORG-TRUSTED-SSL-CERT -t C,, -ai 
>/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT), too, as you only mention 
>getting the rpm (rpm -Uvh 
>http://spacewalk-server/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm)?
>
>Regards
>Phil
>
>From: spacewalk-list-boun...@redhat.com 
> On Behalf Of 
>rui.a.z...@nokia-sbell.com
>Sent: 28 February 2019 09:51
>To: spacewalk-list@redhat.com
>Cc: Zhu, Ting (NSB - CN/Shanghai) 
>Subject: Re: [Spacewalk-list] Registration to the new server via 
>rhnreg_ks returns an SSL error
>
>
>I think this may not the problem of the client, when I try to add new 
>client server it also has the error: The SSL certificate failed 
>verification.
>I find this help, change the
>--serverUrl=https://spacewalk-server/XMLRPC to 
>--serverUrl=http://spacewalk-server/XMLRPC.  The system can be 
>registerd,  The reason maybe:
>
>*   System did not have the correct SSL certificate.(I check, server
>and client have the same sslCACert)
>  *   SSL certificate was corrupted.(how to explain this?)

This is just a standard SSL issue. Nothing special with spacewalk.

If you're connecting to https://spacewalk-server/, "spacewalk-server" has to be 
included within the SSL certificate. And if that is missing, the certificate 
may be valid but you still get the verification error .

Robert

>
>
>From:
>spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-bounces@redhat.
>com> [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of 
>p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>
>Sent: 2019年2月28日 17:35
>To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
>Subject: Re: [Spacewalk-list] Registration to the new server via 
>rhnreg_ks returns an SSL error
>
>Hi
>
>It’s a little more involved than that! I produced these notes, for 
>myself, when un-registering a system from a Dev Spacewalk Server and 
>registering it with a Test Spacewalk Server. It’s effectively the same 
>thing that you need to do though.
>
>
>Spacewalk does not provide an option to un-register a client system 
>(similar to registering - “rhnreg_ks”) - the only option is to remove 
>the client system’s profile from the Spacewalk server.
>
>To remove a client’s profile from the Spacewalk server perform these
>steps:
>
>
>  1.  Log in to the Spacewalk Console.
>2.  Click on the Systems tab in the top navigation bar and then click 
>on the name of the system which you want to remove from the Systems 
>List.
>  3.  Click the Delete System link in the top-right corner of the page.
>4.  Confirm system profile deletion by clicking the Delete Profile 
>button.
>5.  Now go to the client system and execute below command to remove the 
>associated System ID file:
>
># rm /etc/sysconfig/rhn/systemid
>
>In addition, remove Spacewalk certificate for Development and add 
>certificate for Test. Then register client system with Test Spacewalk
>server:
>
># certutil -d sql:/etc/pki/nssdb -Dn RHN-ORG-TRUSTED-SSL-CERT -t C,, 
>-ai /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
># rpm -ev rhn-org-trusted-ssl-cert-1.0-1.noarch
># rpm -Uvh https://https://%3cTest>
>Server>/pub/rhn-org-trusted-ss

Re: [Spacewalk-list] Registration to the new server via rhnreg_ks returns an SSL error

[p.cook...@bham.ac.uk]

Hi

It's a little more involved than that! I produced these notes, for myself, when 
un-registering a system from a Dev Spacewalk Server and registering it with a 
Test Spacewalk Server. It's effectively the same thing that you need to do 
though.


Spacewalk does not provide an option to un-register a client system (similar to 
registering - "rhnreg_ks") - the only option is to remove the client system's 
profile from the Spacewalk server.

To remove a client's profile from the Spacewalk server perform these steps:


1.   Log in to the Spacewalk Console.

2.   Click on the Systems tab in the top navigation bar and then click on 
the name of the system which you want to remove from the Systems List.

3.   Click the Delete System link in the top-right corner of the page.

4.   Confirm system profile deletion by clicking the Delete Profile button.

5.   Now go to the client system and execute below command to remove the 
associated System ID file:

# rm /etc/sysconfig/rhn/systemid

In addition, remove Spacewalk certificate for Development and add certificate 
for Test. Then register client system with Test Spacewalk server:

# certutil -d sql:/etc/pki/nssdb -Dn RHN-ORG-TRUSTED-SSL-CERT -t C,, -ai 
/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
# rpm -ev rhn-org-trusted-ssl-cert-1.0-1.noarch
# rpm -Uvh https:///pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
# certutil -d sql:/etc/pki/nssdb -An RHN-ORG-TRUSTED-SSL-CERT -t C,, -ai 
/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
# rhnreg_ks --serverUrl=https:///XMLRPC 
--sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=[ACTIVATION 
KEY]


Note, if you're using OSAD, the service may have stopped during this process 
and therefore, will need to be re-started. I've also found that, even if it's 
still running, I've had to restart it before actions were automatically picked 
up again:

# systemctl start osad OR service osad start


Hope this is of help?

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of rui.a.z...@nokia-sbell.com
Sent: 28 February 2019 08:57
To: spacewalk-list@redhat.com
Cc: Zhu, Ting (NSB - CN/Shanghai) 
Subject: [Spacewalk-list] Registration to the new server via rhnreg_ks returns 
an SSL error

I re-installed the spacewalk server, and the client can not register to the new 
installed server.

[root@FNSHB109 rhn]# rpm -e rhn-org-trusted-ssl-cert-1.0-1.noarch

[root@FNSHB109 rhn]# rpm -Uvh 
http://spacewalk-server/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
Retrieving http://spacewalk-server/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
Preparing...  # [100%]
Updating / installing...
   1:rhn-org-trusted-ssl-cert-1.0-1   # [100%]

[root@FNSHB109 rhn]# rhnreg_ks --serverUrl=https://spacewalk-server/XMLRPC 
--sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=1-centos7.6 
--force --verbose
D: rpcServer: Calling XMLRPC registration.welcome_message
An error has occurred:
The SSL certificate failed verification.
See /var/log/up2date for more information

[root@FNSHB109 rhn]# cat /etc/sysconfig/rhn/up2date |grep share
sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

[Thu Feb 28 16:53:34 2019] up2date D: rpcServer: Calling XMLRPC 
registration.welcome_message
[Thu Feb 28 16:53:34 2019] up2date
Traceback (most recent call last):
  File "/usr/sbin/rhnreg_ks", line 215, in 
cli.run()
  File "/usr/lib/python2.7/site-packages/up2date_client/rhncli.py", line 94, in 
run
sys.exit(self.main() or 0)
  File "/usr/sbin/rhnreg_ks", line 93, in main
rhnreg.getCaps()
  File "/usr/lib/python2.7/site-packages/up2date_client/rhnreg.py", line 264, 
in getCaps
s.capabilities.validate()
  File "/usr/lib/python2.7/site-packages/up2date_client/rhnserver.py", line 
185, in __get_capabilities
self.registration.welcome_message()
  File "/usr/lib/python2.7/site-packages/up2date_client/rhnserver.py", line 84, 
in __call__
raise_with_tb(up2dateErrors.SSLCertificateVerifyFailedError())
  File "/usr/lib/python2.7/site-packages/up2date_client/rhnserver.py", line 67, 
in __call__
return rpcServer.doCall(method, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/up2date_client/rpcServer.py", line 
214, in doCall
ret = method(*args, **kwargs)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__
return self.__send(self.__name, args)
  File "/usr/lib/python2.7/site-packages/up2date_client/rpcServer.py", line 48, 
in _request1
ret = self._request(methodname, params)
  File "/usr/lib/python2.7/site-packages/rhn/rpclib.py", line 394, in _request
self._handler, request, verbose=self._verbose)
  File "/usr/lib/python2.7/site-packages/rhn/transports.py", line 177, in 
request
headers, fd = req.send_http(host, handler)
  File "/usr/lib/python2.7/site-packages/rhn/transports.py", line 733, in 
send_http
self._connection.request(self.method, 

Re: [Spacewalk-list] Really slow unresponsive GUI

[p.cook...@bham.ac.uk]

Just checking, did you re-start the Taskomatic service after changing the 
setting too?

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of caig...@cines.fr
Sent: 08 March 2019 15:56
To: spacewalk-list 
Subject: Re: [Spacewalk-list] Really slow unresponsive GUI

Hi Phil,

thank for your help. No error about java heap space, but tried to configure 
taskomatic memory like you said without success.

I setup the kickstart part long time ago, just using satellite redhat doc.

- Mail original -
De: "P Cookson" 
À: "spacewalk-list" 
Envoyé: Vendredi 8 Mars 2019 16:43:23
Objet: Re: [Spacewalk-list] Really slow unresponsive GUI

Hi Lionel

Have you looked in /var/log/rhn/rhn_taskomatic_daemon.log too? After seeing 
"java.lang.OutOfMemoryError: Java heap space" messages, in there, I changed 
config for Taskomatic but not sure if this is relevant for you?

Current maxmemory (Xmx) can be seen by checking status of Taskomatic:

# systemctl status taskomatic.service

I increased from 256 to 4096:

# grep taskomatic.java.maxmemory /etc/rhn/rhn.conf
taskomatic.java.maxmemory=4096
#

Then re-started Spacewalk:

# spacewalk-service restart

Also, I've noted you've said something about using Kickstart. After patching 
for some time I need to start looking at provisioning, too, so if you have any 
notes/links about setup that would be useful.


Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of caig...@cines.fr
Sent: 08 March 2019 14:59
To: spacewalk-list 
Subject: [Spacewalk-list] Really slow unresponsive GUI

Hi,

i'm writing here because i've a strange behaviour with no clue on how to 
resolve it. 
There is no load on CPU, ram is mostly free, no IO wait, no processus stuck a 
100%. In log file (tomcat/postresql,...) nothing about error or warning.
No recent modification on the system.

When i want to access spacewalk web interface (or API) this one sometimes 
answer after a very long time, and sometimes get error 500. Same behaviour with 
the spacecmd cli command.

I really don't understand because i've another spacewalk on another server and 
this one work like a charm.

My setup : VM with 2vpcu 8Gb RAM near 200 clients spacewalk 2.8, used only for 
patching and sometimes kickstart new server.
 JAVA_OPTS -Xms2048m -Xmx2048m, tried with 4096 but no difference.

I don't know which log to put here due to the fact i found no error trace.

For now the only solution I imagine is to backup and restore to a new server 
freshly installed my spacewalk.

Thank you for help.

--
Lionel Caignec 

Centre Informatique National de l' Enseignement Supérieur 
950 rue de Saint Priest 
34097 MONTPELLIER Cedex 5 
Tel : (33) 04 67 14 14 14
Fax : (33)04 67 52 37 63 
https://www.cines.fr

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

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

Re: [Spacewalk-list] Really slow unresponsive GUI

[p.cook...@bham.ac.uk]

Hi Lionel

Have you looked in /var/log/rhn/rhn_taskomatic_daemon.log too? After seeing 
"java.lang.OutOfMemoryError: Java heap space" messages, in there, I changed 
config for Taskomatic but not sure if this is relevant for you?

Current maxmemory (Xmx) can be seen by checking status of Taskomatic:

# systemctl status taskomatic.service

I increased from 256 to 4096:

# grep taskomatic.java.maxmemory /etc/rhn/rhn.conf
taskomatic.java.maxmemory=4096
#

Then re-started Spacewalk:

# spacewalk-service restart

Also, I've noted you've said something about using Kickstart. After patching 
for some time I need to start looking at provisioning, too, so if you have any 
notes/links about setup that would be useful.


Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of caig...@cines.fr
Sent: 08 March 2019 14:59
To: spacewalk-list 
Subject: [Spacewalk-list] Really slow unresponsive GUI

Hi,

i'm writing here because i've a strange behaviour with no clue on how to 
resolve it. 
There is no load on CPU, ram is mostly free, no IO wait, no processus stuck a 
100%. In log file (tomcat/postresql,...) nothing about error or warning.
No recent modification on the system.

When i want to access spacewalk web interface (or API) this one sometimes 
answer after a very long time, and sometimes get error 500. Same behaviour with 
the spacecmd cli command.

I really don't understand because i've another spacewalk on another server and 
this one work like a charm.

My setup : VM with 2vpcu 8Gb RAM near 200 clients spacewalk 2.8, used only for 
patching and sometimes kickstart new server.
 JAVA_OPTS -Xms2048m -Xmx2048m, tried with 4096 but no difference.

I don't know which log to put here due to the fact i found no error trace.

For now the only solution I imagine is to backup and restore to a new server 
freshly installed my spacewalk.

Thank you for help.

--
Lionel Caignec 

Centre Informatique National de l' Enseignement Supérieur 
950 rue de Saint Priest 
34097 MONTPELLIER Cedex 5 
Tel : (33) 04 67 14 14 14
Fax : (33)04 67 52 37 63 
https://www.cines.fr

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

[Spacewalk-list] FW: List of patched/to patched systems by commandline

[p.cook...@bham.ac.uk]

Hi Matthias

I’ve come across a “spacecmd” report called “report_outofdatesystems” which may 
be of interest to you as it produces a very simple list of systems with the 
number of outstanding patches?

spacecmd {SSM:0}> report_outofdatesystems
System   Packages
--
server 19
server 22
server 3590
server 4592
spacecmd {SSM:0}>

Regards
Phil

From: Philip Cookson (IT Services)
Sent: 12 February 2019 15:27
To: 'spacewalk-list@redhat.com' 
Subject: RE: [Spacewalk-list] List of patched/to patched systems by commandline

Hi Matthias

Have you looked at the standard Spacewalk reports or “spacecmd” command at all?

The “spacewalk-report” tool outputs information in a CSV format.

The related package needs to be installed from the Spacewalk repository:

# yum -y install spacewalk-reports

The man page for spacewalk-report is in the usual format and there is also an 
option "--list-fields-info" that is helpful:

# spacewalk-report --list-fields

See report descriptions below – the “system-currency” report might be useful 
for what you’re after?
· channel-packages - Packages in channels
· channels - Channel report
· custom-info - Display system custom info
· entitlements - Entitlement and channel list and usage
· errata-channels - List of errata in channels
· errata-list - Errata information based upon compliance checks against 
systems
· errata-list-all - List of all erratas
· errata-systems - Listing of each errata applicable to each affected 
system
· inactive-systems - Inactive systems in Satellite
· inventory - Inventory report
· kickstartable-trees - List of kickstartable trees
· packages-updates-all - List of packages that can be upgraded
· packages-updates-newest - List of packages that can be upgraded
· scap-scan - Results of OpenSCAP xccdf evaluation
· scap-scan-results - Results of OpenSCAP xccdf evaluation
· system-crash-count - Crash count for systems
· system-crash-details - Crash details for systems
· system-currency - System currency list
· system-groups - System groups in Satellite
· system-groups-keys - Activation keys for system groups
· system-groups-systems - Systems in system groups
· system-groups-users - System groups users report
· system-history - System event history
· system-history-channels - Channel event history
· system-history-configuration - Configuration event history
· system-history-entitlements - System entitlement event history
· system-history-errata - Errata event history
· system-history-kickstart - Kickstart event history
· system-history-packages - Package event history
· system-history-scap - OpenSCAP event history
· system-packages-installed - Packages installed on systems
· users - Users in the system
· users-systems - Systems administered by individual users

The output could be piped through awk to get just the columns of info you’re 
interested in perhaps - see example command below:

# spacewalk-report inventory | awk -F"," '{print $4, $3, $8}' > 
inventory.csv

The “spacecmd” tool is also available from the Spacewalk repository and can be 
installed on a system other than the Spacewalk server to execute reporting 
queries and other commands remotely.

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of mgru...@metzler.com
Sent: 12 February 2019 14:56
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] List of patched/to patched systems by commandline

Hi!

I am seeking for a way to determine via commandline or SQL-select, which 
systems are patched (no patches to apply) and which ones needed  to be patched.

I have used system_listerrata with a SSM, but the output is. well a little bit 
verbose, the Hostname would be enough

Does anyone have some hint or trick for me, to get that done?

cheers
Matthias


METZLER
Informationstechnologie

Matthias Gruber
IT-Infrastruktur & -Betrieb

B. Metzler seel. Sohn & Co.
Kommanditgesellschaft auf Aktien
Untermainanlage 1
60329 Frankfurt am Main
Telefon (0 69) 21 04 - 43 30
Telefax (0 69) 21 04 - 40 40
mgru...@metzler.com
www.metzler.com


Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich von 
Metzler, Emmerich Müller, Gerhard Wiesheu
Vorsitzender des Aufsichtsrats: Dr. Christoph Schücking
Sitz der Gesellschaft: Frankfurt am Main, 

Re: [Spacewalk-list] List of patched/to patched systems by commandline

[p.cook...@bham.ac.uk]

Hi Matthias

Have you looked at the standard Spacewalk reports or “spacecmd” command at all?

The “spacewalk-report” tool outputs information in a CSV format.

The related package needs to be installed from the Spacewalk repository:

# yum -y install spacewalk-reports

The man page for spacewalk-report is in the usual format and there is also an 
option "--list-fields-info" that is helpful:

# spacewalk-report --list-fields

See report descriptions below – the “system-currency” report might be useful 
for what you’re after?
· channel-packages - Packages in channels
· channels - Channel report
· custom-info - Display system custom info
· entitlements - Entitlement and channel list and usage
· errata-channels - List of errata in channels
· errata-list - Errata information based upon compliance checks against 
systems
· errata-list-all - List of all erratas
· errata-systems - Listing of each errata applicable to each affected 
system
· inactive-systems - Inactive systems in Satellite
· inventory - Inventory report
· kickstartable-trees - List of kickstartable trees
· packages-updates-all - List of packages that can be upgraded
· packages-updates-newest - List of packages that can be upgraded
· scap-scan - Results of OpenSCAP xccdf evaluation
· scap-scan-results - Results of OpenSCAP xccdf evaluation
· system-crash-count - Crash count for systems
· system-crash-details - Crash details for systems
· system-currency - System currency list
· system-groups - System groups in Satellite
· system-groups-keys - Activation keys for system groups
· system-groups-systems - Systems in system groups
· system-groups-users - System groups users report
· system-history - System event history
· system-history-channels - Channel event history
· system-history-configuration - Configuration event history
· system-history-entitlements - System entitlement event history
· system-history-errata - Errata event history
· system-history-kickstart - Kickstart event history
· system-history-packages - Package event history
· system-history-scap - OpenSCAP event history
· system-packages-installed - Packages installed on systems
· users - Users in the system
· users-systems - Systems administered by individual users

The output could be piped through awk to get just the columns of info you’re 
interested in perhaps - see example command below:

# spacewalk-report inventory | awk -F"," '{print $4, $3, $8}' > 
inventory.csv

The “spacecmd” tool is also available from the Spacewalk repository and can be 
installed on a system other than the Spacewalk server to execute reporting 
queries and other commands remotely.

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mgru...@metzler.com
Sent: 12 February 2019 14:56
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] List of patched/to patched systems by commandline

Hi!

I am seeking for a way to determine via commandline or SQL-select, which 
systems are patched (no patches to apply) and which ones needed  to be patched.

I have used system_listerrata with a SSM, but the output is. well a little bit 
verbose, the Hostname would be enough

Does anyone have some hint or trick for me, to get that done?

cheers
Matthias


METZLER
Informationstechnologie

Matthias Gruber
IT-Infrastruktur & -Betrieb

B. Metzler seel. Sohn & Co.
Kommanditgesellschaft auf Aktien
Untermainanlage 1
60329 Frankfurt am Main
Telefon (0 69) 21 04 - 43 30
Telefax (0 69) 21 04 - 40 40
mgru...@metzler.com
www.metzler.com


Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich von 
Metzler, Emmerich Müller, Gerhard Wiesheu
Vorsitzender des Aufsichtsrats: Dr. Christoph Schücking
Sitz der Gesellschaft: Frankfurt am Main, Handelsregister-Nr. HRB 27 515

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfänger 
sein, so bitten wir Sie höflich, dies unverzüglich dem Absender mitzuteilen und 
die Nachricht zu löschen. Es ist unzulässig, die Nachricht unbefugt 
weiterzuleiten oder zu kopieren. Da wir nicht die Echtheit oder Vollständigkeit 
der in dieser Nachricht enthaltenen Informationen garantieren oder zusichern 
können, sind die vorstehenden Ausführungen rechtlich nicht bindend. Eine 
Haftung hierfür wird ausgeschlossen.
This message is confidential. If you are not the intended recipient, we kindly 
ask you to inform the sender and delete the information. Any unauthorised 
dissemination or copying hereof is prohibited. As we cannot guarantee or assure 
the genuineness or completeness of the information contained in this message, 
the statements set forth above are 

Re: [Spacewalk-list] remote command responses are really slow

[p.cook...@bham.ac.uk]

Hi

This MAY be due to a similar issue someone has reported with systems going 
offline. Are you using OSAD? If so, my personal notes, below, may help to 
identify your problem. If everything has been done correctly it may be an 
infrastructure problem though ie un-reliable network connection or NTP?

By default, the rhnsd daemon on a client system connects to the Spacewalk 
server every four hours (see /etc/sysconfig/rhn/rhnsd) and performs any updates 
or actions that have been scheduled. If you install the OSA daemon, you can 
apply updates and actions to client systems immediately from the Spacewalk 
server.

osa-dispatcher
Server-side service that determines when an osad client instance needs to be 
pinged or run rhn_check and sends a message telling them to do so. This is 
installed when Spacewalk is installed.

Open Source Architecture Daemon (OSAD)
Client-side service that responds to pings and runs rhn_check when told to by 
osa-dispatcher.

See official documentation, at the following link, for more details:

https://github.com/spacewalkproject/spacewalk/wiki/OSADSetup

Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client

Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all

Spacewalk Actions Control - Show Status
# rhn-actions-control --report

Start OSAD
# systemctl start osad.service OR service osad start

Enable OSAD
# systemctl enable osad.service OR chkconfig osad on

OSAD Log File
/var/log/osad


Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of oogiej...@yahoo.com
Sent: 13 February 2019 17:08
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] remote command responses are really slow

We previously ran Spacewalk 2.4 and early on, we were able to run remote 
commands to our registered servers and they pretty much responded right away.  
After a while we got to the point where almost none of the servers would 
respond to remote commands.  We now have spacewalk 2.7 running and I'm trying 
remote commands again, and they are still extremely slow to respond.  Just a 
simple command like hostname, sent out to 60 servers.  Only 12 responses so far 
after 30 minutes, the rest haven't failed they are still trying.  Any idea what 
would cause this slowdown or how to correct it?  We have a total of 430 servers 
registered in our environment.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

[p.cook...@bham.ac.uk]

Hi Harald

Were they ok originally, and stopped working properly, or are you just trying 
to setup OSAD for the first time? Either way if you work through my personal 
notes (for OSAD), below, it may help to identify your problem. If everything 
has been done correctly it may be an infrastructure problem though ie 
un-reliable network connection or NTP?

By default, the rhnsd daemon on a client system connects to the Spacewalk 
server every four hours (see /etc/sysconfig/rhn/rhnsd) and performs any updates 
or actions that have been scheduled. If you install the OSA daemon, you can 
apply updates and actions to client systems immediately from the Spacewalk 
server.

osa-dispatcher
Server-side service that determines when an osad client instance needs to be 
pinged or run rhn_check and sends a message telling them to do so. This is 
installed when Spacewalk is installed.

Open Source Architecture Daemon (OSAD)
Client-side service that responds to pings and runs rhn_check when told to by 
osa-dispatcher.

See official documentation, at the following link, for more details:

https://github.com/spacewalkproject/spacewalk/wiki/OSADSetup

Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client

Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all

Spacewalk Actions Control - Show Status
# rhn-actions-control --report

Start OSAD
# systemctl start osad.service OR service osad start

Enable OSAD
# systemctl enable osad.service OR chkconfig osad on

OSAD Log File
/var/log/osad


Hope this is of help
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of harald.wacha...@akm.at
Sent: 14 February 2019 08:22
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi, Jonathan,

Looks good:

[root@vie-srv-log02 ~]# netstat -tn|grep 5222
tcp0  0 172.21.0.181:46018  172.21.0.166:5222   ESTABLISHED


Nerveless the client is offline in spacewalk.

Warm regards,

Harald


Von: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
Im Auftrag von Jonathan Horne
Gesendet: Mittwoch, 13. Februar 2019 21:48
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients


all your clients should have established traffic to the spacewalk server on 
port 5222.  it should stay in an established state.


[jhorne@dlp-log01 ~]$ netstat -tn|grep 5222
tcp0  0 10.12.59.52:38718  10.12.59.64:5222   ESTABLISHED


From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Wachauer Harald 
mailto:harald.wacha...@akm.at>>
Sent: Wednesday, February 13, 2019 10:17:45 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi  all,

I have the problem that most of my systems (CentOS 6 & 7) are going offline 
after approximately one day.
Only if I run rhn_check the systems come online again, but only for short time.

I have tried to install osad service, the service is running but nerveless the 
client is going offline.

Any help would be very appreciated.


Best regards,

Harald






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

Re: [Spacewalk-list] Sequences going wrong

[p.cook...@bham.ac.uk]

Hi Thomas

The "Internal Server Error" appears to be a really generic and un-helpful 
message that comes out of Spacewalk in all sorts of scenario's! I haven't 
experienced your particular problem but, in the past, I've been advised to look 
at " /var/log/tomcat/catalina.out" to try and get a better idea of what the 
issue is. Don't know if this will help on this occasion?

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of tschwei...@gmail.com
Sent: 14 February 2019 10:31
To: spacewalk 
Subject: [Spacewalk-list] Sequences going wrong

Hi!

We're having a lot of troubble with spacewalk loosing sequences, or
better: loosing sync within sequences. As spacewalk runs all looks ok for some 
time. then you may get "Internal server error" at a variety of places. Mostly 
it starts showing up in "Schedule -> Actions" click on one of the numbers 
behind in columns Finished, Failed, Pending.
Instead of showing me details on where the action hav finished, failed or is 
pending I am prompted with "Internal server error".

Looking into the sql-logs I can find sequences out of sync. Fixing these 
manually makes it work again -- for some time. I do not have any idea why these 
sequences starting to get out of sync. Any idea? Bug?

Spacewalk 2.9
OS: CentOS 7

--
Thomas

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

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

Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

[p.cook...@bham.ac.uk]

No problem Harald. If you want to continue using rhnsd you can still reduce the 
check-in time in /etc/sysconfig/rhn/rhnsd if you want though (default is 240 
mins):

# cat /etc/sysconfig/rhn/rhnsd
INTERVAL=240
#

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of harald.wacha...@akm.at
Sent: 14 February 2019 11:18
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi Phil,

Thanks for your reply.
It looks like it was a rookie mistake.
I am new at Spacewalk and I followed the instructions here to register a client.

https://github.com/spacewalkproject/spacewalk/wiki/RegisteringClients

Unfortunately there was no hint that you have to start the rhnsd service.
So I have started the service now and configured it to start automatically.
And I need no osad at the moment. Every 4 hours check in is fine for me.

Thanks again,

Warm regards,

Harald






Von: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>
Gesendet: Donnerstag, 14. Februar 2019 10:01
An: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi Harald

Were they ok originally, and stopped working properly, or are you just trying 
to setup OSAD for the first time? Either way if you work through my personal 
notes (for OSAD), below, it may help to identify your problem. If everything 
has been done correctly it may be an infrastructure problem though ie 
un-reliable network connection or NTP?

By default, the rhnsd daemon on a client system connects to the Spacewalk 
server every four hours (see /etc/sysconfig/rhn/rhnsd) and performs any updates 
or actions that have been scheduled. If you install the OSA daemon, you can 
apply updates and actions to client systems immediately from the Spacewalk 
server.

osa-dispatcher
Server-side service that determines when an osad client instance needs to be 
pinged or run rhn_check and sends a message telling them to do so. This is 
installed when Spacewalk is installed.

Open Source Architecture Daemon (OSAD)
Client-side service that responds to pings and runs rhn_check when told to by 
osa-dispatcher.

See official documentation, at the following link, for more details:

https://github.com/spacewalkproject/spacewalk/wiki/OSADSetup

Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client

Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all

Spacewalk Actions Control - Show Status
# rhn-actions-control --report

Start OSAD
# systemctl start osad.service OR service osad start

Enable OSAD
# systemctl enable osad.service OR chkconfig osad on

OSAD Log File
/var/log/osad


Hope this is of help
Phil

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of harald.wacha...@akm.at<mailto:harald.wacha...@akm.at>
Sent: 14 February 2019 08:22
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi, Jonathan,

Looks good:

[root@vie-srv-log02 ~]# netstat -tn|grep 5222
tcp0  0 172.21.0.181:46018  172.21.0.166:5222   ESTABLISHED


Nerveless the client is offline in spacewalk.

Warm regards,

Harald


Von: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
Im Auftrag von Jonathan Horne
Gesendet: Mittwoch, 13. Februar 2019 21:48
An: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients


all your clients should have established traffic to the spacewalk server on 
port 5222.  it should stay in an established state.


[jhorne@dlp-log01 ~]$ netstat -tn|grep 5222
tcp0  0 10.12.59.52:38718  10.12.59.64:5222   ESTABLISHED


From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Wachauer Harald 
mailto:harald.wacha...@akm.at>>
Sent: Wednesday, February 13, 2019 10:17:45 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi  all,

I have the problem that most of my systems (CentOS 6 & 7) are going offline 
after approximately one day.
Only if I run rhn_check the systems come online again, but only for short time.

I have tried to install osad service, the service is running but nerveless the 
client is going offline.

Any help would be very appreciated.


Best regards,

Harald






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

Re: [Spacewalk-list] specific repo to a server with kickstart

[p.cook...@bham.ac.uk]

Hi Jérôme

If I understand your question right, you could make the additional repo a Child 
repo of the Parent repo the Activation Key is associated with. Alternatively, 
you could create a separate repo with its own Activation Key. The system you're 
provisioning could then be registered with 2 Activation Keys (channels/repo's) 
perhaps?

If this isn't something you're going to do very often, obviously, you could 
just use Kickstart to provision the system then there isn't anything stopping 
you subscribing the system to the separate repo afterwards.

Regards
Phil


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of jerome.me...@lcsystems.ch
Sent: 06 February 2019 16:23
To: 'spacewalk-list@redhat.com' 
Subject: Re: [Spacewalk-list] specific repo to a server with kickstart

Hi Phil,

Thanks for your quick reply.
Yes, I'm using the Base Channel when a new server is creating with a Kickstart 
Script define on Spacewalk. In that way all is fine and desired packages are 
installed.

I didn't think that the problem is regarding the tree?

Now, for some specifics servers we need specifics repos for particular 
application. My question is : is it possible to insert this particular repo 
during a new kickstart installation? Hope that my question is more 
understandable?

Thanks and best regards,
Jérôme




From: 
spacewalk-list-boun...@redhat.com<mailto: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: Mittwoch, 6. Februar 2019 11:01
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] specific repo to a server with kickstart

Hi Jerome

I've been using Spacewalk to patch systems for a little while but only started 
to look in to provisioning with Spacewalk more recently.

However, if I understand your question properly, the Base Channel is set when 
creating a Kickstart Distribution. Subsequently, this is where the packages 
will come from for installation.

Note, unlike Satellite, Spacewalk does NOT make the OS disk structure 
(Kickstart Tree) required for installation - this needs to be performed as a 
separate task. The Tree Path, within Kickstart Distribution, should be set to 
whatever location you download these to.

As Spacewalk is utilising Kickstart/Koan and Cobbler, under the covers, I 
believe there'll be other ways of achieving the same thing, in an even more 
automated way, though.

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of jerome.me...@lcsystems.ch<mailto:jerome.me...@lcsystems.ch>
Sent: 06 February 2019 09:30
To: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Subject: [Spacewalk-list] specific repo to a server with kickstart

Hi everyone,

Does anyone have an idea if it is possible with kickstart (Spacewalk) to define 
once a specific repo on a server during his creation?

Thanks and best regards,
Jerome

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

Re: [Spacewalk-list] specific repo to a server with kickstart

[p.cook...@bham.ac.uk]

Hi Jerome

I've been using Spacewalk to patch systems for a little while but only started 
to look in to provisioning with Spacewalk more recently.

However, if I understand your question properly, the Base Channel is set when 
creating a Kickstart Distribution. Subsequently, this is where the packages 
will come from for installation.

Note, unlike Satellite, Spacewalk does NOT make the OS disk structure 
(Kickstart Tree) required for installation - this needs to be performed as a 
separate task. The Tree Path, within Kickstart Distribution, should be set to 
whatever location you download these to.

As Spacewalk is utilising Kickstart/Koan and Cobbler, under the covers, I 
believe there'll be other ways of achieving the same thing, in an even more 
automated way, though.

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of jerome.me...@lcsystems.ch
Sent: 06 February 2019 09:30
To: 'spacewalk-list@redhat.com' 
Subject: [Spacewalk-list] specific repo to a server with kickstart

Hi everyone,

Does anyone have an idea if it is possible with kickstart (Spacewalk) to define 
once a specific repo on a server during his creation?

Thanks and best regards,
Jerome

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

Re: [Spacewalk-list] Clients YUM Repos Not Being Updated

[p.cook...@bham.ac.uk]

Hi Matt

There’s a utility called “spacewalk-hostname-rename” for that! It’s part of the 
“spacewalk-utils” package available from the Spacewalk repo. The details in the 
link below may help you identify what bit hasn’t been done, yet, or the utility 
may still work for you?

https://github.com/spacewalkproject/spacewalk/wiki/SpacewalkHostnameRename


Regards

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of matt.die...@sony.com
Sent: 17 April 2019 18:47
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Clients YUM Repos Not Being Updated

I’m having a problem where after a client registers, there are no repos 
assigned to the client. This problem started after a hostname change on the 
spacewalk server itself. The clients checkin with no problems and update the 
database about itself, but it seems that it gets no info back from the server. 
I have been combing through logs. I was able to fix a problem with the jabber 
server and a couple of other things where the legacy hostname was still listed, 
but I’m a bit stuck at the moment.

Thanks!

Matt





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

Re: [Spacewalk-list] How to Replace Self-Signed SSL Certificate

[p.cook...@bham.ac.uk]

Thanks Avi, I should be trying it out next week.

Have a good weekend.

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of avi.mil...@oracle.com
Sent: 17 May 2019 15:44
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] How to Replace Self-Signed SSL Certificate

Hey Phil,

> On 17 May 2019, at 7:40 am, p.cook...@bham.ac.uk wrote:
> 
> Thanks Avi, I'd actually found the Oracle doco a short while ago too. 
> The consistency between the doco's gave me hope that they were a good 
> process to follow:-)

I wrote my Let’s Encrypt process based off the documentation I co-wrote with 
our amazing tech writers for the official process that’s published on 
docs.oracle.com so the consistency is by design. :)

If you do run into any issues or have any questions with that process, feel 
free to email me directly.

Cheers,
Avi

--
Avi Miller | Senior Manager | +61 (03) 8616-3496 Oracle Linux and VM Product 
Management
417 St Kilda Road, Melbourne VIC 3004 Australia


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

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

Re: [Spacewalk-list] How to Replace Self-Signed SSL Certificate

[p.cook...@bham.ac.uk]

Thanks Andreas, I’ll take a look.

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of andreas.dijk...@cygnis.nl
Sent: 17 May 2019 13:49
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] How to Replace Self-Signed SSL Certificate

Have a look at this blog-post: 
https://omg.dje.li/2017/04/using-lets-encrypt-ssl-certificates-with-spacewalk/

Not entirely accurate but almost the same. The procedure is the same. Hope it 
helps!

Andreas Dijkman

On 17 May 2019, at 13:09, p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> 
wrote:

Hello subscribers

I have Spacewalk 2.8 installed on a RHEL 7 server using the original 
self-signed SSL certificate. I need to replace this with a certificate from my 
organisation. Not sure if this can be done from the WebUI or needs to be 
command line but can someone provide a procedure please (haven’t been able to 
spot anything relevant for my setup online or in list, yet, but can’t help 
thinking many people would have wanted to do this)?

Regards

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

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

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

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

Re: [Spacewalk-list] How to Replace Self-Signed SSL Certificate

[p.cook...@bham.ac.uk]

Thanks Avi, I'd actually found the Oracle doco a short while ago too. The 
consistency between the doco's gave me hope that they were a good process to 
follow:-)

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of avi.mil...@oracle.com
Sent: 17 May 2019 15:13
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] How to Replace Self-Signed SSL Certificate

Hey Andreas,

> On 17 May 2019, at 5:48 am, Andreas Dijkman  wrote:
> 
> Have a look at this blog-post: 
> https://omg.dje.li/2017/04/using-lets-encrypt-ssl-certificates-with-sp
> acewalk/
> 
> Not entirely accurate but almost the same. The procedure is the same. Hope it 
> helps!

That’s my blog post, so please share what’s inaccurate about it. :) It was 
tested with Spacewalk 2.7, though so if something has changed with 2.8 and 2.9, 
I haven’t gotten around to installing those yet.

If you want more official documentation that doesn’t reference Let’s Encrypt, 
we’ve published the process here as well: 
https://docs.oracle.com/cd/E92593_01/E90682/html/sw22-replace-cert.html

Cheers,
Avi

--
Avi Miller | Senior Manager | +61 (03) 8616-3496 Oracle Linux and VM Product 
Management
417 St Kilda Road, Melbourne VIC 3004 Australia


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

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

[Spacewalk-list] How to Replace Self-Signed SSL Certificate

[p.cook...@bham.ac.uk]

Hello subscribers

I have Spacewalk 2.8 installed on a RHEL 7 server using the original 
self-signed SSL certificate. I need to replace this with a certificate from my 
organisation. Not sure if this can be done from the WebUI or needs to be 
command line but can someone provide a procedure please (haven't been able to 
spot anything relevant for my setup online or in list, yet, but can't help 
thinking many people would have wanted to do this)?

Regards

Philip Cookson
Linux Administrator
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

Re: [Spacewalk-list] Spacewalk-list Digest, Vol 133, Issue 9

[p.cook...@bham.ac.uk]

Hi Merphis

The “spacewalk-report” tool outputs information in a CSV format.

The related package needs to be installed from the Spacewalk repository:

# yum -y install spacewalk-reports  (note plural 
"s" on end)

The man page for spacewalk-report is in the usual format and there is also an 
option "--list-fields-info" that is helpful:

# spacewalk-report --list-fields

See report descriptions below – we find the “system-currency” report useful:

•   channel-packages - Packages in channels 
•   channels - Channel report 
•   custom-info - Display system custom info 
•   entitlements - Entitlement and channel list and usage 
•   errata-channels - List of errata in channels 
•   errata-list - Errata information based upon compliance checks against 
systems 
•   errata-list-all - List of all erratas 
•   errata-systems - Listing of each errata applicable to each affected 
system 
•   inactive-systems - Inactive systems in Satellite 
•   inventory - Inventory report 
•   kickstartable-trees - List of kickstartable trees 
•   packages-updates-all - List of packages that can be upgraded 
•   packages-updates-newest - List of packages that can be upgraded 
•   scap-scan - Results of OpenSCAP xccdf evaluation 
•   scap-scan-results - Results of OpenSCAP xccdf evaluation 
•   system-crash-count - Crash count for systems 
•   system-crash-details - Crash details for systems 
•   system-currency - System currency list 
•   system-groups - System groups in Satellite 
•   system-groups-keys - Activation keys for system groups 
•   system-groups-systems - Systems in system groups 
•   system-groups-users - System groups users report 
•   system-history - System event history 
•   system-history-channels - Channel event history 
•   system-history-configuration - Configuration event history 
•   system-history-entitlements - System entitlement event history 
•   system-history-errata - Errata event history 
•   system-history-kickstart - Kickstart event history 
•   system-history-packages - Package event history 
•   system-history-scap - OpenSCAP event history 
•   system-packages-installed - Packages installed on systems 
•   users - Users in the system 
•   users-systems - Systems administered by individual users 

The output could be piped through awk to get just the columns of info you’re 
interested in perhaps - see example command below:

# spacewalk-report inventory | awk -F"," '{print $4, $3, $8}' > 
inventory.csv

In addition, the “spacecmd” tool is also available from the Spacewalk 
repository and can be installed on a system other than the Spacewalk server to 
execute reporting queries and other commands remotely.

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mian...@gmail.com
Sent: 12 June 2019 20:08
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk-list Digest, Vol 133, Issue 9

It is not included by default, you'd have to install the "spacewalk-reports" 
package.

This provides approximately 51 reports (and you can easily extend those once 
you see what they are, located in /usr/share/spacewalk/reports/data ).

~Steven


On 6/12/19 12:11, Ellis, Merphis wrote:
> I do not see that program on my system I am running spacewalk 2.7
>
> -Original Message-
> From: spacewalk-list-boun...@redhat.com 
>  On Behalf Of 
> spacewalk-list-requ...@redhat.com
> Sent: Wednesday, June 12, 2019 12:01 PM
> To: spacewalk-list@redhat.com
> Subject: Spacewalk-list Digest, Vol 133, Issue 9
>
> Send Spacewalk-list mailing list submissions to 
> spacewalk-list@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-requ...@redhat.com
>
> You can reach the person managing the list at 
> spacewalk-list-ow...@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. Re: cvs report of packages (Michael Mraka)
>
>
> --
>
> Message: 1
> Date: Wed, 12 Jun 2019 15:55:04 +0200
> From: Michael Mraka 
> To: spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] cvs report of packages
> Message-ID: <20190612135504.gc4...@magni.brq.redhat.com>
> Content-Type: text/plain; charset=utf-8
>
> Ellis, Merphis:
>> I need to get a list of currently install packages on some systems.
>> I see I can get a list of the files that not the same with the compare 
>> function, but do not see how to get a list of what is installed on a base 
>> system.
> Hello Ellis,
>
> as root on spacewalk server run
>
>spacewalk-report system-packages-installed
>
>> Making 

Re: [Spacewalk-list] Oddball question about Spacewalk possibly corrupting yum update

[p.cook...@bham.ac.uk]

Hi Paul

I haven’t got any CentOS systems to patch, with Spacewalk, but a few thoughts…..

Not sure why you would start with 2.7 or sync from a local repo really? If you 
just didn’t want to go too bleeding edge with 2.9 I would at least start with 
2.8. In addition, I wouldn’t bother syncing from a local repo as you can go 
direct to the CentOS web repo’s which are kept up to date – see eg’s below:

http://mirror.centos.org/centos/7/os/x86_64/   #Base
http://mirror.centos.org/centos/7/extras/x86_64/   #Extras
http://mirror.centos.org/centos/7/updates/x86_64/   #Updates

You should find this combination will resolve any issues but, if not, you could 
sync the repo from the command line (using “reposync”) so you can watch it go 
through. However, there are repo sync logs in /var/log/rhn/reposync/ as well.

In addition, you could try manually updating a system from the command line 
(using “yum update”) and/or excluding  the X-Windows package you suspect (using 
“yum update -X ”), which may help you identify the problem too.

Unfortunately, Spacewalk does not provide an option to un-register a client 
system (similar to registering - “rhnreg_ks”) – the only option is to remove 
the client system’s profile from the Spacewalk server, then remove the 
/etc/sysconfig/rhn/systemid file etc on the client system.

Hope this is of help.

Regards
Phil





From: spacewalk-list-boun...@redhat.com  On 
Behalf Of paul.greene...@gmail.com
Sent: 19 June 2019 17:00
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Oddball question about Spacewalk possibly corrupting 
yum update

I built a Spacewalk 2.7 server for managing a couple hundred CentOS 6 
workstations, and synced it to a local yum repository.

After a few months I started adding some CentOS 7 systems to the mix, and also 
synced to the same local yum repository (same server, different path to the 
repositories, of course).

The Spacewalk server always seemed to have an issue getting a successful full 
sync with the CentOS 7 local repository after the 7.6 series came out. I wasn't 
concerned at first because the systems were configured to go to the local yum 
repository anyway (configured in /etc/yum.repos.d).

After the CentOS 7.6 series came out, I started having an issue with any 
machine that got the 7.6 updates where the system would freeze and lock up, 
requiring a hard reboot to get it usable again. That happened on at least a 
daily basis and sometimes multiple times a day. I rolled those users back to 
CentOS 7.5 to get them a functioning stable machine again, and didn't update 
anybody that was running 7.5. It seemed definitely related to X windows - I 
could still go to a command prompt with ctrl-alt-f2 and work from a command 
prompt, but X windows wouldn't come back without a hard reboot. On a couple of 
servers that didn't need X windows and had the run level set to 
multi-user.target, they didn't have an issue - it was only the workstations 
that needed X windows.

I have access to another yum repository independent of the Spacewalk server, 
and noticed if I updated a workstation to that repository and did NOT join the 
machine to the Spacewalk server, they all ran fine with CentOS 7.6. As long as 
I didn't join them to the Spacewalk server there were no issues. I tried 
deleting the CentOS 7 yum repository from the Spacewalk server, thinking maybe 
the yum repository on the Spacewalk server had gotten corrupted and was pushing 
out some bad files, but that didn't work.

The systems still seem to be looking to the Spacewalk server for updates, 
regardless of what is in /etc/yum.repos.d.

Hopefully someone else has seen something like this before. I would either like 
to remove any and all yum configurations from the Spacewalk server, if 
possible, and just point to the local yum repository for any kind of updates.

Barring that, I'm interested in updating to Spacewalk 2.9 anyway, and would 
build a new 2.9 server, migrate everything over to that, and leave out any yum 
repository configuration at all on that new server.

The CentOS 6 systems are fine - no issues at all with updates and/or yum 
repositories.

Thanks,

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

Re: [Spacewalk-list] Oddball question about Spacewalk possibly corrupting yum update

[p.cook...@bham.ac.uk]

May be I should have said, don’t use a local repo unless you really have to – 
and it seems like you do. There are clear benefits in having Spacewalk patching 
though – you get a clearer graphical view of the system’s patch status etc. May 
be you could push for an exception for web access controlled through something 
like Squid but, obviously, I don’t know what hurdles you face within your 
organisation.

As I suggested, running a manual “yum update” or checking out “yum history” may 
help you identify any problem in that area. Equally, tailing the sync log file, 
while syncing, or using “reposync” from the command line.

2.9 has been out since January and still the current version so, yes, I would 
say use that for any new build.

The systems will continue to look to Spacewalk for updates as a yum plugin etc 
is installed during registration. I’ve developed a procedure to un-register a 
system or re-register to a different Spacewalk server, for our environments, if 
you think that would be useful?

Re Scott’s comments, below, I’ve just began using Ansible AWX and starting to 
realise its benefits☺

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of scott.c.worthing...@gmail.com
Sent: 20 June 2019 15:08
To: spacewalk-list 
Subject: Re: [Spacewalk-list] Oddball question about Spacewalk possibly 
corrupting yum update

If you want to stick to your local yum repo, have you considered the following:

* For collecting hardware inventory and installed packages:
1.  https://github.com/fboender/ansible-cmdb

* Using Ansible for configuration management ("sending remote commands to big 
groups at once")?

And if you need a front end for Ansible, you could investigate:
1. https://wiki.jenkins.io/display/JENKINS/Ansible+Plugin
2. https://github.com/Batix/rundeck-ansible-plugin
3. https://github.com/ansible/awx


On Thu, Jun 20, 2019 at 8:29 AM Paul Greene 
mailto:paul.greene...@gmail.com>> wrote:
These systems are on a network that has no access to the internet - local repos 
are the only way to update them.
I have no idea which X package is causing trouble.
I never really wanted to use the Spacewalk server for patching in the first 
place. My local yum repository works just fine. I like using Spacewalk as a 
management tool - it's good at showing the hardware inventory, and for sending 
remote commands to big groups at once. There isn't enough time in the day to 
have to go out and touch 250 systems one by one for basic maintenance tasks.
Why do you call 2.9 "bleeding edge"? Hasn't it been out for awhile already?

On Thu, Jun 20, 2019 at 4:26 AM 
p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> 
mailto:p.cook...@bham.ac.uk>> wrote:
Hi Paul

I haven’t got any CentOS systems to patch, with Spacewalk, but a few thoughts…..

Not sure why you would start with 2.7 or sync from a local repo really? If you 
just didn’t want to go too bleeding edge with 2.9 I would at least start with 
2.8. In addition, I wouldn’t bother syncing from a local repo as you can go 
direct to the CentOS web repo’s which are kept up to date – see eg’s below:

http://mirror.centos.org/centos/7/os/x86_64/   #Base
http://mirror.centos.org/centos/7/extras/x86_64/   #Extras
http://mirror.centos.org/centos/7/updates/x86_64/   #Updates

You should find this combination will resolve any issues but, if not, you could 
sync the repo from the command line (using “reposync”) so you can watch it go 
through. However, there are repo sync logs in /var/log/rhn/reposync/ as well.

In addition, you could try manually updating a system from the command line 
(using “yum update”) and/or excluding  the X-Windows package you suspect (using 
“yum update -X ”), which may help you identify the problem too.

Unfortunately, Spacewalk does not provide an option to un-register a client 
system (similar to registering - “rhnreg_ks”) – the only option is to remove 
the client system’s profile from the Spacewalk server, then remove the 
/etc/sysconfig/rhn/systemid file etc on the client system.

Hope this is of help.

Regards
Phil





From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of paul.greene...@gmail.com<mailto:paul.greene...@gmail.com>
Sent: 19 June 2019 17:00
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] Oddball question about Spacewalk possibly corrupting 
yum update

I built a Spacewalk 2.7 server for managing a couple hundred CentOS 6 
workstations, and synced it to a local yum repository.

After a few months I started adding some CentOS 7 systems to the mix, and also 
synced to the same local yum repository (same server, different path to the 
repositories, of course).

The Spacewalk server always seemed to have an issue getting a successful full 
sync with the CentOS 7 local repository after the 7.6 series came out. I wasn't

[Spacewalk-list] Mail Notifications

[p.cook...@bham.ac.uk]

Good afternoon

I have Spacewalk 2.8 installed on a RHEL 7.6 system with Postfix configured to 
use our own mail relay. If I send an email test, from the command line, to my 
personal email box I receive the email straightaway. However, I'm not receiving 
email Notifications, from Spacewalk, even though they are checked in the Users' 
Preferences screen.

I can see the following type of errors in /var/log/maillog (hostname etc made 
anonymous):

May  2 14:34:50  postfix/smtp[45681]: 422EAE2C60: 
to=@, relay=[]:25, delay=409786, 
delays=409781/0.03/5/0.02, dsn=4.0.0, status=deferred (host relay=[] said: 451 Temporary local problem - please try later (in 
reply to RCPT TO command))

Is there some Spacewalk configuration that needs to be done to enable it to 
utilise Postfix perhaps? As an example I've seen some references to 
web.default_mail_from, in /etc/rhn/rhn.conf, but I'm not sure what it actually 
needs to be set to.

Regards

Philip Cookson
Linux Administrator
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

Re: [Spacewalk-list] Mail Notifications

[p.cook...@bham.ac.uk]

Hi Graeme

Thanks for your response.

If I send a test email the from address is 
root@hostname.domain<mailto:root@hostname.domain> and these appear in my inbox 
immediately.

The from address for the notification emails is 
dev-null@localhost.domain<mailto:dev-null@localhost.domain> and these just 
queue up.

I’ve tried setting the default_mail_from to either of the 2 from addresses, and 
re-started Spacewalk services, but it makes no difference.

However, I’ll check with owners of mail relay, as has been suggested separately.

Best regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Graeme Fowler
Sent: 02 May 2019 15:39
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Mail Notifications

The error message you detail looks to me very much like an Exim response, not 
Postfix; your system looks to be accepting the locally-generated mail but the 
mail relay is struggling with it.

If you’re not sending from a fully-qualified, verifiable sender address within 
your own institution’s email namespace(s) then you might well find the relay 
won’t accept the messages – although the 451 error implies that there’s 
something the relay can’t process rather than something it rejects on.

At Loughborough we set default_mail_from to be 
root@hostname.domain<mailto:root@hostname.domain> – so something like:

default_mail_from = 
r...@dev-spacewalk-instance.birmingham.ac.uk<mailto:r...@dev-spacewalk-instance.birmingham.ac.uk>

(noting that the hostname/domain must resolve in your DNS!)

Graeme

From: 
mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of "p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk>" 
mailto:p.cook...@bham.ac.uk>>
Reply-To: "spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>" 
mailto:spacewalk-list@redhat.com>>
Date: Thursday, 2 May 2019 at 15:19
To: "spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>" 
mailto:spacewalk-list@redhat.com>>
Subject: [Spacewalk-list] Mail Notifications

Good afternoon

I have Spacewalk 2.8 installed on a RHEL 7.6 system with Postfix configured to 
use our own mail relay. If I send an email test, from the command line, to my 
personal email box I receive the email straightaway. However, I’m not receiving 
email Notifications, from Spacewalk, even though they are checked in the Users’ 
Preferences screen.

I can see the following type of errors in /var/log/maillog (hostname etc made 
anonymous):

May  2 14:34:50  postfix/smtp[45681]: 422EAE2C60: 
to=@, relay=[]:25, delay=409786, 
delays=409781/0.03/5/0.02, dsn=4.0.0, status=deferred (host relay=[] said: 451 Temporary local problem - please try later (in 
reply to RCPT TO command))

Is there some Spacewalk configuration that needs to be done to enable it to 
utilise Postfix perhaps? As an example I’ve seen some references to 
web.default_mail_from, in /etc/rhn/rhn.conf, but I’m not sure what it actually 
needs to be set to.

Regards

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

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

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

Re: [Spacewalk-list] Mail Notifications

[p.cook...@bham.ac.uk]

Think this could have been (very) summarised as.

"If Spacewalk notification emails are appearing from dev-null@localhost.domain 
(and therefore queueing) and you would like the address to be a valid one for 
your organization, include the web.default_mail_from variable and appropriate 
value in /etc/rhn/rhn.conf"

Now done that and waiting to see if future notifications get through to me.

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of v...@spamcop.net
Sent: 03 May 2019 14:19
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Mail Notifications

On 03.05.19 10:58, p.cook...@bham.ac.uk wrote:
> The from address for the notification emails is 
> dev-null@localhost.domain <mailto:dev-null@localhost.domain> and these 
> just queue up.

The dev-null address is the default:

web.default_mail_from = Spacewalk 

> I’ve tried setting the default_mail_from to either of the 2 from 
> addresses, and re-started Spacewalk services, but it makes no difference.

What exactly is "no difference"? You don't write your exact configuration but 
only write about "default_mail_from" and not "web.default_mail_from". Thus:

Does it still use the dev-null address as from address

or

does it use the correct from address you have set but it's still not working?

Are you sure you have set the correct variable "web.default_mail_from"?

> However, I’ll check with owners of mail relay, as has been suggested 
> separately.

Well, sending mails with "localhost" as sender domain is generally not a good 
idea, unless it all stays local anyway...

Cheers,

Gerald


> 
> Best regards
> 
> Phil
> 
> *From:*spacewalk-list-boun...@redhat.com
>  *On Behalf Of *Graeme Fowler
> *Sent:* 02 May 2019 15:39
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] Mail Notifications
> 
> The error message you detail looks to me very much like an Exim 
> response, not Postfix; your system looks to be accepting the 
> locally-generated mail but the mail relay is struggling with it.
> 
> If you’re not sending from a fully-qualified, verifiable sender 
> address within your own institution’s email namespace(s) then you 
> might well find the relay won’t accept the messages – although the 451 
> error implies that there’s something the relay can’t process rather 
> than something it rejects on.
> 
> At Loughborough we set default_mail_from to be root@hostname.domain 
> <mailto:root@hostname.domain> – so something like:
> 
> default_mail_from = r...@dev-spacewalk-instance.birmingham.ac.uk
> <mailto:r...@dev-spacewalk-instance.birmingham.ac.uk>
> 
> (noting that the hostname/domain must resolve in your DNS!)
> 
> Graeme
> 
> *From: * <mailto:spacewalk-list-boun...@redhat.com>> on behalf of 
> "p.cook...@bham.ac.uk <mailto:p.cook...@bham.ac.uk>"
> mailto:p.cook...@bham.ac.uk>>
> *Reply-To: *"spacewalk-list@redhat.com 
> <mailto:spacewalk-list@redhat.com>"  <mailto:spacewalk-list@redhat.com>>
> *Date: *Thursday, 2 May 2019 at 15:19
> *To: *"spacewalk-list@redhat.com <mailto:spacewalk-list@redhat.com>" 
> mailto:spacewalk-list@redhat.com>>
> *Subject: *[Spacewalk-list] Mail Notifications
> 
> Good afternoon
> 
> I have *Spacewalk 2.8* installed on a *RHEL 7.6* system with *Postfix* 
> configured to use our *own mail relay*. If I send an email test, from 
> the command line, to my personal email box I receive the email 
> straightaway. However, I’m not receiving email Notifications, from 
> Spacewalk, even though they are checked in the Users’ Preferences screen.
> 
> I can see the following type of errors in */var/log/maillog* (hostname 
> etc made anonymous):
> 
> May  2 14:34:50  postfix/smtp[45681]: 422EAE2C60: 
> to=@, relay=[]:25, delay=409786, 
> delays=409781/0.03/5/0.02, dsn=4.0.0, status=deferred (host 
> relay= name>[] said: 451 Temporary local problem - please try later
> (in reply to RCPT TO command))
> 
> Is there some Spacewalk configuration that needs to be done to enable 
> it to utilise Postfix perhaps? As an example I’ve seen some references 
> to *web.default_mail_from*, in */etc/rhn/rhn.conf*, but I’m not sure 
> what it actually needs to be set to.
> 
> Regards
> 
> Philip Cookson
> 
> Linux Administrator
> 
> IT Services
> 
> ERI Building
> 
> Edgbaston
> 
> Birmingham
> 
> B15 2TT
> 
> Tel: 0121 414 4731
> 
> Email: p.cook...@bham.ac.uk <mailto:p.cook...@bham.ac.uk>
> 
> 
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
> 

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

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

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

[p.cook...@bham.ac.uk]

Hi Lakshmi

Presuming you’ve configured the SSL keys correctly, might be worth 
noting/checking the following about the baseurl:


Add repository URL with more specific details:


From
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os
Tohttps://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os


Note that in 7Server the S must be capitalized. Also, substitute x86_64 for 
$basearch.

[cid:image003.jpg@01D537C5.18CE0EA0]

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mandava2...@gmail.com
Sent: 10 July 2019 22:29
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.8 - Patching RHEL 6/7 Servers


Hi All,
I’ve installed Open Spacewalk 2.8 on a RHEL 7 server  and configured CentOS, 
Oracle Enterprise Linux 7 and able to patch Servers with out any issues

I am planning to configure RHEL 6, RHEL 7 servers into Spacewalk so that all my 
environment systems patch and administration on single patching solution

I have done the below configurations but getting the below errors

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

# update-ca-trust
2.
Red Hat you will need to enter the CA SSL Key, the Customer Entitlement SSL Key 
and the
SSL Client Key.  In the redhat.repo file you'll see something like this:

sslcacert = /etc/rhsm/ca/redhat-uep.pem  (the RHEL CA Signing SSL certificate)
sslclientkey = /etc/pki/entitlement/-key.pem  (RHEL Client 
Key SSL certificate)
sslclientcert = /etc/pki/entitlement/.pem 
(RHEL Entitlement/Client certificate)

The contents of the sslclientcert file is the key you want to register in 
spacewalk as the Red Hat Entitlement Key.   I created my keys with these names:

RHEL CA Signing Certificate, RHEL Client Key, and RHEL Entitlement.  For each 
key you create a key, put in the description, select type SSL and paste the 
contents of the appropriate file into the Key contents field

3. Created Redhat 7.6 channel in spacewalk wegUI
For GPG Key ID: FD431D51, and GPG key fingerprint:  567E 347A D004 4ADE 55BA 
8A5F 199E 2F91 FD43 1D51
baseurl: https://cdn.redhat.com/content/dist/rhel/server/7/7.6/$basearch/os
and
in the repository selected CA signing, RHEL client key and rhel entitlement

4.
{root@spacewalk}-{/etc/yum.repos.d}
 # /usr/bin/spacewalk-repo-sync --channel linux7-x86_64 --type yum
22:37:57 ==
22:37:57 | Channel: linux7-x86_64
22:37:57 ==
22:37:57 Sync of channel started.
22:37:57
22:37:57   Processing repository with URL: 
https://cdn.redhat.com/content/dist/rhel/server/7/7.6/$basearch/os
22:37:58 ERROR: failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 
256] No more mirrors to try.
https://cdn.redhat.com/content/dist/rhel/server/7/7.6/x86_64/os/repodata/repomd.xml:
 [Errno 14] curl#77 - "Problem with the SSL CA cert (path? access rights?)"
22:37:59 Sync of channel completed in 0:00:01.
22:37:59 Total time: 0:00:01

Please help on this issue.

Thanks,
Lakshmi Mandava


On Wed, Jul 3, 2019 at 11:21 PM Lakshmi Narayana 
mailto:mandava2...@gmail.com>> wrote:
Hi All,
I’ve installed Open Spacewalk 2.8 on a RHEL 7 server  and configured CentOS, 
Oracle Enterprise Linux 7 and able to patch Servers with out any issues

I am planning to configure RHEL 6, RHEL 7 servers into Spacewalk so that all my 
environment systems patch and administration on single patching solution

I have done the below configurations but getting the below errors

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

# update-ca-trust
2.
Red Hat you will need to enter the CA SSL Key, the Customer Entitlement SSL Key 
and the
SSL Client Key.  In the redhat.repo file you'll see something like this:

sslcacert = /etc/rhsm/ca/redhat-uep.pem  (the RHEL CA Signing SSL certificate)
sslclientkey = /etc/pki/entitlement/-key.pem  (RHEL Client 
Key SSL certificate)
sslclientcert = /etc/pki/entitlement/.pem 
(RHEL Entitlement/Client certificate)

The contents of the sslclientcert file is the key you want to register in 
spacewalk as the Red Hat Entitlement Key.   I created my keys with these names:

RHEL CA Signing Certificate, RHEL Client Key, and RHEL Entitlement.  For each 
key you create a key, put in the description, select type SSL and paste the 
contents of the appropriate file into the Key contents field

3. Created Redhat 7.6 channel in spacewalk wegUI
For GPG Key ID: FD431D51, and GPG key fingerprint:  567E 347A D004 4ADE 55BA 
8A5F 199E 2F91 FD43 1D51
baseurl: https://cdn.redhat.com/content/dist/rhel/server/7/7.6/$basearch/os
and
in the repository selected CA signing, RHEL client key and rhel entitlement

4.
{root@spacewalk}-{/etc/yum.repos.d}
 # /usr/bin/spacewalk-repo-sync --channel linux7-x86_64 --type yum
22:37:57 ==
22:37:57 | Channel: 

Re: [Spacewalk-list] Spacewalk-list Digest, Vol 134, Issue 19

[p.cook...@bham.ac.uk]

Hi Merphis

You could use "which" to confirm its location but sbin should be in your PATH:

[root@~]# which spacewalk-service
/sbin/spacewalk-service
[root@ ~]#

It may not have found it because you copy/paste with the capital "S" perhaps?!

Initially, you could use "spacewalk-service status" to report on the status of 
all the Spacewalk components.

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of merphis.el...@us.idemia.com
Sent: 23 July 2019 17:19
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk-list Digest, Vol 134, Issue 19

Yea I found that I get the error "command not found" there,  get message that 
command not found I did a find / -name spacewalk* and I do not see much, couple 
config files.

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of spacewalk-list-requ...@redhat.com
Sent: Tuesday, July 23, 2019 12:09 PM
To: spacewalk-list@redhat.com
Subject: Spacewalk-list Digest, Vol 134, Issue 19

Send Spacewalk-list mailing list submissions to
spacewalk-list@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-requ...@redhat.com

You can reach the person managing the list at
spacewalk-list-ow...@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. Re: Spacewalk Start up (bryan.nor...@gmail.com)


--

Message: 1
Date: Tue, 23 Jul 2019 18:08:28 +0200
From: 
To: 
Subject: Re: [Spacewalk-list] Spacewalk Start up
Message-ID: <004101d54170$de6c9be0$9b45d3a0$@gmail.com>
Content-Type: text/plain; charset="us-ascii"

Not sure if it was the same in 2.7 that it is in 2.9, but for 2.9, it's 

 

Spacewalk-service start

 

Bryan

 

 

From: spacewalk-list-boun...@redhat.com 
On Behalf Of Ellis, Merphis
Sent: Tuesday, July 23, 2019 18:06
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk Start up

 

Hey,

I know this should be easy but I could not find an answer on google.   We
had to restart our Spacewalk 2.7 server overnight due to a power issue.
When we start the server the spacewalk did not start up now I cannot figure out 
how to get it started.  

I am running Oracle Linux 7.6 so I would have thought a systemctl start 
spacewalk would have done it.  But hell I cannot find a service to start. I 
have googled for several days and really am puzzled .

Any idea how to get this stuff started?

 

Making plans actionable!

 

 

Regards,

 



  


Merphis Ellis 



M. +1 850 556-6313
E. merphis.el...@us.idemia.com 
125 McAlpin Dr

Winterville, GA 30683


  

 


  



Join us on

  

  

  

  


  


  





 

 

 

  _  


This message is only for the use of the intended recipient and may contain 
information that is CONFIDENTIAL and PROPRIETARY to IDEMIA. If you are not the 
intended recipient, please erase all copies of the message and its attachments 
and notify the sender immediately.

-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2605 bytes
Desc: not available
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 1481 bytes
Desc: not available
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image003.gif
Type: image/gif
Size: 1495 bytes
Desc: not available
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image004.gif
Type: image/gif
Size: 1499 bytes
Desc: not available
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image005.gif
Type: image/gif
Size: 1498 bytes
Desc: not available
URL: 

-- next 

Re: [Spacewalk-list] Spacewalk's planned cert expiration in Aug (Can we simulate this?)

[p.cook...@bham.ac.uk]

Hi Merphis

If you're referring to the SSL certificate created when running 
"spacewalk-setup" I believe the certificate file is 
"/etc/httpd/conf/ssl.crt/server.crt" and the expiration date is the line 
beginning "Not After" so you could try the following:

# grep "Not After" /etc/httpd/conf/ssl.crt/server.crt

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of jmci...@bclc.com
Sent: 23 July 2019 17:17
To: 'spacewalk-list@redhat.com' 
Subject: Re: [Spacewalk-list] Spacewalk's planned cert expiration in Aug (Can 
we simulate this?)

Also, I'm failing to find a solid date for Aug's cert expiry. Does anyone know 
this?


-Original Message-
From: Jody McIvor
Sent: July 19, 2019 7:18 AM
To: spacewalk-list@redhat.com
Subject: Spacewalk's planned cert expiration in Aug (Can we simulate this?)

Hi All,

In preparation for Redhat's dropping of Spacewalk support (And any further 
certificate renewals), we have updated all of our spacewalk servers to no less 
than 2.6. I have been (unsuccessfully, since I'm not sure exactly which file it 
is) attempting to "simulate" the cert expiration by:
 - Renaming what I thought was the cert file (Pretty sure I was wrong)
 - Forcing date/time change to 2019 on Spacewalk server (Everything seemed 
fine, but still not convinced.

My questions are:
 - Can someone enlighten me as to which file is truly the cert that will expire 
next month?
 - Was changing the time on the server my best bet for testing the effects of 
the cert failure?

Any input on this subject is appreciated, because if this doesn't go smoothly 
in Aug it WILL have a massive impact on company income until resolved.

Jody McIvor
Sr. Systems Administrator, Integration
Les Services D'intégration




-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of spacewalk-list-requ...@redhat.com
Sent: July 19, 2019 6:27 AM
To: spacewalk-list@redhat.com
Subject: Spacewalk-list Digest, Vol 134, Issue 13

Send Spacewalk-list mailing list submissions to spacewalk-list@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-requ...@redhat.com

You can reach the person managing the list at spacewalk-list-ow...@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. Needs-Restarting shows perpetual reboot need afterKickstart
  (bryan.nor...@gmail.com)
   2. Re: Needs-Restarting shows perpetual reboot needafter
  Kickstart (bryan.nor...@gmail.com)
   3. Re: Update failing for no public key (Lubbers, Nicholas)


--

Message: 1
Date: Fri, 19 Jul 2019 06:11:15 +0200
From: 
To: 
Subject: [Spacewalk-list] Needs-Restarting shows perpetual reboot need 
afterKickstart
Message-ID: <01d53de8$03363990$09a2acb0$@gmail.com>
Content-Type: text/plain; charset="us-ascii"

Since I couldn't get around the Internal Server Error when attempting to 
Profile Sync, I found a work around using spacecmd and a post script during the 
Kickstart process.



Everything works great, with one exception.  After the provisioning is done, 
and the server is accessible, it shows that it needs a reboot.  After rebooting 
it, it still shows a reboot is needed.  It says (amongst other
components) that the kernel has been updated, yet uname -r shows it is running 
the kernel that it thinks it needs to reboot to use.



Have you all seen this before?  I'm stumped.no amount of googling has produced 
anything close to helpful.



Thanks!

Bryan

-- next part --
An HTML attachment was scrubbed...
URL: 


--

Message: 2
Date: Fri, 19 Jul 2019 10:10:45 +0200
From: 
To: 
Subject: Re: [Spacewalk-list] Needs-Restarting shows perpetual reboot needafter 
Kickstart
Message-ID: <000201d53e09$7890a1f0$69b1e5d0$@gmail.com>
Content-Type: text/plain; charset="us-ascii"

It looks like it was a date/time issue.  When the system was kickstarted, it 
used the default GMT.  Somewhere in the update process after install, the time 
was corrected to GMT+2.  After 2 hours, I rebooted it again, and no it no 
longer thinks it needs to reboot to load a more recent kernel, and shows the 
system is up to date.



From: bryan.nor...@gmail.com 
Sent: Friday, July 19, 2019 06:11
To: spacewalk-list@redhat.com
Subject: Needs-Restarting shows perpetual reboot need after Kickstart



Since I couldn't get around the Internal Server Error when attempting to 
Profile Sync, I found a work around using spacecmd and a post script during the 
Kickstart process.



Everything works great, with one exception.  After the provisioning is done, 
and the server is accessible, it 

Re: [Spacewalk-list] Spacewalk's planned cert expiration in

[p.cook...@bham.ac.uk]

Hi Jody

Spacewalk is the free open source up-stream version of Red Hat Satellite 5 so, 
unless I'm misinterpreting what you're saying, there's no license/certificate 
to expire really (apart from the SSL one I mentioned below - 
/etc/httpd/conf/ssl.crt/server.crt).

Which article are you referring to? If there's something that is going to stop 
Spacewalk syncing RHEL repo's, I imagine it would be a concern for a lot of 
people really!

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of jmci...@bclc.com
Sent: 24 July 2019 15:47
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk's planned cert expiration in

Hi Phil,

Thanks for the response. I checked that one and its expiry is 2038... It was my 
understanding that Redhat's dropping of support for Spacewalk included them no 
longer renewing the entitlement cert for Spacewalk servers. This resulted in 
versions 2.5 and higher not implementing this cert, as Redhat planned this 
final cert to expire this Aug 2019. So the expiry date confuses me, I would 
have expected it to be expiring in the next few weeks?

Maybe I'm just misinterpreting things.

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


jmci...@bclc.com
BCLC.com





-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of spacewalk-list-requ...@redhat.com
Sent: July 24, 2019 2:01 AM
To: spacewalk-list@redhat.com
Subject: Spacewalk-list Digest, Vol 134, Issue 22

Send Spacewalk-list mailing list submissions to spacewalk-list@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-requ...@redhat.com

You can reach the person managing the list at spacewalk-list-ow...@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. Re: Spacewalk-list Digest, Vol 134, Issue 19 (Dennis Pittman)
   2. Re: Spacewalk's planned cert expiration in Aug (Can we
  simulate this?) (p.cook...@bham.ac.uk)


--

Message: 1
Date: Wed, 24 Jul 2019 08:51:13 +
From: Dennis Pittman 
To: "spacewalk-list@redhat.com" 
Subject: Re: [Spacewalk-list] Spacewalk-list Digest, Vol 134, Issue 19
Message-ID:


Content-Type: text/plain; charset="us-ascii"

Since you stated that you had to restart your server, I would make certain that 
all file systems are mounted correctly, then also check for errors in your 
messages and audit files.  Once you have verified that everything is recovered 
successfully then try restarting the spacewalk-Services.



Sent from my iPhone

> On Jul 23, 2019, at 12:22 PM, Ellis, Merphis  
> wrote:
>
> Yea I found that I get the error "command not found" there,  get message that 
> command not found I did a find / -name spacewalk* and I do not see much, 
> couple config files.
>
> -Original Message-
> From: spacewalk-list-boun...@redhat.com 
>  On Behalf Of 
> spacewalk-list-requ...@redhat.com
> Sent: Tuesday, July 23, 2019 12:09 PM
> To: spacewalk-list@redhat.com
> Subject: Spacewalk-list Digest, Vol 134, Issue 19
>
> Send Spacewalk-list mailing list submissions to
>spacewalk-list@redhat.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-listdata=02%7C01%7C%7
> C3296714f56714b54d22108d70f89e5f6%7C84df9e7fe9f640afb435%7
> C1%7C0%7C636994957247832135sdata=qQ%2By%2F0TxWz26lSntVUJBntRARINm
> Cb9E5E5mtv85xKc%3Dreserved=0 or, via email, send a message with 
> subject or body 'help' to
>spacewalk-list-requ...@redhat.com
>
> You can reach the person managing the list at
>spacewalk-list-ow...@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. Re: Spacewalk Start up (bryan.nor...@gmail.com)
>
>
> --
>
> Message: 1
> Date: Tue, 23 Jul 2019 18:08:28 +0200
> From: 
> To: 
> Subject: Re: [Spacewalk-list] Spacewalk Start up
> Message-ID: <004101d54170$de6c9be0$9b45d3a0$@gmail.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Not sure if it was the same in 2.7 that it is in 2.9, but for 2.9, 
> it's
>
>
>
> Spacewalk-service start
>
>
>
> Bryan
>
>
>
>
>
> From: spacewalk-list-boun...@redhat.com 
> 
> On Behalf Of Ellis, Merphis
> Sent: Tuesday, July 2

Re: [Spacewalk-list] Spacewalk's planned cert expiration

[p.cook...@bham.ac.uk]

Thanks for that clarification, fortunately we're running a later version 
already:-)

Regards
Phil

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of jmci...@bclc.com
Sent: 26 July 2019 15:50
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk's planned cert expiration

Hi Phil,

The cert I believe to be in question:
/usr/share/spacewalk/setup/spacewalk-public.cert

Last expiry date of that cert was 2018-07-13. Redhat renewed it one last time, 
stating that it would never be renewed again. I couldn't find a solid date but 
heard somewhere that it was to expire in Aug. This in turn will kill any 
spacewalk 2.4 and earlier installations. Upgrading to Spacewalk 2.5 or better 
apparently resolves this as the cert is simply ignored.

In preparation, we have upgraded all our spacewalk servers (4 servers for 4 
environs) from 2.4 to 2.6. Everything "seems" fine, but I was trying to 
simulate the dreaded cert failure, to simply ease my mind, so there's no 
surprises on day-of.

Details here:
https://github.com/spacewalkproject/spacewalk/wiki/Refreshing-certificate

Cert contents (public):


  SPACEWALK-001
  Spacewalk Default Organization
  2007-07-13 00:00:00
  2018-07-13 00:00:00
  2
  2
  2
  2
  2
  spacewalk
  2
  
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEABECAAYFAlNg/40ACgkQnnKdrwaUeTIXqwCgmRiTmzFuO7x3bitYPWcJFsZe
UPgAn0kTzWo7xUGDpedM0No9nEnWa84P
=FTXc
-END PGP SIGNATURE-



Jody McIvor
Sr. Systems Administrator, Integration
Les Services D'intégration





-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of spacewalk-list-requ...@redhat.com
Sent: July 26, 2019 1:57 AM
To: spacewalk-list@redhat.com
Subject: Spacewalk-list Digest, Vol 134, Issue 28

Send Spacewalk-list mailing list submissions to spacewalk-list@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-requ...@redhat.com

You can reach the person managing the list at spacewalk-list-ow...@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. In light of Satellite 5's inevitable sunset, can you sync
  official RHEL channels somehow? (gargunkle)
   2. Re: In light of Satellite 5's inevitable sunset, can you sync
  official RHEL channels somehow? (Matthew Madey)
   3. Re: Spacewalk's planned cert expiration in (p.cook...@bham.ac.uk)


--

Message: 1
Date: Thu, 25 Jul 2019 14:39:41 -0400
From: gargunkle 
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] In light of Satellite 5's inevitable sunset, can you 
sync official RHEL channels somehow?
Message-ID:

Content-Type: text/plain; charset="utf-8"

I'm 90% sure I know the answer to this, but wanted to check if there might be 
some good news.

My organization has official Red Hat Satellite licenses.  However, I really do 
not care for the Satellite 6 product.

Is there a way to sync official Red Hat channels/content to a Spacewalk server, 
perhaps leveraging the Satellite license my organization is paying for?  Maybe 
using COPR but I haven't figured out how that works yet.

Thanks for any pointers.

EP
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://www.redhat.com/archives/spacewalk-list/attachments/20190725/867af40a/attachment.html>

--

Message: 2
Date: Thu, 25 Jul 2019 14:12:45 -0500
From: Matthew Madey 
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] In light of Satellite 5's inevitable sunset, can 
you sync official RHEL channels somehow?
Message-ID:

Content-Type: text/plain; charset="utf-8"

I believe this method still works:
https://www.suse.com/documentation/suse-best-practices/sbp-sumaforrhel/data/sbp-sumaforrhel.html


On Thu, Jul 25, 2019 at 1:40 PM gargunkle  wrote:

> I'm 90% sure I know the answer to this, but wanted to check if there 
> might be some good news.
>
> My organization has official Red Hat Satellite licenses.  However, I 
> really do not care for the Satellite 6 product.
>
> Is there a way to sync official Red Hat channels/content to a 
> Spacewalk server, perhaps leveraging the Satellite license my 
> organization is paying for?  Maybe using COPR but I haven't figured out how 
> that works yet.
>
> Thanks for any pointers.
>
> EP
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://www.redhat.com/archives/spacewalk-list/attachments/20190725/437f2216/