Skip to main content

Snapshot cleanup expect script for Satellite

My environment does not see a lot of general maintenance or attention in particular ways.  I will occasionally find something that is either causing us grief, or about to...

One of those items is the size of my Satellite Database.  The size is now an issue as I hope to upgrade to Red Hat Satellite 5.6 and migrate to Postgres in the process (yeah!).

Some folks have recommended:
* remove unused channels (seems logical enough)
* remove unused/older snapshots

I'm fairly certain that nobody else in my environment knows or realizes that snapshots even exist, let alone why they are advantageous.  Therefore, I intend to truncate the snapshots to only include those created in the last 4 months.

#!/usr/bin/expect -f
#
# Expect and autoexpect were both written by Don Libes, NIST.
#
set force_conservative 0  ;# set to 1 to force conservative mode even if
                          ;# script wasn't run conservatively originally
if {$force_conservative} {
        set send_slow {1 .1}
        proc send {ignore arg} {
                sleep .1
                exp_send -s -- $arg
        }
}

if { $argc != 1 } {
  puts "\r"
  puts "ERROR: Unexpected parameters.\r"
  puts "$argv0 <SystemUID> \r"
  exit
}

set CLIENTNAME [lindex $argv 0]

set timeout -1
spawn $env(SHELL)
match_max 100000
expect -exact "\[root@rhnsat01 ~\]# "
send -- "sw-system-snapshot --delete --system-id ${CLIENTNAME} --start-date=20100901000000 --end-date \$(date -d \"-4 months\" \"+%Y%m%d0000\")\r"
expect "Red Hat Network username: "
send -- "satadmin\r"
expect -exact "satadmin\r
Red Hat Network password: "
send -- "<redacted>\r"
expect -exact "\r
\[root@rhnsat01 ~\]# "
send -- "exit\r"
expect eof

Comments

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.