Don's try to restart dracut-initqueue if it's already there
    
    Resolves: bz1901024
    Upstream: Fedora
    Conflict: None
    
    commit 108258139a24b596be454c9aaa07b6ebf96e49a1
    Author: Kairui Song <kasong@redhat.com>
    Date:   Mon Apr 26 17:09:55 2021 +0800
    
        Don's try to restart dracut-initqueue if it's already there
    
        kdump's dump_to_rootfs will try to start initqueue unconditionally.
        dump_to_rootfs will run after systemd isolate to emergency
        target, so this is currently accetable.
    
        But there is a problem when initqueue starts the emergency action
        because of initqueue timeout. dump_to_rootfs will start initqueue and
        lead to timeout again.
    
        So following patch will remove the previous isolation wrapper, and
        detect the service status here. Previous isolation makes the detection
        impossible. Now this detection will be valid and helpful to prevent
        double timeout or hang.
    
        Signed-off-by: Kairui Song <kasong@redhat.com>
        Acked-by: Coiby Xu <coxu@redhat.com>
    
    Signed-off-by: Kairui Song <kasong@redhat.com>