Import RPM repository GPG keys from other keyservers temporarily

I’ve been working through some patches to OpenStack-Ansible lately to optimize how we configure yum repositories in our deployments. During that work, I ran into some issues where pgp.mit.edu was returning 500 errors for some requests to retrieve GPG keys. Ansible was returning this error: curl: (22) The requested URL returned error: 502 Proxy Error error: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x61E8806C: import read failed(2) How does the rpm command know which keyserver to use? Let’s use the –showrc argument to show how it is configured:

CoreOS vs. Project Atomic: A Review

This post hasn’t been updated in quite some time. Many of these comparisons still hold true but some don’t. Updating this post is on my list of to-do’s. - MH 2015-04-25 You’ve probably been living under a rock if you haven’t heard about Docker. It simplifies the deployment and management of Linux containers better than anything else I’ve seen so far. Many ecosystems are growing with Docker at the core and two of the most popular hosting platforms for Docker are CoreOS and Project Atomic.

virt-manager: ‘NoneType’ object has no attribute ‘cpus’

After upgrading my Fedora 20 Xen hypervisor to virt-manager 1.0.0, I noticed that I couldn’t open the console or VM details for any of my guests. Running virt-manager –debug gave me the following traceback: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 803, in _show_vm_helper details = self._get_details_dialog(uri, uuid) File "/usr/share/virt-manager/virtManager/engine.py", line 760, in _get_details_dialog obj = vmmDetails(con.get_vm(uuid)) File "/usr/share/virt-manager/virtManager/details.py", line 530, in init self.init_details() File "/usr/share/virt-manager/virtManager/details.py", line 990, in init_details for name in [c.

Keeping bwm-ng 0.6 functional on Fedora 19

If you run bwm-ng and you’ve run a yum upgrade lately on Fedora 19, you have probably seen this: —> Package libstatgrab.x86_64 0:0.17-4.fc19 will be updated –> Processing Dependency: libstatgrab.so.6()(64bit) for package: bwm-ng-0.6-10.fc19.x86_64 –> Finished Dependency Resolution Error: Package: bwm-ng-0.6-10.fc19.x86_64 (@fedora) Requires: libstatgrab.so.6()(64bit) Removing: libstatgrab-0.17-4.fc19.x86_64 (@fedora) libstatgrab.so.6()(64bit) Updated By: libstatgrab-0.90-1.fc19.x86_64 (updates) ~libstatgrab.so.9()(64bit) You could try using –skip-broken to work around the problem You could try running: rpm -Va –nofiles –nodigest The error message mentions that libstatgrab needs to be updated to version 0.

Moving from OS X to Linux: Day One

The thought of using Linux as a manager in a highly Windows- and Mac-centric corporate environment isn’t something to be taken lightly. Integrating with Active Directory, wrangling email with Microsoft Exchange, and taming quirky Microsoft office documents can be a challenge even with a well-equipped Mac. I decided to make a change after using a Mac at Rackspace for six years. Let’s get one thing straight: I’m not a Windows or Mac basher.