Hi, I am doing the upgrade right now from 24.3 to 24.4 following the link below you can see the instruction on how to do dist-upgrade so it goes to 24.4 repos

https://www.microfocus.com/documentation/open-enterprise-server/24.4/inst_oes_lx/b11mrzf5.html#b11msl68

Hope it helps you.

thank you, have to wait to saterday to be out of business hours, for mext try

Hi, 

I did the upgrade yesterday, seams successfull, server comes up as OES 24.4, the 24.4 repos are exists, and sever works fine. But I can not rid of the old repos,

Even if I delete them in YAST they are there again when I restart YAST even after reboot.

And if I do an online update via YAST I get the the following message.

the server is registered at SUSE and at OPENTEXT (Novell) and the customer has a valid subscription

What the hell is wrong?

Regards

Rainer

1. The out of support message is bogus. It will be fixed soon. It has no impact on upgrade. It can safety ignored. 

2. Oes 24.1, 24.2 and 24.3 versions did not have their own repositories, all used the 23.4  . With upgrading to 24.4, you will get the 24.4 repositories.  Type:

zypper lr

24.4 repositories should show active,  23.x disabled.  If that is correct,  you are fine.

but why do I have still repos from OES 2018

I updated at customer site from OEES 24.3 to 24.4 running in problems

. the old repositories are still there and not disabled

the NSS volume cat not mounted because filesystentype nssvol unknown

but why do I have still repos from OES 2018

I updated at customer site from OEES 24.3 to 24.4 running in problems

. the old repositories are still there and not disabled

the NSS volume cat not mounted because filesystentype nssvol unknown

Only the 24.4 should be enabled. Not sure why the old ones are still showing as active. If you follow the 24.4 documentation, you can read which one needs to be active and the rest you can set them in disabled.

There're are still listed because their cache is still present and repos are manage by the subscriptions server. So, as long as they're on your subscription, you can delete from disk but with zypper refresh -s, they will appear again. If you run this command to get more info about a repo:

zypper lr alias name

ie

zypper lr nu_novell_com:OES23.4-Pool

zypper lr nu_novell_com:OES23.4-Pool
Alias : nu_novell_com:OES23.4-Pool
Name : OES23.4-Pool
URI : nu.novell.com/.../sle-15-x86_64
Enabled : No
GPG Check : ----
Priority : 99 (default priority)
Autorefresh : On
Keep Packages : Off
Type : N/A
GPG Key URI :
Path Prefix :
Parent Service : nu_novell_com
Keywords : ---
Repo Info Path : /etc/zypp/repos.d/nu_novell_com:OES23.4-Pool.repo
MD Cache Path : /var/cache/zypp/raw/nu_novell_com:OES23.4-Pool

You see that Repo Info Path still have the cached the repo.

you can use zypper rr alias to delete the repo but you will get this message:

zypper rr nu_novell_com:OES23.4-Pool
Removing repository 'OES23.4-Pool' ........................................................................................................[done]
Repository 'OES23.4-Pool' has been removed. [volatile]
Warning: Repo 'nu_novell_com:OES23.4-Pool' is managed by service 'nu_novell_com'. Volatile changes are reset by the next service refresh!

Now it is gone:

zypper lr nu_novell_com:OES23.4-Pool
Repository 'nu_novell_com:OES23.4-Pool' not found by its alias, number, or URI.
Use 'zypper repos' to get the list of defined repositories.

but a

zypper refresh -s

it will put it back because it is still on your subscription.
but it is nothing bad that they're still listed as long as they're disabled.

Regarding the nss error, without a supportconfig, i can not help you but i'm sure OT support will do thru your case

Thank you very much for the detailed explanation

the important information for me is that it does not harm and has nothing to do with my NSS problem

Regards  

Rainer