John_Gill Trusted Contributor.
Trusted Contributor.
581 views

Upgrade to OES 2018 for DNS/DHCP xen virtual machine

Hi again,

So I managed to get the 4 servers (2 x physical and 2 x VMs') upgraded to SLES11sp4 & OES2015. All services (DNS, DHCP, user access etc) working. ... so far so good.

I then upgraded the primary eDir physical server to OES 2018 ... no issues.

I then upgraded a VM running DNS to OES2018 ... the only issue was that during the install the menu jumped to an "old style" text menu
but in the networking section I add the details of the server and the ftp info and then the upgrade to SLES went thru, the server reboots
and then the OES portion completes. eDir and NTP synced, and the DNS service was working correctly .... all good again.

Next onto the second VM which runs DNS and DHCP. Same type of installation as above. The SLES portion completes and then the server
reboots to start the OES section, but returns an error that the "kernel" failed to load. Information in the GUI window of the VM
configuration menu under "Boot Menu" shows setting for "Kernel Path", "Initrd path" and "Kernet Args". I remove the setting (otherwise the
server will not boot) and start the VM.

I can now start the server and /etc/*release shows that the SLES12sp2 and OES2018 has been updated. DNS is resolving correctly and
Timesync is correct but running "ndsrepair -E" shows that OES is not installed and DHCP service is "dead"

Ideas, thoughts, comments (good or bad) will be appreciated.
John
Labels (2)
0 Likes
3 Replies
Knowledge Partner
Knowledge Partner

Re: Upgrade to OES 2018 for DNS/DHCP xen virtual machine

John Gill wrote:

> Ideas, thoughts, comments (good or bad) will be appreciated.


Hi John,

Have you checked all the various logs for any clues?

There are sometimes issues upgrading a VM from one major release to
another and there were major changes between SLES 11 and SLES 12. The
safest way is to do a fresh install (create a new VM) and migrate
services/data from the old VM.

Are you still using Xen?

Have you upgraded Dom0?

Have you verified that the upgraded DomUs are still supported on the
version of Dom0 you are running?

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
John_Gill Trusted Contributor.
Trusted Contributor.

Re: Upgrade to OES 2018 for DNS/DHCP xen virtual machine

Hi,

I have two host servers (Dom0) running SuSE12 and they each run a number of VMs using XEN. I have upgraded non-OES and OES servers without issue on both hosts.
As a side note, I think there was an issue with VMware and major release updates.

I just had a brain bubble... I will move the troublesome VM to the second host and then try the upgrade ...

John
0 Likes
Knowledge Partner
Knowledge Partner

Re: Upgrade to OES 2018 for DNS/DHCP xen virtual machine

John Gill wrote:

> As a side note, I think there was an issue with VMware and major
> release updates.


VMware does not support major upgrades to a VM's OS. When you create a
new VM you specify the OS so the set of devices that are provisioned
are compatible with that OS. After a major upgrade that may no longer
be the case. This is an issue that can affect any VM running on any
hypervisor. It is just something to keep in mind when issues like yours
arise.

Another reason for creating a new VM and doing a migration is that
newer OSs have new features. Sometimes, to maintain compatibility,
these new features are not implemented when upgrading from an older
release. The one that comes to mind in particular is a different
default filesystem but there are others too.

When an installation fails, I want to know why. The answer is usually
somewhere in one of the logs: you just have to find it. 😉

If you created a snapshot or have a backup, you can restore and try
again. Be aware that doing so on a system with eDirectory can create
additional issues. You can take a look at some of the threads in the
eDirectory forums.

If you are unable or unwilling to determine the cause of the failure,
one workaround may be to do a server down upgrade and boot from the
installation media but this approach also has issues when your VM is a
paravirtual DomU.

Of course, you can always grab a supportconfig and open an SR...

Let us know what you find. Maybe someone else has some other ideas.

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.