- Community Home
- >
- Software
- >
- HPE Morpheus Software
- >
- HPE Morpheus Enterprise
- >
- VMware tagging not being applied
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2023 01:55 AM
08-21-2023 01:55 AM
VMware tagging not being applied
In our catalog we have metadata entry for costcode.
“metadata”: [
{
“name”: “cost code”,
“value”: “<%= customOptions.input_vm_costcode %>”
}
],
When VMware system is created, the tag gets created in vcentre but does not get automatically assigned to the VM.
Within the catalog history of the VM you can also see the tag assigned:
Should the tag be automatically assigned to the VM?
Cheers
Jon

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2023 08:47 AM
08-28-2023 08:47 AM
Re: VMware tagging not being applied
I’m experiencing a similar thing. I have export as tag selected on the option but the tag doesn’t get set in VMware. Don’t see any obvious errors on VMware.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2023 07:45 AM
08-21-2023 07:45 AM
Re: VMware tagging not being applied
I believe you also have to have that input assigned to the layout.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2023 09:51 AM
08-28-2023 09:51 AM
Re: VMware tagging not being applied
Yours is creating the Key / Value in vCenter but not applying to the VM as well?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2023 09:52 AM
08-29-2023 09:52 AM
Re: VMware tagging not being applied
Correct - I think I found out the issue. In my case the field name case did not match the vCenter tag category (BackupSchedule category name vs backupSchedule field name). I had to update everything to match, including some fields that aren’t displayed on the option edit form.
UPDATE option_type SET field_set_name = 'BackupSchedule', field_get_name = 'BackupSchedule' WHERE id = 1;

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2023 12:39 AM
08-22-2023 12:39 AM
Re: VMware tagging not being applied
Hi,
Can you explain more please? Within the layouts I cannot see anything about metadata/tags.
Cheers
Jon

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2023 04:01 AM
08-23-2023 04:01 AM
Re: VMware tagging not being applied
Sadly it’s not working for me.
I have added:
- Add the metadata entry to the catalog
“metadata”: [
{
“name”: “cost code”,
“value”: “<%= customOptions.input_vm_costcode %>”
}
],
- then add to the customoptions:
“cost code”: “<%= customOptions.input_vm_costcode %>”
So apart from those two steps nothing else is required?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2023 04:03 AM
08-23-2023 04:03 AM
Re: VMware tagging not being applied
I check the box on the inputs for “Export as Tag”.
That said, if it’s creating in vCenter and not associating there should be an event/error in vCenter on what’s happening. Are you setting invalid values with your key? Are you trying to do multi-cardinality tags?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2023 07:46 AM
08-22-2023 07:46 AM
Re: VMware tagging not being applied
To get mine to tag, I simply had to add the customOptions under:
"config": {
"customOptions": {
"password": "<%=customOptions.password%>",
"steamBackup": "<%=customOptions.steamBackup%>",
"world": "<%=customOptions.world%>",
"steamPort": "<%=customOptions.steamPort%>",
"optionList": "<%=customOptions.optionList%>",
"nfs": "<%=customOptions.nfs%>",
"newSteamBackup": "<%=customOptions.newSteamBackup%>"
}
}
And I made sure that I have ‘export as tag’ checked on the input in my form.