Sadly IC still not usable in OES environment. 

Docker and IC are running in the installations. However, there is one problem: a few steps need to be carried out each time after a restart.


A question for those who have problems with the UMC and IC:
in /var/log/messeages

is there something similar to this?

2025-01-29T15:45:45.218460+01:00 oesserver systemd[1]: Starting edirapi container...
2025-01-29T15:45:45.233810+01:00 oesserver docker[30437]: Error response from daemon: No such container: edirapi-container

and

2025-01-29T15:44:12.547307+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:12+01:00 ] : info : TreeResolutionService::getAllTrees:Entered method in service to get tree names
2025-01-29T15:44:24.086712+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : info : LocalStrategy::validate:Entered local strategy login method
2025-01-29T15:44:24.086972+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : info : LdapAuthenticationService::authenticate:Entered the method
2025-01-29T15:44:24.087881+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : info : LdapProxyService::login:Entered Ldap Proxy service login method with dn = cn=OESCommonProxy_oesserver,ou=adm,o=myou
2025-01-29T15:44:24.109683+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : error : LdapProxyService::login:Proxy login failed
2025-01-29T15:44:24.109832+01:00 oesserver bash[7970]:  HttpException: Exception while executing edir API login: connect ECONNREFUSED my-ip:9010
2025-01-29T15:44:24.109924+01:00 oesserver bash[7970]:     at t.edirLogin (/opt/novell/umc/apps/umc-server/main.js:1:14912)
2025-01-29T15:44:24.110030+01:00 oesserver bash[7970]:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
2025-01-29T15:44:24.110114+01:00 oesserver bash[7970]:     at async LdapProxyService.login (/opt/novell/umc/apps/umc-server/main.js:1:37075)
2025-01-29T15:44:24.110212+01:00 oesserver bash[7970]:     at async LdapAuthenticationService.tryUserLoginUsingUsername (/opt/novell/umc/apps/umc-server/main.js:1:29497)
2025-01-29T15:44:24.110307+01:00 oesserver bash[7970]:     at async LdapAuthenticationService.authenticate (/opt/novell/umc/apps/umc-server/main.js:1:29225)
2025-01-29T15:44:24.110387+01:00 oesserver bash[7970]:     at async LocalStrategy.callback [as _verify] (/opt/novell/umc/apps/node_modules/@nestjs/passport/dist/passport/passport.strategy.js:11:44)
2025-01-29T15:44:24.110495+01:00 oesserver bash[7970]: In start readCommonProxyCreds
2025-01-29T15:44:24.239746+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : info : LdapProxyService::login:Entered Ldap Proxy service login method with dn = cn=OESCommonProxy_oesserver,ou=adm,o=myou
2025-01-29T15:44:24.251055+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : error : LdapProxyService::login:Proxy login failed
2025-01-29T15:44:24.251141+01:00 oesserver bash[7970]:  HttpException: Exception while executing edir API login: connect ECONNREFUSED my-ip:9010
2025-01-29T15:44:24.251180+01:00 oesserver bash[7970]:     at t.edirLogin (/opt/novell/umc/apps/umc-server/main.js:1:14912)
2025-01-29T15:44:24.251216+01:00 oesserver bash[7970]:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
2025-01-29T15:44:24.251258+01:00 oesserver bash[7970]:     at async LdapProxyService.login (/opt/novell/umc/apps/umc-server/main.js:1:37075)
2025-01-29T15:44:24.251292+01:00 oesserver bash[7970]:     at async LdapAuthenticationService.tryUserLoginUsingUsername (/opt/novell/umc/apps/umc-server/main.js:1:29497)
2025-01-29T15:44:24.251324+01:00 oesserver bash[7970]:     at async LdapAuthenticationService.tryUserLoginUsingUsername (/opt/novell/umc/apps/umc-server/main.js:1:29957)
2025-01-29T15:44:24.251357+01:00 oesserver bash[7970]:     at async LdapAuthenticationService.authenticate (/opt/novell/umc/apps/umc-server/main.js:1:29225)
2025-01-29T15:44:24.251389+01:00 oesserver bash[7970]:     at async LocalStrategy.callback [as _verify] (/opt/novell/umc/apps/node_modules/@nestjs/passport/dist/passport/passport.strategy.js:11:44)
2025-01-29T15:44:24.251435+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : error : LdapAuthenticationService::tryUserLoginUsingUsername:Exception while login with edir credential
2025-01-29T15:44:24.251481+01:00 oesserver bash[7970]:  undefined
2025-01-29T15:44:24.257168+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : error : Exception thrown: {"response":"Exception while login with edir credential","status":401,"message":"Exception while login with edir credential","na
me":"HttpException"}

Please do not comment on what is not yet possible. I just want to know if there are similar entries in the logs.

I have found other things that should be discussed elsewhere. What I can say here is about iManager and OES services that are buggy or based on deprecated configurations at startup. Otherwise I can say that the dev team has done a good job here. Thanks to the Dev Team. I will try to give the dev team my results with your feedback to get a solution.

Greetings George

I have updatted one server so far. It was up to date prior to new updates being released. I did get an error that was weird I thought. I ignored and continued. It finished and rebooted and all seems fine. I even tried running zipper up after the reboot and still same for one item. I have not seen any issues so far after 18 hours. 

Retrieving: libselinux1-3.7-lp154.200.2.x86_64.rpm ..................................................................................................................................................[not found]
File './x86_64/libselinux1-3.7-lp154.200.2.x86_64.rpm' not found on medium 'download.opensuse.org/.../'
Abort, retry, ignore? [a/r/i/...? shows all options] (a): i
Warning: You have chosen to ignore a problem with download or installation of a package which might lead to broken dependencies of other packages. It is recommended to run 'zypper verify' after the operation has finished.

Anyone else seen this. Will try one or two more over the weekend to see if get the same thing.

I have never seen an opensuse repo on an OES system unless we specifically added it for a non-supported feature. You really don't want to do this. Enable repositories should look something like this;

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

#   | Alias                                                               | Name                                                  | Enabled | GPG Check | Refresh
----+---------------------------------------------------------------------+-------------------------------------------------------+---------+-----------+--------
  1 | OES-23.4-23.4-0                                                     | OES-23.4-23.4-0                                       | Yes     | (r ) Yes  | No
 59 | nu_novell_com:OES24.4-Pool                                          | OES24.4-Pool                                          | Yes     | (r ) Yes  | Yes
 67 | nu_novell_com:OES24.4-SLE-Module-Basesystem15-SP4-Pool              | OES24.4-SLE-Module-Basesystem15-SP4-Pool              | Yes     | (r ) Yes  | Yes
 69 | nu_novell_com:OES24.4-SLE-Module-Basesystem15-SP4-Updates           | OES24.4-SLE-Module-Basesystem15-SP4-Updates           | Yes     | (r ) Yes  | Yes
 72 | nu_novell_com:OES24.4-SLE-Module-Containers15-SP4-Pool              | OES24.4-SLE-Module-Containers15-SP4-Pool              | Yes     | (r ) Yes  | Yes
 74 | nu_novell_com:OES24.4-SLE-Module-Containers15-SP4-Updates           | OES24.4-SLE-Module-Containers15-SP4-Updates           | Yes     | (r ) Yes  | Yes
 77 | nu_novell_com:OES24.4-SLE-Module-Desktop-Applications15-SP4-Pool    | OES24.4-SLE-Module-Desktop-Applications15-SP4-Pool    | Yes     | (r ) Yes  | Yes
 79 | nu_novell_com:OES24.4-SLE-Module-Desktop-Applications15-SP4-Updates | OES24.4-SLE-Module-Desktop-Applications15-SP4-Updates | Yes     | (r ) Yes  | Yes
102 | nu_novell_com:OES24.4-SLE-Module-Server-Applications15-SP4-Pool     | OES24.4-SLE-Module-Server-Applications15-SP4-Pool     | Yes     | (r ) Yes  | Yes
104 | nu_novell_com:OES24.4-SLE-Module-Server-Applications15-SP4-Updates  | OES24.4-SLE-Module-Server-Applications15-SP4-Updates  | Yes     | (r ) Yes  | Yes
112 | nu_novell_com:OES24.4-SLE-Product-SLES15-SP4-Pool                   | OES24.4-SLE-Product-SLES15-SP4-Pool                   | Yes     | (r ) Yes  | Yes
114 | nu_novell_com:OES24.4-SLE-Product-SLES15-SP4-Updates                | OES24.4-SLE-Product-SLES15-SP4-Updates                | Yes     | (r ) Yes  | Yes
115 | nu_novell_com:OES24.4-Updates                                       | OES24.4-Updates                                       | Yes     | (r ) Yes  | Yes

crashmaster18

my post from above has an error

libselinux1 is a runtime library from SELinux and it actually comes from the opensuse repo. OT support should clarify why the URL is invalid

crashmaster18

my post from above has an error

libselinux1 is a runtime library from SELinux and it actually comes from the opensuse repo. OT support should clarify why the URL is invalid

When I check my system, I don't see it, perhaps it's inside a container? Why else would they do this? The right version(s) appears to be in SLE 15 SP4 Base Packages?