Upgrade from 3.5rc to 3.5 final question
by Gianluca Cecchi
I see this in release notes for 3.5:
"
If you're using pre-release repo you'll need to re-enable pre release
repository:
[ovirt-3.5-pre]
name=Latest oVirt 3.5 Pre Release
#baseurl=http://resources.ovirt.org/pub/ovirt-3.5-pre/rpm/fc$releasever/
mirrorlist=
http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-3.5-pre-fc$relea...
enabled=1
skip_if_unavailable=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-3.5
and to run:
# yum update "ovirt-engine-setup*"
# engine-setup
"
but this leaves me some doubts...
I currently have RC3 (or 4, I don't remember exactly).
But if I walk through the pre-repo mirror, it seems to me that for example
I will get
ovirt-engine-backend-3.5.0.1-0.0.master.20141009085636.el6.noarch.rpm
while going through 3.5 repo I will get
ovirt-engine-backend-3.5.0.1-1.el6.noarch.rpm
Are they indeed the same?
Can you confirm that if I have a RC release I still have to use -pre repo
to update to official 3.5.0?
Thanks,
Gianluca
10 years
Live snapshot failed but still there ??
by Punit Dambiwal
Hi,
I try to create the live snapshot it failed because of the VM filesystem
inconsistency but in the engine dashboard it shows it created ??
Screen shots attached....
Thanks,
Punit
10 years
migrate from stand alone on FC19 to hosted OK to use CentOS 7?
by Alastair Neil
I am trying to migrate my old ovirt install which started out at 3.3
standalone engine on FC19 to a hosted engine. I want to use CentOS ,
however, the postgresql version on 6.5 is old (8.4.20) and I am unable to
get a clean restore. The version on FC 19 is 9.2.8, it looks like EL 7 has
9.2.7 (I am hoping the difference in the minor rev will not bite me).
I was wondering if there are any issues using EL 7 to host the engine? I
know I had seen some reports of issues with 3.5 on EL7 as hosts but was not
sure if the engine had any gotchas.
Thanks, Alastair
10 years
Re: [ovirt-users] CoreOS can not install on Ovirt
by Brian Harrington
Punit,
Former Red Hatter and current "coreo" here.
First which image are you trying to load? Your best bet will be to use
the QEMU image. Also take a look at the console and see what the boot:
line being supplied is.
--Brian 'redbeard' Harrington
> Hi,
>
> I try to install the CoreOS (https://coreos.com/) as guest VM under ovirt
> 3.5 by ISO...but if i choose this CoreOS iso....
>
> [image: Inline image 1]
>
> But if i choose Centos iso...it start the installation without any problem
> ....i already checked the ISO of CoreOS is perfectly fine...i can install
> it with physical machine...but stuck in the OVirt...
>
> Thanks,
> Punit
10 years
MacPoolRanges not working as expected
by Xavier Naveira
Hi everyone,
First of all I'd like to say that we have been using oVirt successfully
for more than a year, creating an automated deploy system with help of
foreman and puppet.
That being said, we're currently facing the first serious problem and
we'd appreciate some help.
Everything was working fine until we exhausted the default
MacPoolRanges. After looking for a solution to the error message we
found this document:
http://www.ovirt.org/Engine_config_examples#MacPoolRanges
Following the instructions on it we executed the following commands:
First we found out what our current pool was:
# engine-config -g MacPoolRanges
MacPoolRanges: 00:1a:4a:24:26:00-00:1a:4a:24:26:ff version: general
So we proceeded to expand it:
# engine-config -s "MacPoolRanges=00:1a:4a:24:26:00-00:1a:4a:24:27:ff"
# service ovirt-engine restart
After this we were able to create new machines but none of them seemed
to have network.
After some unsuccessful troubleshooting we restored the original pool
and instead added a new one:
# engine-config -s "MacPoolRanges=00:1a:4a:24:26:00-00:1a:4a:24:26:ff"
# service ovirt-engine restart
# engine-config -s
"MacPoolRanges=00:1a:4a:24:26:00-00:1a:4a:24:26:ff,00:1a:4a:24:27:00-00:1a:4a:24:27:ff"
# service ovirt-engine restart
After doing this and test to create a new host everything seemed to work
fine.
The problem is that after the successful creation of some hosts the
original problem where the new hosts didn't seem to have network,
reappeared.
Trying to narrow down the problem what we've find out so far is:
This oVirt environment kickstarts hosts via PXE, when trying to PXE boot
a new host, the DHCP process fails (timeout).
Tracing the network packets, we are able to see that the virtual host
sends the dhcp request, the dhcp server receives it and acknowledges it
and it sends the dhcp offer back. The dhcp offer reaches the hypervisor
to the vnetxx network interface BUT it doesn't go further and it doesn't
reach the virtual host. This behavior is consistent through different
hypervisors and vlans, including the ones that have been used/created
before the problems appeared.
The only pattern that we've been able to identify so far is through
issuing the command "brctl showmacs <bridge_name>"
This command list the mac addresses for the interfaces connected to the
bridge. In the cases where everything works fine the output looks like this:
port no mac addr is local? ageing timer
2 00:1a:4a:24:27:e0 no 0.01
2 fe:1a:4a:24:27:e0 yes 0.00
The virtual host MAC address begins with "00" and it has a corresponding
address beginning with "fe" which is assigned to the "vnetxx" interface
in the hypervisor.
In the cases where the virtual host doesn't get the dhcp answers the
output of "brctl showmacs <bridge_name>" is:
port no mac addr is local? ageing timer
6 fe:1a:4a:24:27:a0 yes 0.00
This is, the actual virtual host's MAC address is missing from the bridge.
We haven't been able to find a detailed explanation on how the network
internals of oVirt should work but hopefully someone in this list can
point us to the right resource.
Thank you.
Xavier.
10 years
oVirt 3.5 on RHEL 6.6 hyperv enabled breaks Windows VMs
by Charles Gruener
https://bugzilla.redhat.com/show_bug.cgi?id=1110305
This enabled the hv_relaxed flag on all my Windows VMs, causing them to no
longer boot. The same thing would happen if I simply booted from the
Windows install media. I would get a screen with a stop error:
Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000001E
Parameters:
0xFFFFFFFFC0000096
0xFFFFF802C4044EA4
0x00000000000000000
0x00000000000000000
I created a file called
/etc/ovirt-engine/osinfo.conf.d/01-windows.properties that had one line:
os.windows_xp.devices.hyperv.enabled.value = false
I restarted ovirt-engine and now I can start my Windows VMs.
Why does this occur? Is it because I upgraded from 3.4 to 3.5? Is there
something else I'm doing wrong? I would like to not need this workaround.
Thanks.
Charles
10 years
CoreOS can not install on Ovirt
by Punit Dambiwal
Hi,
I try to install the CoreOS (https://coreos.com/) as guest VM under ovirt
3.5 by ISO...but if i choose this CoreOS iso....
[image: Inline image 1]
But if i choose Centos iso...it start the installation without any problem
....i already checked the ISO of CoreOS is perfectly fine...i can install
it with physical machine...but stuck in the OVirt...
Thanks,
Punit
10 years
3.5 install issues: failed to setup ovirtmgmt
by Robert Story
--Sig_/UCS9Qt+.3XGZ4pTqVuU5k2x
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
I'm on my 4th attempt to get a 3.5 hosted-engine set up on CentOS 6.5. I
seem to hit a different snag each time. The first 3 were with the ovirtmgmt
bridge on a tagged VLAN, so I decided to go back to an untagged interface
and see if I had better luck. But this install failed even earlier, when
creating the management bridge:
2014-10-25 12:37:24 INFO otopi.plugins.ovirt_hosted_engine_setup.network.br=
idge bridge._misc:198 Configuring the management bridge
2014-10-25 12:37:25 DEBUG otopi.context context._executeMethod:152 method e=
xception
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _e=
xecuteMethod
method['method']()
File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hoste=
d-engine-setup/network/bridge.py", line 207, in _misc
_setupNetworks(conn, networks, {}, {'connectivityCheck': False})
File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hoste=
d-engine-setup/network/bridge.py", line 225, in _setupNetworks
'message: "%s"' % (networks, code, message))
RuntimeError: Failed to setup networks {'ovirtmgmt': {'nic': 'eth0', 'netma=
sk': '255.255.255.0', 'bootproto': 'none', 'ipaddr': '10.69.79.31'}}. Error=
code: "16" message: "Unexpected exception"
2014-10-25 12:37:25 ERROR otopi.context context._executeMethod:161 Failed t=
o execute stage 'Misc configuration': Failed to setup networks {'ovirtmgmt'=
: {'nic': 'eth0', 'netmask': '255.255.255.0', 'bootproto': 'none', 'ipaddr'=
: '10.69.79.31'}}. Error code: "16" message: "Unexpected exception"
2014-10-25 12:37:25 DEBUG otopi.transaction transaction.abort:131 aborting =
'File transaction for '/etc/ovirt-hosted-engine/firewalld/hosted-console.xm=
l''
2014-10-25 12:37:25 DEBUG otopi.transaction transaction.abort:131 aborting =
'File transaction for '/etc/ovirt-hosted-engine/iptables.example''
2014-10-25 12:37:25 DEBUG otopi.transaction transaction.abort:131 aborting =
'File transaction for '/etc/sysconfig/iptables''
2014-10-25 12:37:25 DEBUG otopi.transaction transaction.abort:131 aborting =
'File transaction for '/etc/ovirt-hosted-engine-ha/broker.conf''
Complete log here:
http://futz.org/users/tmp/ovirt5/ovirt-hosted-engine-setup-20141025123111-g=
51fy0.log
I thought it might because there was still a tagged vlan on the interface,
so I tried to deploy again after removing everything else from eth0, but
still no luck. that log is at
http://futz.org/users/tmp/ovirt5/ovirt-hosted-engine-setup-20141025150830-s=
2byre.log
any hints tips appreciated...
Robert
--=20
Senior Software Engineer @ Parsons
--Sig_/UCS9Qt+.3XGZ4pTqVuU5k2x
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlRL94sACgkQ7/fVLLY1mngq5gCghmZXSHf0Svg0QAp4PGSAHpJL
6IIAmgPh23Hd2KBemHszMgcG9OZgMLB6
=jR+l
-----END PGP SIGNATURE-----
--Sig_/UCS9Qt+.3XGZ4pTqVuU5k2x--
10 years
Host remains in contending for storage pool manager
by Gianluca Cecchi
Hello,
an iSCSI SD went down and it seems it is not able to come up again.
>From an iSCSI point of view all seems ok..
[root@ovnode04 vdsm]# iscsiadm -m session -P 1
Target: iqn.2014-07.local.localdomain:store1
Current Portal: 10.10.1.71:3260,1
Persistent Portal: 10.10.1.71:3260,1
**********
Interface:
**********
Iface Name: default
Iface Transport: tcp
Iface Initiatorname: iqn.1994-05.com.redhat:5d9b31319a8e
Iface IPaddress: 10.10.1.61
Iface HWaddress: <empty>
Iface Netdev: <empty>
SID: 1
iSCSI Connection State: LOGGED IN
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE
[root@ovnode04 vdsm]# multipath -l
1p_iscsi_store1_l dm-2 IET,VIRTUAL-DISK
size=200G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=0 status=active
`- 1:0:0:1 sdb 8:16 active undef running
Access to the lun seems ok:
[root@ovnode04 ~]# time dd if=/dev/mapper/1p_iscsi_store1_l of=/dev/null
bs=1024k count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 9.24202 s, 116 MB/s
real 0m9.247s
user 0m0.002s
sys 0m0.463s
But it continues to remain in contending and never comes to master.
Failed to activate Storage Domain istore1 (Data Center iscsidc) by ovadmin
I only have this host in this cluster.
What to do?
Already tried to restart both engine service on engine host and vdsmd
service on the host.
Any other commands to check anything?
Gianluca
10 years
