Internet connectivity is lost after restarting the OVA

[r-wambui]

Problem

After restarting the OVA, sometimes the internet connectivity is lost, the IP address of the VM is also lost; commands that don't require the internet like hctl status raises an error.

This issue was also experienced during the hackathon, multiple users were using the same pre-configured OVA in cloudshare.

The solution was to revert back to an earlier snapshot or deploy/install a new OVA for the users which is not an ideal solution.

Expected behavior

• Internet connection and/or IP address should not be lost after restarting a VM in this case OVA.

How to reproduce

Setup a new OVA, reboot the VM, then check is the vm has an IP address and if you can ping google.com

Note This occurred in some VMs while in others, reboot was working with no issues.

Deployment information

VMware Workstation 16 Pro running on a Windows 10 machine using PI-7 doc

Additional information

No response

[cortx-admin]

For the convenience of the Seagate development team, this issue has been mirrored in a private Seagate Jira Server: https://jts.seagate.com/browse/CORTX-33842. Note that community members will not be able to access that Jira server but that is not a problem since all activity in that Jira mirror will be copied into this GitHub issue.

[mukul-seagate11]

@rshenoy0831, did you tested this scenario as raised?

[rshenoy0831]

@mukul-seagate11 we have tested this scenario. we have not observed this behaviour.

[stale]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @mukul-seagate11 for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[mukul-seagate11]

@r-wambui, as commented by Rahul who haven't observed this issue during QA validation so might be we can close this issue as we are also in the process of starting the next OVA release where most of the know bugs will be fixed

[novium258]

@mukul-seagate11 it sounds like since the team hasn't observed this issue, it wouldn't be a known isssue that would be fixed in a new release? We should probably identify the cause of this issue. Has anyone attempted to replicate this issue? We observed mulitple times. Before we close it, we'd like to know for certain that it has been fixed, or is no longer applicable in newer releases.

[hessio]

ova issues which are reported by community https://github.com/Seagate/cortx/issues?q=is%3Aopen+is%3Aissue+label%3Aova will be further raised to QA and tracked in next sprint

[mukul-seagate11]

Havent observed this issue as per #1644

[mukul-seagate11]

#1657 is validated as per latest OVA image and no issue is observed as well this was passed during the test entry criteria in https://seagate-systems.atlassian.net/wiki/spaces/PRIVATECOR/pages/1170014209/PI-8+Test+Entry+Criteria+Dev+OVA+Community+Build

[novium258]

@mukul-seagate11 were you able to replicate this in the tests for the release in which it occurred?