Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1100758

Summary: After I apply packages, I can see all packages are updated successfully in spacewalk web console; but in client server, all packages are not yet updated
Product: [Community] Spacewalk Reporter: littlekai <littlekai9>
Component: WebUIAssignee: Michael Mráka <mmraka>
Status: CLOSED EOL QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 2.1CC: littlekai9
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 11:43:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screendump
none
screendump1 none

Description littlekai 2014-05-23 11:48:41 UTC 
Description of problem:
After I update packages, I can see all packages are updated successfully in spacewalk web console, 
however in client server(RHEL5.7), all packages are not yet updated

Version-Release number of selected component (if applicable):
spacewalk : Spacewalk release 2.1 nightly
Client Server:  Red Hat Enterprise Linux Server release 5.7 (Tikanga)



How reproducible:


Steps to Reproduce:
1. update packages in spacewalk web console
2. check the packages are updated in spacewalk web console
3. check the packages not yet applied in client server by "rpm -qa" commands 
 

Actual results:
all packages not yet updated

Expected results:
all packaged should be updated

Additional info:
no any log related to packages updated in /var/log/up2date in client servers
Comment 1 Stephen Herr 2014-05-23 11:55:18 UTC 
Sorry for asking dumb questions, but I don't believe that this is possible as you describe. Are you sure you're looking at the client server that corresponds with the server profile in the web? Are there perhaps two client servers with the same systemid (grep ID /etc/sysconfig/rhn/systemid), one which is picking up and executing your update action and the other which you are looking at?
Comment 2 littlekai 2014-05-30 03:57:56 UTC 
grep ID /etc/sysconfig/rhn/systemid in client server find out ID "ID-1000010140"
----------------------------Screen Dump-------------------------
[root@ttid-gp2web1 ~]# grep ID /etc/sysconfig/rhn/systemid
<value><string>ID-1000010140</string></value>
[root@ttid-gp2web1 ~]#
----------------------------End of Screen Dump--------------------

spacewalk-report inventory | grep 1000010140 in patch servers, show only one system" ttid-gp2web1" has this ID 

--------------------Screen Dump in patch server---------------
[root@ttis-patch1 ~]# spacewalk-report inventory | grep 1000010140
1000010140,ttid-gp2web1.egisdctr.hksarg,ttid-gp2web1.egisdctr.hksarg,10.123.11.11,,egisadm,2014-01-07 16:12:56,2014-05-30 11:47:55,2.6.18-274.el5,22,14,RHEL5 Channel,,Spacewalk Management Entitled Servers;Spacewalk Monitoring Entitled Servers;Spacewalk Provisioning Entitled Servers,,Spacewalk Default Organization,,x86_64,2 CPUs unknown Sockets; eth0 10.123.11.11/255.255.255.0 00:50:56:a0:6f:ef; eth0:1 10.123.11.99/255.255.255.0 00:50:56:a0:6f:ef; eth0:2 10.123.11.101/255.255.255.0 00:50:56:a0:6f:ef; eth0:3 10.123.11.103/255.255.255.0 00:50:56:a0:6f:ef; eth0:4 10.123.11.105/255.255.255.0 00:50:56:a0:6f:ef; eth0:5 10.123.11.107/255.255.255.0 00:50:56:a0:6f:ef; eth0:6 10.123.11.109/255.255.255.0 00:50:56:a0:6f:ef; eth1 10.123.20.11/255.255.255.0 00:50:56:a0:1a:79; eth2 10.123.96.41/255.255.255.0 00:50:56:a0:4a:18; lo 127.0.0.1/255.0.0.0 00:00:00:00:00:00
[root@ttis-patch1 ~]#

----------------------End Of Screen Dump in patch Server----------

I don't know there is two client servers with the same systemid, please advise
Comment 3 littlekai 2014-05-30 04:03:33 UTC 
grep ID /etc/sysconfig/rhn/systemid in client server find out ID "ID-1000010140"
----------------------------Screen Dump-------------------------
[root@ttid-gp2web1 ~]# grep ID /etc/sysconfig/rhn/systemid
<value><string>ID-1000010140</string></value>
[root@ttid-gp2web1 ~]#
----------------------------End of Screen Dump--------------------

spacewalk-report inventory | grep 1000010140 in patch servers, show only one system" ttid-gp2web1" has this ID 

--------------------Screen Dump in patch server---------------
[root@ttis-patch1 ~]# spacewalk-report inventory | grep 1000010140
1000010140,ttid-gp2web1.egisdctr.hksarg,ttid-gp2web1.egisdctr.hksarg,10.123.11.11,,egisadm,2014-01-07 16:12:56,2014-05-30 11:47:55,2.6.18-274.el5,22,14,RHEL5 Channel,,Spacewalk Management Entitled Servers;Spacewalk Monitoring Entitled Servers;Spacewalk Provisioning Entitled Servers,,Spacewalk Default Organization,,x86_64,2 CPUs unknown Sockets; eth0 10.123.11.11/255.255.255.0 00:50:56:a0:6f:ef; eth0:1 10.123.11.99/255.255.255.0 00:50:56:a0:6f:ef; eth0:2 10.123.11.101/255.255.255.0 00:50:56:a0:6f:ef; eth0:3 10.123.11.103/255.255.255.0 00:50:56:a0:6f:ef; eth0:4 10.123.11.105/255.255.255.0 00:50:56:a0:6f:ef; eth0:5 10.123.11.107/255.255.255.0 00:50:56:a0:6f:ef; eth0:6 10.123.11.109/255.255.255.0 00:50:56:a0:6f:ef; eth1 10.123.20.11/255.255.255.0 00:50:56:a0:1a:79; eth2 10.123.96.41/255.255.255.0 00:50:56:a0:4a:18; lo 127.0.0.1/255.0.0.0 00:00:00:00:00:00
[root@ttis-patch1 ~]#

----------------------End Of Screen Dump in patch Server----------

I don't know there is two client servers with the same systemid, please advise
Comment 4 littlekai 2014-06-24 17:41:06 UTC 
Hi any update
Comment 5 Stephen Herr 2014-06-24 20:06:09 UTC 
There's no way to tell from the Spacewalk if you have two servers using the same systemId; systemId is how Spacewalk tells servers apart so if they're both using the same systemId then Spacewalk thinks they are the same even though they are not.

You'd have to know your server layout. Is this perhaps a virtual machine that you've replicated the disk of? As a test to see if some other server is using the same systemId I'd propose that you move the systemId to /etc/sysconfig/rhn/systemid.save or something and wait for a day. What *should* happen is that the server will not check in and after a day the system status will become "unknown". What will happen if another server is checking in using the same systemId is that the last checkin date will be updated after it should not have been and the system profile will still appear to be active with a known status. Then you should be able to track down the duplicate server using the reported hostname / ip address.
Comment 6 littlekai 2014-07-08 03:09:22 UTC 
Dear Stephen,

I have already moved the systemID to /etc/sysconfig/rhn/systemid.save and wait for a day, however the system status is "system not checking in with spacewalk".

please advise
Comment 7 Stephen Herr 2014-07-08 13:41:03 UTC 
In that case I have no advice, that means that you only have one physical system using that server profile.

Can you be more specific about step 2 in comment 0? What page are you going to that makes you think the packages have already been applied to the system?
Comment 8 littlekai 2014-07-10 06:06:05 UTC 
Attached please find the page shows packages have already been applied to the system
Comment 9 littlekai 2014-07-10 06:09:21 UTC 
Created attachment 916999 [details]
screendump
Comment 10 littlekai 2014-07-10 06:10:57 UTC 
Created attachment 917000 [details]
screendump1
Comment 11 Michael Mráka 2019-10-16 11:43:56 UTC 
Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.