Re: [Spacewalk-list] spacewalk - GUI console login issue

[Raymond Setchfield]

There is very little information to go on here.

Is the spacewalk service running?

What does the logs say? Are you receiving any error message when you go to the 
url?

Ray

> On 29 Mar 2020, at 17:58, GUPTA, AJAY KUMAR  wrote:
> 
> 
> Hi Team,
>  
> I have spacewalk 2.8 server running on RHEL 7.7. I am not getting login 
> screen to put my credential to get GUI console access. Please help me to fix 
> the issue.
>  
> Regards,
> Ajay Kumar Gupta
> Professional 2 System Administrator (Linux)
> DXC Technology
> A 44/45, Galaxy Business Park Sector-62 Noida- 201301 India
> Mob: +91 – 9971101172
> Advance Leave Notification :
>  
> 
> DXC Technology India Private Limited - Unit 13, Block 2, SDF Buildings, MEPZ 
> SEZ, Tambaram, Chennai 600 045, Tamil Nadu. Registered in India, CIN: 
> U72900TN2015FTC102489. 
> DXC Technology Company -- This message is transmitted to you by or on behalf 
> of DXC Technology Company or one of its affiliates. It is intended 
> exclusively for the addressee. The substance of this message, along with any 
> attachments, may contain proprietary, confidential or privileged information 
> or information that is otherwise legally exempt from disclosure. Any 
> unauthorized review, use, disclosure or distribution is prohibited. If you 
> are not the intended recipient of this message, you are not authorized to 
> read, print, retain, copy or disseminate any part of this message. If you 
> have received this message in error, please destroy and delete all copies and 
> notify the sender by return e-mail. Regardless of content, this e-mail shall 
> not operate to bind DXC Technology Company or any of its affiliates to any 
> order or other contract unless pursuant to explicit written agreement or 
> government initiative expressly permitting the use of e-mail for such 
> purpose. ___
> 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 Filters

[Raymond Setchfield]

I was looking to keep  grafana-*.x86_64.rpm but get rid of anything else

Ray

On Tue, Feb 18, 2020 at 11:47 AM Robert Paschedag 
wrote:

> Shouldn't it be "-grafana..."?
>
> Robert
>
>
> ⁣sent from my mobile device​
>
>
>  Originale Nachricht 
> Von: Raymond Setchfield 
> Gesendet: Tue Feb 18 12:11:22 GMT+01:00 2020
> An: spacewalk-list@redhat.com
> Betreff: [Spacewalk-list] Spacewalk Filters
>
> Hi All,
>
> I am receiving an error message when I am trying to pull down the grafana
> packages, and I thought I'd use the filters to remove the appropriate
> packages.
>
> 10:58:48 197/200 : grafana-6.2.3-1.x86_64.rpm
> 10:58:48 198/200 : grafana-5.2.2-1.armhfp.rpm
> 10:58:48 199/200 : grafana-6.2.2-1.armhfp.rpm
> 10:58:48 200/200 : grafana-6.3.6-1.armhfp.rpm
> 10:58:49
> 10:58:49   Importing packages to DB:
>Importing packages:
> |##| 100.0%
> 10:59:42
> 10:59:42   Linking packages to the channel.
> 10:59:42 ERROR: Unknown arch armhfp
> 10:59:43 Sync of channel completed in 0:03:32.
> 10:59:43 Total time: 0:03:32
>
> So using the filters I am tried;
> +grafana-*.x86_64.rpm
>
> and I am receiving this from the repo  sync
> 11:06:44   Processing repository with URL:
> https://packages.grafana.com/oss/rpm
> 11:06:45 Packages in repo:   201
> 11:06:45 Packages passed filter rules: 0
> 11:06:45 No new packages to sync.
> 11:06:45
> 11:06:45   Errata in repo: 0.
> 11:06:45 Sync of channel completed in 0:01:24.
> 11:06:45 Total time: 0:01:24
>
> Can anyone suggest what I am doing wrong on the filters?
>
> Thanks
>
> Ray
>
>
> 
>
> ___
> 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

[Spacewalk-list] Spacewalk Filters

[Raymond Setchfield]

Hi All,

I am receiving an error message when I am trying to pull down the grafana
packages, and I thought I'd use the filters to remove the appropriate
packages.

10:58:48 197/200 : grafana-6.2.3-1.x86_64.rpm
10:58:48 198/200 : grafana-5.2.2-1.armhfp.rpm
10:58:48 199/200 : grafana-6.2.2-1.armhfp.rpm
10:58:48 200/200 : grafana-6.3.6-1.armhfp.rpm
10:58:49
10:58:49   Importing packages to DB:
   Importing packages:
|##| 100.0%
10:59:42
10:59:42   Linking packages to the channel.
10:59:42 ERROR: Unknown arch armhfp
10:59:43 Sync of channel completed in 0:03:32.
10:59:43 Total time: 0:03:32

So using the filters I am tried;
+grafana-*.x86_64.rpm

and I am receiving this from the repo  sync
11:06:44   Processing repository with URL:
https://packages.grafana.com/oss/rpm
11:06:45 Packages in repo:   201
11:06:45 Packages passed filter rules: 0
11:06:45 No new packages to sync.
11:06:45
11:06:45   Errata in repo: 0.
11:06:45 Sync of channel completed in 0:01:24.
11:06:45 Total time: 0:01:24

Can anyone suggest what I am doing wrong on the filters?

Thanks

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

[Spacewalk-list] Recommended way to remove Client from Ubuntu

[Raymond Setchfield]

Hi All,

Is there a recommended way to remove the spacewalk client from ubuntu?

Thanks

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

[Spacewalk-list] Fwd: Error occurred while processing python2-rhn-client-tools

[Raymond Setchfield]

Been looking into this further, and it seems that someone already
experienced these types of issues before, as I see there is bug which is
open and seems to be similar to what I am currently experiencing
https://bugzilla.redhat.com/show_bug.cgi?id=1658772

 Through the spacewalk-list archive, there is chat about this too a
reference to a script but the url doesn't appear to work.

Does anyone have that information they could share with me?

Thanks

Ray

-- Forwarded message -
From: Raymond Setchfield 
Date: Wed, Jan 8, 2020 at 7:32 PM
Subject: Error occurred while processing python2-rhn-client-tools
To: 


Hi Everyone,

Can anyone help me with this error message? I cannot seem to get past this
error.

Reading package lists... Error!
W: The repository 'spacewalk://cent-mgmt channels: Release' does not have a
Release file.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
E: Problem parsing dependency Depends
E: Error occurred while processing python2-rhn-client-tools (NewVersion2)
E: Problem with MergeList
/var/lib/apt/lists/cent-mgmt_dists_channels:_satellites-development-channel_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

Thanks

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

[Spacewalk-list] Error occurred while processing python2-rhn-client-tools

[Raymond Setchfield]

Hi Everyone,

Can anyone help me with this error message? I cannot seem to get past this
error.

Reading package lists... Error!
W: The repository 'spacewalk://cent-mgmt channels: Release' does not have a
Release file.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
E: Problem parsing dependency Depends
E: Error occurred while processing python2-rhn-client-tools (NewVersion2)
E: Problem with MergeList
/var/lib/apt/lists/cent-mgmt_dists_channels:_satellites-development-channel_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

Thanks

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

[Spacewalk-list] Fwd: FW: osa-dispatcher.service failed

[Raymond Setchfield]

Hi All,


Is this just a case of enabling the SSL? If so where would this be set?


Ray



*From:* spacewalk-list-boun...@redhat.com 
*On Behalf Of *Raymond Setchfield
*Sent:* 20 November 2019 08:08
*To:* spacewalk-list@redhat.com
*Subject:* Re: [Spacewalk-list] osa-dispatcher.service failed



Thanks for the response guys



I appear to have the osaddispatcher now running. This appeared to be an
issue with the hostname, and this was resolved by adding it into the
/etc/hosts file. I am however. seeing this error message on the client side



Nov 19 16:02:49  osad[1920]: 2019-11-19 16:02:49 rhn_log.log_error: Server
does not support ...tanza
Nov 19 16:02:49  osad[1920]: 2019-11-19 16:02:49 rhn_log.log_error:
Traceback (most recent c...ast):
Nov 19 16:02:49 osad[1920]: File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", lin...ction
Nov 19 16:02:49 osad[1920]: c = self._get_jabber_client(js)
Nov 19 16:02:49 osad[1920]: File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", lin...lient
Nov 19 16:02:49 osad[1920]: c.connect()
Nov 19 16:02:49 osad[1920]: File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", lin...nnect
Nov 19 16:02:49 osad[1920]: raise SSLDisabledError
Nov 19 16:02:49 osad[1920]: SSLDisabledError
Nov 19 16:02:49 systemd[1]: Started OSAD daemon.



Any suggestions on this?



Ray



On Tue, Nov 19, 2019 at 5:12 PM David Dales  wrote:

I don't know if this would apply to your situation. But I have had an issue
changing both the spacewalk servername and client name. I use the standard
Cert and the names didn't match after the name change.

Reinstalling the standard cert fixed it for me.

Not sure if that helps though.

-Original Message-
From: spacewalk-list-boun...@redhat.com 
On Behalf Of Robert Paschedag
Sent: Tuesday, November 19, 2019 10:09 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher.service failed


EXTERNAL EMAIL: Ensure you trust this sender and know the content is safe
before clicking on any links or attachments.

Look into /var/log/messages for errors.

Also changing a hostname (of course!) breaks the SSL verification, unless
the new hostname is mentioned as SAN (subject alternative name) within the
certificate or the certificate is a wildcard certificate that Assisi
matches the new hostname.

Robert

⁣sent from my mobile device


 Originale Nachricht ----
Von: Raymond Setchfield 
Gesendet: Tue Nov 19 17:04:20 GMT+01:00 2019
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] osa-dispatcher.service failed

Hi All,

Can anyone assist on this issue?

Ray

On Wed, Nov 6, 2019 at 11:44 AM Raymond Setchfield <
raymond.setchfi...@gmail.com> wrote:

> Hi All,
>
> Been testing this to see if I could potentially recreate the fault.
>
> I have taken a copy of the instance which was working (vanilla install
> with spacewalk applied). When the copy starts up. It appears to be
> loaded and running fine. When I made a change to the server. For
> example, the hostname. The OSAD failed after reboot.
> I then made another machine from known working copy and changed the
> sshd_config file. Rebooted the machine and osad then failed.again.
>
> The failure seems to be the same, and there is nothing within the logs
> which suggest why its failed. It appears to be a time out. anything
> else I could potentially look into?
>
> Thanks
>
> Ray
>
> -- Forwarded message -
> From: Raymond Setchfield 
> Date: Tue, Nov 5, 2019 at 10:00 AM
> Subject: osa-dispatcher.service failed
> To: 
>
>
> Hi All,
>
> I have been following this guide to install the SSL certificate, and
> it appears to have worked fine. As I can see the certificate when
> logging into spacewalk etc.
>
> However, when restarting the services it appears that the
> osa-dispatcher has failed. There is little or no information to go
> with to figure out why it has failed.
>
> ● postgresql.service - PostgreSQL database server
>Loaded: loaded (/usr/lib/systemd/system/postgresql.service;
> enabled; vendor preset: disabled)
>Active: active (running) since Tue 2019-11-05 09:50:15 UTC; 4min 41s
ago
>   Process: 12341 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
> (code=exited, status=0/SUCCESS)
>   Process: 12504 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
> ${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
>   Process: 12487 ExecStartPre=/usr/bin/postgresql-check-db-dir
> ${PGDATA} (code=exited, status=0/SUCCESS)  Main PID: 12518 (postgres)
>CGroup: /system.slice/postgresql.service
>├─12518 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
>├─12529 postgres: logger process
>├─12531 postgres: checkpointer process
>├─12532 postgres: writer process
>├─12533 postgres: wal writer 

Re: [Spacewalk-list] Release' does not have a Release file.

[Raymond Setchfield]

Hi All,

Can anyone help with this at all?

Ray

On Wed, Nov 20, 2019 at 10:36 AM Raymond Setchfield <
raymond.setchfi...@gmail.com> wrote:

> Hi All,
>
> Adding ubuntu clients to spacewalk and receiving this error message. I
> have been following documentation regarding to add release files, and this
> has been done. Ubuntu is still complaining about the release files.
>
> Also the python2-rhn-client-tools concerns me a little. I see there is a
> bug open for this. Is there a workaround?
>
> Reading package lists... Error!
> W: The repository 'spacewalk://smart-cent-mgmt.kinly.com channels:
> Release' does not have a Release file.
> N: Data from such a repository can't be authenticated and is therefore
> potentially dangerous to use.
> N: See apt-secure(8) manpage for repository creation and user
> configuration details.
> E: Problem parsing dependency Depends
> E: Error occurred while processing python2-rhn-client-tools (NewVersion2)
> E: Problem with MergeList
> /var/lib/apt/lists/smart-cent-mgmt.kinly.com_dists_channels:_kinly-masters-internal-channel_binary-amd64_Packages
> E: The package lists or status file could not be parsed or opened.
>
> Thanks
>
> Ray
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Release' does not have a Release file.

[Raymond Setchfield]

Hi All,

Does anyone have a solution to the problem?

Ray

On Wed, Nov 20, 2019 at 10:36 AM Raymond Setchfield <
raymond.setchfi...@gmail.com> wrote:

> Hi All,
>
> Adding ubuntu clients to spacewalk and receiving this error message. I
> have been following documentation regarding to add release files, and this
> has been done. Ubuntu is still complaining about the release files.
>
> Also the python2-rhn-client-tools concerns me a little. I see there is a
> bug open for this. Is there a workaround?
>
> Reading package lists... Error!
> W: The repository 'spacewalk://smart-cent-mgmt.kinly.com channels:
> Release' does not have a Release file.
> N: Data from such a repository can't be authenticated and is therefore
> potentially dangerous to use.
> N: See apt-secure(8) manpage for repository creation and user
> configuration details.
> E: Problem parsing dependency Depends
> E: Error occurred while processing python2-rhn-client-tools (NewVersion2)
> E: Problem with MergeList
> /var/lib/apt/lists/smart-cent-mgmt.kinly.com_dists_channels:_kinly-masters-internal-channel_binary-amd64_Packages
> E: The package lists or status file could not be parsed or opened.
>
> Thanks
>
> Ray
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Release' does not have a Release file.

[Raymond Setchfield]

Hi All,

Adding ubuntu clients to spacewalk and receiving this error message. I have
been following documentation regarding to add release files, and this has
been done. Ubuntu is still complaining about the release files.

Also the python2-rhn-client-tools concerns me a little. I see there is a
bug open for this. Is there a workaround?

Reading package lists... Error!
W: The repository 'spacewalk://smart-cent-mgmt.kinly.com channels: Release'
does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
E: Problem parsing dependency Depends
E: Error occurred while processing python2-rhn-client-tools (NewVersion2)
E: Problem with MergeList
/var/lib/apt/lists/smart-cent-mgmt.kinly.com_dists_channels:_kinly-masters-internal-channel_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

Thanks

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

Re: [Spacewalk-list] osa-dispatcher.service failed

[Raymond Setchfield]

Thanks for the response guys

I appear to have the osaddispatcher now running. This appeared to be an
issue with the hostname, and this was resolved by adding it into the
/etc/hosts file. I am however. seeing this error message on the client side

Nov 19 16:02:49  osad[1920]: 2019-11-19 16:02:49 rhn_log.log_error: Server
does not support ...tanza
Nov 19 16:02:49  osad[1920]: 2019-11-19 16:02:49 rhn_log.log_error:
Traceback (most recent c...ast):
Nov 19 16:02:49 osad[1920]: File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", lin...ction
Nov 19 16:02:49 osad[1920]: c = self._get_jabber_client(js)
Nov 19 16:02:49 osad[1920]: File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", lin...lient
Nov 19 16:02:49 osad[1920]: c.connect()
Nov 19 16:02:49 osad[1920]: File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", lin...nnect
Nov 19 16:02:49 osad[1920]: raise SSLDisabledError
Nov 19 16:02:49 osad[1920]: SSLDisabledError
Nov 19 16:02:49 systemd[1]: Started OSAD daemon.

Any suggestions on this?

Ray

On Tue, Nov 19, 2019 at 5:12 PM David Dales  wrote:

> I don't know if this would apply to your situation. But I have had an
> issue changing both the spacewalk servername and client name. I use the
> standard Cert and the names didn't match after the name change.
>
> Reinstalling the standard cert fixed it for me.
>
> Not sure if that helps though.
>
> -Original Message-
> From: spacewalk-list-boun...@redhat.com 
> On Behalf Of Robert Paschedag
> Sent: Tuesday, November 19, 2019 10:09 AM
> To: spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] osa-dispatcher.service failed
>
>
> EXTERNAL EMAIL: Ensure you trust this sender and know the content is safe
> before clicking on any links or attachments.
>
> Look into /var/log/messages for errors.
>
> Also changing a hostname (of course!) breaks the SSL verification, unless
> the new hostname is mentioned as SAN (subject alternative name) within the
> certificate or the certificate is a wildcard certificate that Assisi
> matches the new hostname.
>
> Robert
>
> ⁣sent from my mobile device​
>
>
>  Originale Nachricht 
> Von: Raymond Setchfield 
> Gesendet: Tue Nov 19 17:04:20 GMT+01:00 2019
> An: spacewalk-list@redhat.com
> Betreff: Re: [Spacewalk-list] osa-dispatcher.service failed
>
> Hi All,
>
> Can anyone assist on this issue?
>
> Ray
>
> On Wed, Nov 6, 2019 at 11:44 AM Raymond Setchfield <
> raymond.setchfi...@gmail.com> wrote:
>
> > Hi All,
> >
> > Been testing this to see if I could potentially recreate the fault.
> >
> > I have taken a copy of the instance which was working (vanilla install
> > with spacewalk applied). When the copy starts up. It appears to be
> > loaded and running fine. When I made a change to the server. For
> > example, the hostname. The OSAD failed after reboot.
> > I then made another machine from known working copy and changed the
> > sshd_config file. Rebooted the machine and osad then failed.again.
> >
> > The failure seems to be the same, and there is nothing within the logs
> > which suggest why its failed. It appears to be a time out. anything
> > else I could potentially look into?
> >
> > Thanks
> >
> > Ray
> >
> > -- Forwarded message -
> > From: Raymond Setchfield 
> > Date: Tue, Nov 5, 2019 at 10:00 AM
> > Subject: osa-dispatcher.service failed
> > To: 
> >
> >
> > Hi All,
> >
> > I have been following this guide to install the SSL certificate, and
> > it appears to have worked fine. As I can see the certificate when
> > logging into spacewalk etc.
> >
> > However, when restarting the services it appears that the
> > osa-dispatcher has failed. There is little or no information to go
> > with to figure out why it has failed.
> >
> > ● postgresql.service - PostgreSQL database server
> >Loaded: loaded (/usr/lib/systemd/system/postgresql.service;
> > enabled; vendor preset: disabled)
> >Active: active (running) since Tue 2019-11-05 09:50:15 UTC; 4min 41s
> ago
> >   Process: 12341 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
> > (code=exited, status=0/SUCCESS)
> >   Process: 12504 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
> > ${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
> >   Process: 12487 ExecStartPre=/usr/bin/postgresql-check-db-dir
> > ${PGDATA} (code=exited, status=0/SUCCESS)  Main PID: 12518 (postgres)
> >CGroup: /system.slice/postgresql.service
> >├─12518 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
> >├─12529 postgres: logger proce

Re: [Spacewalk-list] osa-dispatcher.service failed

[Raymond Setchfield]

Hi All,

Can anyone assist on this issue?

Ray

On Wed, Nov 6, 2019 at 11:44 AM Raymond Setchfield <
raymond.setchfi...@gmail.com> wrote:

> Hi All,
>
> Been testing this to see if I could potentially recreate the fault.
>
> I have taken a copy of the instance which was working (vanilla install
> with spacewalk applied). When the copy starts up. It appears to be loaded
> and running fine. When I made a change to the server. For example, the
> hostname. The OSAD failed after reboot.
> I then made another machine from known working copy and changed the
> sshd_config file. Rebooted the machine and osad then failed.again.
>
> The failure seems to be the same, and there is nothing within the logs
> which suggest why its failed. It appears to be a time out. anything else I
> could potentially look into?
>
> Thanks
>
> Ray
>
> -- Forwarded message -
> From: Raymond Setchfield 
> Date: Tue, Nov 5, 2019 at 10:00 AM
> Subject: osa-dispatcher.service failed
> To: 
>
>
> Hi All,
>
> I have been following this guide to install the SSL certificate, and it
> appears to have worked fine. As I can see the certificate when logging into
> spacewalk etc.
>
> However, when restarting the services it appears that the osa-dispatcher
> has failed. There is little or no information to go with to figure out why
> it has failed.
>
> ● postgresql.service - PostgreSQL database server
>Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled;
> vendor preset: disabled)
>Active: active (running) since Tue 2019-11-05 09:50:15 UTC; 4min 41s ago
>   Process: 12341 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
> (code=exited, status=0/SUCCESS)
>   Process: 12504 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
> ${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
>   Process: 12487 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
> (code=exited, status=0/SUCCESS)
>  Main PID: 12518 (postgres)
>CGroup: /system.slice/postgresql.service
>├─12518 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
>├─12529 postgres: logger process
>├─12531 postgres: checkpointer process
>├─12532 postgres: writer process
>├─12533 postgres: wal writer process
>├─12534 postgres: autovacuum launcher process
>├─12535 postgres: stats collector process
>├─12590 postgres: rhnuser rhnschema 127.0.0.1(44062) idle
>├─12591 postgres: rhnuser rhnschema 127.0.0.1(44065) idle
>├─12592 postgres: rhnuser rhnschema 127.0.0.1(44064) idle
>├─12593 postgres: rhnuser rhnschema 127.0.0.1(44068) idle
>├─12594 postgres: rhnuser rhnschema 127.0.0.1(44070) idle
>├─12762 postgres: rhnuser rhnschema 127.0.0.1(44074) idle
>├─12867 postgres: rhnuser rhnschema 127.0.0.1(44076) idle
>├─12868 postgres: rhnuser rhnschema 127.0.0.1(44078) idle
>├─12869 postgres: rhnuser rhnschema 127.0.0.1(44080) idle
>├─12870 postgres: rhnuser rhnschema 127.0.0.1(44082) idle
>├─12871 postgres: rhnuser rhnschema 127.0.0.1(44084) idle
>├─12872 postgres: rhnuser rhnschema 127.0.0.1(44086) idle
>├─12873 postgres: rhnuser rhnschema 127.0.0.1(44088) idle
>├─12874 postgres: rhnuser rhnschema 127.0.0.1(44090) idle
>├─12875 postgres: rhnuser rhnschema 127.0.0.1(44092) idle
>├─12876 postgres: rhnuser rhnschema 127.0.0.1(44094) idle
>├─12877 postgres: rhnuser rhnschema 127.0.0.1(44096) idle
>├─12878 postgres: rhnuser rhnschema 127.0.0.1(44098) idle
>├─12879 postgres: rhnuser rhnschema 127.0.0.1(44100) idle
>├─12880 postgres: rhnuser rhnschema 127.0.0.1(44102) idle
>├─12881 postgres: rhnuser rhnschema 127.0.0.1(44104) idle
>├─12887 postgres: rhnuser rhnschema 127.0.0.1(44106) idle
>├─12888 postgres: rhnuser rhnschema 127.0.0.1(44108) idle
>├─12889 postgres: rhnuser rhnschema 127.0.0.1(44110) idle
>├─12890 postgres: rhnuser rhnschema 127.0.0.1(44112) idle
>├─12891 postgres: rhnuser rhnschema 127.0.0.1(44114) idle
>├─12930 postgres: rhnuser rhnschema 127.0.0.1(44118) idle
>├─12931 postgres: rhnuser rhnschema 127.0.0.1(44120) idle
>├─12941 postgres: rhnuser rhnschema 127.0.0.1(44126) idle
>├─12942 postgres: rhnuser rhnschema 127.0.0.1(44128) idle
>└─12943 postgres: rhnuser rhnschema 127.0.0.1(44130) idle
>
> ● jabberd.service - Jabber Server
>Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled;
> vendor preset: disabled)
>  

[Spacewalk-list] Fwd: osa-dispatcher.service failed

[Raymond Setchfield]

Hi All,

Been testing this to see if I could potentially recreate the fault.

I have taken a copy of the instance which was working (vanilla install with
spacewalk applied). When the copy starts up. It appears to be loaded and
running fine. When I made a change to the server. For example, the
hostname. The OSAD failed after reboot.
I then made another machine from known working copy and changed the
sshd_config file. Rebooted the machine and osad then failed.again.

The failure seems to be the same, and there is nothing within the logs
which suggest why its failed. It appears to be a time out. anything else I
could potentially look into?

Thanks

Ray

-- Forwarded message -
From: Raymond Setchfield 
Date: Tue, Nov 5, 2019 at 10:00 AM
Subject: osa-dispatcher.service failed
To: 


Hi All,

I have been following this guide to install the SSL certificate, and it
appears to have worked fine. As I can see the certificate when logging into
spacewalk etc.

However, when restarting the services it appears that the osa-dispatcher
has failed. There is little or no information to go with to figure out why
it has failed.

● postgresql.service - PostgreSQL database server
   Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled;
vendor preset: disabled)
   Active: active (running) since Tue 2019-11-05 09:50:15 UTC; 4min 41s ago
  Process: 12341 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
(code=exited, status=0/SUCCESS)
  Process: 12504 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
  Process: 12487 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
(code=exited, status=0/SUCCESS)
 Main PID: 12518 (postgres)
   CGroup: /system.slice/postgresql.service
   ├─12518 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
   ├─12529 postgres: logger process
   ├─12531 postgres: checkpointer process
   ├─12532 postgres: writer process
   ├─12533 postgres: wal writer process
   ├─12534 postgres: autovacuum launcher process
   ├─12535 postgres: stats collector process
   ├─12590 postgres: rhnuser rhnschema 127.0.0.1(44062) idle
   ├─12591 postgres: rhnuser rhnschema 127.0.0.1(44065) idle
   ├─12592 postgres: rhnuser rhnschema 127.0.0.1(44064) idle
   ├─12593 postgres: rhnuser rhnschema 127.0.0.1(44068) idle
   ├─12594 postgres: rhnuser rhnschema 127.0.0.1(44070) idle
   ├─12762 postgres: rhnuser rhnschema 127.0.0.1(44074) idle
   ├─12867 postgres: rhnuser rhnschema 127.0.0.1(44076) idle
   ├─12868 postgres: rhnuser rhnschema 127.0.0.1(44078) idle
   ├─12869 postgres: rhnuser rhnschema 127.0.0.1(44080) idle
   ├─12870 postgres: rhnuser rhnschema 127.0.0.1(44082) idle
   ├─12871 postgres: rhnuser rhnschema 127.0.0.1(44084) idle
   ├─12872 postgres: rhnuser rhnschema 127.0.0.1(44086) idle
   ├─12873 postgres: rhnuser rhnschema 127.0.0.1(44088) idle
   ├─12874 postgres: rhnuser rhnschema 127.0.0.1(44090) idle
   ├─12875 postgres: rhnuser rhnschema 127.0.0.1(44092) idle
   ├─12876 postgres: rhnuser rhnschema 127.0.0.1(44094) idle
   ├─12877 postgres: rhnuser rhnschema 127.0.0.1(44096) idle
   ├─12878 postgres: rhnuser rhnschema 127.0.0.1(44098) idle
   ├─12879 postgres: rhnuser rhnschema 127.0.0.1(44100) idle
   ├─12880 postgres: rhnuser rhnschema 127.0.0.1(44102) idle
   ├─12881 postgres: rhnuser rhnschema 127.0.0.1(44104) idle
   ├─12887 postgres: rhnuser rhnschema 127.0.0.1(44106) idle
   ├─12888 postgres: rhnuser rhnschema 127.0.0.1(44108) idle
   ├─12889 postgres: rhnuser rhnschema 127.0.0.1(44110) idle
   ├─12890 postgres: rhnuser rhnschema 127.0.0.1(44112) idle
   ├─12891 postgres: rhnuser rhnschema 127.0.0.1(44114) idle
   ├─12930 postgres: rhnuser rhnschema 127.0.0.1(44118) idle
   ├─12931 postgres: rhnuser rhnschema 127.0.0.1(44120) idle
   ├─12941 postgres: rhnuser rhnschema 127.0.0.1(44126) idle
   ├─12942 postgres: rhnuser rhnschema 127.0.0.1(44128) idle
   └─12943 postgres: rhnuser rhnschema 127.0.0.1(44130) idle

● jabberd.service - Jabber Server
   Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled; vendor
preset: disabled)
   Active: active (exited) since Tue 2019-11-05 09:50:14 UTC; 4min 42s ago
  Process: 12486 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 12486 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/jabberd.service

● tomcat.service - Apache Tomcat Web Application Container
   Loaded: loaded (/usr/lib/systemd/system/tomcat.service; enabled; vendor
preset: disabled)
   Active: active (running) since Tue 2019-11-05 09:50:14 UTC; 4min 42s ago
 Main PID: 12480 (java)
   CGroup: /system.slice/tomcat.service
   └─12480 /usr/lib/jvm/jre/bin/java -ea -Xms256m -Xmx256m

[Spacewalk-list] osa-dispatcher.service failed

[Raymond Setchfield]

Hi All,

I have been following this guide to install the SSL certificate, and it
appears to have worked fine. As I can see the certificate when logging into
spacewalk etc.

However, when restarting the services it appears that the osa-dispatcher
has failed. There is little or no information to go with to figure out why
it has failed.

● postgresql.service - PostgreSQL database server
   Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled;
vendor preset: disabled)
   Active: active (running) since Tue 2019-11-05 09:50:15 UTC; 4min 41s ago
  Process: 12341 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
(code=exited, status=0/SUCCESS)
  Process: 12504 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
  Process: 12487 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
(code=exited, status=0/SUCCESS)
 Main PID: 12518 (postgres)
   CGroup: /system.slice/postgresql.service
   ├─12518 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
   ├─12529 postgres: logger process
   ├─12531 postgres: checkpointer process
   ├─12532 postgres: writer process
   ├─12533 postgres: wal writer process
   ├─12534 postgres: autovacuum launcher process
   ├─12535 postgres: stats collector process
   ├─12590 postgres: rhnuser rhnschema 127.0.0.1(44062) idle
   ├─12591 postgres: rhnuser rhnschema 127.0.0.1(44065) idle
   ├─12592 postgres: rhnuser rhnschema 127.0.0.1(44064) idle
   ├─12593 postgres: rhnuser rhnschema 127.0.0.1(44068) idle
   ├─12594 postgres: rhnuser rhnschema 127.0.0.1(44070) idle
   ├─12762 postgres: rhnuser rhnschema 127.0.0.1(44074) idle
   ├─12867 postgres: rhnuser rhnschema 127.0.0.1(44076) idle
   ├─12868 postgres: rhnuser rhnschema 127.0.0.1(44078) idle
   ├─12869 postgres: rhnuser rhnschema 127.0.0.1(44080) idle
   ├─12870 postgres: rhnuser rhnschema 127.0.0.1(44082) idle
   ├─12871 postgres: rhnuser rhnschema 127.0.0.1(44084) idle
   ├─12872 postgres: rhnuser rhnschema 127.0.0.1(44086) idle
   ├─12873 postgres: rhnuser rhnschema 127.0.0.1(44088) idle
   ├─12874 postgres: rhnuser rhnschema 127.0.0.1(44090) idle
   ├─12875 postgres: rhnuser rhnschema 127.0.0.1(44092) idle
   ├─12876 postgres: rhnuser rhnschema 127.0.0.1(44094) idle
   ├─12877 postgres: rhnuser rhnschema 127.0.0.1(44096) idle
   ├─12878 postgres: rhnuser rhnschema 127.0.0.1(44098) idle
   ├─12879 postgres: rhnuser rhnschema 127.0.0.1(44100) idle
   ├─12880 postgres: rhnuser rhnschema 127.0.0.1(44102) idle
   ├─12881 postgres: rhnuser rhnschema 127.0.0.1(44104) idle
   ├─12887 postgres: rhnuser rhnschema 127.0.0.1(44106) idle
   ├─12888 postgres: rhnuser rhnschema 127.0.0.1(44108) idle
   ├─12889 postgres: rhnuser rhnschema 127.0.0.1(44110) idle
   ├─12890 postgres: rhnuser rhnschema 127.0.0.1(44112) idle
   ├─12891 postgres: rhnuser rhnschema 127.0.0.1(44114) idle
   ├─12930 postgres: rhnuser rhnschema 127.0.0.1(44118) idle
   ├─12931 postgres: rhnuser rhnschema 127.0.0.1(44120) idle
   ├─12941 postgres: rhnuser rhnschema 127.0.0.1(44126) idle
   ├─12942 postgres: rhnuser rhnschema 127.0.0.1(44128) idle
   └─12943 postgres: rhnuser rhnschema 127.0.0.1(44130) idle

● jabberd.service - Jabber Server
   Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled; vendor
preset: disabled)
   Active: active (exited) since Tue 2019-11-05 09:50:14 UTC; 4min 42s ago
  Process: 12486 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 12486 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/jabberd.service

● tomcat.service - Apache Tomcat Web Application Container
   Loaded: loaded (/usr/lib/systemd/system/tomcat.service; enabled; vendor
preset: disabled)
   Active: active (running) since Tue 2019-11-05 09:50:14 UTC; 4min 42s ago
 Main PID: 12480 (java)
   CGroup: /system.slice/tomcat.service
   └─12480 /usr/lib/jvm/jre/bin/java -ea -Xms256m -Xmx256m
-Djava.awt.headless=true
-Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser
-Dorg.apache.tomcat.util.htt...

● spacewalk-wait-for-tomcat.service - Spacewalk wait for tomcat
   Loaded: loaded
(/usr/lib/systemd/system/spacewalk-wait-for-tomcat.service; static; vendor
preset: disabled)
   Active: active (exited) since Tue 2019-11-05 09:50:31 UTC; 4min 25s ago
  Process: 12481 ExecStart=/usr/sbin/spacewalk-startup-helper
wait-for-tomcat (code=exited, status=0/SUCCESS)
 Main PID: 12481 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/spacewalk-wait-for-tomcat.service

● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor
preset: disabled)
   Active: active (running) since Tue 2019-11-05 09:50:31 UTC; 4min 24s ago
 Docs: 

Re: [Spacewalk-list] Ubuntu 16.04 / 18.04 Errata

[Raymond Setchfield]

Thanks for that Robert :)

On Fri, Sep 13, 2019 at 9:20 AM Robert Paschedag 
wrote:

> I still use it on sw2.7
>
> ⁣sent from my mobile device​
>
>
>  Originale Nachricht ----
> Von: Raymond Setchfield 
> Gesendet: Fri Sep 13 09:52:39 GMT+02:00 2019
> An: spacewalk-list@redhat.com
> Betreff: Re: [Spacewalk-list] Ubuntu 16.04 / 18.04 Errata
>
> Hi Robert
>
> Thank you for that. I see that this appears to be a forked version of one I
> have mentioned. So is this still relevant? As I see it mentioned spacewalk
> 2.3 and older versions of ubuntu
>
> Ray
>
> On Thu, Sep 12, 2019 at 8:50 PM Robert Paschedag 
> wrote:
>
> > You could try my repo or the upstream fork from @philicious
> >
> > https://github.com/rpasche/spacewalk-scripts
> >
> > Robert
> >
> > ⁣sent from my mobile device​
> >
> >
> >  Originale Nachricht 
> > Von: Raymond Setchfield 
> > Gesendet: Thu Sep 12 17:17:38 GMT+02:00 2019
> > An: spacewalk-list@redhat.com
> > Betreff: [Spacewalk-list] Ubuntu 16.04 / 18.04 Errata
> >
> > Hi All,
> >
> > Just wondering if any of you have documentation on how to pull down the
> > errata for ubuntu?
> > I found a link on git but it looks a bit dated. Can this still be used? (
> > https://github.com/pandujar/spacewalk-scripts)  Or has anyone got
> > something
> > else which might be useful?
> >
> > Thanks
> >
> > Ray
> >
> >
> > 
> >
> > ___
> > 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
>
> ___
> 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] Ubuntu 16.04 / 18.04 Errata

[Raymond Setchfield]

Hi Robert

Thank you for that. I see that this appears to be a forked version of one I
have mentioned. So is this still relevant? As I see it mentioned spacewalk
2.3 and older versions of ubuntu

Ray

On Thu, Sep 12, 2019 at 8:50 PM Robert Paschedag 
wrote:

> You could try my repo or the upstream fork from @philicious
>
> https://github.com/rpasche/spacewalk-scripts
>
> Robert
>
> ⁣sent from my mobile device​
>
>
>  Originale Nachricht 
> Von: Raymond Setchfield 
> Gesendet: Thu Sep 12 17:17:38 GMT+02:00 2019
> An: spacewalk-list@redhat.com
> Betreff: [Spacewalk-list] Ubuntu 16.04 / 18.04 Errata
>
> Hi All,
>
> Just wondering if any of you have documentation on how to pull down the
> errata for ubuntu?
> I found a link on git but it looks a bit dated. Can this still be used? (
> https://github.com/pandujar/spacewalk-scripts)  Or has anyone got
> something
> else which might be useful?
>
> Thanks
>
> Ray
>
>
> 
>
> ___
> 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

[Spacewalk-list] Ubuntu 16.04 / 18.04 Errata

[Raymond Setchfield]

Hi All,

Just wondering if any of you have documentation on how to pull down the
errata for ubuntu?
I found a link on git but it looks a bit dated. Can this still be used? (
https://github.com/pandujar/spacewalk-scripts)  Or has anyone got something
else which might be useful?

Thanks

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

Re: [Spacewalk-list] Ubuntu 16.04 - OpenSCAP & OSAD

[Raymond Setchfield]

Hi All,

Can anyone assist?

I have been able to get the remote commands working, but cannot seem to
find any information on spacewalk-oscap.

Ray

On Tue, Jul 30, 2019 at 12:07 PM Raymond Setchfield <
raymond.setchfi...@gmail.com> wrote:

> Hi All,
>
> I am looking into the possibility of using spacewalk for ubuntu servers.
> So far its fine as I am able to register the servers and download packages
> etc.
>
> However, I am also looking to use remote commands and also to audit the
> servers as well. Looking through the archives and also what I can find
> online. There doesn't appear to be much information available. Can you
> please help me on how to add the servers to allow remote commands and also
> utilise the use of openSCAP scans.
>
> Thanks
>
> Ray
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Ubuntu 16.04 - OpenSCAP & OSAD

[Raymond Setchfield]

Hi All,

I am looking into the possibility of using spacewalk for ubuntu servers. So
far its fine as I am able to register the servers and download packages
etc.

However, I am also looking to use remote commands and also to audit the
servers as well. Looking through the archives and also what I can find
online. There doesn't appear to be much information available. Can you
please help me on how to add the servers to allow remote commands and also
utilise the use of openSCAP scans.

Thanks

Ray
___
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

[Raymond Setchfield]

Hi Phil

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

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

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

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

run

#> update-ca-trust


But from there I ran into authentication issues.


If you get further than I please let me know


Ray

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

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

[Spacewalk-list] Spacewalk Ubuntu kickstarts

[Raymond Setchfield]

Hi All,

Its been a while now that ubutnu has had kickstart capability, I was
wondering if there is any upgrade as to when spacewalk will allow you to do
ubuntu kickstarts without having to fudge a fix for it?

Thanks

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

Re: [Spacewalk-list] vmware snapshots

[Raymond Setchfield]

The way I would probably tackle that one is by executing via remote command
the snapshot - this will have to be a bespoke script which is written on
this machine which can speak to the API of your vcenter. I would be using
something like pyvmomi to do the execution of the snapshot, and once thats
completed to do the patch work of the machine via the remote command too.
If your hostname matches your vmware name then you could do something
smarter, but you may need to change the script for each host.

https://github.com/vmware/pyvmomi

There is probably better ways of doing this, and cleaner ways. But this is
something that I would think about doing this off the top of my head.

I hope this helps

Ray

On Sat, Nov 24, 2018 at 5:26 PM Casey Gadd  wrote:

> Is there any way to create snapshots before the patch process? We are
> using VMware.
>
>
>
> *--*
>
> *Casey H Gadd, M.S.*
>
> *Information Systems Technician*
>
> Office:  (509) 422-8495
>
> Cell:  (509) 560-0668
>
>
>
> Okanogan County Public Utility District No. 1
>
> 1331 Second Ave. N.
>
> Okanogan, WA 98840
>
>
> ___
> 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] Cobbler PXE boot.

[Raymond Setchfield]

Hi

I use this quite frequently and experienced any issues with this so far

What version are you using of spacewalk? Also is it possible to see a
screenshot was youre seeing?

Ray

On Thu, Oct 25, 2018 at 8:13 PM Máté Csörsz  wrote:

> Hi!
>
> I use CentOS7 for all my work. I made a Spacewalk server and created
> everything for kickstart installations.
>
> When PXE tries to boot from the spacewalk server I got a blue Cobbler
> screen.
> There are two options: (local) and the kickstart profile name.
> If I hit enter on the kickstart profile name nothing happens.
>
> Does anybody have any idea what causing this, where should I search for
> errors?
>
> Thanks!
> ___
> 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] RHEL repo sync error - CURL #60

[Raymond Setchfield]

Hi Robert

Thanks for the reply.

For me the RHEL subscriptions are brand new and therefore I don’t think that 
this is the problem.

I’ll look further into the SSL issue though, as that would potentially make 
sense. I thought it was just done through the subscription manager using 
username and password. 

Ray

> On 9 Oct 2018, at 19:33, Robert Paschedag  wrote:
> 
> Am 9. Oktober 2018 18:46:27 MESZ schrieb Matt Moldvan :
>> No, unfortunately, I gave up on trying a long time ago, as it seemed
>> like a
>> very hokey approach to first sync using reposync on additional VMs, run
>> createrepo, then add those as channels in Spacewalk.  Due to that and
>> other
>> cost saving initiatives, I gave up and changed our infrastructure to
>> avoid
>> using RHEL as much as possible in favor of CentOS...
> 
> I'm pretty sure, that all red hat customers here with this "SSL cert error" 
> or "403 error" while syncing repos are mixing those errors.
> 
> Note: I'm not a red hat customer. But as far as I know, red hat uses SSL 
> certificates to identify customers and grant access to the repos.
> 
> So if the access to the repos returns "403" (suddenly), maybe your 
> subscription expired. So you might need to refresh these certificates. 
> (Again, I'm not sure).
> 
> The SSL validation error (curl) is something "general".
> 
> And, I also thought, that there are rpms within the red hat repos, that 
> contain these CA certs that are used on their Webservers so the customers do 
> *not* get these "curl" errors.
> 
> Robert
>> 
>> On Tue, Oct 9, 2018 at 11:55 AM Raymond Setchfield <
>> raymond.setchfi...@gmail.com> wrote:
>> 
>>> Have you got this working, Matt?
>>> 
>>> On 9 Oct 2018, at 16:21, Matt Moldvan  wrote:
>>> 
>>> Oops, looks like my replies weren't making it to the mailing list
>> (forgot
>>> to change the "From" option).
>>> 
>>> Anyway, I intended to reply to the list and not just Robert...
>>> 
>>> On Tue, Oct 9, 2018 at 11:18 AM Matt Moldvan 
>>> wrote:
>>> 
>>>> Yeah, makes sense.  My point was that Red Hat expecting this to be
>> done
>>>> by it's customers is silly and they shouldn't be using self signed
>> certs in
>>>> the path and making their customers do extra work...
>>>> 
>>>> On Tue, Oct 9, 2018 at 9:50 AM Robert Paschedag
>> 
>>>> wrote:
>>>> 
>>>>> Am 9. Oktober 2018 15:24:55 MESZ schrieb sandwormusmc <
>>>>> sandwormu...@gmail.com>:
>>>>>> Looks like an issue Red Hat should fix, too be honest.  While you
>> could
>>>>>> pull the CA cert of the issuer and import it, I get an invalid
>> issuer
>>>>>> error when I pull up that URL in my browser, too.  So updating
>> your CA
>>>>>> certs may not help either (unless Red Hat provides the root cert
>> for
>>>>>> whomever generated the cert for cdn.redhat.com).
>>>>>> If you have a Red Hat support contract, I would open a ticket with
>> this
>>>>>> information and ask for their input.
>>>>>> 
>>>>>> 
>>>>>> Sent from my Verizon, Samsung Galaxy smartphone
>>>>>>  Original message From: "Irwin, Jeffrey"
>>>>>>  Date: 10/9/18  8:46 AM 
>> (GMT-05:00)
>>>>>> To: Robert Paschedag ,
>>>>>> spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] RHEL repo
>> sync
>>>>>> error - CURL #60
>>>>>> I have tried this with a local mirror repo..no dice, tried it
>> with
>>>>>> subscribed RHEL repo, no dice, trying to track this pesky cert
>> issue.
>>>>>> Will check out the man page and see, would be nice to see a more
>>>>>> verbose indication of what cert it is trying to use, where it is,
>> etc..
>>>>>> 
>>>>>> From: Robert Paschedag 
>>>>>> Sent: Tuesday, October 9, 2018 8:41 AM
>>>>>> To: spacewalk-list@redhat.com; Irwin, Jeffrey;
>>>>>> spacewalk-list@redhat.com
>>>>>> Subject: Re: [Spacewalk-list] RHEL repo sync error - CURL #60
>>>>>> 
>>>>>> Am 9. Oktober 2018 14:04:25 MESZ schrieb "Irwin, Jeffrey"
>>>>>> :
>>>>>>> ?Same issue I ma having, interested to see 

Re: [Spacewalk-list] RHEL repo sync error - CURL #60

[Raymond Setchfield]

Have you got this working, Matt?

> On 9 Oct 2018, at 16:21, Matt Moldvan  wrote:
> 
> Oops, looks like my replies weren't making it to the mailing list (forgot to 
> change the "From" option).
> 
> Anyway, I intended to reply to the list and not just Robert...
> 
>> On Tue, Oct 9, 2018 at 11:18 AM Matt Moldvan  wrote:
>> Yeah, makes sense.  My point was that Red Hat expecting this to be done by 
>> it's customers is silly and they shouldn't be using self signed certs in the 
>> path and making their customers do extra work...
>> 
>>> On Tue, Oct 9, 2018 at 9:50 AM Robert Paschedag  
>>> wrote:
>>> Am 9. Oktober 2018 15:24:55 MESZ schrieb sandwormusmc 
>>> :
>>> >Looks like an issue Red Hat should fix, too be honest.  While you could
>>> >pull the CA cert of the issuer and import it, I get an invalid issuer
>>> >error when I pull up that URL in my browser, too.  So updating your CA
>>> >certs may not help either (unless Red Hat provides the root cert for
>>> >whomever generated the cert for cdn.redhat.com).
>>> >If you have a Red Hat support contract, I would open a ticket with this
>>> >information and ask for their input. 
>>> >
>>> >
>>> >Sent from my Verizon, Samsung Galaxy smartphone
>>> > Original message From: "Irwin, Jeffrey"
>>> > Date: 10/9/18  8:46 AM  (GMT-05:00)
>>> >To: Robert Paschedag ,
>>> >spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] RHEL repo sync
>>> >error - CURL #60 
>>> >I have tried this with a local mirror repo..no dice, tried it with
>>> >subscribed RHEL repo, no dice, trying to track this pesky cert issue. 
>>> >Will check out the man page and see, would be nice to see a more
>>> >verbose indication of what cert it is trying to use, where it is, etc..
>>> >
>>> >From: Robert Paschedag 
>>> >Sent: Tuesday, October 9, 2018 8:41 AM
>>> >To: spacewalk-list@redhat.com; Irwin, Jeffrey;
>>> >spacewalk-list@redhat.com
>>> >Subject: Re: [Spacewalk-list] RHEL repo sync error - CURL #60
>>> >
>>> >Am 9. Oktober 2018 14:04:25 MESZ schrieb "Irwin, Jeffrey"
>>> >:
>>> >>?Same issue I ma having, interested to see the solution.
>>> >
>>> >I think manpage of update-ca-certificates should help.
>>> >
>>> >Get the issuer cert, update the local CA certs and it should run (in
>>> >case, there is no new rpm which updates the certs)
>>> >
>>> >Robert
>>> >>
>>> >>
>>> >>From: spacewalk-list-boun...@redhat.com
>>> >> on behalf of Raymond Setchfield
>>> >>
>>> >>Sent: Monday, October 8, 2018 6:47 AM
>>> >>To: spacewalk-list@redhat.com
>>> >>Subject: [Spacewalk-list] RHEL repo sync error - CURL #60
>>> >>
>>> >>Hi
>>> >>
>>> >>I have been attempting to pull the RHEL updates into spacewalk, and I
>>> >>am receiving the following error;
>>> >>
>>> >># spacewalk-repo-sync -c rhel07-update
>>> >>11:44:03 ==
>>> >>11:44:03 | Channel: rhel07-update
>>> >>11:44:03 ==
>>> >>11:44:03 Sync of channel started.
>>> >>11:44:03
>>> >>11:44:03   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
>>> >>11:44:03 ERROR: failure: repodata/repomd.xml from rhel07-update.repo:
>>> >>[Errno 256] No more mirrors to try.
>>> >>https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
>>> >>[Errno 14] curl#60 - "Peer's certificate issuer has been marked as not
>>> >>trusted by the user."
>>> >>11:44:03 Sync of channel completed in 0:00:00.
>>> >>11:44:03 Total time: 0:00:00
>>> >>
>>> >>Looking into this it appears to be a certificate issue from what I can
>>> >>gather. My assumption is to use the "redhat-uep.pem" Is this correct?
>>> >>If so where do I place this to allow the curl to work? Or am I off in
>>> >>the wrong direction
>>> >>
>>> >>Thanks
>>> >>
>>> >>Ray
>>> >
>>> >
>>> >--
>>> >sent from my mobile device
>>> >
>>> >___
>>> >Spacewalk-list mailing list
>>> >Spacewalk-list@redhat.com
>>> >https://www.redhat.com/mailman/listinfo/spacewalk-list
>>> 
>>> There is a self signed cert within the SSL path, which does not seem to be 
>>> on your cert parts.
>>> 
>>> So download the certs via the browser (export root ca and intermediate 
>>> cas), put the in the "anchors" directory  (where update-ca-trust or 
>>> update-ca-certificates wants them to be), update the certs... Then try 
>>> again.
>>> 
>>> Robert
>>> -- 
>>> sent from my mobile device
> ___
> 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] RHEL repo sync error - CURL #60

[Raymond Setchfield]

Hi mate

I pulled it from a RHEL machine which I built to see what the difference
was, and intensive googling :)

Ray

On Tue, Oct 9, 2018 at 2:15 PM Irwin, Jeffrey <
jeffrey.ir...@rivertechllc.com> wrote:

> ​Ray, Thank you..Where is this copied from?  Do you have a local repo?
> --
> *From:* spacewalk-list-boun...@redhat.com <
> spacewalk-list-boun...@redhat.com> on behalf of Raymond Setchfield <
> raymond.setchfi...@gmail.com>
> *Sent:* Tuesday, October 9, 2018 8:36 AM
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] RHEL repo sync error - CURL #60
>
> Hi Jeffrey
>
> Hopefully getting closer to resolving the problem.
>
> 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
>
> This will resolve the trust issue, but now I am receiving an issue when
> attempting to run the sync. Getting a 403 forbidden message.
>
> [root@spacewalk ~]# spacewalk-repo-sync -c rhel07-update
> 13:32:44 ==
> 13:32:44 | Channel: rhel07-update
> 13:32:44 ==
> 13:32:44 Sync of channel started.
> 13:32:44
> 13:32:44   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
> 13:32:44 ERROR: failure: repodata/repomd.xml from rhel07-update.repo:
> [Errno 256] No more mirrors to try.
> https://:@
> cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
> [Errno 14] HTTPS Error 403 - Forbidden
> 13:32:45 Sync of channel completed in 0:00:00.
> 13:32:45 Total time: 0:00:00
> [root@spacewalk ~]#
>
> Thanks
>
> Ray
>
>
> On Tue, Oct 9, 2018 at 1:05 PM Irwin, Jeffrey <
> jeffrey.ir...@rivertechllc.com> wrote:
>
>> ​Same issue I ma having, interested to see the solution.
>> --
>> *From:* spacewalk-list-boun...@redhat.com <
>> spacewalk-list-boun...@redhat.com> on behalf of Raymond Setchfield <
>> raymond.setchfi...@gmail.com>
>> *Sent:* Monday, October 8, 2018 6:47 AM
>> *To:* spacewalk-list@redhat.com
>> *Subject:* [Spacewalk-list] RHEL repo sync error - CURL #60
>>
>> Hi
>>
>> I have been attempting to pull the RHEL updates into spacewalk, and I am
>> receiving the following error;
>>
>> # spacewalk-repo-sync -c rhel07-update
>> 11:44:03 ==
>> 11:44:03 | Channel: rhel07-update
>> 11:44:03 ==
>> 11:44:03 Sync of channel started.
>> 11:44:03
>> 11:44:03   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
>> 11:44:03 ERROR: failure: repodata/repomd.xml from rhel07-update.repo:
>> [Errno 256] No more mirrors to try.
>>
>> https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
>> [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not
>> trusted by the user."
>> 11:44:03 Sync of channel completed in 0:00:00.
>> 11:44:03 Total time: 0:00:00
>>
>> Looking into this it appears to be a certificate issue from what I can
>> gather. My assumption is to use the "redhat-uep.pem" Is this correct? If so
>> where do I place this to allow the curl to work? Or am I off in the wrong
>> direction
>>
>> Thanks
>>
>> Ray
>>
>>
>>
>>
>> ___
>> 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] RHEL repo sync error - CURL #60

[Raymond Setchfield]

Hi Robert

>From my previous mail. I have got that working fine :)

Just forbidden now. Are you aware of anything which I am potentially
missing?

Ray

On Tue, Oct 9, 2018 at 1:41 PM Robert Paschedag 
wrote:

> Am 9. Oktober 2018 14:04:25 MESZ schrieb "Irwin, Jeffrey" <
> jeffrey.ir...@rivertechllc.com>:
> >?Same issue I ma having, interested to see the solution.
>
> I think manpage of update-ca-certificates should help.
>
> Get the issuer cert, update the local CA certs and it should run (in case,
> there is no new rpm which updates the certs)
>
> Robert
> >
> >____
> >From: spacewalk-list-boun...@redhat.com
> > on behalf of Raymond Setchfield
> >
> >Sent: Monday, October 8, 2018 6:47 AM
> >To: spacewalk-list@redhat.com
> >Subject: [Spacewalk-list] RHEL repo sync error - CURL #60
> >
> >Hi
> >
> >I have been attempting to pull the RHEL updates into spacewalk, and I
> >am receiving the following error;
> >
> ># spacewalk-repo-sync -c rhel07-update
> >11:44:03 ==
> >11:44:03 | Channel: rhel07-update
> >11:44:03 ==
> >11:44:03 Sync of channel started.
> >11:44:03
> >11:44:03   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
> >11:44:03 ERROR: failure: repodata/repomd.xml from rhel07-update.repo:
> >[Errno 256] No more mirrors to try.
> >
> https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml
> :
> >[Errno 14] curl#60 - "Peer's certificate issuer has been marked as not
> >trusted by the user."
> >11:44:03 Sync of channel completed in 0:00:00.
> >11:44:03 Total time: 0:00:00
> >
> >Looking into this it appears to be a certificate issue from what I can
> >gather. My assumption is to use the "redhat-uep.pem" Is this correct?
> >If so where do I place this to allow the curl to work? Or am I off in
> >the wrong direction
> >
> >Thanks
> >
> >Ray
>
>
> --
> sent from my mobile device
>
> ___
> 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] RHEL repo sync error - CURL #60

[Raymond Setchfield]

Hi Jeffrey

Hopefully getting closer to resolving the problem.

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

This will resolve the trust issue, but now I am receiving an issue when
attempting to run the sync. Getting a 403 forbidden message.

[root@spacewalk ~]# spacewalk-repo-sync -c rhel07-update
13:32:44 ==
13:32:44 | Channel: rhel07-update
13:32:44 ==
13:32:44 Sync of channel started.
13:32:44
13:32:44   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
13:32:44 ERROR: failure: repodata/repomd.xml from rhel07-update.repo:
[Errno 256] No more mirrors to try.
https://:@
cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] HTTPS Error 403 - Forbidden
13:32:45 Sync of channel completed in 0:00:00.
13:32:45 Total time: 0:00:00
[root@spacewalk ~]#

Thanks

Ray


On Tue, Oct 9, 2018 at 1:05 PM Irwin, Jeffrey <
jeffrey.ir...@rivertechllc.com> wrote:

> ​Same issue I ma having, interested to see the solution.
> --
> *From:* spacewalk-list-boun...@redhat.com <
> spacewalk-list-boun...@redhat.com> on behalf of Raymond Setchfield <
> raymond.setchfi...@gmail.com>
> *Sent:* Monday, October 8, 2018 6:47 AM
> *To:* spacewalk-list@redhat.com
> *Subject:* [Spacewalk-list] RHEL repo sync error - CURL #60
>
> Hi
>
> I have been attempting to pull the RHEL updates into spacewalk, and I am
> receiving the following error;
>
> # spacewalk-repo-sync -c rhel07-update
> 11:44:03 ==
> 11:44:03 | Channel: rhel07-update
> 11:44:03 ==
> 11:44:03 Sync of channel started.
> 11:44:03
> 11:44:03   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
> 11:44:03 ERROR: failure: repodata/repomd.xml from rhel07-update.repo:
> [Errno 256] No more mirrors to try.
>
> https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
> [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not
> trusted by the user."
> 11:44:03 Sync of channel completed in 0:00:00.
> 11:44:03 Total time: 0:00:00
>
> Looking into this it appears to be a certificate issue from what I can
> gather. My assumption is to use the "redhat-uep.pem" Is this correct? If so
> where do I place this to allow the curl to work? Or am I off in the wrong
> direction
>
> Thanks
>
> Ray
>
>
>
>
> ___
> 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] RHEL repo sync error - CURL #60

[Raymond Setchfield]

Hi

I have been attempting to pull the RHEL updates into spacewalk, and I am
receiving the following error;

# spacewalk-repo-sync -c rhel07-update
11:44:03 ==
11:44:03 | Channel: rhel07-update
11:44:03 ==
11:44:03 Sync of channel started.
11:44:03
11:44:03   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
11:44:03 ERROR: failure: repodata/repomd.xml from rhel07-update.repo:
[Errno 256] No more mirrors to try.
https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml:
[Errno 14] curl#60 - "Peer's certificate issuer has been marked as not
trusted by the user."
11:44:03 Sync of channel completed in 0:00:00.
11:44:03 Total time: 0:00:00

Looking into this it appears to be a certificate issue from what I can
gather. My assumption is to use the "redhat-uep.pem" Is this correct? If so
where do I place this to allow the curl to work? Or am I off in the wrong
direction

Thanks

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

Re: [Spacewalk-list] RHEL 7 - Spacewalk

[Raymond Setchfield]

Thanks for the clarification and the answer from RedHat.


Does anyone have a how to guide on adding this into spacewalk?


Ray


Op Donderdag, 13-09-2018 om 08:41 schreef Andrei Popenta:

> Hi,

>

> I've opened a case at redhat and asked them about this.

> here is their answer:

>

> Getting back to you question "Is it ok to sync RHEL channels in

> Spacewalk and use that to manage updates for servers running rhel or

> is this considered to be a license infringement ?"

> Answer: Systems will be under no support from Red Hat if you are

> updating them from upstream spacewalk.

>

> BR,

> Andrei



Seems like too easy an answer. I don't recall reading anywhere that Red Hat
can dictate which package distribution tool you use on your end. They even
document how to make a local repository for internal distribution of
packages, so whether or not you do that via spacewalk should then be none
of their concern.

I think that as long as you pay your license fee and you install official
Red Hat packages, Red Hat must provide you with the support you paid for. I
never received the question from Red Hat on "how I updated a server", but
if relevant "did you update the server".



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

Re: [Spacewalk-list] Scheduling update for updating the packages in spacewalk

[Raymond Setchfield]

Francis

Are you referring to upgrading individual hosts via a schedule?

You can do this via the Systems > Software > Upgrade/Install Packages

>From there you should be able to schedule the installation

I hope this helps

Ray

On Thu, Sep 13, 2018 at 12:09 AM Yakin, Francis 
wrote:

>
>
> Hello All,
>
>
>
>
>
> I understand there is lock/unlock feature on the system, so the system
> doesn’t get any update from the repository.
>
>
>
> Is there anyway to setup  a schedule in spacewalk for updating the
> patches/packages from repository.
>
>
>
> Thanks
>
>
>
>
>
> Francis Yakin | IT System Admin |  direct: 510-749-2027
>
> 500 Wind River Way, Alameda, CA  94501
>
> [image: cid:image001.png@01D12D0C.E17713F0] 
>
>
>
>
> ___
> 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] GPG Key Error

[Raymond Setchfield]

Hi All,

I recently added a new channel which I forgot to put the GPG key into. I
have now added it to the channel, but for some reason any new servers using
this channel are still complaining about not importing the GPG key.

Is there a step which I am missing to ensure that the GPG key is used by
server instead of manually importing it into the server/host?

Thanks

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

[Spacewalk-list] RHEL 7 - Spacewalk

[Raymond Setchfield]

Hi Everyone

Does anyone have a guide to pull RHEL 7 packages into spacewalk? Also is
there a particular license you need to do the pull or can you use a normal
subscription license?

Thanks

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

Re: [Spacewalk-list] Kickstart Template Issues

[Raymond Setchfield]

Thank you Colin

I'll review your comments, and give them a try. Again, thanks for you help
on this matter

Ray

On Fri, Aug 24, 2018 at 1:29 PM Colin Coe  wrote:

> Or if you're are not using any of the templating functionality, un-check
> the 'template' check box on the script page
> https://sat.server.com/rhn/kickstart/KickstartScriptEdit.do
>
> On Fri, Aug 24, 2018 at 8:27 PM Colin Coe  wrote:
>
>> Or, if you are not using snippets, wrap the code in
>>
>> #raw
>> code here
>> #end raw
>>
>> On Fri, Aug 24, 2018 at 8:25 PM Colin Coe  wrote:
>>
>>> Yes, try that
>>>
>>> On Fri, Aug 24, 2018 at 8:24 PM Raymond Setchfield <
>>> raymond.setchfi...@gmail.com> wrote:
>>>
>>>> Hi Colin
>>>>
>>>> Thank you for your assistance on this. Yes, its all very fustrating,
>>>> especially when you can't figure out what is actually wrong :)
>>>>
>>>> Are you suggesting that removing $() and replacing it with just ``?
>>>>
>>>> Thanks
>>>>
>>>> Ray
>>>>
>>>> On Fri, Aug 24, 2018 at 5:59 AM Colin Coe  wrote:
>>>>
>>>>> Hmm, I just got this in one of my kickstart profiles when using
>>>>> "$(something)".  If I change it to "`something`" then the error goes 
>>>>> away...
>>>>>
>>>>> On Fri, Aug 24, 2018 at 8:34 AM Colin Coe  wrote:
>>>>>
>>>>>> Historically, I see this when I comment out some shell script, like:
>>>>>>
>>>>>> #if sometest
>>>>>>
>>>>>> The fix to the above is to a space between the hash and 'if' like
>>>>>> below:
>>>>>>
>>>>>> # if sometest
>>>>>>
>>>>>>
>>>>>>
>>>>>> I couldn't see anything obvious so I created a new kickstart profile
>>>>>> on my Satellite v5.8 system using your post script.  There were no
>>>>>> templating errors.
>>>>>>
>>>>>> Sorry, I know this isn't that helpful...
>>>>>>
>>>>>> CC
>>>>>>
>>>>>>
>>>>>> On Thu, Aug 23, 2018 at 6:43 PM Raymond Setchfield <
>>>>>> raymond.setchfi...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> I am experiencing some problems around the kickstart templates, and
>>>>>>> I am attempting to following the guidelines, but it looks like I am 
>>>>>>> still
>>>>>>> running into problems.
>>>>>>>
>>>>>>> I am receiving an error message of;
>>>>>>> # There is a templating error preventing this file from rendering
>>>>>>> correctly.
>>>>>>> #
>>>>>>> # This is most likely not due to a bug in Cobbler and is something
>>>>>>> you can fix.
>>>>>>> #
>>>>>>> # Look at the message below to see what things are causing
>>>>>>> problems.
>>>>>>> #
>>>>>>> # (1) Does the template file reference a $variable that is not
>>>>>>> defined?
>>>>>>> # (2) is there a formatting error in a Cheetah directive?
>>>>>>> # (3) Should dollar signs ($) be escaped that are not being escaped?
>>>>>>> #
>>>>>>> # Try fixing the problem and then investigate to see if this message
>>>>>>> goes
>>>>>>> # away or changes.
>>>>>>> #
>>>>>>> #
>>>>>>> # unexpected EOF while parsing (, line 1)
>>>>>>> #   File "/usr/lib/python2.7/site-packages/cobbler/templar.py", line
>>>>>>> 142, in render
>>>>>>> # data_out = t.respond()
>>>>>>> #
>>>>>>> #   File
>>>>>>> "cheetah_DynamicallyCompiledCheetahTemplate_1535020182_58_55849.py", 
>>>>>>> line
>>>>>>> 445, in respond
>>>>>>> #
>>>>>>> #   File
>>>>>>> "cheetah_DynamicallyCompiledCheetahTemplate_1535020182_58_55849.py", 
>>>>>>> line
>>>>>>> 77, in __errorCatcher2
>>>>>>> #
>>>>>>>
>>>>>>> Is it possible someone could please have a look at the kickstart
>>>>>>> template I am attempting to use, or could someone please share a 
>>>>>>> template
>>>>>>> which they are using which has variables etc. So at least I can take a 
>>>>>>> look
>>>>>>> at possible issues of where I am going wrong?
>>>>>>>
>>>>>>> Many Thanks
>>>>>>>
>>>>>>> Ray
>>>>>>> ___
>>>>>>> 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
>>>
>>> ___
> 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] Kickstart Template Issues

[Raymond Setchfield]

Hi Colin

Thank you for your assistance on this. Yes, its all very fustrating,
especially when you can't figure out what is actually wrong :)

Are you suggesting that removing $() and replacing it with just ``?

Thanks

Ray

On Fri, Aug 24, 2018 at 5:59 AM Colin Coe  wrote:

> Hmm, I just got this in one of my kickstart profiles when using
> "$(something)".  If I change it to "`something`" then the error goes away...
>
> On Fri, Aug 24, 2018 at 8:34 AM Colin Coe  wrote:
>
>> Historically, I see this when I comment out some shell script, like:
>>
>> #if sometest
>>
>> The fix to the above is to a space between the hash and 'if' like below:
>>
>> # if sometest
>>
>>
>>
>> I couldn't see anything obvious so I created a new kickstart profile on
>> my Satellite v5.8 system using your post script.  There were no templating
>> errors.
>>
>> Sorry, I know this isn't that helpful...
>>
>> CC
>>
>>
>> On Thu, Aug 23, 2018 at 6:43 PM Raymond Setchfield <
>> raymond.setchfi...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> I am experiencing some problems around the kickstart templates, and I am
>>> attempting to following the guidelines, but it looks like I am still
>>> running into problems.
>>>
>>> I am receiving an error message of;
>>> # There is a templating error preventing this file from rendering
>>> correctly.
>>> #
>>> # This is most likely not due to a bug in Cobbler and is something you
>>> can fix.
>>> #
>>> # Look at the message below to see what things are causing problems.
>>> #
>>> # (1) Does the template file reference a $variable that is not defined?
>>> # (2) is there a formatting error in a Cheetah directive?
>>> # (3) Should dollar signs ($) be escaped that are not being escaped?
>>> #
>>> # Try fixing the problem and then investigate to see if this message goes
>>> # away or changes.
>>> #
>>> #
>>> # unexpected EOF while parsing (, line 1)
>>> #   File "/usr/lib/python2.7/site-packages/cobbler/templar.py", line
>>> 142, in render
>>> # data_out = t.respond()
>>> #
>>> #   File
>>> "cheetah_DynamicallyCompiledCheetahTemplate_1535020182_58_55849.py", line
>>> 445, in respond
>>> #
>>> #   File
>>> "cheetah_DynamicallyCompiledCheetahTemplate_1535020182_58_55849.py", line
>>> 77, in __errorCatcher2
>>> #
>>>
>>> Is it possible someone could please have a look at the kickstart
>>> template I am attempting to use, or could someone please share a template
>>> which they are using which has variables etc. So at least I can take a look
>>> at possible issues of where I am going wrong?
>>>
>>> Many Thanks
>>>
>>> Ray
>>> ___
>>> 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

[Spacewalk-list] Kickstart Template Issues

[Raymond Setchfield]

Hi All,

I am experiencing some problems around the kickstart templates, and I am
attempting to following the guidelines, but it looks like I am still
running into problems.

I am receiving an error message of;
# There is a templating error preventing this file from rendering
correctly.
#
# This is most likely not due to a bug in Cobbler and is something you can
fix.
#
# Look at the message below to see what things are causing problems.
#
# (1) Does the template file reference a $variable that is not defined?
# (2) is there a formatting error in a Cheetah directive?
# (3) Should dollar signs ($) be escaped that are not being escaped?
#
# Try fixing the problem and then investigate to see if this message goes
# away or changes.
#
#
# unexpected EOF while parsing (, line 1)
#   File "/usr/lib/python2.7/site-packages/cobbler/templar.py", line 142,
in render
# data_out = t.respond()
#
#   File
"cheetah_DynamicallyCompiledCheetahTemplate_1535020182_58_55849.py", line
445, in respond
#
#   File
"cheetah_DynamicallyCompiledCheetahTemplate_1535020182_58_55849.py", line
77, in __errorCatcher2
#

Is it possible someone could please have a look at the kickstart template I
am attempting to use, or could someone please share a template which they
are using which has variables etc. So at least I can take a look at
possible issues of where I am going wrong?

Many Thanks

Ray


kickstart.ks
Description: Binary data
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Kickstart Templates - Import Error

[Raymond Setchfield]

Hi

Still having difficulties with the kickstart template which I am importing.
I have received the following error;

# *** ERROR ***
#
# There is a templating error preventing this file from rendering
correctly.
#
# This is most likely not due to a bug in Cobbler and is something you can
fix.
#
# Look at the message below to see what things are causing problems.
#
# (1) Does the template file reference a $variable that is not defined?
# (2) is there a formatting error in a Cheetah directive?
# (3) Should dollar signs ($) be escaped that are not being escaped?
#
# Try fixing the problem and then investigate to see if this message goes
# away or changes.
#
#
# invalid syntax (, line 1)
#   File "/usr/lib/python2.7/site-packages/cobbler/templar.py", line 142,
in render
# data_out = t.respond()
#
#   File
"cheetah_DynamicallyCompiledCheetahTemplate_1534333865_22_95256.py", line
559, in respond
#
#   File
"cheetah_DynamicallyCompiledCheetahTemplate_1534333865_22_95256.py", line
91, in __errorCatcher4
#

I have attached the kickstart which I am attempting to import. Any help
would be greatly appreciated

Ray
# Kickstart Template Based on CIS (Centre for Internet Security)
# This kickstart conforms to the stardard on benchmark version 2.1.1
# Raymond Setchfield
# Date 13/08/18
#


install
lang en_GB.UTF-8
keyboard --vckeymap=uk --xlayouts='uk'
timezone Europe/London --isUtc
auth --useshadow --passalgo=sha512  # CIS 5.3.4
firewall --enabled
services --enabled=NetworkManager,sshd
eula --agreed
ignoredisk --only-use=sda
reboot

bootloader --location=mbr --append=" crashkernel=auto"
zerombr
clearpart --all --initlabel
part swap --asprimary --fstype="swap" --recommended
part /boot --fstype xfs --size=1024
part pv.01 --size=1 --grow
volgroup vg_root pv.01
logvol / --fstype xfs --name=root --vgname=vg_root --size=5120 --grow
# CIS 1.1.2-1.1.5
logvol /tmp --vgname vg_root --name tmp --size=500 
--fsoptions="nodev,nosuid,noexec"
# CIS 1.1.11
logvol /var/log --vgname vg_root --name log --size=1024
# CIS 1.1.12
logvol /var/log/audit --vgname vg_root --name audit --size=1024
# CIS 1.1.13-1.1.14
logvol /home --vgname vg_root --name home --size=1024 --fsoptions="nodev"

rootpw yourpasswordhere

cdrom

%packages --ignoremissing
@core
aide# CIS 1.3.1
tcp_wrappers# CIS 3.4
rsyslog # CIS 4.2.1
#cronie-anacron
-setroubleshoot # CIS 1.6.1.4
-mcstrans   # CIS 1.6.1.5
-telnet # CIS 2.3.4
-rsh-server # CIS 2.2.17
-rsh# CIS 2.3.2
-ypbind # CIS 2.1.1
-ypserv # CIS 2.2.16
-tftp   # CIS 2.1.7
-tftp-server# CIS 2.2.20
-talk   # CIS 2.3.3
-talk-server# CIS 2.2.18
-xinetd # CIS 2.1.7
-xorg-x11-server-common # CIS 2.2.2
-avahi-daemon   # CIS 2.2.3
-cups   # CIS 2.2.4
-dhcp   # CIS 2.2.5
-openldap   # CIS 2.2.6
%end

%post --log=/root/postinstall.log

###
# /etc/fstab
# CIS 1.1.6 + 1.1.15-1.1.17
cat << EOF >> /etc/fstab
/tmp  /var/tmpnonebind0 0
none/dev/shmtmpfs   nosuid,nodev,noexec 0 0
EOF

###

# Disable mounting of unneeded filesystems CIS 1.1.1 and CIS 3.5
cat << EOF >> /etc/modprobe.d/CIS.conf
install cramfs /bin/true
install freevxfs /bin/true
install jffs2 /bin/true
install hfs /bin/true
install hfsplus /bin/true
install squashfs /bin/true
install udf /bin/true
install dccp /bin/true
install sctp /bin/true
install rds /bin/true
install tipc /bin/true
EOF

df --local -P | awk {'if (NR!=1) print $6'} | xargs -I '{}' find '{}' -xdev 
-type d \( -perm -0002 -a ! -perm -1000 \) 2>/dev/null | xargs chmod a+t

rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release# CIS 1.2.3

systemctl enable firewalld  # CIS 3.6
systemctl enable rsyslog# CIS 4.2.1.1
systemctl enable auditd # CIS 4.1.2
systemctl enable crond  # CIS 5.1.1

# Set bootloader password   # CIS 1.5.3
# qwe123#@!
cat << EOF2 >> /etc/grub.d/01_users
#!/bin/sh -e

cat << EOF
set superusers="bootuser"
password_pbkdf2 bootuser 
grub.pbkdf2.sha512.1.44D91DCFB72B53F27C58A4EAEBF29A210CB57469FB5CAA8935585856232A6CE70A2B58CE8BBAF7A9618848836F1793EC575AD1BF5959472D3AA5ECB6A05C92D2.89E0A18B9AB9080642209EAC8FC69CB988062579B68C27A16281900FFC79CE60AE1155409F78DDCFC92C40FF87A7C2F5A80899515B5CF9D15044E34658CBBD

[Spacewalk-list] Kickstart Import Error

[Raymond Setchfield]

Hi all,

I was wondering if you could assist with this import, and advise why it is
possibly not working;

:

Long-form placeholders - ${}, $(), $[], etc. are not valid inside
expressions. Use them in top-level $placeholders only.
Line 303, column 45

Line|Cheetah Code
|-
300 |sed -i 's/\#PermitEmptyPasswords no/PermitEmptyPasswords no/'
${sshd_config} # CIS 5.2.9
301 |sed -i 's/\#PermitUserEnvironment no/PermitUserEnvironment no/'
${sshd_config} # CIS 5.2.10
302 |
303 |line_num=$(grep -n "^\# Ciphers and keying" ${sshd_config} | cut -d:
-f1)
 ^
304 |sed -i '${line_num} a MACs hmac-sha1-...@openssh.com,
umac-64-...@openssh.com,umac-128-...@openssh.com,
hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,
hmac-ripemd160-...@openssh.com,hmac-sha1,umac...@openssh.com,
umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160'
${sshd_config}  # CIS 5.2.12
305 |sed -i '${line_num} a Ciphers aes128-ctr,aes192-ctr,aes256-ctr'
${sshd_config}  # CIS 5.2.11
306 |

I have attached the kickstart for you to review if needed

Thanks

Ray


kickstart.ks
Description: Binary data
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Setting up Cobbler - URL redirect on the steps

[Raymond Setchfield]

Hi Avi

Thanks for that information. My question then really is, considering that
the information on the github page is out of date, is this something which
wont be with us that much longer? As I dont want to invest too much time on
something which eventually be a dead technology?

Thanks

Ray

On Tue, Jun 19, 2018 at 9:30 PM Avi Miller  wrote:

> Hi,
>
> On 19 Jun 2018, at 7:32 pm, Raymond Setchfield <
> raymond.setchfi...@gmail.com> wrote:
>
> The link I used is this one
> https://github.com/spacewalkproject/spacewalk/wiki/HowToKickstartCobbler
>
>
> That's woefully out of date, I'm afraid.
>
> Try this instead:
> https://docs.oracle.com/cd/E92593_01/E90694/html/swk24-provclisys.html --
> you'll need to tweak things if you're not using Oracle Linux as the client,
> but otherwise it should work a lot smoother. All the required RPMs are now
> part of the Spacewalk client repos, you don't need to find/install them
> manually or anything like that.
>
> Cheers,
> Avi
>
> --
> Oracle <http://www.oracle.com>
> Avi Miller | Product Management Director | +61 (3) 8616 3496
> Oracle Linux and Virtualization
> 417 St Kilda Road, Melbourne, Victoria 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] Setting up Cobbler - URL redirect on the steps

[Raymond Setchfield]

Hi Avi

The link I used is this one
https://github.com/spacewalkproject/spacewalk/wiki/HowToKickstartCobbler

Ray

On Mon, Jun 18, 2018 at 10:06 PM Avi Miller  wrote:

> Hi,
>
> > On 18 Jun 2018, at 8:31 pm, Raymond Setchfield <
> raymond.setchfi...@gmail.com> wrote:
> >
> > I am following the how to guide on github and when I have came to the
> following step;
>
> Which how-to guide? I ask so that the link can be reviewed and fixed.
>
> > Can someone please advise as to where to find the packages to download.
>
> All the server and client packages have moved to COPR:
>
> https://copr-be.cloud.fedoraproject.org/archive/spacewalk/
>
> Thanks,
> Avi
>
> --
> Oracle <http://www.oracle.com>
> Avi Miller | Product Management Director | +61 (3) 8616 3496
> Oracle Linux and Virtualization
> 417 St Kilda Road, Melbourne, Victoria 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] Setting up Cobbler - URL redirect on the steps

[Raymond Setchfield]

Hi

I am following the how to guide on github and when I have came to the
following step;


   1. Download the following packages from the client repo here
   http://spacewalk.redhat.com/yum/:


   - pyOpenSSL (in rawhide for F11)
   - rhnlib (in rawhide for F11)
   - libxml2-python (in rawhide for F11)
   - spacewalk-koan*

It seems that the URL doesn't show those packages to download.It takes you
to the following URL;
https://spacewalkproject.github.io/

Can someone please advise as to where to find the packages to download.

Thanks

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

Re: [Spacewalk-list] Cobbler Invalid Profile Name

[Raymond Setchfield]

Hi Robert

Thanks for the reply, but yes found the error of my ways. There was a
missing "-" in my addition :(

Sorry about that

Ray

On Tue, May 22, 2018 at 1:17 PM, Paschedag, Robert <
paschedag.netlut...@swr.de> wrote:

>
>
>
> --
> *Von:* spacewalk-list-boun...@redhat.com <spacewalk-list-bounces@
> redhat.com> im Auftrag von Raymond Setchfield <
> raymond.setchfi...@gmail.com>
> *Gesendet:* Dienstag, 22. Mai 2018 12:04
> *An:* spacewalk-list@redhat.com
> *Betreff:* [Spacewalk-list] Cobbler Invalid Profile Name
>
> Hi all,
>
> I am having an issue with cobbler and showing invalid profile name. I have
> set this one up just like CentOS7 which is working fine, but it doesn't
> seem to want to accept rhel7 for some reason. Is there something which I am
> doing wrong?
>
>
> [root@spacewalk-test ~]# cobbler distro list
>centos07-base:1:Company
>rhel-base:1:Company
> [root@spacewalk-test ~]# cobbler system add --name test-rhel --mac
> 00:50:56:aa:aa:aa --profile rhel-base:1:Company
> invalid profile name: rhel-base:1:Company
> [root@spacewalk-test ~]#
>
> I have done a cobbler sync, restart etc for no luck
>
> Any ideas as to what I am doing wrong?
>
> Ray
>
> Wellwhat does "cobbler profile list" say?
>
> Robert
>
>
> ___
> 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] Cobbler Invalid Profile Name

[Raymond Setchfield]

Hi all,

I am having an issue with cobbler and showing invalid profile name. I have
set this one up just like CentOS7 which is working fine, but it doesn't
seem to want to accept rhel7 for some reason. Is there something which I am
doing wrong?


[root@spacewalk-test ~]# cobbler distro list
   centos07-base:1:Company
   rhel-base:1:Company
[root@spacewalk-test ~]# cobbler system add --name test-rhel --mac
00:50:56:aa:aa:aa --profile rhel-base:1:Company
invalid profile name: rhel-base:1:Company
[root@spacewalk-test ~]#

I have done a cobbler sync, restart etc for no luck

Any ideas as to what I am doing wrong?

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

[Spacewalk-list] Cobbler Error

[Raymond Setchfield]

Hi All,

I followed the how to on the github website and came across a couple of
errors;

When doing a "cobbler check" it states that its missing the
"cobbler-loaders" when I tried to install this. I am receiving the
following error message;

Loaded plugins: fastestmirror
Repository group_spacewalkproject-java-packages is listed more than once in
the configuration
Loading mirror speeds from cached hostfile
 * base: mirror.as29550.net
 * extras: mirror.vorboss.net
 * updates: mirror.econdc.com
Resolving Dependencies
--> Running transaction check
---> Package cobbler-loaders.noarch 0:1.0.3-2.el7.centos will be installed
--> Processing Dependency: cobbler2 for package:
cobbler-loaders-1.0.3-2.el7.centos.noarch
--> Running transaction check
---> Package cobbler-epel.noarch 0:2.0.11-77.el7.centos will be installed
--> Processing Dependency: cobbler >= 2.2 for package:
cobbler-epel-2.0.11-77.el7.centos.noarch
--> Finished Dependency Resolution
Error: Package: cobbler-epel-2.0.11-77.el7.centos.noarch (spacewalk)
   Requires: cobbler >= 2.2
   Installed: cobbler20-2.0.11-77.el7.centos.noarch (@spacewalk)
   cobbler = 2.0.11-77.el7.centos
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


According to the bug I found, this was resolved in 2.8, but still receiving
the error;
#> rpm -qa | grep spacewalk
spacewalk-usix-2.8.3-1.el7.centos.noarch

Can anyone help with this error?

Thanks

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

[Spacewalk-list] Cobbler UI

[Raymond Setchfield]

Hi all,

With cobbler being integrated with spacewalk, is the GUI in use in anyway
shape or form? I see you can manage the kickstart files within spacewalk,
but wondering if you can for the ISO, interfaces it PXE from etc?

Or is this done only from the CLI?

Thanks

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

Re: [Spacewalk-list] How to confirm that spacewalk is fetching updates (for mitigating meltdown bug)

[Raymond Setchfield]

Thanks for that Michael. Will continue to diagnose and troubleshoot from
this end.

On Mon, Jan 15, 2018 at 9:41 AM, Michael Mraka <michael.mr...@redhat.com>
wrote:

> Raymond Setchfield:
> > Hi Michael
> >
> > I have been keeping an eye out on the updates, but cannot see them on
> > spacewalk
> >
> > kernel versions which the servers are running
> > 2.6.32-696.16.1.el6.x86_64 -centos6
> > 3.10.0-693.11.1.el7.x86_64 - centos7
>
> Hi Raymond,
>
> I can see packages at
> http://mirror.centos.org/centos-6/6/updates/x86_64/Packages/
>  [ ] kernel-2.6.32-696.18.7.el6.x86_64.rpm   04-Jan-2018 19:42 32M
> http://mirror.centos.org/centos-7/7/updates/x86_64/Packages/
>  [ ] kernel-3.10.0-693.11.6.el7.x86_64.rpm   2018-01-04 10:24 43M
>
> Could the mirror you sync from be outdated?
>
> > There is no updates available to the centos6 server, but there is for
> > centos 7. However, this appears to ext updates (e2fsprogs)
> >
> > Ray
> >
> >
> > On Mon, Jan 15, 2018 at 9:22 AM, Michael Mraka <michael.mr...@redhat.com
> >
> > wrote:
> >
> > > Raymond Setchfield:
> > > > Hi
> > > >
> > > > Our spacewalk server is still currently in development, along with
> two
> > > > servers, a Centos6 and a Centos7 box. These haven't been patched
> before
> > > the
> > > > meltdown issue came about.
> > > >
> > > > Been looking out for the patches and kernels coming through, but I
> do see
> > > > these coming through on spacewalk, however not seeing the kernel
> patches
> > > > which should be there? Is anyone else experiencing this problem? Or
> am I
> > > > looking for the wrong updates here? Updates are scheduled weekly and
> > > should
> > > > have at least picked this up twice now?
> > >
> > > Hi Raymond,
> > >
> > > Fixes for meltdown bug went live in
> > > CESA-2018:0007 for CentOS 7  (kernel-3.10.0-693.11.6.el7)
> > > CESA-2018:0008 for CentOS 6  (kernel-2.6.32-696.18.7.el6)
> > > Check than you have appropriate erratum / kernel version installed.
> > >
> > > > Base/EPEL/Extra is the channels that I have subscribed to
> > > >
> > > > Thanks
> > > >
> > > > Ray
> > >
> > > Regards,
> > >
> > > --
> > > Michael Mráka
> > > System Management Engineering, Red Hat
>
> 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] How to confirm that spacewalk is fetching updates (for mitigating meltdown bug)

[Raymond Setchfield]

Hi Michael

I have been keeping an eye out on the updates, but cannot see them on
spacewalk

kernel versions which the servers are running
2.6.32-696.16.1.el6.x86_64 -centos6
3.10.0-693.11.1.el7.x86_64 - centos7

There is no updates available to the centos6 server, but there is for
centos 7. However, this appears to ext updates (e2fsprogs)

Ray


On Mon, Jan 15, 2018 at 9:22 AM, Michael Mraka <michael.mr...@redhat.com>
wrote:

> Raymond Setchfield:
> > Hi
> >
> > Our spacewalk server is still currently in development, along with two
> > servers, a Centos6 and a Centos7 box. These haven't been patched before
> the
> > meltdown issue came about.
> >
> > Been looking out for the patches and kernels coming through, but I do see
> > these coming through on spacewalk, however not seeing the kernel patches
> > which should be there? Is anyone else experiencing this problem? Or am I
> > looking for the wrong updates here? Updates are scheduled weekly and
> should
> > have at least picked this up twice now?
>
> Hi Raymond,
>
> Fixes for meltdown bug went live in
> CESA-2018:0007 for CentOS 7  (kernel-3.10.0-693.11.6.el7)
> CESA-2018:0008 for CentOS 6  (kernel-2.6.32-696.18.7.el6)
> Check than you have appropriate erratum / kernel version installed.
>
> > Base/EPEL/Extra is the channels that I have subscribed to
> >
> > Thanks
> >
> > Ray
>
> 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] How to confirm that spacewalk is fetching updates (for mitigating meltdown bug)

[Raymond Setchfield]

Hi

Our spacewalk server is still currently in development, along with two
servers, a Centos6 and a Centos7 box. These haven't been patched before the
meltdown issue came about.

Been looking out for the patches and kernels coming through, but I do see
these coming through on spacewalk, however not seeing the kernel patches
which should be there? Is anyone else experiencing this problem? Or am I
looking for the wrong updates here? Updates are scheduled weekly and should
have at least picked this up twice now?

Base/EPEL/Extra is the channels that I have subscribed to

Thanks

Ray

On Fri, Jan 5, 2018 at 6:55 PM, Soham Chakraborty 
wrote:

> Hi,
>
> I was trying to sync my repositories (subscribed with Red Hat) to bring
> the patches for meltdown bug (possibly everyone on earth who works with
> computers know this by now).
>
> I manually issued a reposync on my repositories. However the updated
> kernel didn't reach the spacewalk server and reposync completed saying that
> there are no packages to sync.
>
> The spacewalk server is a RHEL7.2 box. When I checked manually on the
> server by running "yum --security check-update", I noticed the updated
> kernel in the yum output.
>
> Does anyone know how can I verify that spacewalk is successfully fetching
> updates? And can anyone point out why I could be unable to fetch this
> kernel (anything to do with subscriptions)? Since Red Hat guys frequent
> this mailing list, decided to give it a try.
>
> Thanks,
>
> ___
> 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] Grafana Repository

[Raymond Setchfield]

Hi

Has anyone had any success adding grafana as a repository for CentOS7?

The URL which I have been using, or at least attempted appears to throw up
404 errors. If you have successfully got this working, what is the URL you
are using

Thanks

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

[Spacewalk-list] Systems Requiring Updates - DB Entry postgres

[Raymond Setchfield]

Hi

I am looking to monitoring a few things within spacewalk and I have found
what I need within the db schema, However I am looking for the db entries
for updates, so that I can monitoring and place a value to this, but I
cannot find the entry within the db

Does anyone know where this is located in the db? Or if not how this is
calculated?

Thanks

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