Unsolved

This post is more than 5 years old

8012

June 19th, 2019 05:00

OME 3.2 Available

3.2.0.241

New features include Auto Deploy, IOA Switch cloning, Chassis Template Editing capability, Firmware updates enhancements, Warranty report enhancements, PowerVault ME4 Storage support, Programmatic appliance deployment on ESXi, AD enhancements, GUI advanced filtering and sorting enablement...

June 19th, 2019 07:00

Any idea when we can expect full documentation for 3.2 and a direct DL link? Currently this version is only available via the update console option if you have a previous version deployed. 

 

Note: I did kick off the update a few hours ago and while I did get an email from the appliance stating that the update was completed I still get the 'upgrade is in progress' message trying to logon....

12 Elder

 • 

6.2K Posts

June 19th, 2019 11:00

My update completed after 43 minutes, total. Update times will vary based on download speed and system resources.

12 Elder

 • 

6.2K Posts

June 19th, 2019 11:00

Hello

The release process can take a day or two. Most of our sites have scheduled update times, so the download site may be updated at one time and the support site at another. The documentation is managed separately from the update, so it may take longer than a few days for the OMEnt 3.2 support page to be created.

I am testing the update right now. It took 16 minutes for me to get a login prompt, once I logged in the previous on-screen message was displayed, indicating that the update process is still proceeding. It appears to be restarting the appliance and continuing the update process after the restart. I suggest that you continue waiting, this update is taking some time.

OpenManage Enterprise 3.2 updatingOpenManage Enterprise 3.2 updating

Thanks

5 Posts

June 19th, 2019 13:00

Hello,

my 1st try of updating my OME 3.1 to 3.2 was unsuccessful. After the download and upgrade while booting i got the dracut console.

I shutdown the VM before taking the snapshot.

I noticed these warning/error messages by journalctl  (attached screenshots),

i am trying to figure out what went wrong.

The "vda2 too small for target" is something i don't get. Any help is welcome.

 

Thank you

Screenshot from 2019-06-19 16-11-43.pngScreenshot from 2019-06-19 16-11-35.pngScreenshot from 2019-06-19 16-11-26.pngScreenshot from 2019-06-19 16-10-57.pngScreenshot from 2019-06-19 16-10-26.pngScreenshot from 2019-06-19 16-07-49.png

June 19th, 2019 15:00

I was finally able to get past that updating page once I powered down the appliance and then powered it back up. This was after letting it sit for several hours and attempting a few reboots before I tried the power down.

12 Elder

 • 

6.2K Posts

June 19th, 2019 15:00

It looks like it is creating a mapping to a virtual device that is smaller than what it is trying to mount on it. It is truncating the image because it is too big for the partition or device that is attempting to mount.

I would try the update again.

June 19th, 2019 16:00

The update completed successfully, I just had to power the appliance all the way down and power it back up to get into it and get it off that upgrading screen.

1 Rookie

 • 

16 Posts

June 25th, 2019 01:00

Hi

After update I see this after login:

image.png

But appliance itself is on version 3.2

image.png

 

 

 

 

 

 

 

 

Its about one hour from update..

VP

1 Rookie

 • 

16 Posts

June 25th, 2019 03:00

After restart I can login, but alert windows pop-up

image.png

1 Rookie

 • 

52 Posts

June 25th, 2019 06:00

Hi VP, The Console Upgrade from Terminal User Interface is completed but it would take about 50 Min to complete the entire procedure of running the upgrade of the appliance and then run the post upgrade task. Try launching the appliance from different browser and see, it should work correctly. Thanks, Anil Kumar V K R

1 Message

June 25th, 2019 11:00

after i updated to the newest Version, i´m unable to Access the console. after entering the username and Password it stucks in "Console is updating. Please standby...".

What can i do to aceess the console normaly. Rebooting the vm did also not solve the Problem.

1 Rookie

 • 

16 Posts

June 26th, 2019 05:00

Hi Anil.

After manually running post upgrade task job is everything OK, no alert popups.

Thanks

1 Rookie

 • 

52 Posts

June 26th, 2019 08:00

@VlPs,

Great to hear that the issue is resolved once you have rerun the post upgrade task and there is no alerts popup coming up on the screen.

 

Thanks,

Anil Kumar V K R

Dell EMC

5 Posts

June 27th, 2019 10:00

Ive been sitting at this screen for over 50 minutes. :(

 

"System is updating. Will reboot in some time(approx 50 minutes)..."

June 27th, 2019 11:00

I ultimately tried to update (and rollback to a snapshot) approximately 5 times.  Each time seemed to fail for a slightly different reason. 

1) Our local admin password that worked through the GUI cannot be entered via the console.  It would error out related to SQL handling

2) After the first upgrade reboot, the console sat trying to load the firewall settings (if I remember correctly) for over 40 minutes so I powered it off and booted it back up.  Console showed version 3.2 but could never log in

3) The only "successful" upgrade where I could log in.  After the update I got blasted with the "Alert" errors someone else got on the previous screen.  I rolled back to a snap, deleted all alerts (~50k), then attempted to update again.

4) Either got stuck on the console (after waiting for the better part of an hour) or couldn't log in with a local user or AD user

5) Either got stuck on the console (after waiting for the better part of an hour) or couldn't log in with a local user or AD user

 

Gave up by this point which is pretty disappointing given that this is an "Enterprise" product and simple upgrades don't work right.  We've hit enough random bugs in Tech-3.0-3.1 that we were looking forward to the latest attempt at a stable product.

No Events found!

Top