Wind River Support Network

Description

Deployment a broken OS to target, the target OS upgrade fail and rollback to the good OS successfully. Then deployment a good OS to the target will always fail. 

Workaround

After the target OS rollback, trigger a reboot manually and then do the new OS deployment could be successful.

Steps to Reproduce

1) setup.sh
--machine bcm-2xxx-rpi4 --dl-layers --template feature/fullmetalupdate feature/ostree --layers meta-lat
2) source environment-setup-x86_64-wrlinuxsdk-linux && source oe-init-build-env
3) cat >> config.cfg << EOF
[client]
hawkbit_vendor_name = WRLinux
hawkbit_url_port = 8080
hawkbit_ssl = false
hawkbit_tenant_id = DEFAULT
hawkbit_target_name = FullMetalUpdate_Demo
hawkbit_auth_token = 380ff2b5908e776cb69159f3f4477e4f
log_level = debug

[ostree]
ostree_name_remote = fullmetalupdate
ostree_gpg-verify = false
ostree_ssl = false
ostree_url_port = 8000
ostreepush_ssh_port = 8022
ostreepush_ssh_user = root
ostreepush_ssh_pwd = root

[server]
server_host_name = <ota_server_ip>
EOF

4) cat >> conf/local.conf <<EOF
HAWKBIT_CONFIG_FILE = "${TOPDIR}/config.cfg"
EOF

5) bitbake  wrlinux-image-small 

6) boot the target by wrlinux-image-small-bcm-2xxx-rpi4.wic

7) generate a good os for deployment
$ echo 'IMAGE_INSTALL:append = "strace"' >> conf/local.conf 
$ bitbake wrlinux-image-small  

8) generate a broken OS for deployment 
$ sed 's/exit 0/reboot/g' ../layers/wrlinux/wrlinux-distro/recipes-core/wr-init/files/rc.local.example -i 
$ bitbake wrlinux-image-small

9) At hawkbit server, deployment the broken OS to the target

10) At hawkbit server, deployment the good OS to the target