After enabling unified-services in version 22.4R1-S2.1 Subscriber Management is coming up in 32-bit mode.
LAB Replication done with version 22.4R1-S2.1
We loaded version 22.4R1-S2.1 in RE0.
lab@re0> show vmhost version invoke-on all-routing-engines | no-more
Nov 22 19:42:20
re0:
--------------------------------------------------------------------------
Current root details, Device sda, Label: jrootb_P, Partition: sda4
Current boot disk: Primary
Current root set: b
UEFI Version: REH_P_MTR1_00.30.07
Primary Disk, Upgrade Time: Wed Nov 22 15:47:48 PST 2023
Version: set p
VMHost Version: 7.2670
VMHost Root: vmhost-x86_64-22.3R3-20230406_1215_builder
VMHost Core: vmhost-core-x86-64-22.3R3.8
kernel: 5.2.60-rt15-LTS19
Junos Disk: junos-install-mx-x86-64-22.3R3.8
Version: set b
VMHost Version: 7.2674
VMHost Root: vmhost-x86_64-22.4R1-S1-20230201_1649_builder
VMHost Core: vmhost-core-x86-64-22.4R1-S2.1
Junos Disk: junos-install-mx-x86-64-22.4R1-S2.1
lab@re0# set system services subscriber-management enable
lab@re0# commit check
Nov 22 19:43:40
[edit system services subscriber-management]
'enable'
warning: Chassis configuration for subscriber-management has been changed. A system reboot is mandatory. Please reboot the system NOW. Continuing without a reboot might result in unexpected system behavior.
configuration check succeeds
lab@re0> request system enable unified-services
Nov 22 20:16:45
Before enabling unified services, please move to baseline configuration.
Are above conditions satisfied ? [yes,no] (no) yes
Nov 22 20:16:50
Verified junos-unified-services signed by PackageProductionECP256_2023 method ECDSA256+SHA256
NOTICE: 'pending' set will be activated at next reboot...
Verified junos-unified-services-x86-32-20230322 signed by PackageProductionECP256_2023 method ECDSA256+SHA256
Unified-Services upgrade staged. Please reboot with 'request system reboot' command to complete the upgrade
lab@re0> request vmhost reboot
Nov 22 20:17:42
Reboot the vmhost ? [yes,no] (no) yes
Nov 22 20:17:45
After doing the reboot we lost SSH connection, but from the console we can see that subscriber-management is booting in 32-bit mode.
root> show system processes | grep libexec
24978 - S 0:00.62 /usr/libexec/bslockd -mp -N
25061 - S 0:00.43 /usr/libexec32/smid -N
25884 - S 0:07.28 /usr/libexec32/authd -N
26605 - S 0:05.49 /usr/libexec64/rpd -N
26611 - S 0:01.09 /usr/libexec32/cosd
26633 - S 0:01.15 /usr/libexec32/jdhcpd -N
26656 - S 0:01.10 /usr/libexec32/pfed -N
26657 - S 0:00.42 /usr/libexec32/dfwd -N
26662 - S 0:04.15 /usr/libexec32/jpppd -N
26663 - S 0:06.03 /usr/libexec32/jl2tpd -N
If you encounter this issue please open a case in JTAC as this is still under internal investigation.