On 04/09/2015 10:12 AM, Sandro Bonazzola wrote:
> Il 09/04/2015 10:03, Vinzenz Feenstra ha scritto:
>> On 04/09/2015 09:55 AM, Jorick Astrego wrote:
>>>
>>> On 04/09/2015 08:56 AM, Vinzenz Feenstra wrote:
>>>> On 04/08/2015 04:34 PM, Jorick Astrego wrote:
>>>>> Hi,
>>>> Hi,
>>>>> Testing 3.5.2rc3, I see AVC denied messages for the ovrit-guest agent
(installed through cloud-init).
>>>>>
>>>>> type=AVC msg=audit(1428510418.333:142): avc: denied { read }
for pid=1113 comm="ovirt-guest-age" name="online" dev=sysfs ino=23
>>>>> scontext=system_u:system_r:rhev_agentd_t:s0
tcontext=system_u:object_r:sysfs_t:s0 tclass=file
>>>>> type=AVC msg=audit(1428510418.333:142): avc: denied { open }
for pid=1113 comm="ovirt-guest-age" name="online" dev=sysfs ino=23
>>>>> scontext=system_u:system_r:rhev_agentd_t:s0
tcontext=system_u:object_r:sysfs_t:s0 tclass=file
>>>>> type=SYSCALL msg=audit(1428510418.333:142): arch=c000003e
syscall=2 success=yes exit=6 a0=7f8a655612b8 a1=80000 a2=2803ff a3=0 items=0 ppid=1
>>>>> pid=1113 auid=4294967295 uid=175 gid=175 euid=175 suid=175
fsuid=175 egid=175 sgid=175 fsgid=175 tty=(none) ses=4294967295
>>>>> comm="ovirt-guest-age" exe="/usr/bin/python"
subj=system_u:system_r:rhev_agentd_t:s0 key=(null)
>>>>>
>>>>> And when I check the rpm I see:
>>>>>
>>>>> rpm -qa|grep ovirt
>>>>> ovirt-release-el6-10.0.1-3.noarch
>>>>> ovirt-guest-agent-1.0.8-1.el6.noarch
>>>>>
>>>> Well the latest guest agent is always available on epel for el5/6/7 and
for fedora in the fedora repos I am not sure why it's not available in the
>>>> public ovirt repositories, however that was somehow always a problem with
ovirt releases, but I recommend anyway to use epel for the ovirt guest
>>>> agent due to the fact that I am releasing the guest agent always to epel
and it will get updated from there.
>>>>
>>>> Please also note that the repo location has changed. ovirt-3.5 for el6 is
now here:
http://resources.ovirt.org/pub/ovirt-3.5/rpm/el6/
>>>>
>>>> However what I don't know, is how the 3.3.3 repository got installed
for you, I am not sure that this was done by the bare 'cloud-init', that might
>>>> be specific to your cloud init configuration.
>>> Well that can't be specific. I completely wipe the test environment every
couple weeks and just provisioned a completely fresh ovirt 3.5.2rc3
install.
>>>
>>> Normally I don't use cloud-init as we have foreman, but I was testing it.
The only thing I did was, create new VM and checked the cloud-init/sysprep
>>> checkbox. The rest oVirt did automatically.
>>>
>>> What I think is happening is that the CentOS 6.5 image in the
ovirt-image-repository glance provider is outdated. I used this as template for quick
>>> testing.
>>>
>>> Does anyone know who maintains these images?
>> Sandro, do you by any chance know who does?
> Nobody maintains actively the images in the glance repository.
> I raised the issue a while ago[1] and proposed as "get involved" task to
provide updated images[2] for the glance repository.
> Once new images will be available, Oved can upload them into the glance repository.
>
> [1]
http://lists.ovirt.org/pipermail/devel/2015-April/010193.html
> [2]
http://lists.ovirt.org/pipermail/devel/2015-April/010199.html
>
>
Ok, I will schedule some time to update them as I had been planning to
"get involved" some more ;-)
Will upload somewhere next week.
**
Met vriendelijke groet, With kind regards,
Jorick Astrego*
Netbulae Virtualization Experts *
------------------------------------------------------------------------------------------------------------------------------------------------------
Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180
Fax: 053 20 30 271
www.netbulae.eu 7547 TA Enschede BTW NL821234584B01
------------------------------------------------------------------------------------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at