Anonymous_User Absent Member.
Absent Member.
3383 views

Software repositories did not need to be changed.

Hi,
I had new activation keys for my systems. One server is causing an issue
and I can not obtain patches. In the Yast Novell Customer Center
Configuration I receive the error:
"Software repositories did not need to be changed. "

On Novell's Customer Centre Web SITE the systems shows as active but
security patches are alerted.

I have tried this TID twice but to no avail.
http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=3303599&sliceId=1&docTypeID=DT_TID_1_1&dialogID=80282181&stateId=1%200%2080278962
Any ideas?

System Details.
SPident

CONCLUSION: System is NOT up-to-date!
found SLE-10-x86_64-SP2 + "online updates"
expected SLE-10-x86_64-SP3

oes-SPident

CONCLUSION: System is up-to-date!
found SLES-10-OES2-SP2-x86_64 + "online updates"

[5]- Done docTypeID=DT_TID_1_1
[6]+ Done dialogID=80282181


Thank you,
Labels (2)
0 Likes
6 Replies
Brunold Rainer
New Member.

Re: Software repositories did not need to be changed.

DrumDude,

I know there was or maybe is a problem with SPident which reports old package versions, but that is not really an error. I think it was something with ruby.

To check that, can you run "SPident -vv" and report that output please ?

And regarding the NCC registrations, as long as the online source might be configured, that message can appear. If you really want to reregister it, remote those existing sources either via yast / software / installation sources or via rug (rug sl - lists all services and the rug sd <nr> deletes the service). But before doing that I would check the SPident report.

Rainer
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Software repositories did not need to be changed.

brunold wrote:
> DrumDude,
>
> I know there was or maybe is a problem with SPident which reports old
> package versions, but that is not really an error. I think it was
> something with ruby.
>
> To check that, can you run "SPident -vv" and report that output please
> ?
>
> And regarding the NCC registrations, as long as the online source might
> be configured, that message can appear. If you really want to reregister
> it, remote those existing sources either via yast / software /
> installation sources or via rug (rug sl - lists all services and the rug
> sd <nr> deletes the service). But before doing that I would check the
> SPident report.
>
> Rainer
>
>

Hi,
Here is your request.
Thank you,

# SPident -vv

Summary (using 1147 packages)
Product/ServicePack conflict match update (shipped)
UnitedLinux-1.0-x86_64 0 0% 0 0% 44 (884 0%)
SLES-8-x86_64 0 0% 0 0% 3 (90 0%)
SLES-8-Supplementary-x86_64 0 0% 0 0% 2 (403 0%)
UnitedLinux-1.0-x86_64-SP2 0 0% 0 0% 9 (97 0%)
UnitedLinux-1.0-x86_64-SP3 0 0% 0 0% 18 (221 0%)
UnitedLinux-1.0-x86_64-SP4 0 0% 0 0% 27 (316 0%)
SLES-9-x86_64 0 0% 0 0% 78 (1597 0%)
NLD-9-x86_64-SP1 0 0% 0 0% 77 (1648 0%)
SLES-9-x86_64-SP1 0 0% 0 0% 51 (524 0%)
SLES-9-x86_64-SP2 0 0% 0 0% 60 (700 0%)
SLES-9-x86_64-SP3 0 0% 0 0% 68 (833 0%)
SLES-10-x86_64 0 0% 295 25.7% 123 (2100 14.0%)
SLE-10-x86_64 0 0% 295 25.7% 127 (2754 10.7%)
SLED-10-x86_64 0 0% 263 22.9% 102 (2030 13.0%)
SLE-10-x86_64-SP1 0 0% 389 33.9% 135 (2938 13.2%)
SLE-10-x86_64-SP2 0 0% 509 44.4% 139 (3111 16.4%)
SLE-10-x86_64-SP3 1 0.0% 799 69.7% 146 (3275 24.4%)
- ruby 1.8.4-17.20 < 1.8.6.p369-0.4
Unknown 349 30.4%

Legend for Package Details:
- conflicting package (found < expected)

CONCLUSION: System is NOT up-to-date!
found SLE-10-x86_64-SP2 + "online updates"
expected SLE-10-x86_64-SP3
0 Likes
Brunold Rainer
New Member.

Re: Software repositories did not need to be changed.

DrumDude,

the SPident reports that there is exactly one package (ruby) on the system that has an older version (1.8.4-17.20) then it should have (1.8.6.p369-0.4).

And that is exactly the package I mentioned in my first reply on this thread. That version mismatch is not correct and is a package problem from the SPident package itself. You can ignore that.

Rainer
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Software repositories did not need to be changed.

brunold wrote:
> DrumDude,
>
> the SPident reports that there is exactly one package (ruby) on the
> system that has an older version (1.8.4-17.20) then it should have
> (1.8.6.p369-0.4).
>
> And that is exactly the package I mentioned in my first reply on this
> thread. That version mismatch is not correct and is a package problem
> from the SPident package itself. You can ignore that.
>
> Rainer
>
>


Right, still can not get patches even though the systems in CCCenter are
active, still getting access denied errors as well on some systems.
0 Likes
Brunold Rainer
New Member.

Re: Software repositories did not need to be changed.

DrumDude,

as a test you can try to give on system a new id and then reregister it against the Novell Customer Center and see if that will get updates.

Just to make sure, your activation key has not expired ?

To give a system anew id you might do the following:

# rug sl

then delete all services listed by rug sl by running rug sd for each service number, till all services are deleted.

# rug sd <service number>

then continue with

# rczmd stop
# rm /dev/zmd/deviceid
# rm /dev/zmd/secret
# rczmd start

Then register this system newly against the Novell Customer Cneter via yast and provide your activation key. That should register it and add the update services. After that check if you see updates.

Rainer
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Software repositories did not need to be changed.

brunold wrote:
> DrumDude,
>
> as a test you can try to give on system a new id and then reregister it
> against the Novell Customer Center and see if that will get updates.
>
> Just to make sure, your activation key has not expired ?
>
> To give a system anew id you might do the following:
>
> # rug sl
>
> then delete all services listed by rug sl by running rug sd for each
> service number, till all services are deleted.
>
> # rug sd <service number>
>
> then continue with
>
> # rczmd stop
> # rm /dev/zmd/deviceid
> # rm /dev/zmd/secret
> # rczmd start
>
> Then register this system newly against the Novell Customer Cneter via
> yast and provide your activation key. That should register it and add
> the update services. After that check if you see updates.
>
> Rainer
>
>


Problem is that zmd was in some hung state... apparently fixed in SLES
11. I had to reboot my server.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.