#For stories, please include the information below: **User Statement:** A brief statement describe who, what and why of the story for example - As a job seeker, I want to search for a job, so I can advance my career. **Details:** Any details of what you want that might clarify for the developer how to approach the implementation. **Acceptance Criteria:** Specific deliverable and actionable items that the story needs to deliver in order to be considered complete, the more detail here the more accurate the implementation will be. #For bug reports, please include the information below: **VIC version:** x.y.z / master / commit ID **Deployment details:** What was the vic-machine create command used to deploy the VCH? **Steps to reproduce:** **Actual behavior:** **Expected behavior:** **Logs:** * If you can access the VCH Admin portal, please download and attach the log bundle(s). See https://vmware.github.io/vic/assets/files/html/vic_admin/log_bundles.html for details. * If the VCH Admin portal is inaccessible, you can enable SSH to the VCH endpoint VM to obtain logs manually. See https://vmware.github.io/vic/assets/files/html/vic_admin/vch_ssh_access.html for details. The VCH logs will be under /var/log/vic/ on the VM. **Additional details as necessary:**