Applicable scenario

• Product: ZCF
• Component: ZCE-X
• Versions: 4.8.x, 5.2.x
• Affected object: glib2 2.56.x
• Trigger: glib2 must be upgraded from 2.56.x to 2.56.1-10.el7.

Symptoms

• The current physical host has glib2 version 2.56.x.
• Each host must be upgraded to 2.56.1-10.el7.
• The new version requires a libvirtd restart, temporarily disconnecting the physical host.

Determination method

1. Confirm the current glib2 version before upgrade.
2. After restarting libvirtd, wait for the physical host to reconnect.
3. Check that platform services and VMs are normal.

Cause

This is a glib2 component-upgrade scenario. Upgrade glib2 and restart libvirtd for the new version to take effect.

Resolution

1. Preparation

• Risk level: low.
• Disable global HA.
• Process physical hosts one at a time to avoid affecting multiple nodes simultaneously.

2. Log in to ZStack Cloud and disable global HA.

• Expected result: HA is not triggered unexpectedly during the change.

3. Upgrade glib2 on each physical host:

   yum --disablerepo=* --enablerepo=zstack-mn update glib2

• Target version: 2.56.1-10.el7
• Expected result: The glib2 upgrade completes.

4. Restart libvirtd:

   systemctl restart libvirtd

• Expected result: The new glib2 version is loaded by related runtime services.

5. Wait for the physical host to reconnect.

• Expected result: The node comes back online.

6. Check platform services and VMs.

• Expected result: Services are unaffected.

7. Enable HA.

• Expected result: The platform returns to normal operation.

Verification

• The glib2 version is upgraded.
• The node reconnects after libvirtd restarts.
• Platform and VM states are normal.

Risks and rollback

• Risk: Restarting libvirtd temporarily disconnects the physical host.
• Risk level: low.
• Rollback:

  yum --disablerepo=* --enablerepo=zstack-local downgrade glib2-2.56.1-9.el7_6.x86_64