[Spacewalk-list] RollBack issue

2018-03-30 Thread Yakin, Francis
Apparently, I am having issue with rollback after I upgraded the packages, it 
doesn't roll back to previous snapshot for some reason.

The system is running centOS 6.8, I had 32 packages upgraded, I created a 
snapshot tag before I ran the upgrade.
The upgraded was fine, now packages is 0.

Now, I want to rollback to the snapshot tag that I created, so the system 
should have 32 packages packages needs to be upgraded.

It doesn't work for some reason. No error, it showing successful, but the 
system still showing 0 packages.

What did I do wrong? Please advice.

Thanks


Francis Yakin | IT System Admin |  direct: 510-749-2027
500 Wind River Way, Alameda, CA  94501
[cid:image001.png@01D12D0C.E17713F0]
AN INTEL COMPANY

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

[Spacewalk-list] Install/upgrade Patch ubuntu/debian system using spacewalk

2018-03-30 Thread Yakin, Francis
Does anyone have experience or documentation to install spacewalk client and 
install the packages on Ubuntu/Debian systems?

Thanks

Francis Yakin | IT System Admin |  direct: 510-749-2027
500 Wind River Way, Alameda, CA  94501
[cid:image001.png@01D12D0C.E17713F0]
AN INTEL COMPANY

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

Re: [Spacewalk-list] Cannot install updates on spacewalk client

2018-03-30 Thread Michael Watters


On 03/29/2018 06:48 AM, Paschedag, Robert wrote:
> You can check the path with
>
> select * from rhnpackage where id = 11570;
>
> But the message indicates some sort of error while you were synchronizing 
> your repos. I would try to locate this problem "package" within SW in the 
> "Channels" -> "Manage Software Channels" -> "Manage software packages" and 
> try to *fully* delete this package and try to re-sync.
>
> Robert

No luck.  I deleted the package and reran spacewalk-repo-sync which
claims to have downloaded the package but yum updates still fail.  The
interesting part is spacewalk-repo-sync keeps trying to download the
same 33 packages every time I download it.  For example, here's the output.

[root@spacewalk rhn]# spacewalk-repo-sync -v -c centos7-x86_64-updates  

  
12:34:49 ==
12:34:49 | Channel: centos7-x86_64-updates
12:34:49 ==
12:34:49 Sync of channel started.
12:34:50 Repo URL: 
http://mirrorlist.centos.org/?release=7=x86_64=updates
12:34:55 Packages in repo:  2416
12:35:05 Packages already synced:   2383
12:35:05 Packages to sync:33
12:35:05 New packages to download:33
12:35:05 Downloading total 33 files from 1 queues.
12:35:06 1/33 : NetworkManager-1.8.0-11.el7_4.x86_64.rpm
12:35:06 2/33 : git-email-1.8.3.1-12.el7_4.noarch.rpm
12:35:06 3/33 : debugmode-9.49.39-1.el7_4.1.x86_64.rpm
12:35:06 4/33 : bind-lite-devel-9.9.4-51.el7_4.2.i686.rpm
12:35:07 5/33 : NetworkManager-glib-devel-1.8.0-11.el7_4.i686.rpm
12:35:07 6/33 : kmod-devel-20-15.el7_4.7.x86_64.rpm
12:35:07 7/33 : java-1.8.0-openjdk-demo-1.8.0.161-0.b14.el7_4.i686.rpm
12:35:07 8/33 : kmod-libs-20-15.el7_4.4.i686.rpm
12:35:07 9/33 : libdb-cxx-devel-5.3.21-21.el7_4.x86_64.rpm
12:35:07 10/33 : libgudev1-219-42.el7_4.7.x86_64.rpm
12:35:08 11/33 : kernel-abi-whitelists-3.10.0-693.1.1.el7.noarch.rpm
12:35:08 12/33 : libgudev1-devel-219-42.el7_4.7.x86_64.rpm
12:35:08 13/33 : libguestfs-xfs-1.36.3-6.el7_4.3.x86_64.rpm
12:35:08 14/33 : java-1.8.0-openjdk-devel-debug-1.8.0.141-2.b16.el7_4.x86_64.rpm
12:35:08 15/33 : libquadmath-4.8.5-16.el7_4.1.i686.rpm
12:35:08 16/33 : libtsan-static-4.8.5-16.el7_4.1.x86_64.rpm
12:35:08 17/33 : nss-pkcs11-devel-3.28.4-12.el7_4.x86_64.rpm
12:35:08 18/33 : pacemaker-cluster-libs-1.1.16-12.el7_4.7.i686.rpm
12:35:09 19/33 : pacemaker-cluster-libs-1.1.16-12.el7_4.2.i686.rpm
12:35:09 20/33 : libdb-devel-static-5.3.21-21.el7_4.i686.rpm
12:35:09 21/33 : motif-2.3.4-12.el7_4.i686.rpm
12:35:10 22/33 : pki-kra-10.4.1-17.el7_4.noarch.rpm
12:35:10 23/33 : pacemaker-libs-devel-1.1.16-12.el7_4.2.x86_64.rpm
12:35:10 24/33 : 
java-1.8.0-openjdk-javadoc-zip-debug-1.8.0.161-0.b14.el7_4.noarch.rpm
12:35:10 25/33 : pacemaker-libs-devel-1.1.16-12.el7_4.4.i686.rpm
12:35:10 26/33 : pki-symkey-10.4.1-17.el7_4.x86_64.rpm
12:35:10 27/33 : python-rhsm-1.19.10-1.el7_4.x86_64.rpm
12:35:10 28/33 : pacemaker-libs-devel-1.1.16-12.el7_4.7.i686.rpm
12:35:10 29/33 : rubygem-rdoc-4.0.0-33.el7_4.noarch.rpm
12:35:10 30/33 : tuned-utils-2.8.0-5.el7_4.2.noarch.rpm
12:35:10 31/33 : sssd-1.15.2-50.el7_4.6.x86_64.rpm
12:35:11 32/33 : tzdata-2017c-1.el7.noarch.rpm
12:35:11 33/33 : xorg-x11-server-Xnest-1.19.3-11.el7_4.1.x86_64.rpm
Importing packages: |##| 
100.0% 
12:35:32 Linking packages to channel.
12:35:32 Repo http://mirrorlist.centos.org/?release=7=x86_64=updates 
has 0 errata.
12:35:33 Sync of channel completed in 0:00:43.
12:35:33 Total time: 0:00:43

Running spacewalk-repo-sync again results in the same 33 packages being 
downloaded.


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

Re: [Spacewalk-list] All attempts to connect to the database failed when installing Spacewalk 2.7 with PostgreSQL backend

2018-03-30 Thread Vitaly Y. | ServerBee
Got it.

But I prepared my external PostgreSQL installation by other ansible role
before running of spacewalk-setup script .

Also Populate_db stage work out correctly and I can see all needed tables
inside spacewalk pgsql database.

I understand that problem can be from other side and the error can be not
explicit.

I’m still trying to find solution.

El El vie, mar. 30, 2018 a las 09:16, Andrei Popenta <
andrei.pope...@visma.com> escribió:

> Hi,
>
> I am sorry it didn't work for you. I had the same problem and the
> workaround suggested by Eric Burgueño  fixed the installation.
> "you need to initialise the database **before** running spacewalk-setup.
>
> BR,
> Andrei
>
> On Thu, Mar 29, 2018 at 9:45 PM, Vitaly Y. | ServerBee <
> vitaly.yakove...@serverbee.net> wrote:
>
>> Hi,
>>
>> Unfortunately with locale all good on my server:
>>
>> # locale
>> LANG=en_US.UTF-8
>> LC_CTYPE="en_US.UTF-8"
>> LC_NUMERIC="en_US.UTF-8"
>> LC_TIME="en_US.UTF-8"
>> LC_COLLATE="en_US.UTF-8"
>> LC_MONETARY="en_US.UTF-8"
>> LC_MESSAGES="en_US.UTF-8"
>> LC_PAPER="en_US.UTF-8"
>> LC_NAME="en_US.UTF-8"
>> LC_ADDRESS="en_US.UTF-8"
>> LC_TELEPHONE="en_US.UTF-8"
>> LC_MEASUREMENT="en_US.UTF-8"
>> LC_IDENTIFICATION="en_US.UTF-8"
>> LC_ALL=
>>
>>
>> postgres=# \l
>>List of databases
>>Name| Owner  | Encoding |   Collate   |Ctype|
>>Access privileges
>>
>> ---++--+-+-+---
>>  postgres  | postgres   | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
>>  spacewalk | spacewalk_user | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
>> spacewalk_user=CTc/spacewalk_user
>>  template0 | postgres   | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
>> =c/postgres  +
>>||  | | |
>> postgres=CTc/postgres
>>  template1 | postgres   | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
>> =c/postgres  +
>>||  | | |
>> postgres=CTc/postgres
>> (4 rows)
>>
>>
>> It's another problem but I still not resolved it.
>>
>> On Tue, Mar 6, 2018 at 1:34 PM, Andrei Popenta 
>> wrote:
>>
>>> Hi,
>>>
>>> Take a look here, it might help.
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1524221
>>> Andrei
>>>
>>> On Mon, Mar 5, 2018 at 11:10 PM, Vitaly Y. | ServerBee <
>>> vitaly.yakove...@serverbee.net> wrote:
>>>
 Hi,

 I try to setup Spacewalk server by following command:
 # spacewalk-setup --answer-file=/root/spacewalk-answer-file
 --external-postgresql

 I use --external-postgresql option because custom PostgreSQL 9.4
 version has been installed on EL7.

 # cat /root/spacewalk-answer-file
 admin-email = root@localhost
 ssl-set-org = O
 ssl-set-org-unit = OU
 ssl-set-city = L
 ssl-set-state = P
 ssl-set-country = US
 ssl-password = s3cret
 ssl-set-email = root@localhost
 ssl-config-sslvhost = Y
 db-backend=postgresql
 db-name=spacewalk
 db-user=spacewalk_user
 db-password=s3crets3crets3crets3cret
 db-host=localhost
 db-port=5432
 enable-tftp=N

 # cat /var/lib/pgsql/9.4/data/pg_hba.conf
 # PostgreSQL Client Authentication Configuration File (Ansible)
 # TYPE  DATABASEUSERADDRESS METHOD
 local   all all peer
 hostall all 127.0.0.1/32md5
 hostall all ::1/128 md5


 From shell I can connect to PostgreSQL:

 # psql -h localhost -U spacewalk_user -W -d spacewalk
 Password for user spacewalk_user:
 psql (9.2.23, server 9.4.17)
 WARNING: psql version 9.2, server version 9.4.
  Some psql features might not work.
 Type "help" for help.

 spacewalk=# \l
List of databases
Name| Owner  | Encoding |   Collate   |Ctype|
  Access privileges


 ---++--+-+-+--
 -
  postgres  | postgres   | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
  spacewalk | spacewalk_user | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
 spacewalk_user=CTc/spacewalk_user



 Populate_db stage finished without any errors:

 # tail /var/log/rhn/populate_db.log
 INSERT 0 1
 INSERT 0 1
 INSERT 0 1
 INSERT 0 1
 CREATE FUNCTION
  create_varnull_constriants
 
   0
 (1 row)



 But within next setups I always get an error:

 Preparing packages...
 rhn-org-httpd-ssl-key-pair-sw-1.0-1.noarch
 ERROR: there was a problem 

Re: [Spacewalk-list] All attempts to connect to the database failed when installing Spacewalk 2.7 with PostgreSQL backend

2018-03-30 Thread Andrei Popenta
Hi,

I am sorry it didn't work for you. I had the same problem and the
workaround suggested by Eric Burgueño  fixed the installation.
"you need to initialise the database **before** running spacewalk-setup.

BR,
Andrei

On Thu, Mar 29, 2018 at 9:45 PM, Vitaly Y. | ServerBee <
vitaly.yakove...@serverbee.net> wrote:

> Hi,
>
> Unfortunately with locale all good on my server:
>
> # locale
> LANG=en_US.UTF-8
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
>
>
> postgres=# \l
>List of databases
>Name| Owner  | Encoding |   Collate   |Ctype|
>Access privileges
> ---++--+-+--
> ---+---
>  postgres  | postgres   | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
>  spacewalk | spacewalk_user | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
> spacewalk_user=CTc/spacewalk_user
>  template0 | postgres   | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
> =c/postgres  +
>||  | | |
> postgres=CTc/postgres
>  template1 | postgres   | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
> =c/postgres  +
>||  | | |
> postgres=CTc/postgres
> (4 rows)
>
>
> It's another problem but I still not resolved it.
>
> On Tue, Mar 6, 2018 at 1:34 PM, Andrei Popenta 
> wrote:
>
>> Hi,
>>
>> Take a look here, it might help.  https://bugzilla.redhat.com/sh
>> ow_bug.cgi?id=1524221
>> Andrei
>>
>> On Mon, Mar 5, 2018 at 11:10 PM, Vitaly Y. | ServerBee <
>> vitaly.yakove...@serverbee.net> wrote:
>>
>>> Hi,
>>>
>>> I try to setup Spacewalk server by following command:
>>> # spacewalk-setup --answer-file=/root/spacewalk-answer-file
>>> --external-postgresql
>>>
>>> I use --external-postgresql option because custom PostgreSQL 9.4 version
>>> has been installed on EL7.
>>>
>>> # cat /root/spacewalk-answer-file
>>> admin-email = root@localhost
>>> ssl-set-org = O
>>> ssl-set-org-unit = OU
>>> ssl-set-city = L
>>> ssl-set-state = P
>>> ssl-set-country = US
>>> ssl-password = s3cret
>>> ssl-set-email = root@localhost
>>> ssl-config-sslvhost = Y
>>> db-backend=postgresql
>>> db-name=spacewalk
>>> db-user=spacewalk_user
>>> db-password=s3crets3crets3crets3cret
>>> db-host=localhost
>>> db-port=5432
>>> enable-tftp=N
>>>
>>> # cat /var/lib/pgsql/9.4/data/pg_hba.conf
>>> # PostgreSQL Client Authentication Configuration File (Ansible)
>>> # TYPE  DATABASEUSERADDRESS METHOD
>>> local   all all peer
>>> hostall all 127.0.0.1/32md5
>>> hostall all ::1/128 md5
>>>
>>>
>>> From shell I can connect to PostgreSQL:
>>>
>>> # psql -h localhost -U spacewalk_user -W -d spacewalk
>>> Password for user spacewalk_user:
>>> psql (9.2.23, server 9.4.17)
>>> WARNING: psql version 9.2, server version 9.4.
>>>  Some psql features might not work.
>>> Type "help" for help.
>>>
>>> spacewalk=# \l
>>>List of databases
>>>Name| Owner  | Encoding |   Collate   |Ctype|
>>>  Access privileges
>>>
>>> ---++--+-+--
>>> ---+--
>>> -
>>>  postgres  | postgres   | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
>>>  spacewalk | spacewalk_user | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
>>> spacewalk_user=CTc/spacewalk_user
>>>
>>>
>>>
>>> Populate_db stage finished without any errors:
>>>
>>> # tail /var/log/rhn/populate_db.log
>>> INSERT 0 1
>>> INSERT 0 1
>>> INSERT 0 1
>>> INSERT 0 1
>>> CREATE FUNCTION
>>>  create_varnull_constriants
>>> 
>>>   0
>>> (1 row)
>>>
>>>
>>>
>>> But within next setups I always get an error:
>>>
>>> Preparing packages...
>>> rhn-org-httpd-ssl-key-pair-sw-1.0-1.noarch
>>> ERROR: there was a problem trying to initialize the database:
>>>
>>> Exception reported from xx.example.com
>>> Time: Mon Mar  5 22:33:50 2018
>>> Exception type >> ase.SQLConnectError'>
>>>
>>> Exception Handler Information
>>> Traceback (most recent call last):
>>>   File 
>>> "/usr/lib/python2.7/site-packages/spacewalk/satellite_tools/rhn_ssl_dbstore.py",
>>> line 55, in processCommandline
>>> rhnSQL.initDB()
>>>   File 
>>> "/usr/lib/python2.7/site-packages/spacewalk/server/rhnSQL/__init__.py",
>>> line 158, in initDB
>>> raise_with_tb(e, sys.exc_info()[2])
>>>   File 
>>>