<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Dec 14, 2015 at 11:06 AM, Sandro Bonazzola <span dir="ltr">&lt;<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div><div class="h5"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
</blockquote></div><br><br></div></div>Adding Fabian.</div><div class="gmail_extra">You can use the released appliance but you&#39;ll need to manually update it.</div><div class="gmail_extra"> We have a nightly built appliance available in jenkins, waiting fabian for releasing it with RC4 rpms included.</div><div class="gmail_extra">You can find an updated appliance here: <a href="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" target="_blank">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</a></div><span class=""><div class="gmail_extra"><br><br><br></div></span></div></blockquote><div><br></div><div>OK. I have used the jenkins link and all the initial configuration went ok without error.</div><div>But at the admin portal I see &quot;Version 3.6.0.3-1.el7.centos&quot; ...</div><div><br></div><div>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?</div><div>I don&#39;t think so.....</div><div><br></div><div>All set of packages is... </div><div> [root@shengine ovirt-engine]# rpm -qa|grep ovirt</div><div>ovirt-vmconsole-1.0.0-1.el7.centos.noarch</div><div>ovirt-engine-setup-base-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-host-deploy-java-1.4.0-1.el7.centos.noarch</div><div>ovirt-engine-restapi-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-dbscripts-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-iso-uploader-3.6.0-1.el7.centos.noarch</div><div>ovirt-engine-extensions-api-impl-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-vmconsole-proxy-1.0.0-1.el7.centos.noarch</div><div>ovirt-engine-cli-3.6.0.1-1.el7.centos.noarch</div><div>ovirt-engine-wildfly-8.2.0-1.el7.x86_64</div><div>ovirt-engine-lib-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-setup-plugin-ovirt-engine-common-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-websocket-proxy-3.6.0.3-1.el7.centos.noarch</div><div>ebay-cors-filter-1.0.1-0.1.ovirt.el7.noarch</div><div>ovirt-engine-backend-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-userportal-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-webadmin-portal-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-vmconsole-proxy-helper-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-setup-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-setup-plugin-ovirt-engine-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-guest-agent-common-1.0.11-1.el7.noarch</div><div>ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-image-uploader-3.6.0-1.el7.centos.noarch</div><div>ovirt-engine-extension-aaa-jdbc-1.0.1-1.el7.noarch</div><div>ovirt-host-deploy-1.4.0-1.el7.centos.noarch</div><div>ovirt-engine-wildfly-overlay-001-2.el7.noarch</div><div>ovirt-engine-setup-plugin-websocket-proxy-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-tools-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-engine-setup-plugin-vmconsole-proxy-helper-3.6.0.3-1.el7.centos.noarch</div><div>ovirt-release36-002-2.noarch</div><div><br></div></div>even if it is wrong, is there anything to test, eg upgrading the engine to 3.6.1rc4?</div><div class="gmail_extra"><br></div><div class="gmail_extra">BTW I was able to add an NFS storage domain and ISO storage domain at the moment to the single host.</div><div class="gmail_extra"><br></div><div class="gmail_extra">When adding the NFS domain I got in events pane:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">Storage Domain NFS was added by admin@internal</div><div class="gmail_extra">Data Center is being initialized, please wait for initialization to complete.</div><div class="gmail_extra">Storage Pool Manager runs on Host hosted_engine_1 (Address: ovc71.localdomain.local).</div><div class="gmail_extra"><br></div><div class="gmail_extra">and then</div><div class="gmail_extra"><br></div><div class="gmail_extra">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.</div><div class="gmail_extra"><br></div><div class="gmail_extra">and then</div><div class="gmail_extra">Storage Domain NFS (Data Center Default) was activated by admin@internal</div><div class="gmail_extra">Storage Domains were attached to Data Center Default by admin@internal</div><div class="gmail_extra">Storage Domain NFS was attached to Data Center Default by admin@internal</div></div><div class="gmail_extra"><br></div><div class="gmail_extra">Is the compatibility message only iformative, to be shown also when you add (and don&#39;t import), or is a messge related to the datacenter itself, as with the forst data domain I&#39;m going to activate the DC too..?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Gianluca</div></div>