Issue #14761 has been updated by Stefan Schulte.

I currently do not have a SLES system around but I suspect the issue is still 
present as explained in https://projects.puppetlabs.com/issues/14615#note-12
----------------------------------------
Bug #14761: puppet resource service will kill your sles system
https://projects.puppetlabs.com/issues/14761#change-83065

Author: Matthaus Owens
Status: Closed
Priority: Normal
Assignee: Matthaus Owens
Category: 
Target version: 2.7.15
Affected Puppet version: 
Keywords: 
Branch: 
https://github.com/haus/puppet/tree/ticket/2.7rc/14761_add_excludes_for_sles_services_to_redhat_provider


Executing `puppet resource service` on a sles11 system will run the reboot init 
script, which ignore any arguments like status and proceeds to reboot the 
system, which is generally not the desired effect. It will also run the boot 
script, which does odd things and occasionally hangs indefinitely.

Here's an example of the boot script oddness.

    blogd: console=/dev/console, stdin=/dev/console, must differ, boot logging 
disabled
    Starting udevd: error binding control socket, seems udevd is already running
    done
    Activating swap-devices in /etc/fstab...                                    
                                      done
    /bin/mknod -m600 /dev/shm/root b 8 2
    /bin/mknod: `/dev/shm/root': File exists
    *** ERROR!  Cannot fsck because root is not read-only!
    Set System Time to the current Hardware Clock                               
                                      done
    Activating device mapper...
    done
    Loading required kernel modules                                             
                                      done
    Starting MD RAID                                                            
                                      unused
    Checking file systems...
    fsck from util-linux 2.19.1
    Checking all file systems.                                                  
                                      done
    Mounting local file systems...
    proc on /proc type proc (rw)
    sysfs on /sys type sysfs (rw)
    debugfs on /sys/kernel/debug type debugfs (rw)
    devtmpfs on /dev type devtmpfs (rw,mode=0755)
    tmpfs on /dev/shm type tmpfs (rw,mode=1777)
    devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
    nothing was mounted                                                         
                                      done
    Check if the profiles matches the system                                    
                                      done
    Creating /var/log/boot.msg

It hangs there not infrequently until killed.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to