Autodeploy Image: An error occurred while generating the image [Entry is too large to be added]

This issue occurred with below environment:

vcsa 6.5, embedded vum,autodeploy and image builder service enabled.

  • For image customization we mapped more images [ approx 2 GB] so it was not allowing to map new image, and throwing below error message
Error while Autodeploy Image... An error occurred while generating the image : Error : An error occurred while performing the task Entry is too large to be added to cache, please remove any imported depots you are not using...
  • Delete the images, which are not in-use, or apply the below workaround [increase the cacheSize]
cat /etc/vmware-imagebuilder/sca-config/imagebuilder-config.propsloglevel=INFO
vmomiPort=8098
httpPort=8099
cacheSize_GB=4

ls -lh /storage/imagebuilder/exports/
total 361M

Go in vcsa --> Administrator-->System Configuration-->Services

Restart Auto Deploy

Restart ImageBuilder Service

 

 

How to set vrops [vrealize operation manager] forgotten root password

Recently, in my testing environment i forgot the root password. I did the following step to reset password:

-Restart the vrops node

-Edit the Boot option “init=/bin/bash”

Boot Options vga=0x311 elevator=noop noexec=on nousb audit=1 init=/bin/bash

-Once system boots, type below command:

"passwd root"

It will prompt for new password. Provide the new password and reboot the system!!!

kubelet service is failing :Unable to update cni config: No networks found in /etc/cni/net.d

Hi,

Small troubleshooting  tip:

“kubeadm reset” and try to initiate the cluster again but it is failing ,due to kubelet service was not running.

Executed this command “journalctl -xeu kubelet”

Error message “Unable to update cni config: No networks found in /etc/cni/net.d”

I checked on github : https://github.com/kubernetes/kubernetes/issues/54918

Applied the workaround “chmod 777 /etc/cni/net.d” and try to start the service.

systemctl start kubelet.service

This worked!!!

This all has been done in centos7

 

vSphere On-disk Metadata Analyzer (VOMA)

VOMA helps in performing VMFS file system metadata checks. This utility scans the VMFS volume metadata and highlights any inconsistencies.

VOMA provides four modules, and except for lvm, each of them has a fix function:

lvm-  Checks datastore’s logical device header,logical volume header and physical extent mapping

  • vmfs – This module checks vmfs hearder,resource file, heartbeat region, file descriptor ,connectivity etc.0
  • ptbl –  Module checks the partition table and provide table structure.
    • Phase 1: Checking device for valid primary GPT
    • Phase 2: Checking device for a valid backup GPT
    • Phase 3: Checking device for valid MBR table
    • Phase 4: Searching for valid file system headers
voma [OPTIONS] -m module -d device

-m, --module      Name of the module to run.

                    Available Modules are

                      1. lvm

                      2. vmfs

                      3. ptbl

-f, --func        Function(s) to be done by the module.

                     Options are

                       query   - list functions supported by module

                       check   - check for Errors

                       fix     - check & fix

                       dump    - collect metadata dump

-d, --device      Device/Disk to be used

-s, --logfile     Path to file, redirects the output to given file

-x, --extractDump Extract the dump collected using VOMA

-D, --dumpfile    Dump file to save the metadata dump collected

-v, --version     Prints voma version and exit.

-h, --help        Print this help message.
Example:

voma -m vmfs -f check -d /vmfs/devices/disks/naa.xxxx:x

voma -m vmfs -f dump -d /vmfs/devices/disks/naa.xxxx:x -D dumpfilename
voma -m vmfs -f check -d /vmfs/devices/disks/<device-id>

Checking if device is actively used by other hosts

Initializing VMFS Checker..|Scanning for VMFS-3/VMFS-5 host activity (512 bytes/HB, 2048 HBs).

Found 3  actively heartbeating hosts on device '/vmfs/devices/disks/<device id>

1): MAC address

2): MAC address

3): MAC address
voma -m ptbl -f check -d /vmfs/devices/disks/<device id>

Running Partition table checker version 0.1 in check mode

Phase 1: Checking device for valid primary GPT

Phase 2: Checking device for a valid backup GPT

Phase 3: Checking device for valid MBR table

Phase 4: Searching for valid file system headers

No valid LVM headers detected

Add-EsxSoftwareDepot : 32 At line:1 char:1 Error message

Unable to add using “Add-EsxSoftwareDepot “, Giving Below error message

“Add-EsxSoftwareDepot : 32 At line:1 char:1”

Checked vmware kb and vmtn :

https://communities.vmware.com/thread/495611

I also checked the “get-culture”, This is also reporting.

Facing the issue due to space, Check your C: drive on the image builder windows server.

This issue occurred, C: drive was having only 4 MB!!!

 

 

 

 

Error reading file \’/usr/lib/vmware-imagebuilder/etc/schemas/vib20-extensibility.rng

While downloading the new image from auto-deploy, I got the following error message:

Something went wrong while converting items to pxe profile:(vmodl.fault.SystemError) {

   dynamicType = <unset>,

   dynamicProperty = (vmodl.DynamicProperty) [],

   msg = 'Invalid Fault',

   faultCause = (imagebuilder.fault.IbFault) {

      dynamicType = <unset>,

      dynamicProperty = (vmodl.DynamicProperty) [],

      msg = 'Unable to obtain XML schema: Error loading schema XML data: Error reading file \'/usr/lib/vmware-imagebuilder/etc/schemas/vib20-extensibility.rng\': failed to load external entity "/usr/lib/vmware-imagebuilder/etc/schemas/vib20-extensibility.rng".',

      faultCause = <unset>,

      faultMessage = (vmodl.LocalizableMessage) [

         (vmodl.LocalizableMessage) {

            dynamicType = <unset>,

            dynamicProperty = (vmodl.DynamicProperty) [],

            key = '',

            arg = (vmodl.KeyAnyValue) [],

            message = 'Unable to obtain XML schema: Error loading schema XML data: Error reading file \'/usr/lib/vmware-imagebuilder/etc/schemas/vib20-extensibility.rng\': failed to load external entity "/usr/lib/vmware-imagebuilder/etc/schemas/vib20-extensibility.rng".'

         }

      ],

      errorCode = 0,

      errorMessage = (vmodl.LocalizableMessage) {

         dynamicType = <unset>,

         dynamicProperty = (vmodl.DynamicProperty) [],

         key = '',

         arg = (vmodl.KeyAnyValue) [],

         message = 'Unable to obtain XML schema: Error loading schema XML data: Error reading file \'/usr/lib/vmware-imagebuilder/etc/schemas/vib20-extensibility.rng\': failed to load external entity "/usr/lib/vmware-imagebuilder/etc/schemas/vib20-extensibility.rng".'

      },

      additionalData = (vmodl.KeyAnyValue) []

   },

   faultMessage = (vmodl.LocalizableMessage) [],

   reason = 'Method DepotManagerDownloadVib threw undeclared fault of type imagebuilder.fault.IbFault'

}

Solution:

-Install powercli 6.5. And check on this location for vib20-extensibility

 

C:\Program Files (x86)\VMware\Infrastructure\PowerCLI\Modules\VMware.ImageBuilder

-copy this file to vcsa appliance :

/usr/lib/vmware-imagebuilder/etc/schemas

This will resolve the issue!!!