date:20200319

Re: [Spacewalk-list] Error creating CentOS 8 channel

2020-03-19 Thread Eckert, Doug

I'm setting up child channels for CentOS 8. Running this

# spacewalk-common-channels -v -u  -p  -a x86_64 -k unlimited
'spacewalk210-client-centos8'

Returns relatively quickly, with no output or error message/

In the same file (/etc/rhn/spacewalk-common-channels.ini).  In this section

[spacewalk210-client-centos8]
name = Spacewalk Client 2.10 for %(base_channel_name)s
archs= %(_x86_archs)s
base_channels = centos8-%(arch)s
gpgkey_url = %(_spacewalk_210client_gpgkey_url)s
gpgkey_id = %(_spacewalk_210client_gpgkey_id)s
gpgkey_fingerprint = %(_spacewalk_210client_gpgkey_fingerprint)s
yumrepo_url =
https://copr-be.cloud.fedoraproject.org/results/@spacewalkproject/spacewalk-2.10-client/epel-8-%(arch)s/

This
   base_channels = centos8-%(arch)s

Needs to be changed to this, in order for the channel to be created
base_channels = centos8-baseos-%(arch)s





On Thu, Mar 19, 2020 at 11:01 AM Eckert, Doug 
wrote:

> Thanks! Was wondering if I should modify it or wait for an spacewalk-utils
> RPM.
>
> On Thu, Mar 19, 2020 at 10:58 AM Michael Mraka 
> wrote:
>
>> Eckert, Doug:
>> > FYI -
>> >
>> > >From /etc/rhn/spacewalk-common-channels.ini:
>> >
>> > [centos8-baseos]
>> > archs= x86_64
>> > name = CentOS 8 BaseOS (%(arch)s)
>> > gpgkey_url = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
>> > gpgkey_id = 05B555B38483C65D
>>
>> Change it to 8483C65D to fix the issue.
>>
>> > gpgkey_fingerprint = 99DB 70FA E1D7 CE22 7FB6  4882 05B5 55B3 8483 C65D
>> > yumrepo_url =
>> > http://mirrorlist.centos.org/?release=8=%(arch)s=BaseOS
>> > dist_map_release = 8
>>
>> 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
>
>
>
> --
> Doug Eckert
> LEAD ENGINEER, COMPUTE
> [image: NewsTech] 
> M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993
> <+1+555+555+>
> E: doug.eck...@dowjones.com 
> A: PO Box 300, Princeton, NJ 08543
>


-- 
Doug Eckert
LEAD ENGINEER, COMPUTE
[image: NewsTech] 
M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993 <+1+555+555+>
E: doug.eck...@dowjones.com 
A: PO Box 300, Princeton, NJ 08543
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Eckert, Doug

Thanks. So, in my instance, it should get '106' right?

rhnschema=# select * from rhnPackageProvider;
 id  |   name   |created|   modified
-+--+---+---

 100 | Red Hat Inc. | 2020-02-18 10:56:43.314315-05 | 2020-02-18
10:56:43.314315-05
 101 | Fedora   | 2020-02-18 10:56:43.316934-05 | 2020-02-18
10:56:43.316934-05
 102 | CentOS   | 2020-02-18 10:56:43.318202-05 | 2020-02-18
10:56:43.318202-05
 103 | Scientific Linux | 2020-02-18 10:56:43.319269-05 | 2020-02-18
10:56:43.319269-05
 104 | SUSE | 2020-02-18 10:56:43.320548-05 | 2020-02-18
10:56:43.320548-05
 105 | Oracle Inc.  | 2020-02-18 10:56:43.321994-05 | 2020-02-18
10:56:43.321994-05
 106 | Spacewalk| 2020-02-18 10:56:43.323291-05 | 2020-02-18
10:56:43.323291-05
 107 | EPEL | 2020-02-18 10:56:43.324363-05 | 2020-02-18
10:56:43.324363-05
 108 | Novell Inc.  | 2020-02-18 10:56:43.325785-05 | 2020-02-18
10:56:43.325785-05
(9 rows)

On Thu, Mar 19, 2020 at 10:56 AM Michael Mraka 
wrote:

> Eckert, Doug:
> > If someone would run the below, I'd be very grateful:
> >
> > select name from rhnPackageProvider where id=(select provider_id from
> > rhnPackageKey where key_id='49fc0fd89bd837ba');
>
> It's Spacewalk 2.9 client key.
>
> 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



-- 
Doug Eckert
LEAD ENGINEER, COMPUTE
[image: NewsTech] 
M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993 <+1+555+555+>
E: doug.eck...@dowjones.com 
A: PO Box 300, Princeton, NJ 08543
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Error creating CentOS 8 channel

2020-03-19 Thread Eckert, Doug

Thanks! Was wondering if I should modify it or wait for an spacewalk-utils
RPM.

On Thu, Mar 19, 2020 at 10:58 AM Michael Mraka 
wrote:

> Eckert, Doug:
> > FYI -
> >
> > >From /etc/rhn/spacewalk-common-channels.ini:
> >
> > [centos8-baseos]
> > archs= x86_64
> > name = CentOS 8 BaseOS (%(arch)s)
> > gpgkey_url = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
> > gpgkey_id = 05B555B38483C65D
>
> Change it to 8483C65D to fix the issue.
>
> > gpgkey_fingerprint = 99DB 70FA E1D7 CE22 7FB6  4882 05B5 55B3 8483 C65D
> > yumrepo_url =
> > http://mirrorlist.centos.org/?release=8=%(arch)s=BaseOS
> > dist_map_release = 8
>
> 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



-- 
Doug Eckert
LEAD ENGINEER, COMPUTE
[image: NewsTech] 
M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993 <+1+555+555+>
E: doug.eck...@dowjones.com 
A: PO Box 300, Princeton, NJ 08543
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Error creating CentOS 8 channel

2020-03-19 Thread Michael Mraka

Eckert, Doug:
> FYI -
> 
> >From /etc/rhn/spacewalk-common-channels.ini:
> 
> [centos8-baseos]
> archs= x86_64
> name = CentOS 8 BaseOS (%(arch)s)
> gpgkey_url = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
> gpgkey_id = 05B555B38483C65D

Change it to 8483C65D to fix the issue.

> gpgkey_fingerprint = 99DB 70FA E1D7 CE22 7FB6  4882 05B5 55B3 8483 C65D
> yumrepo_url =
> http://mirrorlist.centos.org/?release=8=%(arch)s=BaseOS
> dist_map_release = 8

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

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Michael Mraka

Eckert, Doug:
> If someone would run the below, I'd be very grateful:
> 
> select name from rhnPackageProvider where id=(select provider_id from
> rhnPackageKey where key_id='49fc0fd89bd837ba');

It's Spacewalk 2.9 client key.

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

Re: [Spacewalk-list] Error creating CentOS 8 channel

2020-03-19 Thread Eckert, Doug

FYI -

>From /etc/rhn/spacewalk-common-channels.ini:

[centos8-baseos]
archs= x86_64
name = CentOS 8 BaseOS (%(arch)s)
gpgkey_url = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
gpgkey_id = 05B555B38483C65D
gpgkey_fingerprint = 99DB 70FA E1D7 CE22 7FB6  4882 05B5 55B3 8483 C65D
yumrepo_url =
http://mirrorlist.centos.org/?release=8=%(arch)s=BaseOS
dist_map_release = 8

On Thu, Mar 19, 2020 at 10:41 AM Eckert, Doug 
wrote:

> Upgraded to Spacewalk 2.10 finally.  Trying to create the CentOS 8
> channel(s) but am getting the below.
>
> # spacewalk-common-channels -v -u xx -p xxx -a x86_64 -k unlimited
> 'centos8-baseos'
> Connecting to http://localhost/rpc/api
> Base channel 'CentOS 8 BaseOS (x86_64)' - creating...
> ERROR: centos8-baseos-x86_64: redstone.xmlrpc.XmlRpcFault: The GPG id must
> be of form 'DB42A60E'
>
> Any clues as to where I should look to resolve this?
>
>
> --
>
>

-- 
Doug Eckert
LEAD ENGINEER, COMPUTE
[image: NewsTech] 
M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993 <+1+555+555+>
E: doug.eck...@dowjones.com 
A: PO Box 300, Princeton, NJ 08543
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Error creating CentOS 8 channel

2020-03-19 Thread Eckert, Doug

Upgraded to Spacewalk 2.10 finally.  Trying to create the CentOS 8
channel(s) but am getting the below.

# spacewalk-common-channels -v -u xx -p xxx -a x86_64 -k unlimited
'centos8-baseos'
Connecting to http://localhost/rpc/api
Base channel 'CentOS 8 BaseOS (x86_64)' - creating...
ERROR: centos8-baseos-x86_64: redstone.xmlrpc.XmlRpcFault: The GPG id must
be of form 'DB42A60E'

Any clues as to where I should look to resolve this?


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

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Eckert, Doug

If someone would run the below, I'd be very grateful:

select name from rhnPackageProvider where id=(select provider_id from
rhnPackageKey where key_id='49fc0fd89bd837ba');



On Thu, Mar 19, 2020 at 9:00 AM Eckert, Doug 
wrote:

> I still have one key (49fc0fd89bd837ba) with a NULL provider_id. That one
> isn't inserted in the schema_upgrade. Not sure what to use for the
> 'lookup_package_provider' function.
>
> So, I checked out the code for the function (rhnschema=# \df+
> lookup_package_provider;) and saw it queries rhnPackageProvider;
>
> Anyone know which is the appropriate provided for key_id
> 49fc0fd89bd837ba?
>
> rhnschema=# select * from rhnPackageProvider;
>  id  |   name   |created|
> modified
>
> -+--+---+---
>  100 | Red Hat Inc. | 2020-02-18 10:56:43.314315-05 | 2020-02-18
> 10:56:43.314315-05
>  101 | Fedora   | 2020-02-18 10:56:43.316934-05 | 2020-02-18
> 10:56:43.316934-05
>  102 | CentOS   | 2020-02-18 10:56:43.318202-05 | 2020-02-18
> 10:56:43.318202-05
>  103 | Scientific Linux | 2020-02-18 10:56:43.319269-05 | 2020-02-18
> 10:56:43.319269-05
>  104 | SUSE | 2020-02-18 10:56:43.320548-05 | 2020-02-18
> 10:56:43.320548-05
>  105 | Oracle Inc.  | 2020-02-18 10:56:43.321994-05 | 2020-02-18
> 10:56:43.321994-05
>  106 | Spacewalk| 2020-02-18 10:56:43.323291-05 | 2020-02-18
> 10:56:43.323291-05
>  107 | EPEL | 2020-02-18 10:56:43.324363-05 | 2020-02-18
> 10:56:43.324363-05
>  108 | Novell Inc.  | 2020-02-18 10:56:43.325785-05 | 2020-02-18
> 10:56:43.325785-05
> (9 rows)
>
> On Thu, Mar 19, 2020 at 8:47 AM Ree, Jan-Albert van 
> wrote:
>
>> Thanks a lot , the update works perfectly here as well
>>
>> I had 3 updates to make and now all is as it should be
>>
>> --
>>
>> Jan-Albert
>>
>>
>>
>> Jan-Albert van Ree | HPC Specialist | Digital Services
>> MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | www.marin.nl
>>
>> [image: LinkedIn]  [image:
>> YouTube]  [image: Twitter]
>>  [image: Facebook]
>> 
>> MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship
>> design
>> 
>>
>> --
>> *From:* spacewalk-list-boun...@redhat.com <
>> spacewalk-list-boun...@redhat.com> on behalf of Eckert, Doug <
>> doug.eck...@dowjones.com>
>> *Sent:* Thursday, March 19, 2020 13:28
>> *To:* spacewalk-list@redhat.com
>> *Subject:* Re: [Spacewalk-list] Spacewalk 2.10 Released!
>>
>> I tried, but it wouldn't let me remove the record due to foreign key
>> reference, so I updated the existing record instead with the value it
>> would've used from the 'insert' command:
>>
>> rhnschema=# update rhnPackageKey set
>> provider_id=lookup_package_provider('CentOS') where
>> key_id='05b555b38483c65d';
>> UPDATE 1
>> rhnschema=# select * from rhnPackageKey where key_id='05b555b38483c65d';
>>  id  |  key_id  | key_type_id | provider_id |created
>>|   modified
>>
>> -+--+-+-+---+---
>>  157 | 05b555b38483c65d | 100 | 102 | 2020-02-21
>> 09:06:55.782751-05 | 2020-03-19 08:26:56.268446-04
>> (1 row)
>>
>> 
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
>
> --
> Doug Eckert
> LEAD ENGINEER, COMPUTE
> [image: NewsTech] 
> M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993
> <+1+555+555+>
> E: doug.eck...@dowjones.com 
> A: PO Box 300, Princeton, NJ 08543
>


-- 
Doug Eckert
LEAD ENGINEER, COMPUTE
[image: NewsTech] 
M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993 <+1+555+555+>
E: doug.eck...@dowjones.com 
A: PO Box 300, Princeton, NJ 08543
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Eckert, Doug

I still have one key (49fc0fd89bd837ba) with a NULL provider_id. That one
isn't inserted in the schema_upgrade. Not sure what to use for the
'lookup_package_provider' function.

So, I checked out the code for the function (rhnschema=# \df+
lookup_package_provider;) and saw it queries rhnPackageProvider;

Anyone know which is the appropriate provided for key_id  49fc0fd89bd837ba?

rhnschema=# select * from rhnPackageProvider;
 id  |   name   |created|   modified
-+--+---+---
 100 | Red Hat Inc. | 2020-02-18 10:56:43.314315-05 | 2020-02-18
10:56:43.314315-05
 101 | Fedora   | 2020-02-18 10:56:43.316934-05 | 2020-02-18
10:56:43.316934-05
 102 | CentOS   | 2020-02-18 10:56:43.318202-05 | 2020-02-18
10:56:43.318202-05
 103 | Scientific Linux | 2020-02-18 10:56:43.319269-05 | 2020-02-18
10:56:43.319269-05
 104 | SUSE | 2020-02-18 10:56:43.320548-05 | 2020-02-18
10:56:43.320548-05
 105 | Oracle Inc.  | 2020-02-18 10:56:43.321994-05 | 2020-02-18
10:56:43.321994-05
 106 | Spacewalk| 2020-02-18 10:56:43.323291-05 | 2020-02-18
10:56:43.323291-05
 107 | EPEL | 2020-02-18 10:56:43.324363-05 | 2020-02-18
10:56:43.324363-05
 108 | Novell Inc.  | 2020-02-18 10:56:43.325785-05 | 2020-02-18
10:56:43.325785-05
(9 rows)

On Thu, Mar 19, 2020 at 8:47 AM Ree, Jan-Albert van 
wrote:

> Thanks a lot , the update works perfectly here as well
>
> I had 3 updates to make and now all is as it should be
>
> --
>
> Jan-Albert
>
>
>
> Jan-Albert van Ree | HPC Specialist | Digital Services
> MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | www.marin.nl
>
> [image: LinkedIn]  [image:
> YouTube]  [image: Twitter]
>  [image: Facebook]
> 
> MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship
> design
> 
>
> --
> *From:* spacewalk-list-boun...@redhat.com <
> spacewalk-list-boun...@redhat.com> on behalf of Eckert, Doug <
> doug.eck...@dowjones.com>
> *Sent:* Thursday, March 19, 2020 13:28
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] Spacewalk 2.10 Released!
>
> I tried, but it wouldn't let me remove the record due to foreign key
> reference, so I updated the existing record instead with the value it
> would've used from the 'insert' command:
>
> rhnschema=# update rhnPackageKey set
> provider_id=lookup_package_provider('CentOS') where
> key_id='05b555b38483c65d';
> UPDATE 1
> rhnschema=# select * from rhnPackageKey where key_id='05b555b38483c65d';
>  id  |  key_id  | key_type_id | provider_id |created
>  |   modified
>
> -+--+-+-+---+---
>  157 | 05b555b38483c65d | 100 | 102 | 2020-02-21
> 09:06:55.782751-05 | 2020-03-19 08:26:56.268446-04
> (1 row)
>
> 
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list



-- 
Doug Eckert
LEAD ENGINEER, COMPUTE
[image: NewsTech] 
M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993 <+1+555+555+>
E: doug.eck...@dowjones.com 
A: PO Box 300, Princeton, NJ 08543
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Ree, Jan-Albert van

Yes indeed, I just went on as described and saw now adverse effects.

--

Jan-Albert

Jan-Albert van Ree | HPC Specialist | Digital Services
MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | 
www.marin.nl

[LinkedIn] [YouTube] 
  [Twitter] 
  [Facebook] 

MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship 
design


From: spacewalk-list-boun...@redhat.com  on 
behalf of Eckert, Doug 
Sent: Thursday, March 19, 2020 13:36
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.10 Released!

One last question... when you were done, you just proceeded with 
'spacewalk-setup --upgrade'?


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

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Ree, Jan-Albert van

Thanks a lot , the update works perfectly here as well

I had 3 updates to make and now all is as it should be

--

Jan-Albert


Jan-Albert van Ree | HPC Specialist | Digital Services
MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | 
www.marin.nl

[LinkedIn] [YouTube] 
  [Twitter] 
  [Facebook] 

MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship 
design


From: spacewalk-list-boun...@redhat.com  on 
behalf of Eckert, Doug 
Sent: Thursday, March 19, 2020 13:28
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.10 Released!

I tried, but it wouldn't let me remove the record due to foreign key reference, 
so I updated the existing record instead with the value it would've used from 
the 'insert' command:

rhnschema=# update rhnPackageKey set 
provider_id=lookup_package_provider('CentOS') where key_id='05b555b38483c65d';
UPDATE 1
rhnschema=# select * from rhnPackageKey where key_id='05b555b38483c65d';
 id  |  key_id  | key_type_id | provider_id |created
|   modified
-+--+-+-+---+---
 157 | 05b555b38483c65d | 100 | 102 | 2020-02-21 
09:06:55.782751-05 | 2020-03-19 08:26:56.268446-04
(1 row)




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

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Eckert, Doug

One last question... when you were done, you just proceeded with
'spacewalk-setup --upgrade'?

On Thu, Mar 19, 2020 at 8:32 AM Eckert, Doug 
wrote:

> FYI - I also had the same issue with the last key insert. Did the same for
> it, using the ' lookup_package_provider' as specified in the insert command
>
> rhnschema=# insert into rhnPackageKey (id, key_id, key_type_id,
> provider_id) values
> rhnschema-# (sequence_nextval('rhn_pkey_id_seq'), '21ea45ab2f86d6a1',
> lookup_package_key_type('gpg'), lookup_package_provider('EPEL'));
> ERROR:  duplicate key value violates unique constraint "rhn_pkey_keyid_uq"
> DETAIL:  Key (key_id)=(21ea45ab2f86d6a1) already exists.
>
> rhnschema=# update rhnPackageKey set
> provider_id=lookup_package_provider('EPEL') where key_id='21ea45ab2f86d6a1';
> UPDATE 1
>
> rhnschema=# select * from rhnPackageKey where key_id='21ea45ab2f86d6a1';
>  id  |  key_id  | key_type_id | provider_id |created
>  |   modified
>
> -+--+-+-+---+---
>  158 | 21ea45ab2f86d6a1 | 100 | 107 | 2020-02-21
> 10:53:24.558639-05 | 2020-03-19 08:30:05.672277-04
> (1 row)
>
> On Thu, Mar 19, 2020 at 8:28 AM Eckert, Doug 
> wrote:
>
>> I tried, but it wouldn't let me remove the record due to foreign key
>> reference, so I updated the existing record instead with the value it
>> would've used from the 'insert' command:
>>
>> rhnschema=# update rhnPackageKey set
>> provider_id=lookup_package_provider('CentOS') where
>> key_id='05b555b38483c65d';
>> UPDATE 1
>> rhnschema=# select * from rhnPackageKey where key_id='05b555b38483c65d';
>>  id  |  key_id  | key_type_id | provider_id |created
>>|   modified
>>
>> -+--+-+-+---+---
>>  157 | 05b555b38483c65d | 100 | 102 | 2020-02-21
>> 09:06:55.782751-05 | 2020-03-19 08:26:56.268446-04
>> (1 row)
>>
>> On Thu, Mar 19, 2020 at 8:21 AM Eckert, Doug 
>> wrote:
>>
>>> I asked because on my server, the matching key_id has an empty
>>> 'provider_id' field
>>>
>>> rhnschema=# insert into rhnPackageKey (id, key_id, key_type_id,
>>> provider_id) values
>>> rhnschema-# (sequence_nextval('rhn_pkey_id_seq'), '05b555b38483c65d',
>>> lookup_package_key_type('gpg'), lookup_package_provider('CentOS'));
>>> ERROR:  duplicate key value violates unique constraint
>>> "rhn_pkey_keyid_uq"
>>> DETAIL:  Key (key_id)=(05b555b38483c65d) already exists.
>>>
>>> rhnschema=# select * from rhnPackageKey where key_id='05b555b38483c65d';
>>>  id  |  key_id  | key_type_id | provider_id |created
>>>|   modified
>>>
>>> -+--+-+-+---+---
>>>  157 | 05b555b38483c65d | 100 | | 2020-02-21
>>> 09:06:55.782751-05 | 2020-02-21 09:06:55.782751-05
>>> (1 row)
>>>
>>> Actually, there are 3 rows (out of 160) with a NULL provider_id.
>>>
>>> 156 | 49fc0fd89bd837ba | 100 | | 2020-02-19
>>> 02:06:37.884325-05 | 2020-02-19 02:06:37.884325-05
>>> 157 | 05b555b38483c65d | 100 | | 2020-02-21
>>> 09:06:55.782751-05 | 2020-02-21 09:06:55.782751-05
>>> 158 | 21ea45ab2f86d6a1 | 100 | | 2020-02-21
>>> 10:53:24.558639-05 | 2020-02-21 10:53:24.558639-05
>>>
>>> Wondering if it would be wiser to remove the record
>>>
>>> delete from  rhnPackageKey  where key_id='05b555b38483c65d';
>>>
>>> Then re-insert it with the same id (157 in my case):
>>>
>>> insert into rhnPackageKey (id, key_id, key_type_id, provider_id) values
>>> (157, '05b555b38483c65d', lookup_package_key_type('gpg'),
>>> lookup_package_provider('CentOS'));
>>>
>>>
>>>
>>>
>>> On Thu, Mar 19, 2020 at 8:14 AM Ree, Jan-Albert van 
>>> wrote:
>>>
 I skipped nothing but executed all queries, continuing on errors with
 the next one and assumed that if there was an existing record it would be
 fine already...

 Maybe not the best way, but it worked.

 --

 Jan-Albert



 Jan-Albert van Ree | HPC Specialist | Digital Services
 MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | www.marin.nl

 [image: LinkedIn]  [image:
 YouTube]  [image: Twitter]
  [image: Facebook]
 
 MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship
 design
 

 --
 *From:* spacewalk-list-boun...@redhat.com <
 spacewalk-list-boun...@redhat.com> on behalf of Eckert, Doug <

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Eckert, Doug

FYI - I also had the same issue with the last key insert. Did the same for
it, using the ' lookup_package_provider' as specified in the insert command

rhnschema=# insert into rhnPackageKey (id, key_id, key_type_id,
provider_id) values
rhnschema-# (sequence_nextval('rhn_pkey_id_seq'), '21ea45ab2f86d6a1',
lookup_package_key_type('gpg'), lookup_package_provider('EPEL'));
ERROR:  duplicate key value violates unique constraint "rhn_pkey_keyid_uq"
DETAIL:  Key (key_id)=(21ea45ab2f86d6a1) already exists.

rhnschema=# update rhnPackageKey set
provider_id=lookup_package_provider('EPEL') where key_id='21ea45ab2f86d6a1';
UPDATE 1

rhnschema=# select * from rhnPackageKey where key_id='21ea45ab2f86d6a1';
 id  |  key_id  | key_type_id | provider_id |created
 |   modified
-+--+-+-+---+---
 158 | 21ea45ab2f86d6a1 | 100 | 107 | 2020-02-21
10:53:24.558639-05 | 2020-03-19 08:30:05.672277-04
(1 row)

On Thu, Mar 19, 2020 at 8:28 AM Eckert, Doug 
wrote:

> I tried, but it wouldn't let me remove the record due to foreign key
> reference, so I updated the existing record instead with the value it
> would've used from the 'insert' command:
>
> rhnschema=# update rhnPackageKey set
> provider_id=lookup_package_provider('CentOS') where
> key_id='05b555b38483c65d';
> UPDATE 1
> rhnschema=# select * from rhnPackageKey where key_id='05b555b38483c65d';
>  id  |  key_id  | key_type_id | provider_id |created
>  |   modified
>
> -+--+-+-+---+---
>  157 | 05b555b38483c65d | 100 | 102 | 2020-02-21
> 09:06:55.782751-05 | 2020-03-19 08:26:56.268446-04
> (1 row)
>
> On Thu, Mar 19, 2020 at 8:21 AM Eckert, Doug 
> wrote:
>
>> I asked because on my server, the matching key_id has an empty
>> 'provider_id' field
>>
>> rhnschema=# insert into rhnPackageKey (id, key_id, key_type_id,
>> provider_id) values
>> rhnschema-# (sequence_nextval('rhn_pkey_id_seq'), '05b555b38483c65d',
>> lookup_package_key_type('gpg'), lookup_package_provider('CentOS'));
>> ERROR:  duplicate key value violates unique constraint "rhn_pkey_keyid_uq"
>> DETAIL:  Key (key_id)=(05b555b38483c65d) already exists.
>>
>> rhnschema=# select * from rhnPackageKey where key_id='05b555b38483c65d';
>>  id  |  key_id  | key_type_id | provider_id |created
>>|   modified
>>
>> -+--+-+-+---+---
>>  157 | 05b555b38483c65d | 100 | | 2020-02-21
>> 09:06:55.782751-05 | 2020-02-21 09:06:55.782751-05
>> (1 row)
>>
>> Actually, there are 3 rows (out of 160) with a NULL provider_id.
>>
>> 156 | 49fc0fd89bd837ba | 100 | | 2020-02-19
>> 02:06:37.884325-05 | 2020-02-19 02:06:37.884325-05
>> 157 | 05b555b38483c65d | 100 | | 2020-02-21
>> 09:06:55.782751-05 | 2020-02-21 09:06:55.782751-05
>> 158 | 21ea45ab2f86d6a1 | 100 | | 2020-02-21
>> 10:53:24.558639-05 | 2020-02-21 10:53:24.558639-05
>>
>> Wondering if it would be wiser to remove the record
>>
>> delete from  rhnPackageKey  where key_id='05b555b38483c65d';
>>
>> Then re-insert it with the same id (157 in my case):
>>
>> insert into rhnPackageKey (id, key_id, key_type_id, provider_id) values
>> (157, '05b555b38483c65d', lookup_package_key_type('gpg'),
>> lookup_package_provider('CentOS'));
>>
>>
>>
>>
>> On Thu, Mar 19, 2020 at 8:14 AM Ree, Jan-Albert van 
>> wrote:
>>
>>> I skipped nothing but executed all queries, continuing on errors with
>>> the next one and assumed that if there was an existing record it would be
>>> fine already...
>>>
>>> Maybe not the best way, but it worked.
>>>
>>> --
>>>
>>> Jan-Albert
>>>
>>>
>>>
>>> Jan-Albert van Ree | HPC Specialist | Digital Services
>>> MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | www.marin.nl
>>>
>>> [image: LinkedIn]  [image:
>>> YouTube]  [image: Twitter]
>>>  [image: Facebook]
>>> 
>>> MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship
>>> design
>>> 
>>>
>>> --
>>> *From:* spacewalk-list-boun...@redhat.com <
>>> spacewalk-list-boun...@redhat.com> on behalf of Eckert, Doug <
>>> doug.eck...@dowjones.com>
>>> *Sent:* Thursday, March 19, 2020 13:08
>>> *To:* spacewalk-list@redhat.com
>>> *Subject:* Re: [Spacewalk-list] Spacewalk 2.10 Released!
>>>
>>> Did you skip the one with the duplicate key constraint error, or did you
>>> remove the existing record with the matching key and re-insert?

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Eckert, Doug

I tried, but it wouldn't let me remove the record due to foreign key
reference, so I updated the existing record instead with the value it
would've used from the 'insert' command:

rhnschema=# update rhnPackageKey set
provider_id=lookup_package_provider('CentOS') where
key_id='05b555b38483c65d';
UPDATE 1
rhnschema=# select * from rhnPackageKey where key_id='05b555b38483c65d';
 id  |  key_id  | key_type_id | provider_id |created
 |   modified
-+--+-+-+---+---
 157 | 05b555b38483c65d | 100 | 102 | 2020-02-21
09:06:55.782751-05 | 2020-03-19 08:26:56.268446-04
(1 row)

On Thu, Mar 19, 2020 at 8:21 AM Eckert, Doug 
wrote:

> I asked because on my server, the matching key_id has an empty
> 'provider_id' field
>
> rhnschema=# insert into rhnPackageKey (id, key_id, key_type_id,
> provider_id) values
> rhnschema-# (sequence_nextval('rhn_pkey_id_seq'), '05b555b38483c65d',
> lookup_package_key_type('gpg'), lookup_package_provider('CentOS'));
> ERROR:  duplicate key value violates unique constraint "rhn_pkey_keyid_uq"
> DETAIL:  Key (key_id)=(05b555b38483c65d) already exists.
>
> rhnschema=# select * from rhnPackageKey where key_id='05b555b38483c65d';
>  id  |  key_id  | key_type_id | provider_id |created
>  |   modified
>
> -+--+-+-+---+---
>  157 | 05b555b38483c65d | 100 | | 2020-02-21
> 09:06:55.782751-05 | 2020-02-21 09:06:55.782751-05
> (1 row)
>
> Actually, there are 3 rows (out of 160) with a NULL provider_id.
>
> 156 | 49fc0fd89bd837ba | 100 | | 2020-02-19
> 02:06:37.884325-05 | 2020-02-19 02:06:37.884325-05
> 157 | 05b555b38483c65d | 100 | | 2020-02-21
> 09:06:55.782751-05 | 2020-02-21 09:06:55.782751-05
> 158 | 21ea45ab2f86d6a1 | 100 | | 2020-02-21
> 10:53:24.558639-05 | 2020-02-21 10:53:24.558639-05
>
> Wondering if it would be wiser to remove the record
>
> delete from  rhnPackageKey  where key_id='05b555b38483c65d';
>
> Then re-insert it with the same id (157 in my case):
>
> insert into rhnPackageKey (id, key_id, key_type_id, provider_id) values
> (157, '05b555b38483c65d', lookup_package_key_type('gpg'),
> lookup_package_provider('CentOS'));
>
>
>
>
> On Thu, Mar 19, 2020 at 8:14 AM Ree, Jan-Albert van 
> wrote:
>
>> I skipped nothing but executed all queries, continuing on errors with
>> the next one and assumed that if there was an existing record it would be
>> fine already...
>>
>> Maybe not the best way, but it worked.
>>
>> --
>>
>> Jan-Albert
>>
>>
>>
>> Jan-Albert van Ree | HPC Specialist | Digital Services
>> MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | www.marin.nl
>>
>> [image: LinkedIn]  [image:
>> YouTube]  [image: Twitter]
>>  [image: Facebook]
>> 
>> MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship
>> design
>> 
>>
>> --
>> *From:* spacewalk-list-boun...@redhat.com <
>> spacewalk-list-boun...@redhat.com> on behalf of Eckert, Doug <
>> doug.eck...@dowjones.com>
>> *Sent:* Thursday, March 19, 2020 13:08
>> *To:* spacewalk-list@redhat.com
>> *Subject:* Re: [Spacewalk-list] Spacewalk 2.10 Released!
>>
>> Did you skip the one with the duplicate key constraint error, or did you
>> remove the existing record with the matching key and re-insert?
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
>
> --
> Doug Eckert
> LEAD ENGINEER, COMPUTE
> [image: NewsTech] 
> M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993
> <+1+555+555+>
> E: doug.eck...@dowjones.com 
> A: PO Box 300, Princeton, NJ 08543
>


-- 
Doug Eckert
LEAD ENGINEER, COMPUTE
[image: NewsTech] 
M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993 <+1+555+555+>
E: doug.eck...@dowjones.com 
A: PO Box 300, Princeton, NJ 08543
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Elsever Sadigov


Jan-Albert,

Thank you for explanation, it works for me. Btw update process takes 
long time, if anyone wonders.


--
*Best Regards,*
***Sadigov Elsevar*

*
*

On 3/19/2020 11:55, Ree, Jan-Albert van wrote:


I followed these steps :


cat 
/etc/sysconfig/rhn/schema-upgrade/spacewalk-schema-2.9-to-spacewalk-schema-2.10/006-distribution-keys.sql.postgresql


su - postgres

psql -d rhnschema


Then just copy all the queries , one at a time , from the cat above in 
the postgresql session and then quit postgresql and continued the 
upgrade as if the database upgrade was successful.



Regards,

--

Jan-Albert



Jan-Albertvan Ree| HPC Specialist| Digital Services
MARIN| T +31 317 49 35 48| j.a.v@marin.nl 
 | www.marin.nl 


LinkedIn  YouTube 
 Twitter 
 Facebook 

MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship 
design 
 



*From:* spacewalk-list-boun...@redhat.com 
 on behalf of Elsever Sadigov 


*Sent:* Thursday, March 19, 2020 08:08
*To:* spacewalk-list@redhat.com
*Subject:* Re: [Spacewalk-list] Spacewalk 2.10 Released!

Hi Jan-Albert,

Can you share what exactly you did?

I'm facing same issue:


--
*Best Regards,*
***Sadigov Elsevar*

On 3/19/2020 00:45, Ree, Jan-Albert van wrote:

Congrats to the devel team.

Just performed an upgrade and am back up and running with 2.10

Ran in to one minor issue ,

  
spacewalk-schema-2.9-to-spacewalk-schema-2.10/006-distribution-keys.sql.postgresql
(1 row)

INSERT 0 1
INSERT 0 1
psql:/var/log/spacewalk/schema-upgrade/20200318-170518-script.sql:289: ERROR:  duplicate 
key value violates unique constraint "rhn_pkey_keyid_uq"
DETAIL:  Key (key_id)=(05b555b38483c65d) already exists.

Solved it by running all the queries in that (last) upgrade script manually

Thanks for all the hard work!
--
Jan-Albert van Ree


Jan-Albert van Ree  | HPC Specialist | Digital Services
MARIN | T +31 317 49 35 48 |mailto:j.a.v@marin.nl  |http://www.marin.nl


From:spacewalk-list-boun...@redhat.comon 
behalf of Michael Mraka
Sent: Wednesday, March 18, 2020 16:10
To:spacewalk-announce-l...@redhat.com;spacewalk-list@redhat.com;spacewalk-de...@redhat.com
Subject: [Spacewalk-list] Spacewalk 2.10 Released!

Hello everyone,

We are proudly announcing release of Spacewalk 2.10, a systems management 
solution.

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



**


*Help us improve the spam filter. If this message contains SPAM, click 
here 
 
to report. Thank you, MARIN Support Group*



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

**

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

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Eckert, Doug

I asked because on my server, the matching key_id has an empty
'provider_id' field

rhnschema=# insert into rhnPackageKey (id, key_id, key_type_id,
provider_id) values
rhnschema-# (sequence_nextval('rhn_pkey_id_seq'), '05b555b38483c65d',
lookup_package_key_type('gpg'), lookup_package_provider('CentOS'));
ERROR:  duplicate key value violates unique constraint "rhn_pkey_keyid_uq"
DETAIL:  Key (key_id)=(05b555b38483c65d) already exists.

rhnschema=# select * from rhnPackageKey where key_id='05b555b38483c65d';
 id  |  key_id  | key_type_id | provider_id |created
 |   modified
-+--+-+-+---+---
 157 | 05b555b38483c65d | 100 | | 2020-02-21
09:06:55.782751-05 | 2020-02-21 09:06:55.782751-05
(1 row)

Actually, there are 3 rows (out of 160) with a NULL provider_id.

156 | 49fc0fd89bd837ba | 100 | | 2020-02-19
02:06:37.884325-05 | 2020-02-19 02:06:37.884325-05
157 | 05b555b38483c65d | 100 | | 2020-02-21
09:06:55.782751-05 | 2020-02-21 09:06:55.782751-05
158 | 21ea45ab2f86d6a1 | 100 | | 2020-02-21
10:53:24.558639-05 | 2020-02-21 10:53:24.558639-05

Wondering if it would be wiser to remove the record

delete from  rhnPackageKey  where key_id='05b555b38483c65d';

Then re-insert it with the same id (157 in my case):

insert into rhnPackageKey (id, key_id, key_type_id, provider_id) values
(157, '05b555b38483c65d', lookup_package_key_type('gpg'),
lookup_package_provider('CentOS'));




On Thu, Mar 19, 2020 at 8:14 AM Ree, Jan-Albert van 
wrote:

> I skipped nothing but executed all queries, continuing on errors with the
> next one and assumed that if there was an existing record it would be fine
> already...
>
> Maybe not the best way, but it worked.
>
> --
>
> Jan-Albert
>
>
>
> Jan-Albert van Ree | HPC Specialist | Digital Services
> MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | www.marin.nl
>
> [image: LinkedIn]  [image:
> YouTube]  [image: Twitter]
>  [image: Facebook]
> 
> MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship
> design
> 
>
> --
> *From:* spacewalk-list-boun...@redhat.com <
> spacewalk-list-boun...@redhat.com> on behalf of Eckert, Doug <
> doug.eck...@dowjones.com>
> *Sent:* Thursday, March 19, 2020 13:08
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] Spacewalk 2.10 Released!
>
> Did you skip the one with the duplicate key constraint error, or did you
> remove the existing record with the matching key and re-insert?
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list



-- 
Doug Eckert
LEAD ENGINEER, COMPUTE
[image: NewsTech] 
M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993 <+1+555+555+>
E: doug.eck...@dowjones.com 
A: PO Box 300, Princeton, NJ 08543
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Ree, Jan-Albert van

I skipped nothing but executed all queries, continuing on errors with the next 
one and assumed that if there was an existing record it would be fine already...

Maybe not the best way, but it worked.

--

Jan-Albert


Jan-Albert van Ree | HPC Specialist | Digital Services
MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | 
www.marin.nl

[LinkedIn] [YouTube] 
  [Twitter] 
  [Facebook] 

MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship 
design


From: spacewalk-list-boun...@redhat.com  on 
behalf of Eckert, Doug 
Sent: Thursday, March 19, 2020 13:08
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.10 Released!

Did you skip the one with the duplicate key constraint error, or did you remove 
the existing record with the matching key and re-insert?


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

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Eckert, Doug

Did you skip the one with the duplicate key constraint error, or did you
remove the existing record with the matching key and re-insert?

On Thu, Mar 19, 2020 at 3:56 AM Ree, Jan-Albert van 
wrote:

> I followed these steps :
>
>
> cat
> /etc/sysconfig/rhn/schema-upgrade/spacewalk-schema-2.9-to-spacewalk-schema-2.10/006-distribution-keys.sql.postgresql
>
> su - postgres
>
> psql -d rhnschema
>
>
> Then just copy all the queries , one at a time , from the cat above in the
> postgresql session and then quit postgresql and continued the upgrade as if
> the database upgrade was successful.
>
>
> Regards,
>
> --
>
> Jan-Albert
>
>
>
> Jan-Albert van Ree | HPC Specialist | Digital Services
> MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | www.marin.nl
>
> [image: LinkedIn]  [image:
> YouTube]  [image: Twitter]
>  [image: Facebook]
> 
> MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship
> design
> 
>
> --
> *From:* spacewalk-list-boun...@redhat.com <
> spacewalk-list-boun...@redhat.com> on behalf of Elsever Sadigov <
> e.sadi...@millikart.az>
> *Sent:* Thursday, March 19, 2020 08:08
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] Spacewalk 2.10 Released!
>
>
> Hi Jan-Albert,
>
> Can you share what exactly you did?
>
> I'm facing same issue:
>
>
> --
> *Best Regards,*
> *Sadigov Elsevar*
> On 3/19/2020 00:45, Ree, Jan-Albert van wrote:
>
> Congrats to the devel team.
>
> Just performed an upgrade and am back up and running with 2.10
>
> Ran in to one minor issue ,
>
>  
> spacewalk-schema-2.9-to-spacewalk-schema-2.10/006-distribution-keys.sql.postgresql
> (1 row)
>
> INSERT 0 1
> INSERT 0 1
> psql:/var/log/spacewalk/schema-upgrade/20200318-170518-script.sql:289: ERROR: 
>  duplicate key value violates unique constraint "rhn_pkey_keyid_uq"
> DETAIL:  Key (key_id)=(05b555b38483c65d) already exists.
>
> Solved it by running all the queries in that (last) upgrade script manually
>
> Thanks for all the hard work!
> --
> Jan-Albert van Ree
>
>
> Jan-Albert van Ree  | HPC Specialist | Digital Services
> MARIN | T +31 317 49 35 48 | mailto:j.a.v@marin.nl  | 
> http://www.marin.nl
>
> 
> From: spacewalk-list-boun...@redhat.com  
>  on behalf of Michael Mraka 
>  
> Sent: Wednesday, March 18, 2020 16:10
> To: spacewalk-announce-l...@redhat.com; spacewalk-list@redhat.com; 
> spacewalk-de...@redhat.com
> Subject: [Spacewalk-list] Spacewalk 2.10 Released!
>
> Hello everyone,
>
> We are proudly announcing release of Spacewalk 2.10, a systems management 
> solution.
>
> ___
> Spacewalk-list mailing 
> listSpacewalk-list@redhat.comhttps://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
>
>
> *Help us improve the spam filter. If this message contains SPAM, click
> here
> 
> to report. Thank you, MARIN Support Group*
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list



-- 
Doug Eckert
LEAD ENGINEER, COMPUTE
[image: NewsTech] 
M: +1.732.666.3681 <+1+555+555+>O: +1.609.520.4993 <+1+555+555+>
E: doug.eck...@dowjones.com 
A: PO Box 300, Princeton, NJ 08543
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Issue encountered while trying to sync RHEL repository on channel

2020-03-19 Thread Brian Long

In my experience, this means your RHEL entitlement certificates expired and
you need to login to rhn.redhat.com, download a new set of certificates and
update your sync client to use the new certificates.

/Brian/

On Thu, Mar 19, 2020 at 6:08 AM Wenkai Chen <
wenkai_c...@ensigninfosecurity.com> wrote:

> Hi Spacewalk users,
>
>
>
> I encountered the following issue while trying to sync the repository for
> RHEL.
>
>
>
> 020/03/19 17:59:16 +08:00   Processing repository with URL:
> https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os
>
> 2020/03/19 17:59:17 +08:00 ERROR: failure: repodata/repomd.xml from
> rhel7-server-rpms: [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
>
> 2020/03/19 17:59:17 +08:00 ERROR: failure: repodata/repomd.xml from
> rhel7-server-rpms: [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
>
>
>
> Previously it was working fine and I could sync it.
>
> Any ideas as to what might happen?
>
>
>
> [image: A close up of a sign Description generated with very high
> confidence]
>
>
> *Chen Wenkai*
>
> Infrastructure Security Engineer
>
>[image: A picture containing building Description generated with
> high confidence] 
>  [image: A picture containing tableware Description generated with
> high confidence]  [image: A close up of
> a sign Description generated with high confidence]
> 
>
>
> *  E:*  wenkai_c...@ensigninfosecurity.com
>
>   *A:*  30A Kallang Place, Level 9 Right Wing, Singapore 339213
>
>
>
>
>
> --
>
> CONFIDENTIALITY NOTICE: *“This email is confidential and may also be
> privileged. If this email has been sent to you in error, please delete it
> immediately and notify us. Please do not copy, distribute or disseminate
> part or whole of this email if you are not the intended recipient or if you
> have not been authorized to do so. We reserve the right, to the extent and
> under circumstances permitted by applicable laws, to monitor, retain,
> intercept and block email messages to and from our systems. Thank you.” *
>
> ___
> 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] Issue encountered while trying to sync RHEL repository on channel

2020-03-19 Thread Wenkai Chen

Hi Spacewalk users,

I encountered the following issue while trying to sync the repository for RHEL.

020/03/19 17:59:16 +08:00   Processing repository with URL: 
https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os
2020/03/19 17:59:17 +08:00 ERROR: failure: repodata/repomd.xml from 
rhel7-server-rpms: [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
2020/03/19 17:59:17 +08:00 ERROR: failure: repodata/repomd.xml from 
rhel7-server-rpms: [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

Previously it was working fine and I could sync it.
Any ideas as to what might happen?

[A close up of a sign  Description generated with very high confidence]

Chen Wenkai
Infrastructure Security Engineer

   [A picture containing building  Description generated with high 
confidence]   [A 
picture containing tableware  Description generated with high confidence] 
  [A close up of a sign  Description 
generated with high confidence] 

  E:  wenkai_c...@ensigninfosecurity.com
  A:  30A Kallang Place, Level 9 Right Wing, Singapore 339213





CONFIDENTIALITY NOTICE: "This email is confidential and may also be privileged. 
If this email has been sent to you in error, please delete it immediately and 
notify us. Please do not copy, distribute or disseminate part or whole of this 
email if you are not the intended recipient or if you have not been authorized 
to do so. We reserve the right, to the extent and under circumstances permitted 
by applicable laws, to monitor, retain, intercept and block email messages to 
and from our systems. Thank you."

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

Re: [Spacewalk-list] [spacewalk-list] - package not found on centos8 client for "CEBA-2019:3337"

2020-03-19 Thread Michael Mraka

BARRIERE Benoit:
> Hello,
> 
> I have an issue concerning this errata. I push a schedule from my spacewalk 
> server 2.9 to my client centos8 with 2.10 release.
...
> So the Errata indicate that news packages fixed are :
> CentOS 8 AppStream x86_64 
> 
> sha256:bab4f2d595a4465f87e2d280270abb2f0523060fccc368e3cb644e2fc7587be0 
> perl-5.24.4-404.module_el8.1.0+229+cd132df8:4-x86_64 
> 
...
> 
> All packages are existing on my server and can dowload them by gui.
> 
> But the client Centos8 can't download them because package name are changed. 
> See errors on up2date logs :
> 
> [Wed Mar 18 17:28:52 2020] up2date updateLoginInfo() login info
> [Wed Mar 18 17:28:52 2020] up2date logging into up2date server
> [Wed Mar 18 17:28:52 2020] up2date successfully retrieved authentication 
> token from up2date server
> [Wed Mar 18 17:28:53 2020] up2date E: Package 
> perl-4:5.24.4-404.module_el8.1.0+229+cd132df8.x86_64 is not available for 
> installation
...
> You can see below packages are renamed adding < -X : > after name package so 
> packages are missing with syntax.
> 
> Is this a bug on client ?

Hello,

It is not a bug. perl-5.24.4-404.module_el8.1.0+229+cd132df8 is a part
of module (as the version suffix suggests). And your client does not
have this module enabled which means theres nothing to update.
Spacewalk webUI can't properly display updates for modular systems, this
is known limitation.

The different package name you see is only an inconsistency in name
formating (name-version-release:epoch-arch vs. name-epoch:version-release.arch).
 
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

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Michael Mraka

Eckert, Doug:
> Have a relatively recent fresh-install of Spacewalk 2.9 trying to update to
> 2.10, but getting the following from 'yum upgrade'
> 
> I know a lot of 'jpp5' RPMs are/removed with previous updates, but this
> one's in there.
> 
> Error: Package: cglib-2.1.3-4.jpp5.noarch (@jpackage-generic)
>Requires: asm >= 1.5.3
>Removing: asm-1.5.3-7.jpp5.noarch (@jpackage-generic)
>asm = 1.5.3-7.jpp5
>Obsoleted By: spacewalk-java-2.10.19-1.el7.noarch (spacewalk)
>Not found
> Error: Package: google-guice-3.1.3-9.el7.noarch (base)
>Requires: mvn(cglib:cglib)
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest

Hello Doug,

Jpp5 packages has been removed in Spacewalk 2.7. If you still have one
please remove /etc/yum.repos.d/jpackage-generic.repo and remove
any leftover packages comming from it.
  
  rpm -e *.jpp5

Also check if there are not locked packages, namely cglib and c3p0

  yum versionlock list
  yum versionlock delete cglib c3p0

Subsequent upgrade should download correct packages from CentOS.


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

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Ree, Jan-Albert van

I followed these steps :


cat 
/etc/sysconfig/rhn/schema-upgrade/spacewalk-schema-2.9-to-spacewalk-schema-2.10/006-distribution-keys.sql.postgresql

su - postgres

psql -d rhnschema


Then just copy all the queries , one at a time , from the cat above in the 
postgresql session and then quit postgresql and continued the upgrade as if the 
database upgrade was successful.


Regards,

--

Jan-Albert


Jan-Albert van Ree | HPC Specialist | Digital Services
MARIN | T +31 317 49 35 48 | j.a.v@marin.nl | 
www.marin.nl

[LinkedIn] [YouTube] 
  [Twitter] 
  [Facebook] 

MARIN news: Courses Hydrodynamics  Floating Offshore Structures & Ship 
design


From: spacewalk-list-boun...@redhat.com  on 
behalf of Elsever Sadigov 
Sent: Thursday, March 19, 2020 08:08
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.10 Released!


Hi Jan-Albert,

Can you share what exactly you did?

I'm facing same issue:
[cid:part1.69431512.B31AE872@millikart.az]

--
Best Regards,
Sadigov Elsevar

On 3/19/2020 00:45, Ree, Jan-Albert van wrote:

Congrats to the devel team.

Just performed an upgrade and am back up and running with 2.10

Ran in to one minor issue ,

 
spacewalk-schema-2.9-to-spacewalk-schema-2.10/006-distribution-keys.sql.postgresql
(1 row)

INSERT 0 1
INSERT 0 1
psql:/var/log/spacewalk/schema-upgrade/20200318-170518-script.sql:289: ERROR:  
duplicate key value violates unique constraint "rhn_pkey_keyid_uq"
DETAIL:  Key (key_id)=(05b555b38483c65d) already exists.

Solved it by running all the queries in that (last) upgrade script manually

Thanks for all the hard work!
--
Jan-Albert van Ree


Jan-Albert van Ree  | HPC Specialist | Digital Services
MARIN | T +31 317 49 35 48 | mailto:j.a.v@marin.nl | http://www.marin.nl


From: 
spacewalk-list-boun...@redhat.com 
 
on behalf of Michael Mraka 

Sent: Wednesday, March 18, 2020 16:10
To: 
spacewalk-announce-l...@redhat.com; 
spacewalk-list@redhat.com; 
spacewalk-de...@redhat.com
Subject: [Spacewalk-list] Spacewalk 2.10 Released!

Hello everyone,

We are proudly announcing release of Spacewalk 2.10, a systems management 
solution.

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







Help us improve the spam filter. If this message contains SPAM, click 
here
 to report. Thank you, MARIN Support Group


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

Re: [Spacewalk-list] Spacewalk 2.10 Released!

2020-03-19 Thread Elsever Sadigov


Hi Jan-Albert,

Can you share what exactly you did?

I'm facing same issue:


--
*Best Regards,*
***Sadigov Elsevar*

On 3/19/2020 00:45, Ree, Jan-Albert van wrote:

Congrats to the devel team.

Just performed an upgrade and am back up and running with 2.10

Ran in to one minor issue ,

  
spacewalk-schema-2.9-to-spacewalk-schema-2.10/006-distribution-keys.sql.postgresql
(1 row)

INSERT 0 1
INSERT 0 1
psql:/var/log/spacewalk/schema-upgrade/20200318-170518-script.sql:289: ERROR:  duplicate 
key value violates unique constraint "rhn_pkey_keyid_uq"
DETAIL:  Key (key_id)=(05b555b38483c65d) already exists.

Solved it by running all the queries in that (last) upgrade script manually

Thanks for all the hard work!
--
Jan-Albert van Ree


Jan-Albert van Ree  | HPC Specialist | Digital Services
MARIN | T +31 317 49 35 48 | mailto:j.a.v@marin.nl | http://www.marin.nl


From: spacewalk-list-boun...@redhat.com  on behalf 
of Michael Mraka 
Sent: Wednesday, March 18, 2020 16:10
To: spacewalk-announce-l...@redhat.com; spacewalk-list@redhat.com; 
spacewalk-de...@redhat.com
Subject: [Spacewalk-list] Spacewalk 2.10 Released!

Hello everyone,

We are proudly announcing release of Spacewalk 2.10, a systems management 
solution.

___
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] Error creating CentOS 8 channel

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Error creating CentOS 8 channel

Re: [Spacewalk-list] Error creating CentOS 8 channel

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Error creating CentOS 8 channel

[Spacewalk-list] Error creating CentOS 8 channel

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Issue encountered while trying to sync RHEL repository on channel

[Spacewalk-list] Issue encountered while trying to sync RHEL repository on channel

Re: [Spacewalk-list] [spacewalk-list] - package not found on centos8 client for "CEBA-2019:3337"

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

Re: [Spacewalk-list] Spacewalk 2.10 Released!

24 matches

Site Navigation

Mail list logo

Footer information