[Spacewalk-list] RHEV 3 support

[Colin Coe]

Hmmm, or maybe not.

I'm getting heaps of mail to root on my fat RHEL 6.2 RHEV hypervisors
that are resulting from "python
/usr/share/rhn/virtualization/poller.py" failing.  these are being
called every two minutes from /etc/cron.d/rhn-virtualization.cron.

The trace back is
---
Traceback (most recent call last):
  File "/usr/share/rhn/virtualization/poller.py", line 289, in <module>
    domain_list = poll_through_vdsm()
  File "/usr/share/rhn/virtualization/poller.py", line 139, in poll_through_vdsm
    import localvdsm
  File "/usr/share/rhn/virtualization/localvdsm.py", line 30, in <module>
    from config import config
  File "/usr/share/vdsm/config.py", line 69, in <module>
    config.set('vars', 'trust_store_path', constants.P_TRUSTSTORE)
ImportError: local vdsm not found
---

I've had a brief poke at this but not sure how to resolve.  Any ideas?

Thanks

CC

On Sat, Dec 24, 2011 at 9:17 AM, Colin Coe <colin.coe at gmail.com> wrote:
> Hi all
>
> After cursory testing , looks like rhev3 works OK now.  Will do further
> testing next week.
>
> CC
>
> ---
>
> Sent from my Galaxy Nexus
>
> On Dec 22, 2011 7:52 AM, "Colin Coe" <colin.coe at gmail.com> wrote:
>>
>> Hi all
>>
>> Is RHEV 3 support on the TODO list?  As I emailed a week or two ago,
>> I'm unable to register RHEV VMs against spacewalk due to entitlement
>> errors.
>>
>> ---
>> Problem registering system:
>>
>> Error Class Code: 70
>> Error Class Info:
>>     All available subscriptions for the requested channel have been
>> exhausted. Please contact a Red Hat Network Sales associate.
>> Explanation:
>>     An error has occurred while processing your request. If this
>> problem persists please enter a bug report at bugzilla.redhat.com.
>>     If you choose to submit the bug report, please be sure to include
>> details of what you were trying to do when this error occurred and
>> details on how to reproduce this problem.
>> ---
>>
>> I've tried just doing a plain rhn_register and walking through the
>> TUI.  This gives me exactly the same error as if the node had tried to
>> register after being provisioned through a kickstart profile and PXE
>> boot.
>>
>> There is no activation key in use using rhn_register.  When happening
>> via provisioning from PXE, there is an activation key but no
>> entitlements are specified.
>>
>> Hope I've provided sufficient detail.
>>
>> Thanks
>>
>> CC
>>
>>
>> --
>> RHCE#805007969328369



-- 
RHCE#805007969328369