Skip to main content

Red Hat Satellite: Cleanup "Actions" history

I had run in to a situation where my Satellite had several hundred-thousand previously run scheduled jobs sitting in the history... I could delete them 25 at a time... and if I did "Select All" it would puke.

So - I created the following

#!/usr/bin/env python
import xmlrpclib
import time

SATELLITE_URL = "http://rhnsat01.company.com/rpc/api"
SATELLITE_LOGIN = "satadmin"
SATELLITE_PASSWORD = "notMyPassword"

client = xmlrpclib.Server(SATELLITE_URL, verbose=0)
delete = 1

key = client.auth.login(SATELLITE_LOGIN, SATELLITE_PASSWORD)

###############################
# CHANGE THINGS AFTER THIS LINE
#

## Delete all Failed Actions
x = "Deleting all Failed Actions"
print(x)
failed_list = client.schedule.listFailedActions(key)
action_ids=[]
for action in failed_list:
    action_ids.append(action['id'])

archive_result=client.schedule.archiveActions(key,action_ids)

## Archive all Completed Actions
## Generate an Array of size (max_num_ids) and purge it
x = "Archiving all Completed Actions"
print(x)
counter = 0
max_num_ids = 100
archived_list = client.schedule.listCompletedActions(key)
action_ids=[]
for action in archived_list:
    print action.get('id')
    action_ids.append(action['id'])
    counter = counter + 1
    if counter == max_num_ids:
        del_result=client.schedule.archiveActions(key,action_ids)
        time.sleep(.1)
        action_ids=[]
        counter = 0

## Delete all Archived Actions
## Generate an Array of size (max_num_ids) and purge it
x = "Deleting all Completed Actions"
print(x)
counter = 0
max_num_ids = 100
archived_list = client.schedule.listArchivedActions(key)
action_ids=[]
## Traverse Array in reverse [::-1]
#for action in archived_list[::-1]:
## Traverse Array in forward [:]
for action in archived_list:
    print action.get('id')
    action_ids.append(action['id'])
    counter = counter + 1
    if delete == 1:
        if counter == max_num_ids:
          del_result=client.schedule.deleteActions(key,action_ids)
          time.sleep(.1)
          action_ids=[]
          counter = 0

##
## CHANGE THINGS BEFORE THIS LINE
###############################
client.auth.logout(key)

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.