-
Notifications
You must be signed in to change notification settings - Fork 72
Child-Devices c8y_SupportedOperations not set after moving to another tenant #3738
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
I'm having a Gateway Device and a connected child-device with tedge-agent running on both. When onboarding it the first time to a Cumulocity tenant, everything works well and all supported Operations by the tedge-agent (e.g. config management, log file management, etc) are shown in the UI.
After moving the Devices to another tenant, the child-device in Cumulocity does not have any c8y_SupportedOperations fragment, thus the UI does not offer everything the tedge-agent could do.
To Reproduce
- Onboard Device + Child-Device to Tenant A
- Remove certificate from main device and onboard it to another Tenant B
- Check the
c8y_SupportedOperationsfragment of the child-device in Tenant B
Environment (please complete the following information):
- OS: Debian Bookworm
- Hardware: RPI5/4
- System-Architecture: aarch64
- thin-edge.io version: 1.5.1
Additional context
The problem seems to be caused by a Cache that only submits the c8y_SupportedOperations fragment on change. One can get the supported operations set by:
- delete any inbuilt operation file (e.g: c8y_Restart ) of that child device from the
/etc/tedge/operations/c8y/<child-device-id>/directory on the main device - restart the
tedge-agenton child device.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working