[ovirt-devel] [ovirt-users] [QE] oVirt 3.6.1 Hosted Engine test day

[Gianluca Cecchi]

On Mon, Dec 14, 2015 at 11:06 AM, Sandro Bonazzola <sbonazzo at redhat.com>
wrote:

>
>>
>
> Adding Fabian.
> You can use the released appliance but you'll need to manually update it.
>  We have a nightly built appliance available in jenkins, waiting fabian
> for releasing it with RC4 rpms included.
> You can find an updated appliance here:
> http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-3.6_build-artifacts-el7-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/ovirt-engine-appliance-3.6-20151211.1.el7.centos.noarch.rpm
>
>
>
>
OK. I have used the jenkins link and all the initial configuration went ok
without error.
But at the admin portal I see "Version 3.6.0.3-1.el7.centos" ...

Is it correct/expected that on engine VM the version
is ovirt-engine-3.6.0.3-1.el7.centos.noarch like in current 3.6.0
environments?
I don't think so.....

All set of packages is...
 [root at shengine ovirt-engine]# rpm -qa|grep ovirt
ovirt-vmconsole-1.0.0-1.el7.centos.noarch
ovirt-engine-setup-base-3.6.0.3-1.el7.centos.noarch
ovirt-host-deploy-java-1.4.0-1.el7.centos.noarch
ovirt-engine-restapi-3.6.0.3-1.el7.centos.noarch
ovirt-engine-dbscripts-3.6.0.3-1.el7.centos.noarch
ovirt-engine-3.6.0.3-1.el7.centos.noarch
ovirt-iso-uploader-3.6.0-1.el7.centos.noarch
ovirt-engine-extensions-api-impl-3.6.0.3-1.el7.centos.noarch
ovirt-vmconsole-proxy-1.0.0-1.el7.centos.noarch
ovirt-engine-cli-3.6.0.1-1.el7.centos.noarch
ovirt-engine-wildfly-8.2.0-1.el7.x86_64
ovirt-engine-lib-3.6.0.3-1.el7.centos.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.6.0.3-1.el7.centos.noarch
ovirt-engine-websocket-proxy-3.6.0.3-1.el7.centos.noarch
ebay-cors-filter-1.0.1-0.1.ovirt.el7.noarch
ovirt-engine-backend-3.6.0.3-1.el7.centos.noarch
ovirt-engine-userportal-3.6.0.3-1.el7.centos.noarch
ovirt-engine-webadmin-portal-3.6.0.3-1.el7.centos.noarch
ovirt-engine-vmconsole-proxy-helper-3.6.0.3-1.el7.centos.noarch
ovirt-engine-setup-3.6.0.3-1.el7.centos.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.6.0.3-1.el7.centos.noarch
ovirt-guest-agent-common-1.0.11-1.el7.noarch
ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch
ovirt-image-uploader-3.6.0-1.el7.centos.noarch
ovirt-engine-extension-aaa-jdbc-1.0.1-1.el7.noarch
ovirt-host-deploy-1.4.0-1.el7.centos.noarch
ovirt-engine-wildfly-overlay-001-2.el7.noarch
ovirt-engine-setup-plugin-websocket-proxy-3.6.0.3-1.el7.centos.noarch
ovirt-engine-tools-3.6.0.3-1.el7.centos.noarch
ovirt-engine-setup-plugin-vmconsole-proxy-helper-3.6.0.3-1.el7.centos.noarch
ovirt-release36-002-2.noarch

even if it is wrong, is there anything to test, eg upgrading the engine to
3.6.1rc4?

BTW I was able to add an NFS storage domain and ISO storage domain at the
moment to the single host.

When adding the NFS domain I got in events pane:

Storage Domain NFS was added by admin at internal
Data Center is being initialized, please wait for initialization to
complete.
Storage Pool Manager runs on Host hosted_engine_1 (Address:
ovc71.localdomain.local).

and then

This Data center compatibility version does not support importing a data
domain with its entities (VMs and Templates). The imported domain will be
imported without them.

and then
Storage Domain NFS (Data Center Default) was activated by admin at internal
Storage Domains were attached to Data Center Default by admin at internal
Storage Domain NFS was attached to Data Center Default by admin at internal

Is the compatibility message only iformative, to be shown also when you add
(and don't import), or is a messge related to the datacenter itself, as
with the forst data domain I'm going to activate the DC too..?

Gianluca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20151214/8766c1b0/attachment-0001.html>