VxRail update 02-February-2022 7.0.320

Same situation here. After installing the 7.0.300 update, having some issues with it, and seeing that Dell pulled it, I have decided to take a much slower, wait and see approach. Now .320 is no longer showing up on the internet updates, but is still showing up as download at Dell support. Is this version having issues as well?

Same situation, I tried many times to update by internet and by local last Thursday, but I received always an error.

I opened a case on Friday, now the case is "closed" without an answer to my question/issue.

Now the update disappear..I've no words!

Same thing here. I tried to create an advisory report but got an error message. So I opened a case : it was closed with no response.

I think it's possible. But it's a little bit frustrating that the log4j issue can't be applicable by a VxRail update.

The last working update 7.0.240 is dated September. Isn't it too old for security issues ?

Do we have to do the security updates by hand ?

hotlineR,

I followed Dell's mitigation workarounds regarding Log4j, but I agree with you, I would much rather have the whole deployment with the mitigation already done.

Hello swervie,

Here is the link to the download.

https://dell.to/3Hya4tJ

Hi DELL-Sam L,

I am aware of the download location for the bundle. I stated that the download existed on Dell Support in my original reply. The issue is that many of us are no longer seeing it as an internet update within our VxRail environment, and that usually happens when Dell decides to pull the update for some reason.

Hello swervie,

I am checking with the vxrail team to see if there is an issue with that.  I will let you know once I get an update.

Thank you!

Hello all !

The upgrade procedure is available again. But every time I click on the "CREATE ADVISORY REPORT" button, I get this error message: "Failed to generate advisory report, please check the log. ".

Is it the same for you? @swervie @DELL-Sam L @Cipo80 

No news from the support. The ticket does not seem to be closed. But no news from support for 6 days.

@hotlineR ,

I get the same error: "Failed to generate advisory report, please check the log."

I found a solution to be able to create the ADVISORY REPORT anyway. You just have to connect to https://myvxrail.dell.com/ with your DELL login and do it through this.

Updating is not possible via this interface, but you will be able to view the ADISORY REPORT.

Hi @hotlineR , sorry for late reply, finally I've just complete the upgrade,Hallelujah!!

I've open yesterday another ticket targetting another Host, this time I chose "Hardware problem", the only one that enable the "chat support" button.

In two minutes a guy write me, I've explain the problem and remark the frustration about waiting an answer in the other ticket.

Him told me "strange,bla,bla", anyway then connect by Zoom and after 3 hours of log checks he found the problem, in my case the space in Vxmanger /data/store2 wasn't enough.

It's necessary more than double of the space of the upgrade package (package size+archive extract), actally 12GB*2.

There was a lot of garbage files of the .241 on /data/store2/do_services  , after delete it the upgrade procedure completed successfully, except for the witness, I never seen the witness upgrade automatically by this procedure! I've upgraded manually by LCM->baseline.

Check the screenshots below, before cleaning:

After :

Another thing, I've upgraded without the report, isn't mandatory.

This upgrade did not go very smoothly from 7.0.241 on E560 nodes.  

It eventually worked.  But I had to keep waiting for the upgrade script to time out to hit actions->restart at the firmware staging point just after it updates idrac from 4.4 to 5.0.  No errors on the advisory report, pre-check, or vxverify checks.  It just crashed the next node at firmware staging requiring you reboot it, wait for the timeout to restart the process and it would complete.  Problem is the timeout is like 2 hours so you wait a LONG time between nodes.  (note I do not have license for DRS and I do not accept their temporary DRS license)

It would say " Upgrade preparation stopped on ESXi host: host2.domain.com due to internal problems but will be ignored.  I look at the console of the next node and see it has crashed and waiting for you to press f1 to try a normal boot.  I let it boot up, reboot it one more time so that idrac stops complaining about a cpu bug check.  And it looks like it is stuck at this point but you just need to wait and wait and wait (like 2 hours or more).  Then you finally get option to restart the upgrade and it will resume and complete that node and once it complete that node, the next one starts, crashes and you repeat the process.

Since I saw it was crashing nodes (likely bugs in the older firmware or bios it's upgrading from) I made sure no VM was running on the current or the next node in the sequence.  During the 2 hours waiting all nodes are working fine so I just let the process churn.  Did 2 nodes one night, 2 the next night.  Now it's complete, verify shows everything healthy on the correct versions.  vxrail VM shows the right version, no strange files left behind so I think it's all fine.  Had support double check and it looked good.