Description of problem: a) rh-amazon-rhui-client still uses legacy init.d b) removing rh-amazon-rhui-client leads to dangling symlinks in /etc/rc.d/* Version-Release number of selected component (if applicable): - How reproducible: Always Steps to Reproduce: 1. Run AWS image with rh-amazon-rhui-client installed. 2. # rpm -e rh-amazon-rhui-client 3. # ls -l /etc/rc.d/rc*.d/*rh-cloud-firstboot lrwxrwxrwx. 1 root root 28 Nov 19 12:52 /etc/rc.d/rc0.d/K95rh-cloud-firstboot -> ../init.d/rh-cloud-firstboot lrwxrwxrwx. 1 root root 28 Nov 19 12:52 /etc/rc.d/rc1.d/K95rh-cloud-firstboot -> ../init.d/rh-cloud-firstboot lrwxrwxrwx. 1 root root 28 Feb 13 08:23 /etc/rc.d/rc2.d/S45rh-cloud-firstboot -> ../init.d/rh-cloud-firstboot lrwxrwxrwx. 1 root root 28 Feb 13 08:23 /etc/rc.d/rc3.d/S45rh-cloud-firstboot -> ../init.d/rh-cloud-firstboot lrwxrwxrwx. 1 root root 28 Feb 13 08:23 /etc/rc.d/rc4.d/S45rh-cloud-firstboot -> ../init.d/rh-cloud-firstboot lrwxrwxrwx. 1 root root 28 Feb 13 08:23 /etc/rc.d/rc5.d/S45rh-cloud-firstboot -> ../init.d/rh-cloud-firstboot lrwxrwxrwx. 1 root root 28 Nov 19 12:52 /etc/rc.d/rc6.d/K95rh-cloud-firstboot -> ../init.d/rh-cloud-firstboot # ls -l ../init.d/rh-cloud-firstboot ls: cannot access ../init.d/rh-cloud-firstboot: No such file or directory Actual results: legacy init.d + dangling symlinks after package removal Expected results: uses systemd and correctly disabled/removes the service upon package removal. Additional info: Customer case will be linked. There is also a sysconfig file in /etc/sysconfig/rh-cloud-firstboot, which doesn't seem to be owned by the RPM. This applies to both RHEL7 and RHEL8.
Same applies to choose_repo rcX.d files: /etc/rc.d/rc0.d/K50choose_repo /etc/rc.d/rc1.d/K50choose_repo /etc/rc.d/rc2.d/S50choose_repo /etc/rc.d/rc3.d/S50choose_repo /etc/rc.d/rc4.d/S50choose_repo /etc/rc.d/rc5.d/S50choose_repo /etc/rc.d/rc6.d/K50choose_repo
Indeed Peter! I missed these - thanks for adding the comment!
An updated rh-amazon-rhui-client package has been made available globally.