Highlighted
Anonymous_User Absent Member.
Absent Member.
294 views

Upgrade OES2018 -> OES2018SP1: IDM BE - missing requirements

Hi,

I upgrade a OES2018 -> OES2018SP1 as usual. But when it is an IBM-BE the
host throws:

======================
# zypper dup --from OES2018-SP1-SLES12-SP3-Pool --from
OES2018-SP1-SLES12-SP3-Updates --from OES2018-SP1-Pool --from
OES2018-SP1-Updates --from OES2018-SP1-SLE-Module-Containers12-Pool
--from OES2018-SP1-SLE-Module-Containers12-Updates
Refreshing service 'SMT-http_mydom_local'.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
3 Problems:
Problem: novell-DXMLeventx-4.6.2-0.x86_64 requires novell-NDSserv, but
this requirement cannot be provided
Problem: novell-DXMLengnx-4.6.2-0.x86_64 requires novell-DXMLeventx, but
this requirement cannot be provided
Problem: novell-DXMLjntlsx-4.6.0-0.x86_64 requires novell-DXMLengnx, but
this requirement cannot be provided


Problem: novell-DXMLeventx-4.6.2-0.x86_64 requires novell-NDSserv, but
this requirement cannot be provided
uninstallable providers:
novell-NDSserv-9.0.3.2-1.15.x86_64[SMT-http_mydom_local:OES2018-Pool]


novell-NDSserv-9.1.0-10.7.x86_64[SMT-http_mydom_local:OES2018-Updates]

Solution 1: Following actions will be done:
keep obsolete novell-NDSserv-9.1.3-17.5.x86_64
keep obsolete novell-dclient-9.1.3-14.14.x86_64
keep obsolete novell-edirectory-filesystem-9.1.3-7.2.x86_64
keep obsolete novell-edirectory-libxerces-c-3.1.1-0.15.2.x86_64
keep obsolete novell-libsal-9.1.3-7.2.x86_64
keep obsolete novell-nmas-server-9.1.3-13.9.x86_64
keep obsolete novell-npkiapi-9.1.3-9.6.x86_64
keep obsolete novell-npkit-9.1.3-9.6.x86_64
keep obsolete novell-ntls-9.1.3-7.6.x86_64
keep obsolete novell-nmas-client-9.1.3-9.4.x86_64
Solution 2: deinstallation of novell-DXMLeventx-4.6.2-0.x86_64
Solution 3: break novell-DXMLeventx-4.6.2-0.x86_64 by ignoring some of
its dependencies

Choose from above solutions by number or skip, retry or cancel
[1/2/3/s/r/c] (c):

# zypper lr -E
Repository priorities are without effect. All enabled repositories share
the same priority.

# | Alias
| Name | Enabled | GPG
Check | Refresh
---+----------------------------------------------------------------------------+----------------------------------------------+---------+-----------+--------
1 | SMT-http_mydom_local:OES2018-Pool
| OES2018-Pool | Yes | (r ) Yes |
Yes
8 | SMT-http_mydom_local:OES2018-SLE-Module-Containers-12-SP2-Pool
| OES2018-SLE-Module-Containers-12-SP2-Pool | Yes | (r ) Yes |
Yes
9 | SMT-http_mydom_local:OES2018-SLE-Module-Containers-12-SP2-Updates
| OES2018-SLE-Module-Containers-12-SP2-Updates | Yes | (r ) Yes |
Yes
16 | SMT-http_mydom_local:OES2018-SLES12-SP2-Pool |
OES2018-SLES12-SP2-Pool | Yes | (r ) Yes | Yes
17 | SMT-http_mydom_local:OES2018-SLES12-SP2-Updates |
OES2018-SLES12-SP2-Updates | Yes | (r ) Yes | Yes
18 | SMT-http_mydom_local:OES2018-SP1-Pool |
OES2018-SP1-Pool | Yes | (r ) Yes | Yes
19 | SMT-http_mydom_local:OES2018-SP1-SLE-Module-Containers12-Pool |
OES2018-SP1-SLE-Module-Containers12-Pool | Yes | (r ) Yes | Yes
20 | SMT-http_mydom_local:OES2018-SP1-SLE-Module-Containers12-Updates |
OES2018-SP1-SLE-Module-Containers12-Updates | Yes | (r ) Yes | Yes
21 | SMT-http_mydom_local:OES2018-SP1-SLES12-SP3-Pool |
OES2018-SP1-SLES12-SP3-Pool | Yes | (r ) Yes | Yes
22 | SMT-http_mydom_local:OES2018-SP1-SLES12-SP3-Updates |
OES2018-SP1-SLES12-SP3-Updates | Yes | (r ) Yes | Yes
23 | SMT-http_mydom_local:OES2018-SP1-Updates |
OES2018-SP1-Updates | Yes | (r ) Yes | Yes
24 | SMT-http_mydom_local:OES2018-Updates |
OES2018-Updates | Yes | (r ) Yes | Yes


======================

I did not found any hints in documentation or relesae notes.

Where should I look for?

I assume that solution 1 will do the trick but I am not sure. Any
recommendations?

Bernd
Labels (2)
0 Likes
7 Replies
Knowledge Partner
Knowledge Partner

Re: Upgrade OES2018 -> OES2018SP1: IDM BE - missing requirements

Hi.

On 30.04.2019 10:01, nntp-user wrote:
> Hi,
>
> I upgrade a OES2018 -> OES2018SP1 as usual. But when it is an IBM-BE the
> host throws:


Probably same as:

https://support.microfocus.com/kb/doc.php?id=7023797

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
obscurityPrivacy Respected Contributor.
Respected Contributor.

Re: Upgrade OES2018 -> OES2018SP1: IDM BE - missing requirements

Is this fixed meanwhile?
0 Likes
Knowledge Partner
Knowledge Partner

Re: Upgrade OES2018 -> OES2018SP1: IDM BE - missing requirements

*Very* unlikely. I wouldn't expect this exact issue to ever be fixed. 

 

CU,

Massimo

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Knowledge Partner
Knowledge Partner

Re: Upgrade OES2018 -> OES2018SP1: IDM BE - missing requirements

Hi Bernd,

Just a reminder: If you don't get your issue resolved here, you should consider opening a Service Request with Micro Focus.

_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
obscurityPrivacy Respected Contributor.
Respected Contributor.

Re: Upgrade OES2018 -> OES2018SP1: IDM BE - missing requirements

hmm ... the TID is from the beginning of the year ... and it seems that there is not a lot of effort neccessary to correct the upgrade... If there was no activity yet I think it is not neccessary to ask for more ... MF let it die ... like the most of the old Novell SW ... so why they buy them?
0 Likes
Knowledge Partner
Knowledge Partner

Re: Upgrade OES2018 -> OES2018SP1: IDM BE - missing requirements


@obscurityPrivacy wrote:
hmm ... the TID is from the beginning of the year ... and it seems that there is not a lot of effort neccessary to correct the upgrade... If there was no activity yet I think it is not neccessary to ask for more ... MF let it die ... like the most of the old Novell SW ... so why they buy them?

I think you're wrong. Quite the opposite, there is a *LOT* of effort necessary to correct this, and that's the whole reason why I believe it will enver be fixed, as it's close to impossible.

Let's look what happened here: In OES2018SP1, someone decided to change the names of the eDirectory components for political reasons, and to finally remove "novell" from it. Unfortunately, without proper checking or ignoring (see: political) that there are other packages out there that look for those package names in their dependencies, like e.g IDM. So now those dependencies fail.

Now, considering the damage is already done: How do you think it is easy to "fix" that? You can't change the dependencies of an already installed, old software. You can also hardly revert the change of the new eDirectory package names, as you'll break other, current products that already have their dependencies changed to match those.

So yes, this is oen of those changes done without proper planning or considering the consequences. But it is not easy to fix at all, the problem will go away on it's own as soon as people update to supported IDM versions (4.6.2 is not supported on OES2018SP1 BTW), and I really fail to understand how you arive at the conclusion anybody is letting anything die here...

CU,

Massimo

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
obscurityPrivacy Respected Contributor.
Respected Contributor.

Re: Upgrade OES2018 -> OES2018SP1: IDM BE - missing requirements

Hi Massimo,
thx for your explanation!
I was thought that is cloud be able to add the 'ignore' option into the RPM.

So the dependency were met the requirements.

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.