DCO upgrade 8.2.12 failed

[DCIM_Support]

This question was originally posted on DCIM Support by Luis Lopez Borbon on 2019-03-19

---

Hello Jef and DCIM support team

Today I tried to upgrade a DCO server from version 8.2.7 to 8.2.12 and the server failed the upgrade, and the upgrade logs shows “the upgrade process did not result in a new version of DCO”. The options  “no third-party RPM” and “Do not download packages from internet” were seleted… the DCO log file from the webmin was downloaded, if you needed please let me know how the best way is to share you. Please your support because I have scheduled many customers to upgrade their servers.

(CID:141264689)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-19

---

Hi Luis,

Please share the server logs with me, then I will take a look.

Server logs (complete set) (in 8.2.7) can be collected from webmin interface, StruxureWare DC Operation > Download Lof Files > Download log files

I will send you an invite to my =S= box shortly, thanks.

Kind regards

(CID:141264738)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-20

---

Hi Luis,

My invite (from yesterday) appears to be pending, so I have resend the invite moment ago.

Kind regards

(CID:141264896)

[DCIM_Support]

This comment was originally posted on DCIM Support by Luis Lopez Borbon on 2019-03-21

---

Hi Jef,

the DCO log file was uploaded in the box.. if you need additional information please let me know

regards

(CID:141265647)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-21

---

Hi Luis,

Thanks, I will look into it and will get back to you as soon as possible,

Kind regards

(CID:141265669)

[DCIM_Support]

This answer was originally posted on DCIM Support by Jef Faridi on 2019-03-25

---

Hi Luis,

Thanks again for providing the server logs. According to the log entries it appears you have correctly selected the offline installation option, but upgrade fails anyway due to server being unable to connect to the Internet (it looks it's trying to check for updates related to the OS). I have registered a bug report for details investigation (and possible enhancements in future version(s)).

Thanks,

Kind regards

(CID:141266457)

[DCIM_Support]

This comment was originally posted on DCIM Support by Luis Lopez Borbon on 2019-03-25

---

Hi Jef,

thank you for your support! According your feedback about this issue, the root cause is a bug in the ISO file. This means all upgrades in version 8.2.12 will failed, right? Do you recommend upgrade the servers in a new clean DCO server with version 8.2.12 and restore it with the backup 8.2.7 or Do you recommend do not upgrade my customer servers at all until a new ISO file is released? Is a newsletter released explained this issue? I ask you because many customers are waiting this upgrade and I may to write a letter explain the situation…I appreciate your advises how to proceed…

Regards,

(CID:141266871)

[DCIM_Support]

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

---

Luis, Yes. The scenario you outlined in your previous response is a common workaround for upgrade problems.

Customers who experience difficulty upgrading to a release sometimes provision a new DCO server, fresh install the newer DCO release on the new server, and then restore the backup from the older DCO release on the new server. The restore process will upgrade the database if necessary.

Regards

Greg Sterling

(CID:141267390)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-27

---

Hi Luis,

We have been running some local tests, and it seems the only way we could reproduce a similar upgrade issue is to have a machine (with no internet access), but not selecting the "Do not download packages from the Internet" option.

You mentioned, you had both options selected: "No thirdparty RPMs" and "Do not download packages from the Internet"

My suggestion would be to try with just this one: "Do not download packages from the Internet"

If it should fail, clean instillation and then restoring the latest good backup file could be an alternative.

Kind regards

(CID:141267612)

[DCIM_Support]

This comment was originally posted on DCIM Support by Luis Lopez Borbon on 2019-03-27

---

Hi Jef and Greg

I will do the upgrade next week according your recommendation. I will provide you a feedback if the upgrade fails or is successfully. Regards

(CID:141267623)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-27

---

Hi Luis,

Sounds fine, thanks.

Kind regards

(CID:141267644)

[DCIM_Support]

This comment was originally posted on DCIM Support by Luis Lopez Borbon on 2019-04-10

---

Hello Jef,

I did a clean installation to upgrade the DCO server… not issue during the restore process and right now the server is up and running. But two licenses were missing during the process… the energy cost license and the Insight license were missing. I will write an mail to get support to recover this two licenses.

(CID:142051220)

[DCIM_Support]

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

---

Hello Luis. I believe this item has been answered in the direct emails you had sent. In the release notes for DCO 8.3 you'll find the energy cost license is now included as part of the based dco rack licenses (so its included by default) and the Insight license is no longer offered. If insight is needed you can continue to use the Insight client from the previous DCO release.

Regards

Greg Sterling

(CID:142051277)

[DCIM_Support]

This answer was originally posted on DCIM Support by jean-claude WILSON on 2019-04-02

---

I had the same problem on several servers, and finally i found the bug:

the upgrade looks for a directory which does not exist on DCO 8.2.7

you have to create it on the server:  "/data/upgrad/

after that my update went well

Regards

(CID:141270058)

[DCIM_Support]

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