Hmm, turns out that comment those lines, while it does make Spacewalk
happy, results in 'non-responsive' (fat RHEL) RHEV hypervisors after
going putting the host into maintenance mode and then attempting to
make the host active again.
I think this still needs some investigation but my previous 'so
> Oops, sorry. Completely missed this question.
>
> Just spinning up a new spacewalk server (1.7 on postgres) in a new dev
> environment and I'm running into this again. RHEV 3.0.2.
>
> [root@benvir2d ~]# python /usr/share/rhn/virtualization/poller.py
> Traceback (most recent call last):
> Fi
Oops, sorry. Completely missed this question.
Just spinning up a new spacewalk server (1.7 on postgres) in a new dev
environment and I'm running into this again. RHEV 3.0.2.
[root@benvir2d ~]# python /usr/share/rhn/virtualization/poller.py
Traceback (most recent call last):
File "/usr/share/r
> Re-sending with subject...
>
> On Wed, Nov 30, 2011 at 12:29 PM, Colin Coe wrote:
> > Hi all
> >
> > Was having a look at my (fat RHEL 6.1) RHEV hypervisors. I updated
> > rhn-virtualization* to 5.4.30-1.el6.noarch (out of nightly)
> >
> > When running 'python /usr/share/rhn/virtualization/p
Re-sending with subject...
On Wed, Nov 30, 2011 at 12:29 PM, Colin Coe wrote:
> Hi all
>
> Was having a look at my (fat RHEL 6.1) RHEV hypervisors. I updated
> rhn-virtualization* to 5.4.30-1.el6.noarch (out of nightly)
>
> When running 'python /usr/share/rhn/virtualization/poller.py' I get a
>
