- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - VMware
- >
- Boot Disk Validation Bypass in VCF
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
11 hours ago
11 hours ago
Boot Disk Validation Bypass in VCF
Backup SDDC Manager (File Level and Snapshot)
Before starting this activity take snapshot and file level backup for SDDC manager.
Log into the database
# psql -h localhost -U postgres
# \c domainmanager
# \x
Retrieve Task ID’s
# select task_name,id,execution_order,status from processing_task where execution_id='ID' order by execution_order;
# select task_name,id,execution_order,status from processing_task where execution_id='4ca26ccf-ddcd-440a-873a-9b53f97838fb' order by execution_order;
# select * from processing_task where id='7f000001-8c77-12c4-818c-f3b6f3c203c0';
# select * from processing_context where id='7f000001-8c77-12c4-818c-f3b6f3c103bf';
Update Task Status
Update Process IDs identified in last step.
Processing tasks
# update processing_task set status='POSTVALIDATION_COMPLETED_WITH_SUCCESS' where id='7f000001-8c77-12c4-818c-f3b6f3c203c0';
Processing Context
# Update processing_context set status='COMPLETED_WITH_SUCCESS' where id='7f000001-8c77-12c4-818c-f3b6f3c103bf';
Restart Services
Now restart the domainmanager, operationsmanager and commonsvcs.service services. Wait about 3 – 5 minutes depending on your environment and log back into SDDC Manager. This is optional. Only required in case retry task not working after update database.
# systemctl restart domainmanager, operationsmanager and commonsvcs. service
Retry Workflow
Retry same failed workflow from SDDC management console so it can proceed without boot disk validation.
Contributer - Kamleshjha(kamlesh-kumar.jha@hpe.com)