Here are the doc updates with the workarounds:

Release Notes:
Upgrade Issue in XEN Environment: https://www.microfocus.com/documentation/open-enterprise-server/23.4/oes_readme/t4j7pxvg1gs6.html#t4nvyk4jqnj5

Installation Guide:

• Upgrading to OES 23.4:  https://www.microfocus.com/documentation/open-enterprise-server/23.4/inst_oes_lx/bv6uejh.html
• Channel Upgrade from OES 2023 to OES 23.4: https://www.microfocus.com/documentation/open-enterprise-server/23.4/inst_oes_lx/b11mrzf5.html
• Troubleshooting - Upgrade Issue in XEN Environment: https://www.microfocus.com/documentation/open-enterprise-server/23.4/inst_oes_lx/t4nvyk4jqnj5.html

Very good statement, but this is not the problem.

we had all read the documentation and do so, i had prerer to take the iso from the released version 23.4

But what will you do when the registration server is not reachable on 2 days (saturday, sunday) for registration? (we use the week-ends to upgrade our server)

What will you do when there are any bugs/troubles when on this oes23.4 server Groupwise 23.4 is installed?

What will you do when links in conf-Files are on ../lib/..., but there are no files there, there are all in ../lib64/...?

What will you do when you must renew your certificates and not all certificates are renew, there are different directories with ohter certificate names

What will you do when after the upgrade you can not start the graphical interface (init 5 or directly starting in graphical mode)?

What will you do when NRM will not started after this upgrade (due on certificates)

What will you do when DNS/DHCP will not run and can't be configured?

What will you do when you are not able to configure Nagios due with pam troubles?

Etc, etc, etc

And you wait long for support and then you will become old documentation or commands that bring nothing!

Thanks on many specialists on the community, that had help me on the major trouble and i am a long novell/Microfocus/OT-Customer since 1986 and had many experience, but never see so much trouble after a simple upgrade named 23.4 and this is only oes2023sp1!

We can only hope, that OT will be better in future and must better assist the new people on the support, but here must be the backline more better.

And since times, it is better to assist with Webex and not only communication with mails. For each trouble i have upload a fresh supportconfig and the really problems are not seen!

I hope that OT had analyzing tools and must give us (the customers) a report of this and all other troubles.

Are we customer able with tools to analyze the supportconfig, without extracting the zip file and take a look in all individual files.

Thanks for transmitting your experience, only share this can help the community and give the possibility to OT to be better in the future

i don't shame me, this is the way for better future in our jobs!!!

cg

I have a publixsuffix conflict when running the upgrade.

this may be a split (brain) dns or mdns problem. I keep seeing this in the field. Unfortunately I don't know the environment in which the publixsuffix conflict occurs. A drawing of how nameservice takes place internally and from internal to external and external is helpful here to isolate the error. Furthermore, it should be noted how name resolution forwarding is done and for which subnet a DNS is authoritative. Please also check whether ipv6 is active, how the IP stack is configured and whether .local is used. The .local domain can have effects that cause public suffix problems. Another aspect to consider is whether public IP ranges are used internally.  Finally, check whether the domain that is used internally is perhaps registered by another company and you are not the owner of the domain. Such a case can also be solved by running a "Black DNS" that is able to provide name resolution via appropriate policies.  Just a quick thought in the blue.

Maybe my answer was too short, on installing the upgrade ; I get a package confilct resolution where I need to downgrade publicsuffix or to download it from one of the repositories which is getting deleted.

Well, this doesn't seem to be a problem of the upgrade per se. You obviously have third party software installed on your to-be-upgraded server that doesn't even exist in the OS repositories (neither in OES2018 nor OES23). This thread really should be limited to real, common upgrade issues in supported scenarios. 

Ehh Massimo, this is a pure OES2023 server, no third party software.
The package conflict arises, since the newer version of publicsuffix is on a reposity which is being deleted with the upgrade.
The upgrade failed on some other part, so I rolled back.Clear to me the upgrade process needs to 'mature" a bit.

Well, this thread is really about OES2018 upgrades, not 2023. That is a completely different issue (and not really an "upgrade" at all, as the base OS is the same).
Nonetheless, I just checked the OES2023 and 23.4 repositories, and the publicsuffix rpms in both repos are 100% the same (literally, as on my SMT server they're linked). So I have to assume you have an isolated problem with your OES23.4 repository.

dear mrosen, you can have your own mind, you had a small and little experience and not able to read all bugs and troubles reported by the community. We have here in Europe a good and working netzwork and we have regulary exchange from information.

Each installation is make other and had a older histtory and there are other aplications installed on the server.

My virtual server has bieen installed with oes11 and gw?? and i had do all upgrades from oes11 to all other version, 2015, 2018, 2023 and now 23.4. And on this server run Groupwise, Kanaka, DNS/DHCP-Console.

I think i know what i do and had a long experience with novell/wicrofocus and now OT.

When by installation the CA Root crashed, on /boot not enough disk size is (but enough to install the new files by removing the old), you find your server with ipv6 that i never had configured. May be i am to old and alos my server.

The false symbolic links and links to non existing files comes from the sky sending from the OT-Angel!

And YES, we had do a fresh a new installation with the ISO and find a many bugs and troubles. On this new OES23.4 we had installed only the newest docker webaccess and the config had each time other dns names in new created files.

Open your eyes and accept the contribution of other specialist we are exchanging!

You are very alone with your statements and only in group we want to communicate to OT to give more security and better scripts on upodates/upgrades with better reporting! And then a better support as now!

Greiner Claude said:

dear mrosen, you can have your own mind,

Yes Claude, he can...

We have rules in the Open Text Community Forums to help everyone get along and to make it easier for community members locate the information they need. I am the first to agree that these rules are not always followed.

Rule: Every thread should be limited to a single topic. A new thread should be started for similar but different issues.

Massimo (mrosen) began this thread and was pointing out to stelgenkamp that he probably should have started a new thread because his was a different issue and then offered a clue to help. 

Rule: Everyone is entitled to express his or her own opinion.

In these technical forums, most of the information we share is based on facts that reveal themselves as the discussions evolve but sometimes when sufficient facts are unavailable members can assess a situation and offer an opinion that may help. We don't have to agree with someone's opinion but they are free to express it.

When we disagree with someone's opinion we are free to offer our own opinion to provide a different point of view but criticising someone for expressing their opinion is not the behaviour we expect.

Greiner Claude said:

But constructive criticism should also be allowed.

Yes!

Kevin Boyle said:

When we disagree with someone's opinion we are free to offer our own opinion to provide a different point of view but criticising someone for expressing their opinion is not the behaviour we expect.

Greiner Claude said:

And portraying others as stupid and incompetent is not constructive!

Agreed. We must choose our words carefully to ensure that does not happen.

Greiner Claude said:

dear mrosen, you can have your own mind, you had a small and little experience and not able to read all bugs and troubles reported by the community.

Greiner Claude said:

Open your eyes and accept the contribution of other specialist we are exchanging!

Greiner Claude said:

You are very alone with your statements

Kevin, you don't accept you own rules

And my ´mind is that your are not "Batman", but only a bad man!

The winner is not Kevin alone, i have phone with your chief and you are fired!!!

This is the end for me, a never ending stroy! 

Greiner Claude said:

And my ´mind is that your are not "Batman", but only a bad man!

Claude,

I am one of the Forum Moderators. Moderators are responsible for assessing the forum content.

We approve posts that are incorrectly flagged as spam and have the ability to remove posts that are abusive or violate forum rules.

In severe cases we can require that all posts from a member be pre-approved before they are posted. Community members who continue to ignore the rules can have their accounts suspended or even removed.

I assumed you were unaware of the rules I posted above or that your criticisms may have been unintentional. I simply wanted to make you aware.

Posts that contain accusations and threats are definitely considered abusive and require further attention. Please do not escalate this matter further.

Seriously Claude. Step back for a day, and reconsider your words (and your wording). You are very well over the line here, and on top, you misunderstand half of what is posted, and falsely accuse the wrong people with thing *you* have misunderstood.
You area  valued long term contributor hewre, but we won't and can't tolerate such behaviour, so kindly reconsider it. Thank you.

Seriously Claude. Step back for a day, and reconsider your words (and your wording). You are very well over the line here, and on top, you misunderstand half of what is posted, and falsely accuse the wrong people with thing *you* have misunderstood.
You area  valued long term contributor hewre, but we won't and can't tolerate such behaviour, so kindly reconsider it. Thank you.

Thank you @mrosen and @Kevin Boyle for reminding everyone about our rules and standards!