QA Changelog 7.1.2
Released 2026-09-04 · v7.1.2.a · 14 issues
For test planning. Lists every Jira issue in the release together with the maintenance work that came with it. What those issues mean for a customer is in the external changelog.
Jira References
-
DEV-1194 - OneIoT ACS > TR-069 > Add option for ACS to generate individual username/password for each device
-
DEV-2049 - OneIoT ACS > USP > Big device tree > Group of devices > Register > Hazelcast related errors in server log
-
DEV-2129 - OneIoT ACS > ProductClassGroupCache > Possible wrong groupId returned by getForManufacturerAndModel() method
-
DEV-2332 - FT Configs > ACS > "config_custom_data.xml" > Configuration file missing
-
DEV-2520 - OneIoT ACS > "ISP = 2" > Device in specific domain > Re-register device to another domain > Device not transferred to domain
-
DEV-2606 - Angular Project > Management Portal > TR-181 > Find device > File upload > "Vendor Configuration File <i>" > "Instance" drop-down is unclickable
-
DEV-2671 - A: OneIoT ACS > Management Portal > TR-181 > Find device > File upload > "Vendor Configuration File <i>" > "Instance" isn’t saved
-
DEV-2749 - OneIoT ACS > "ISP = 0" > Register device > Incorrect "location_id" is stored in DB
-
DEV-2784 - One IoT ACS > TR-069 > Session initiated by device > "cwmp:ID" not empty > "mustUnderstand=1" > ACS responds with empty "cwmp:ID"
-
DEV-2787 - FTACS WS authentication does not recover after Hazelcast restart
-
DEV-2796 - B: Angular Project > Management Portal > ISP = 1 / 2 > Specific domain > Settings > Alert and Events > Events > The settings are not inherited from the Super domain
-
DEV-2832 - Angular Project / CPE Admin > Management Portal > "ISP = 1/2" > Settings > Alerts and events > Hardcoded events > Save > ACS Exception
-
DEV-2855 - OneIoT ACS > Non-default ClickHouse "ftacs" user password > Run > Failed to connect to ClickHouse
-
DEV-2900 - Device > Onboarding issue
Chores
-
Add deployment.yaml contract for Deployment Manager
Deployment Manager reads this file from the tip of this branch to know the service’s image, ports, volumes, clustering pattern and the variables an operator must fill in. It was previously vendored in ft-internal-tools (deployment-manager/catalogue/contracts/ftacs.yaml); this repository now owns it.
-
Add the deployment/ config tree Deployment Manager mounts
These are the application config files a generated Compose bundle mounts into this service’s container. They were vendored in ft-internal-tools (deployment-manager/catalogue/services/); this repository now owns them, and Deployment Manager reads them from the tip of this branch.
Private key material is deliberately NOT here: keys and keystores stay in the one place they already live and are laid over this tree at generation time, so the same private key does not gain a copy per repository.
-
Add the key material this service’s bundle mounts
Completes the deployment/ tree: the keystores and TLS private key a generated Compose bundle mounts into this container, which were held back from the previous commit while their placement was decided.
They are tracked here rather than in ft-internal-tools so a service’s install payload is one thing in one place. Rotating a key is now a commit in this repository — the same file was previously copied across two repositories, and a rotation had to find both.