- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Appliances stucked at booting kernel phase after upgrading to 8.5.0
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2020 02:42 AM
Hello everybody,
In my test environment I upgraded my Grid system from 8.4.6 to the 8.5.0 version. In my test environment I have virtual 1420 GM and virtual 1420 GMC. During upgrade GM stuck at the booting kernel phase. And I have to reinstall GM and tried to upgrade again, then I can successfully upgrade my system.
Today I tried to change my v1420 GM appliance with v1415. The steps I have done;
-backup Grid config from old Grid Master (v1420)
-restore Grid config to new Grid Master (v1415)
-Change new GM's IP addresses as old ones.
-Then members restart.
-After restart GMC (v1420) again stucked in the booting kernel phase. I am waiting 1,5 hours and nothing happened.
I have added the screenshoot. Does anyone experience this kind of failure with 8.5.0 version?
Thanks
Re: Appliances stucked at booting kernel phase after upgrading to 8.5.0
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2023 11:15 AM
Hey - we have same issue with 8.6.3 anyone?
Re: Appliances stucked at booting kernel phase after upgrading to 8.5.0
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2023 10:07 PM
hi , i have similar issue when my Infoblox VM has undersize hardware specifications, once i increase the VM specs following to Infoblox recommendation, i no longer facing this issue. Perhaps you can verify the same?
Re: Appliances stucked at booting kernel phase after upgrading to 8.5.0
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
I'm seeing the same thing with a fresh install of IB-V5005 reporting appliance. CPUs and memory were auto-configured by the OVA deploy and it's stuck at booting the Kernel.