@florent I would love to....but I transitioned from Hyper-V a few months ago. No VMWare to be found around here.

Without fail, these OVAs will be downloads from a variety of applications.

Thanks again!

@florent SUCCESS!

Just grabbed and built XOCE with that branch, ran an import and it worked just as expected.

I'll probably run a half dozen more imports over the next day or so. If anything weird pops up, I'll report back but this looks like it fixed the problem.

Thank you, I appreciate it!

@florent I would love to....but I transitioned from Hyper-V a few months ago. No VMWare to be found around here.

Without fail, these OVAs will be downloads from a variety of applications.

Thanks again!

@florent SUCCESS!

Just grabbed and built XOCE with that branch, ran an import and it worked just as expected.

I'll probably run a half dozen more imports over the next day or so. If anything weird pops up, I'll report back but this looks like it fixed the problem.

Thank you, I appreciate it!

Any updates on this?
As of this morning's build (afadc) it's still an issue.

While I was waiting on a fix for the OVA import issues I was experiencing, I decided to work on a solution myself to getting a template I could use Cloud Configs on.

Through much trial and error, I managed to figure out a build template that works for Ubuntu 22.04 LTS that gets you a base image that will recognize standard Cloud Configs in XOCE and apply them successfully. I thought I'd write it up for anyone else who may be banging their heads against the wall like I was.

***Note: almost ALL of this was knowledge gleaned from other users in other posts, comments and various forum posts here and on other websites. All I did was figure out what worked, in a repeatable fashion, so I could actually use the configs as intended.

How I built my cloud disk and used Cloud Config ;

• Installed Ubuntu 22.04 LTS as VM, (I used 2 cpu, 8G ram, 10G drive)

• Upon reboot, I updated/upgraded w/apt

• Installed Guest Tools

• Ran sudo apt install cloud-initramfs-growroot

  • (an absolute MUST if you want your VM to apply a Cloud Config...took me 4 or 5 times reinstalling and trying various things not realizing how important this was for success. I thought it was automatically installed with the Cloud-Init package.....it is not).

• Ran sudo cloud-init clean

• Ran sudo truncate -s 0 /etc/machine-id /var/lib/dbus/machine-id

  • Used to clear out machine-id for regeneration. Found that if you deleted the file, it would not be regenerated during the reboot but if you zeroed it out, it would.

Shutdown VM and created a template from that image.

Doing this allowed me to apply Cloud Configs and have them actually stick to any new VM created from that image.

One thing...the configs MUST be in perfect YAML format so running through a verifier helps spot issues. I was missing a space between the hashed_passwd: colon and the start of the password. It took a verifier to point that out.

Hopefully this helps someone in the future

@florent I tried a barebones cloud disk from Ubuntu (22.04) in OVA format last night for grins and giggles...... and that failed with the same message.

@olivierlambert Yep, here is the link:

LibreNMS OVA

Trying to import an OVA file via the XOCE import VM section and it's failing with this log entry in settings -
No user expected grain marker, received [object Object]

Here's a clip from the full error if that helps.

"crash_dumps": [],
    "virtual_size": 10485760000,
    "physical_utilisation": 24064,
    "type": "user",
    "sharable": false,
    "read_only": false,
    "other_config": {},
    "storage_lock": false,
    "location": "2538546e-f69b-4ed5-8b77-9b0caba33c02",
    "managed": true,
    "missing": false,
    "parent": "OpaqueRef:NULL",
    "xenstore_data": {},
    "sm_config": {},
    "is_a_snapshot": false,
    "snapshot_of": "OpaqueRef:NULL",
    "snapshots": [],
    "snapshot_time": "19700101T00:00:00Z",
    "tags": [],
    "allow_caching": false,
    "on_boot": "persist",
    "metadata_of_pool": "",
    "metadata_latest": false,
    "is_tools_iso": false,
    "cbt_enabled": false
  },
  "message": "expected grain marker, received [object Object]",
  "name": "Error",
  "stack": "Error: expected grain marker, received [object Object]
    at VMDKDirectParser.parseMarkedGrain (/opt/xo/xo-builds/xen-orchestra-202304010309/packages/xo-vmdk-to-vhd/src/vmdk-read.js:163:13)
    at VMDKDirectParser.blockIterator (/opt/xo/xo-builds/xen-orchestra-202304010309/packages/xo-vmdk-to-vhd/src/vmdk-read.js:197:17)
    at generateBlocks (/opt/xo/xo-builds/xen-orchestra-202304010309/packages/vhd-lib/createReadableSparseStream.js:119:22)
    at iterator (/opt/xo/xo-builds/xen-orchestra-202304010309/packages/vhd-lib/createReadableSparseStream.js:142:5)"
} 

Any ideas what's malfunctioning? I'm using the latest CE build - 8a07b
It's been doing this for the past few builds (been trying for a few days updating thinking it was maybe being fixed in the most recent build).

Thanks

Tony

@julien-f Thank you!!!! Just applied and so far, so good.
I assume that also screwed with the stats because they are now working again....

Much appreciated!

A clue!

Logs are filling up with "unable to parse XAPI datetime "2023-03-06T03:56:43.000Z""

Anyone else see this happen before? I couldn't find anyone discussing it in the forums. Also....no stats on any of the VMs suddenly. Was there this morning and a reboot of the host doesn't clear it up. Connected perhaps?

Running XO built from sources...latest build 00a13 commit

Thanks