ovirt-imageio-proxy not working after updating SSL certificates with a wildcard cert issued by AlphaSSL (intermediate)
by Lynn Dixon
All,
I recently bought a wildcard certificate for my lab domain (shadowman.dev)
and I replaced all the certs on my RHV4.3 machine per our documentation.
The WebUI presents the certs successfully and without any issues, and
everything seemed to be fine, until I tried to upload a disk image (or an
ISO) to my storage domain. I get this error in the events tab:
https://share.getcloudapp.com/p9uPvegx
[image: image.png]
I also see that the disk is showing up in my storage domain, but its
showing "Paused by System" and I can't do anything with it. I cant even
delete it!
I have tried following this document to fix the issue, but it didn't work:
https://access.redhat.com/solutions/4148361
I am seeing this error pop into my engine.log:
https://pastebin.com/kDLSEq1A
And I see this error in my image-proxy.log:
WARNING 2020-07-24 15:26:34,802 web:137:web:(log_error) ERROR [172.17.0.30]
PUT /tickets/ [403] Error verifying signed ticket: Invalid ovirt ticket
(data='------my_ticket_data-----', reason=Untrusted certificate)
[request=0.002946/1]
Now, when I bought my wildcard, I was given a root certificate for the CA,
as well as a separate intermediate CA certificate from the provider.
Likewise, they gave me a certificate and a private key of course. The root
and intermediate CA's certificates have been added
to /etc/pki/ca-trust/source/anchors/ and I did an update-ca-trust.
I also started experiencing issues with the ovpn network provider at the
same time I replaced the SSL certs, but I disregarded it at the time, but
now I am thinking its related. Any advice on what to look for to fix the
ovirt-imageio-proxy?
Thanks!
*Lynn Dixon* | Red Hat Certified Architect #100-006-188
*Solutions Architect* | NA Commercial
Google Voice: 423-618-1414
Cell/Text: 423-774-3188
Click here to view my Certification Portfolio <http://red.ht/1XMX2Mi>
3 years, 5 months
VM with illegal snapshots
by Giorgio Biacchi
Hi,
due to a bug in our Ovirt integrated backup system now we have some VMs
with snapshots in illegal state.
It seems that there's an inconsistency between the db and the real
status of images on disk.
Let me show an example:
engine=# select
image_guid,parentid,imagestatus,vm_snapshot_id,volume_type,volume_format,active
from images where image_group_id='e34f77cb-54d5-40d0-b539-e0a5fd512d2d';
image_guid | parentid |
imagestatus | vm_snapshot_id | volume_type |
volume_format | active
--------------------------------------+--------------------------------------+-------------+--------------------------------------+-------------+---------------+--------
a107b6c4-842e-4b40-9215-c965431a0c0f |
00000000-0000-0000-0000-000000000000 | 4 |
d19d6ca3-1989-4c67-8ee7-c0c43b3e6d74 | 2 | 4 | f
a4c86a68-9123-454c-b417-1b15038a4bf2 |
a107b6c4-842e-4b40-9215-c965431a0c0f | 1 |
e7a405ee-8fd4-4733-ae9c-5252bf07c9d3 | 2 | 4 | f
f6a61f2e-26bd-4b63-97c6-d66913ce48c5 |
a4c86a68-9123-454c-b417-1b15038a4bf2 | 1 |
9d0958b9-4995-4e11-a027-a32d4bac52e4 | 2 | 4 | t
(3 rows)
[root@host02 ~]# lvs -o+lv_tags |grep e34f77cb-54d5-40d0-b539-e0a5fd512d2d
a107b6c4-842e-4b40-9215-c965431a0c0f
459011cf-ebb6-46ff-831d-8ccfafd82c8a -wi------- 149.50g
IU_e34f77cb-54d5-40d0-b539-e0a5fd512d2d,MD_68,PU_00000000-0000-0000-0000-000000000000
f6a61f2e-26bd-4b63-97c6-d66913ce48c5
459011cf-ebb6-46ff-831d-8ccfafd82c8a -wi------- 10.00g
IU_e34f77cb-54d5-40d0-b539-e0a5fd512d2d,MD_348,PU_a107b6c4-842e-4b40-9215-c965431a0c0f
so image guid a4c86a68-9123-454c-b417-1b15038a4bf2 is not present on
disk, i think that the image was correctly merged but not removed from
the database.
Any suggestion on how to fix the database to reflect the real situation
on disk??
TIA
--
gb
PGP Key: http://pgp.mit.edu/
Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
3 years, 5 months
rhv 4.3.11 but not ovirt 4.3.11
by Gianluca Cecchi
Hello,
I see that a 4.3.11 version is available for downstream RHV but not for
upstream oVirt.
Will it be released for oVirt too?
Are there only security fixes inside or also bug fixes (like the few lines
one related to export as OVA)?
Thanks,
Gianluca
3 years, 5 months
Single Node HCI upgrade procedure from CentOS7/oVirt 4.3 to CentOS8/oVirt 4.4?
by thomas＠hoberg.net
I can hear you saying: "You did understand that single node HCI is just a toy, right?"
For me the primary use of a single node HCI is adding some disaster resilience in small server edge type scenarios, where a three node HCI provides the fault tolerance: 3+1 with a bit of distance, warm or even cold stand-by, potentially manual switch and reduced workload in case disaster strikes.
Of course, another 3nHCI would be better, but who gets that type of budget, right?
What I am trying say: If you want oVirt to gain market share, try to give HCI more love. And while you're at it, try to make expanding from 1nHCI to 3nHCI (and higher counts) a standard operational procedure to allow expanding a disaster stand-by into a production setup, while the original 3nHCI is being rebuilt.
For me low-budget HCI is where oVirt has its biggest competitive advantage against vSan and Nutanix, so please don't treat the HCI/gluster variant like an unwanted child any more.
In the mean-time OVA imports (from 4.3.10 exports) on my 4.4.2 1nHCI fail again, which I'll report separately.
3 years, 5 months
Problem with Cluster-wise BIOS Settings in oVirt 4.4
by Rodrigo G. López
Hi all,
We are running an oVirt 4.4 Hosted Engine as a VM, and after changing
the Cluster's BIOS type from Q35 with Legacy BIOS (the default one after
installation) to Preexistent, the VM fails with the following error:
XML error: The device at PCI address 0000:00:02.0 cannot be plugged into
the PCI controller with index='0'. It requires a controller that accepts
a pcie-root-port.
We need it so that we can run imported VMs from a previous version of
oVirt, namely 4.0.
Applying the BIOS settings individually works but as an attempt to
generalize the settings we decided to apply it to the full cluster.
Tell me if you need more data.
Cheers,
-rodri
3 years, 5 months
The Master data domain can't be activated
by Miguel Angel Costas
Hi all!!
I had a terrible problem with my blade and I lost the 2 nodes. I have installed a new server as a node ( ovirt-node-iso-3.6-0.999.201608311021.el7.centos.iso) but for any reason the data domain don't start. It the same node version.
The ovirt manager is 3.6.7
If I create a new datacenter I can attach a lv from the same lun with the problem..
Someone could help me.. I have been working to solve the problem fron the saturday..
Thanks!
3 years, 5 months
ovirt guest agent ubuntu 16.04.6 LTS
by suporte＠logicworks.pt
What is the best way to install ovirt guest on Ubuntu 16.04.6?
What I did:
# apt-get install ovirt-guest-agent
I changed value in /etc/ovirt-guest-agent.conf to look like:
[virtio]
# device = /dev/virtio-ports/com.redhat.rhevm.vdsm
device = /dev/virtio-ports/ovirt-guest-agent.0
# systemctl start ovirt-guest-agent
Error on the log:
OSError: [Errno 13] Permission denied: '/dev/virtio-ports/ovirt-guest-agent.0
Than I set the owner and group
# chown ovirtagent:ovirtagent /dev/virtio-ports/ovirt-guest-agent.0
Than I was able to start the agent
# systemctl status ovirt-guest-agent
● ovirt-guest-agent.service - oVirt Guest Agent
Loaded: loaded (/lib/systemd/system/ovirt-guest-agent.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2020-10-31 19:50:03 WET; 9min ago
Process: 6531 ExecStartPre=/bin/chown ovirtagent:ovirtagent /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS)
Process: 6527 ExecStartPre=/bin/touch /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS)
Process: 6524 ExecStartPre=/sbin/modprobe virtio_console (code=exited, status=0/SUCCESS)
Main PID: 6537 (python)
Tasks: 3
Memory: 68.7M
CPU: 5.462s
CGroup: /system.slice/ovirt-guest-agent.service
└─6537 /usr/bin/python /usr/share/ovirt-guest-agent/ovirt-guest-agent.py
Oct 31 19:52:05 alfa.acloud.pt python[6537]: [100B blob data]
Oct 31 19:54:06 alfa.acloud.pt python[6537]: [90B blob data]
Oct 31 19:54:06 alfa.acloud.pt python[6537]: [155B blob data]
Oct 31 19:54:06 alfa.acloud.pt python[6537]: [100B blob data]
Oct 31 19:56:06 alfa.acloud.pt python[6537]: [90B blob data]
Oct 31 19:56:07 alfa.acloud.pt python[6537]: [155B blob data]
Oct 31 19:56:07 alfa.acloud.pt python[6537]: [100B blob data]
Oct 31 19:58:07 alfa.acloud.pt python[6537]: [90B blob data]
Oct 31 19:58:08 alfa.acloud.pt python[6537]: [155B blob data]
Oct 31 19:58:08 alfa.acloud.pt python[6537]: [100B blob data]
Everytime I restart the VM I need to set the owner and group
# chown ovirtagent:ovirtagent /dev/virtio-ports/ovirt-guest-agent.0
--
Jose Ferradeira
http://www.logicworks.pt
3 years, 5 months
20+ Fresh Installs Failing in 20+ days [newbie & frustrated]
by info＠worldhostess.com
I have no idea if it is Hardware or Software. It crashed every time after it
starts with the storage setup
Error in ovirt-hosted-engine-setup-ansilble-setup-final_clean [FAILED]
DESTROYED LOCAL STORAGE-POOL
HTTPS --- "certificate invalid"
The system is very unstable and impossible to do anything remotely ONLY
accessible on local terminal.
This is my hardware
SuperMicro X11SSF-M
Intel Xeon E3-1230
16 GB ECC RAM
2 x 1 TB Micron 1300 SSD
Key Features
X11SSM-F specifications
Single socket H4 (LGA 1151) supports IntelR XeonR processor E3-1200 v6/v5,
IntelR 7th/6th Gen. CoreT i3 series,
IntelR CeleronR and IntelR PentiumR
IntelR C236 chipset
Up to 64GB Unbuffered ECC UDIMM DDR4 2400MHz; 4 DIMM slots
Expansion slots:
1 PCI-E 3.0 x8 (in x16),
1 PCI-E 3.0 x8,
2 PCI-E 3.0 x4 (in x8)
Dual GbE LAN with IntelR i210-AT
8 SATA3 (6Gbps) via C236;
RAID 0, 1, 5, 10
I/O: 1 VGA, 2 COM, 2 SuperDOM, and TPM header
5 USB 3.0 (2 rear, 2 via header(s), 1 Type A), 6 USB 2.0 (2 rear, 4 via
header(s))
Integrated IPMI 2.0 and KVM with Dedicated LAN
Yours Sincerely,
Henni
3 years, 5 months
POWER9 (ppc64le) Support on oVirt 4.4.1
by Vinícius Ferrão
Hello, I was using oVirt 4.3.10 with IBM AC922 (POWER9 / ppc64le) without any issues.
Since I’ve moved to 4.4.1 I can’t add the AC922 machine to the engine anymore, it complains with the following error:
The host CPU does not match the Cluster CPU type and is running in degraded mode. It is missing the following CPU flags: model_POWER9, powernv.
Any ideia of what’s may be happening? The engine runs on x86_64, and I was using this way on 4.3.10.
Machine info:
timebase : 512000000
platform : PowerNV
model : 8335-GTH
machine : PowerNV 8335-GTH
firmware : OPAL
MMU : Radix
Thanks,
3 years, 5 months
Select host for image upload
by C Williams
Hello,
I am having problems selecting the host that I want to use for .iso and
other image uploads via the oVirt Web Console. I have 20+ servers of
varying speeds.
Somehow oVirt keeps wanting to select my oldest and slowest system to use
for image uploads.
Please Help !
Thank You !
C Williams
3 years, 5 months
