Highlighted
Knowledge Partner
Knowledge Partner
105 views

CASA version chaos depending how ZCM server arrived at 2017.4.1

Hi.

Due to authentication issues I had at a site, I started checking into CASA on various ZCM servers, and found a true chaos, apparently depending how they were installed and patched inbetween.

A Server installed as 2017.0, and then patched to 2017.4.1  has the following installed:

CASA_auth_token_jaas_support-1.7.1910-1.1.noarch
CASA-32bit-1.7.1885-1.x86_64
CASA-1.7.1885-1.x86_64
CASA_auth_token_svc-1.7.1923-3.1.noarch


A server that started it's life at some point as Zenworks 11, and has been updated over time, also at 2017.4.1 now, has:

CASA_auth_token_jaas_support-1.7.1910-1.1.noarch

CASA-32bit-1.7.1769-1.x86_64
CASA-1.7.1769-1.x86_64

CASA_auth_token_svc-1.7.1923-3.1.noarch

 

These are also the same versions that on each of these servers sit in the /opt/novell-zenworks-install/downloads/rpm directory, aka on the second one, despite it definitely having been updated with 2017, the CASA rpms that ZCM 2017 ships with are nowhere on the local drive. 

And finally my problem server that broke after updating it from 2017.1 to 2017.4.1, that one has

CASA-32bit-1.7.1669-1.x86_64

installed, but no more CASA x86_64 installed at all, most likely because in the novell-zenworks-install/rpm directory holds CASA-1.7.1720-1.*

Something's *really* fisky here, and IMHO the core problem is that *updating* a server with ZCM2017 does very obviously *not* update CASA to the versions included wit 2017 properly.

 

 

 



A Server installed 

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
Labels (1)
Tags (1)
0 Likes
1 Reply
Knowledge Partner
Knowledge Partner

Re: CASA version chaos depending how ZCM server arrived at 2017.4.1

And it goes on.

I think I know why the different CASA versions exist. CASA has a dependency for mono > 1.13, but that dependency can't be provided on SLES. ZCM itself installs a novell-zenworks-zcm-mono-2.0.1-1.x86_64, but of course that doesn't match CASA's requirement, legally.

So I have to assume that the ZCM2017 iso install fails to install/update CASA because of the unfulfilled dependancy for mono, *but* that zcm patches install the RPMs using --nodeps, ignoring those dependancies.

And while I was debugging this, I found that the ZCM2017 iso also contains a 

CASA_auth_token_jaas_support-1.7.1915-1.1.noarch

That is oddly not installed on any of my servers, instead they have

CASA_auth_token_jaas_support-1.7.1910-1.1.noarch

That's because the former, newer version doesn't install as it's corrupt, it fails the signature check.

 

Oh wow...

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
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.