Currently Device.X_PRPLWARE-COM_GenericNetworkInterface. is missed on the USP bus.
Thus the component is not available in USP controller. Fixed it by adding needed USP registration ODL configuration.
Fixes: PPW-1000
Signed-off-by: Ashik Ahmed <ashik-ahmed.a@capgemini.com>
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org> [fix author name to match SoB, rebase]
Following components are adapted to make sure the needed parameters of the datamodel survive an upgrade.
- tr181-led
- tr181-dhcpv6client: bump to v1.12.1
- oopsmonitor: bump to v1.2.1
- wan-manager: bump to v1.10.1
- reboot-service: bump to v1.0.6
- ethernet-manager: bump to v1.29.1
- amx-faultmonitor: bump to v1.3.1
- tr181-bulkdata: bump to v0.2.6
- tr181-periodicfileupload: bump to v0.3.1
- cellular-manager: bump to v1.1.1
- tr181-firewall: bump to v8.14.1
- tr181-mqttbroker: bump to v0.3.1
References: FEAT-132, PPW-609
Signed-off-by: Matthias Franck <matthias.franck@softathome.com>
During integration of tr181-conntrack-query it was seen that two config options were named incorectly:
- CONFIG_SAH_AMX_TR181_CONNTRACK_QUERY_AS_GROUP="tr181_app"
- CONFIG_SAH_AMX_TR181_CONNTRACK_QUERY_AS_USER="tr181_app"
During integration these options were replaced in the system by:
- CONFIG_SAH_AMX_TR181_CONNTRACK_QUERY_RUN_AS_GROUP="tr181_app"
- CONFIG_SAH_AMX_TR181_CONNTRACK_QUERY_RUN_AS_USER="tr181_app"
This commit adjusts the tests accordingly.
References: PCF-2107
Signed-off-by: Matthias Franck <matthias.franck@softathome.com>
Problem: CRAM tests are failing because the new parameter Device.DHCPv6.Client.{i}.X_PRPLWARE-COM_DHCPv6Status is not recognized.
Solution: Update the CRAM test definitions to include the new DHCPv6Status parameter.
References: PCF-1839
Signed-off-by: Sarra Kacem <sarra.kacem_ext@softathome.com>
Signed-off-by: Matthias Franck <matthias.franck@softathome.com>
(cherry picked from commit 935387da12)
Currently the cram testbeds doesn't support DHCPv6, so the test needs to be disabled
to keep CI green. Will be enabled later when testbed properly supports DHCPv6.
References: PCF-1786
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
Signed-off-by: Hela Saadani <hela.saadani_ext@softathome.com>
Signed-off-by: Matthias Franck <matthias.franck@softathome.com>
Add test for tr181-conmon.
The cram test checks ConMon status and checks that the error counters are 0.
References: PCF-1840
Signed-off-by: Nicolas BESNARD <nicolas.besnard_ext@softathome.com>
Update the reverse portmapping NAT test that uses the LCM
agent to correctly assign the necessary Linux capabilities.
Additionally, leverage the existing LCM infrastructure
for related operations such as installation, EE setup,
and execution within the container.
Signed-off-by: Nabil BIZID <nabil.bizid@softathome.com>
Integrates following changes:
- cthulhu: ApplicationUUID should point to UUID iso DUID (f440089e)
- cthulhu: Container creation should fail if metadata is invalid (59d4c96f)
- cthulhu: ApplicationData input validation (b879ee49)
- cthulhu: Ensure AppData entry is created for disabled containers (b6d90908)
References: LCMFT-552, PPW-922
Signed-off-by: prplbot <bot@prplfoundation.org>
We've started adding more features recently which increased rootfs size,
resulting to the following builds errors:
Pseudo file "dev" exists in source filesystem "/builds/prpl-foundation/prplos/prplos/build_dir/target-x86_64_musl/root-x86/dev".
...
Creating 4.0 filesystem on /builds/prpl-foundation/prplos/prplos/build_dir/target-x86_64_musl/linux-x86_64/root.squashfs, block size 262144.
[| ] 0/4678 0%error: ext4_allocate_best_fit_partial: failed to allocate 135 blocks, out of space?
Creating filesystem with parameters:
Size: 136314880
Block size: 4096
...
make[4]: *** Waiting for unfinished jobs....
So lets fix it by increasing the size of rootfs to 150MiB.
References: PCF-2021, FEAT-54
Fixes: b58f476c16 ("profiles: prpl: add support for pkcs11 and softHSM")
Link: https://gitlab.com/prpl-foundation/prplos/prplos/-/jobs/11402124317#L9008
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
As per PCF-1940, the PeriodicFileUpload datamodel is replaced by PeriodicFileTransfer. The test should be updated accordingly
References: PCF-1940
Signed-off-by: Toon Caeyers <toon.caeyers_ext@softathome.com>
As per PCF-1940, the PeriodicFileUpload datamodel is replaced by PeriodicFileTransfer. The test should be updated accordingly
References: PCF-1940
Signed-off-by: Toon Caeyers <toon.caeyers_ext@softathome.com>
Integrates following changes:
-lib_filetransfer: give the possibility to enforce a preferred IP version for a transfer (96cc196d)
-PeriodicFileUpload: Use Security.Certificate / ForceTransfer refactor (9d2a9652)
-ci: add missing zlib and mod-dmext to baf.yml (c5390406)
-FileTransfer: Making hook script async (917e29fa)
-tr181-periodicfileupload: Path Taken Without Trailing Dot Causes Error in libfiletransfer (ed41b811)
-FileTransfer: Upstep to new architecture (a95d9fbc)
References: PCF-1940
Signed-off-by: Toon Caeyers <toon.caeyers_ext@softathome.com>
Add Mozart entry to get_container_name() and get_board_arch script
functions to correctly select the container arch and name for the
Arcadyan Mozart device.
References: PPM-3436
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Currently the prplMesh operational state test is failing after the
rebase onto OpenWrt 24.10:
$ R "/opt/prplmesh/scripts/prplmesh_utils.sh status" | LC_ALL=C sort
pgrep: pattern that searches for process name longer than 15 characters will result in zero matches
Try `pgrep -f' option to match against the complete command line.
So lets disable the test until the issue is fixed.
References: PPM-3436
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Sync Arcadyan Mozart build config test with new package/config
introduced with 24.10 prplOS release.
References: PCF-1970
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
On updating the test for the new variable "PollingMaxRetry", the regex
for the NumberOfEntries was wrongly hardcoded to 13.
Restore the original matching for the test.
Fixes: 38dc179bb4 ("ci: cram: 105-temperature.t: update tests after adding PollingMaxRetry parameter")
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
This reverts commit 743214c800.
Enable test for Mozart board now that they are supported again.
References: PCF-1970
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Update mediatek feed to track new latest-24.10 branch to better support
prplOS 24.10 release.
References: PCF-1970
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
New U-Boot dependency require the additional Swig package to correctly
build for some Target.
Add it to the list of Host package in the builder Dockerfile.
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
This reverts commit e26e856459.
From release 24.10 we always use wifi-scripts and netifd doesn't ship
netifd-wireless.sh anymore.
When wifi-scripts is selected, the netifd install fails as it can't find
the local script to remove.
To fix it, drop the workaround entirely.
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
While Docker image is updated for Swig package inclusion, install it in
build workflow.
References: PPM-3436
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* remove unused omci, omci-base, and trex-drv packages to resolve build errors
The image build process generated error messages for three unused packages: omci, omci-base, and trex-drv. Removed these packages to prevent unnecessary build errors.
* remove dependencies on nonexistent packages
This commit addresses build warnings caused by references to nonexistent packages in several Makefiles During the build process, multiple warnings were reported indicating dependencies on packages such as kmod-crypto-ocf, kmod-qca-wifi, kmod-qca-nss-crypto, kmod-qca-mcs, kmod-qca-hyfi-bridge, qca-nss-fw-eip-al, and kmod-qca-rfs , which do not exist in the current build environment.
Removed dependencies on missing packages in the affected Makefiles to resolve these warnings. This fix was originally made by Nikhil Gurram in branch dev_ath13.0-ipq95xx.
* Enable CONFIG_PSTORE_RAM
kernelfaults module will retrieve panics and oops form pstore. 64 KiB reserved for ramoops/pstore
* add support for EFR32MG
Enable UART and I/O expander to support ATH13.0 for EFR32MG on the Freedom board.
* add support for LED driver
The I2C multiplexer TCA9548A is connected to the I2C3 bus. The I/O expander TCA6416A is connected to channel 5 of the I2C multiplexer TCA9548A and is controlled by GPIO17/18 for interrupt and reset. The LED driver LP5562 is connected to the I2C3 bus and enabled by GPIO13 of the I/O expander TCA6416A. The LED driver LP5562 controls one RGB LED and one white LED. Set up the system indicator lights.
Fixes: PCF-1968 PCF-1977 PCF-2028 PCF-2027 PCF-2059
Signed-off-by: Tim Hsu <tim.hsu@wnc.com.tw>
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org> [rebase]
Integrates following changes:
- baf: introduce the baf.yml file (c70cd7a0)
- ci: include the ci templates (66f7fc15)
- ci: baf: update autogenerated files (925a95f9)
- InterfacePath: Add compatibility for non dot terminated paths (de04786d)
- odl: make data model parameters read-only according to TR-181(PCF-1850) (de3ebdb9)
- route information: automatically create instances at startup (PCF-1850) (93685f69)
- unit test: add test for automatic RouteInformation.InterfaceSetting (PCF-1850) (75fa6a9a)
- ipv6,route information: don't modify (PCF-1850) (4971bc0e)
References: PCF-1850
Signed-off-by: prplbot <bot@prplfoundation.org>
Problem:
========
No POSIX check was done for the Time.LocalTimeZone
Solution:
=========
Add a check for a random POSIX compatible timezone and a check for non
valid POSIX timezone
References: PPW-511
Signed-off-by: Alexandre Fiset <alexandre.fiset@softathome.com>
Introduce a flash health monitoring service to support wear-level tracking and predictive failure analysis of NAND and eMMC flash devices under TR-181 data model.
- Enumerates all flash devices (eMMC, NAND via UBI) and exposes wear metrics
- Supports vendor-specific and standard wear indicators via mmc-utils and ubinfo
- Enables operators to assess device reliability and take preemptive action
- Proposes TR-181 extension for flash health, targeting BBF standardization
This component enhances operational visibility into flash degradation, enabling smarter lifecycle management and reducing field failures in prplOS deployments.
Implements: PCF-2008, FEAT-92
Signed-off-by: Ashik Ahmed A <ashik-ahmed.a@capgemini.com>
Integrates following changes:
- librlyeh: do not print registry password in clear text (fce2dd0f)
References: LCMFT-423, PPW-863
Signed-off-by: prplbot <bot@prplfoundation.org>
Integrates following changes:
- ci: enable crosscompilations and unit tests (284ee28e)
- dynds: ddns-script: fix Protocl by replacing https by http (1602d8cd)
- dyndns: dns_disable_service: remove deprecated function (735634a4)
- dyndns: mod_ddns_uci: remove script wrapper with sleep and use only libamxp (6d72e20b)
- dyndns: odl: allow expanded Server parameter in Client (0d8a539c)
- dyndns: odl: make DynamicDNS.Server object upgrade persistent (f4a27a10)
- dyndns: ddns-script: improve ServerAddress parsing (5c83e953)
- dyndns: odl: make the Alias write once (343a106a)
References: PCF-1683
Signed-off-by: prplbot <bot@prplfoundation.org>
Problem:
========
mstpd is still enable in the configuration files were it was removed
from the bridge plugin
Solution:
=========
Remove the package configs of the bridge and mstpd
References: PPW-679
Signed-off-by: Alexandre Fiset <alexandre.fiset@softathome.com>
Problem:
During the mlo.t cram test execution, the wld process may get stuck for
the same reason when previously the pwhm.t test was causing a similar
issue. (cf 72689c9980)
Cause:
- When mlo.t starts, we suspend the beerocks processes using SIGSTOP.
- When pwhm raises an event through the USP socket, it expects an
acknowledgement from prplmesh (the client). Since prplmesh is suspended
it never replies.
- This concerns ony the direct socket case, which is point-to-point
connection. With ubus, events are broadcasted, so no pear acknowledgement
is required.
- The issue became visible after unfiltering custom events in amxb_usp.
Solution:
Do the same fix as done in pwhm.t. ie: stop prplmesh properly before
starting the script so that it cleanly disconnects from the USP backend.
Fixes: PPW-1017
Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>
In CDRouter-UPnP-IPv46 we've now all passing UPnP tests from both upnp
and upnp-v6 modules, which are known to be working as of today.
From the list of available 111 tests in CDRouter version 15.8.1 in both
upnp-v6.tcl (60) and upnp.tcl(51) modules we've removed following 30
tests currently known to be not failing:
cdrouter_upnp_203, cdrouter_upnp_204, cdrouter_upnp_220,
cdrouter_upnp_igd2_203, cdrouter_upnp_igd2_204, cdrouter_upnp_igd2_220,
ipv6_upnp_35, ipv6_upnp_36, ipv6_upnp_40, ipv6_upnp_41, ipv6_upnp_45,
ipv6_upnp_50, ipv6_upnp_100, ipv6_upnp_203, ipv6_upnp_204,
ipv6_upnp_220, ipv6_upnp_igd2_20, ipv6_upnp_igd2_25, ipv6_upnp_igd2_35,
ipv6_upnp_igd2_36, ipv6_upnp_igd2_40, ipv6_upnp_igd2_41,
ipv6_upnp_igd2_45, ipv6_upnp_igd2_50, ipv6_upnp_igd2_100, ipv6_upnp_igd2_200,
ipv6_upnp_igd2_203, ipv6_upnp_igd2_204, ipv6_upnp_igd2_220,
ipv6_upnp_igd2_307
So lets introduce a new CDRouter-UPnP-IPv46-Failing package, with the
above mentioned failing tests (29) which would allow us tracking the
potentially remaining bits which needs to be fixed.
Link: https://support.qacafe.com/cdrouter/knowledge-base/upnp-testing-guide
References: PCF-720, PPW-336, FEAT-85, FEAT-244
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
We're currently using just a subset of UPnP test cases as being
available in CDRouter via PCF-720.
We need to increase the QA of UPnP, so lets add complete upnp and
upnp-v6 modules, which are known to be working as of today. From the
list of available 111 tests in CDRouter version 15.8.1 in both upnp-v6.tcl
(60) and upnp.tcl(51) modules we're removing following 30 tests currently known
to be not passing:
cdrouter_upnp_203, cdrouter_upnp_204, cdrouter_upnp_220,
cdrouter_upnp_igd2_203, cdrouter_upnp_igd2_204, cdrouter_upnp_igd2_220,
ipv6_upnp_35, ipv6_upnp_36, ipv6_upnp_40, ipv6_upnp_41, ipv6_upnp_45,
ipv6_upnp_50, ipv6_upnp_100, ipv6_upnp_203, ipv6_upnp_204,
ipv6_upnp_220, ipv6_upnp_igd2_20, ipv6_upnp_igd2_25, ipv6_upnp_igd2_35,
ipv6_upnp_igd2_36, ipv6_upnp_igd2_40, ipv6_upnp_igd2_41,
ipv6_upnp_igd2_45, ipv6_upnp_igd2_50, ipv6_upnp_igd2_200, ipv6_upnp_igd2_203,
ipv6_upnp_igd2_204, ipv6_upnp_igd2_220, ipv6_upnp_igd2_307
So we can regression test UPnP stack in current state and thus improve the QA.
Cap the CI job runtime to 60 minutes as currently it seems, that it
takes around 53 minutes to complete.
References: PCF-720, PPW-336, FEAT-85, FEAT-244
Link: https://support.qacafe.com/cdrouter/knowledge-base/upnp-testing-guide
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
Co-authored-by: Nikolai Merinov <n.merinov@inango-systems.com>
Changes in FEAT-97 are affecting the sfp datamodel.
It is now seen that the test to check detection of the sfp stick is failing.
The test will need adaptation later to make it aligned with the new datamodel.
Let's disable the test for now so that we can continue with a green CI.
Fixing this test is tracked in PPW-1015
References: PPW-1015, FEAT-97, PCF-1924
Signed-off-by: Matthias Franck <matthias.franck@softathome.com>
Last days we introduced new features and tests in the CI.
Because of that we are hitting now and then the maximum excecution time.
So let's increase the timeout from 40 to 44 minutes.
Signed-off-by: Matthias Franck <matthias.franck@softathome.com>
