Users are not working after DCO upgrade to version 8.3

[DCIM_Support]

This question was originally posted on DCIM Support by Andres Cordero on 2019-05-03

---

Hello Support,
We performed the DCO upgrade from 8.2 to version 8.3 using the link below as guide:

https://sxwhelpcenter.ecostruxureit.com/display/public/UADCO8x/Getting+from+previous+versions+to+DCO... 

The upgrade logs shows the process as successful (Attached file "upgrade logs")
The about section shows the version correctly. (Attached file "upgrade completed")

Also, the webmin seems to be working normal.

The problem is with the User authentication.
The service is not working at all. So, we can't get access to the platform.
Local Users and AD User are useless. (Attached file "error users").


upgrade logs.txt

(CID:143755215)

[DCIM_Support]

This comment was originally posted on DCIM Support by Greg Sterling on 2019-05-03

---

Can you also attach the server.log file from the dco server?

Also, does webmin show the DCO application and database services are all running?

How much time since the upgrade completed has passed since the server rebooted?

You're upgrading from DCO 8.2.2 to 8.3, there are a few database schema update which have to be applied before the dco server upgrade is completed. These updates can take some time to complete.

Regards

Greg Sterling

(CID:143755222)

[DCIM_Support]

This comment was originally posted on DCIM Support by Andres Cordero on 2019-05-04

---

Hello Greg,

1. I will to schedule with our customer to try again the upgrade on next monday.
   Please confirm the path to download the server.log file.
2. Yes, Please check attached file. (status)
   
3. 20 minutes, more or less.

(CID:143755231)

[DCIM_Support]

This comment was originally posted on DCIM Support by Greg Sterling on 2019-05-04

---

I dont think I would rerun the upgrade, it looked like it worked based on the log file you had attached.

Can you upload the server.log file so we can see if there were errors in the DCO services when they restarted? The server log can be found in this folder on the dco server /opt/jboss-as/standalone/log

Regards

Greg Sterling

(CID:143755236)

[DCIM_Support]

This comment was originally posted on DCIM Support by Andres Cordero on 2019-05-04

---

Greg,

This server is in production.

That's why before run the upgrade we created a snapshot,  to have a restore point.

So after the upgrade and seeing that the server was not working as expected. We restored the VM to the snapshot point.

Currently the server is on version 8.2.
We must re-run the upgrade in order to extract the requested file.

By the way, we ran the upgrade process 3 times and we had the same result.

(CID:143755239)

[DCIM_Support]

This answer was originally posted on DCIM Support by Lukas Jegerlehner on 2019-07-26

---

Hi all. I have the exact same issue. 

the field "force_single_sign_on" is missing in the table public.users. --> no user can login. 

I m wondering if you got the issue solved and how?

The upgrade went well. I am suspecting an issue after rebooting within the java which should adjust the database. somehow it did not happen. 

Br Lukas

(CID:147198830)

[DCIM_Support]

This comment was originally posted on DCIM Support by Greg Sterling on 2019-07-26

---

I'm waiting on dev help for the other reported problem (perhaps you logged that call?)

Regards

Greg Sterling

(CID:147198880)

[DCIM_Support]

This comment was originally posted on DCIM Support by Lukas Jegerlehner on 2019-07-28

---

Hi Greg, what was the other reported problem?

Could it have anything to do with custom property fields  ....

I hope the waiting doesn't take too long 😉

Cheers Lukas

(CID:147199338)

[DCIM_Support]

This comment was originally posted on DCIM Support by Lukas Jegerlehner on 2019-08-05

---

please see my findings below:

here is a quick description how to provoke the case. Can you and your development team please look into fixing the issue for the next release. Thank you in advance.

1. Two clean dco installations (version 8.2.12)

2. Connect DR node.
3. For dco2 the ISXO_BACKUP_SITE field, within the /etc/isx-operations/config file, will become 1 (slave).
4. promote dco2 —> ISXO_BACKUP_SITE for dco2 will become 2 (master)
5. upgrade dco2 to the latest version 8.3.2. Schema will not update due to ISXO_BACKUP_SITE = 2 (wasn’t cleared).  
6. ExecStartPre=/usr/libexec/dco-platform/schemaUpgrade.sh —> The IF within the schemaUpgrade Shell checks if the field ISXO_BACKUP_SITE is empty.  
7. In the case of switching the DR back and forth between two servers (this could happen over time), both servers will end up with a field entry ISXO_BACKUP_SITE = 2, once disconnected again. 
8. —> solution: check the IF statement within schemaUpgrade.sh, which was added after version 8.2.12. For the slave ISXO_BACKUP_SITE = 1 it makes sense to not run a schema update. For 2 and ‘ ‘ schema upgrades may should be performed ?

(CID:147201855)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.