Christopher Nolan

Hi @ishanVshah a new release, OpenNESS 20.12.02, has just been completed with new updates, could you please try deploying the new release and see if the issues are cleared?

Hi @supriya-s-mane, OpenNESS does not currently support deploying Azure IoT Edge as an application.

Hi @kmaloor, The interfaceservice reads the MAC address of the interfaces on the edgenode from the system itself via the Golang net package. Looking at the OVS documentation for ovs-vsctl,...

Hi @kmaloor The cause of the failure with the interfaceservice is that the uevent is not being populated with the PCI addresses of the network interfaces. This appears to be...

Hi @kmaloor Yes, we can look to alter the interfaceservice to work with deployments on virtualized infrastructure as part of a future OpenNESS release.

@ss5829 could you share logs from the alerting-monitor pod on the orchestrator from the time when the alerts are created in the web-ui please?

@ss5829 I can see some errors related to authentication and token refresh in the alert-monitor logs, could you check if the service is able to retrieve a valid token and...

@lokesh0013 the HW agent loops approximately every 30 seconds to update the HW information for the edge node, which is why there are multiple copies of the errors in the...

@lokesh0013 I've checked the HW agent loop and the error was coming when the agent ran an ethtool get for the interface settings. Could you check that there are no...