[ovirt-users] Re: gerrit.ovirt.org upgrade

2022-02-01 Thread Marcin Sobczyk 



On 2/1/22 09:58, Denis Volkov wrote:

Hello Marcin

Sorry for the late reply

I will try checking if that feature can be disabled. Meanwhile I think 
you could use the `comments` url to get the comments directly:
`curl -s -L https://gerrit.ovirt.org/changes/118398/comments|sed 
<https://gerrit.ovirt.org/changes/118398/comments|sed> 1d|jq '.'`
If needed, field `change_message_id` can be used to link message in 
`details` and `comments` URLs


Hi, yeah, I was able to use the /comments endpoint for my purposes,
so we can stick with comment chips (although I still find them really 
weird :) ).


Thanks, Marcin




On Mon, Jan 31, 2022 at 12:32 PM Marcin Sobczyk <mailto:msobc...@redhat.com>> wrote:


Hi,

thanks for handling the upgrade.

With the new version it's not possible anymore to get contents of the
comments which we need for OST gating.

i.e. for this patch:

https://gerrit.ovirt.org/c/ovirt-system-tests/+/118398
<https://gerrit.ovirt.org/c/ovirt-system-tests/+/118398>

if you try:

curl -L https://gerrit.ovirt.org/changes/118398/detail
<https://gerrit.ovirt.org/changes/118398/detail> | \
      sed 1d | \
      jq -r '.messages[]'

you'll see for one of my last comments:

...
"message": "Patch Set 1:\n\n(1 comment)"
...

but there's no "ci ost" string, which is what I actually wrote.

It's probably because of the new "comment chips" feature.
If it's possible and there are no objections could you please try
turning it off?

Regards, Marcin


On 1/28/22 18:48, Denis Volkov wrote:
 > Hello
 >
 > Upgrade to version 3.4.3 is finished. Gerrit is up and running.
 >
 > In case of issues please create ticket in issue tracking system:
 > https://issues.redhat.com/projects/CPDEVOPS/issues
<https://issues.redhat.com/projects/CPDEVOPS/issues>
 > <https://issues.redhat.com/projects/CPDEVOPS/issues
<https://issues.redhat.com/projects/CPDEVOPS/issues>>
 >
 > --
 >
 > Denis Volkov
 >
 >
 >
 > ___
 > Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
 > To unsubscribe send an email to users-le...@ovirt.org
<mailto:users-le...@ovirt.org>
 > Privacy Statement: https://www.ovirt.org/privacy-policy.html
<https://www.ovirt.org/privacy-policy.html>
 > oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
<https://www.ovirt.org/community/about/community-guidelines/>
 > List Archives:

https://lists.ovirt.org/archives/list/users@ovirt.org/message/I676ITKOHKLH4Q7CMRGVSYHYYTPKKHXA/

<https://lists.ovirt.org/archives/list/users@ovirt.org/message/I676ITKOHKLH4Q7CMRGVSYHYYTPKKHXA/>



--

Denis Volkov

Red Hat <https://www.redhat.com>

<https://www.redhat.com>


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4QQKN27UYE3B3H2NDWIRTZYAZBTIGG4X/

[ovirt-users] Re: gerrit.ovirt.org upgrade

2022-01-31 Thread Marcin Sobczyk 

Hi,

thanks for handling the upgrade.

With the new version it's not possible anymore to get contents of the 
comments which we need for OST gating.


i.e. for this patch:

https://gerrit.ovirt.org/c/ovirt-system-tests/+/118398

if you try:

curl -L https://gerrit.ovirt.org/changes/118398/detail | \
sed 1d | \
jq -r '.messages[]'

you'll see for one of my last comments:

...
"message": "Patch Set 1:\n\n(1 comment)"
...

but there's no "ci ost" string, which is what I actually wrote.

It's probably because of the new "comment chips" feature.
If it's possible and there are no objections could you please try 
turning it off?


Regards, Marcin


On 1/28/22 18:48, Denis Volkov wrote:

Hello

Upgrade to version 3.4.3 is finished. Gerrit is up and running.

In case of issues please create ticket in issue tracking system: 
https://issues.redhat.com/projects/CPDEVOPS/issues 



--

Denis Volkov



___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/I676ITKOHKLH4Q7CMRGVSYHYYTPKKHXA/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/U4RFPFAGCTHEN4Y7HD4LF5ADPEWHJYU4/

[ovirt-users] Re: upgrading to 4.4.6 with Rocky Linux 8

2021-07-13 Thread Marcin Sobczyk 



On 7/12/21 2:11 AM, Nir Soffer wrote:

On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic  wrote:

It was a fresh install of 2 VMs on top of VirtualBox with Rocky fully updated 
on both prior to oVirt installation. I installed it yesterday and followed the 
usual way of installing it: 
https://www.ovirt.org/download/alternate_downloads.html.

Here are the oVirt packages that are installed on the hypervisor:

Unfortunately vdsm (the core package for ovirt host) does not
have ovirt-prefix. Which version do you have?
...

ovirt-imageio-client-2.2.0-1.el8.x86_64

This package requires qemu-img >= 5.2.0
Maybe the requirement is broken (missing epoch).

As you quoted, the requirement states:

%if 0%{?rhel} >= 8
%if 0%{?centos}


Rocky linux probably doesn't have these macros.
OTOH 'ovirt-host' package requires plain 'libvirt',
no version limitations, and that probably sucks in "any 'qemu-kvm' 
possible".


Regards, Marcin



What does "qemu-img --version" tell?

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FGKGSVRMFVED3HK4KGFL6JZRV574YMKW/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LDCXTAYEKN3L7LXYKYAP2BYQ3QITJ6PA/

[ovirt-users] Re: 4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem

2020-05-22 Thread Marcin Sobczyk 

Hi,

On 5/22/20 7:06 AM, Stephen Panicho wrote:
Hi all! I'm using Cockpit to perform an HCI install, and it fails at 
the hosted engine deploy. Libvirtd can't restart because of a missing 
/etc/pki/CA/cacert.pem file.


The log (tasks seemingly from 
/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/initial_clean.yml):

[ INFO ] TASK [ovirt.hosted_engine_setup : Stop libvirt service]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Drop vdsm config statements]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial abrt config 
files]

[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Restart abrtd service]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Drop libvirt sasl2 
configuration by vdsm]

[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Stop and disable services]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial libvirt 
default network configuration]

[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Start libvirt]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": 
"Unable to start service libvirtd: Job for libvirtd.service failed 
because the control process exited with error code.\nSee \"systemctl 
status libvirtd.service\" and \"journalctl -xe\" for details.\n"}


journalctl -u libvirtd:
May 22 04:33:25 node1 libvirtd[26392]: libvirt version: 5.6.0, 
package: 10.el8 (CBS mailto:c...@centos.org>>, 
2020-02-27-01:09:46, )

May 22 04:33:25 node1 libvirtd[26392]: hostname: node1
May 22 04:33:25 node1 libvirtd[26392]: Cannot read CA certificate 
'/etc/pki/CA/cacert.pem': No such file or directory
May 22 04:33:25 node1 systemd[1]: libvirtd.service: Main process 
exited, code=exited, status=6/NOTCONFIGURED
May 22 04:33:25 node1 systemd[1]: libvirtd.service: Failed with result 
'exit-code'.

May 22 04:33:25 node1 systemd[1]: Failed to start Virtualization daemon.

Can you please share journalctl logs for vdsmd and supervdsmd?

Regards, Marcin



From a fresh CentOS 8.1 minimal install, I've installed the following:
- The 4.4 repo
- cockpit
- ovirt-cockpit-dashboard
- vdsm-gluster (providing glusterfs-server and allowing the Gluster 
Wizard to complete)

- gluster-ansible-roles (only on the bootstrap host)

I'm not exactly sure what that initial bit of the playbook does. 
Comparing the bootstrap node with another that has yet to be touched, 
both /etc/libvirt/libvirtd.conf and /etc/sysconfig/libvirtd are the 
same on both hosts. Yet the bootstrap host can no longer start 
libvirtd while the other host can. Neither host has the 
/etc/pki/CA/cacert.pem file.


Please let me know if I can provide any more information. Thanks!

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XNW4HWUQUTN44VMATT4B6ARSEYVURDP7/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/J7UI5QALFSDGTVKLGIRB24WH3WR7XFDN/

[ovirt-users] Re: 4.3.0 rc2 cannot mount glusterfs volumes on ovirt node ng

2019-01-30 Thread Marcin Sobczyk 

Hi,

I will probably be able to look into hanged supervdsmd issue only next week.
I'll reply as soon as I have some insight.

Regards, Marcin

On 1/29/19 12:19 PM, Jorick Astrego wrote:


Hi,

I know people are busy but do we have any progress on this, I removed 
the OVS cluster and recreated it with bridge networking.


But I'm still stuck on the "failed to fetch volume file" and am unable 
to activate the hosts to continue testing...


Anything else I can try to debug? The storage network is ip based 
without dns.


Regards, Jorick

On 1/25/19 3:53 PM, Jorick Astrego wrote:



On 1/25/19 3:26 PM, Sahina Bose wrote:



On Fri, Jan 25, 2019 at 7:36 PM Jorick Astrego > wrote:




The mount failure is probably related to glusterfs. There are
glusterfs logs on the host that
can give more info on this error.

Oh duh, sorry forgot to check :-&

"failed to fetch volume file"


[2019-01-25 14:02:45.067440] I 
[glusterfsd-mgmt.c:2424:mgmt_rpc_notify] 0-glusterfsd-mgmt: 
disconnected from remote-host: *.*.*.*


Are you able to access this host, and the gluster ports open?
Anything in the glusterd.log of the gluster server?

Adding Sanju to help



From the host:

Telnet *.*.*.14 24007
Trying *.*.*.14...
Connected to *.*.*.14.
Escape character is '^]'.

glusterd.log on *.*.*.14:

Chain INPUT (policy ACCEPT)
target prot opt source   destination
ACCEPT all  --  anywhere anywhere state
RELATED,ESTABLISHED
ACCEPT icmp --  anywhere anywhere
ACCEPT all  --  anywhere anywhere
ACCEPT tcp  --  anywhere anywhere tcp dpt:54321
ACCEPT tcp  --  anywhere anywhere tcp dpt:54322
ACCEPT tcp  --  anywhere anywhere tcp dpt:sunrpc
ACCEPT udp  --  anywhere anywhere udp dpt:sunrpc
ACCEPT tcp  --  anywhere anywhere tcp dpt:ssh
ACCEPT udp  --  anywhere anywhere udp dpt:snmp
ACCEPT tcp  --  anywhere anywhere tcp dpt:websm
ACCEPT tcp  --  anywhere anywhere tcp dpt:24007
ACCEPT tcp  --  anywhere anywhere tcp dpt:webcache
ACCEPT tcp  --  anywhere anywhere tcp dpt:38465
ACCEPT tcp  --  anywhere anywhere tcp dpt:38466
ACCEPT tcp  --  anywhere anywhere tcp dpt:38467
ACCEPT tcp  --  anywhere anywhere tcp dpt:nfs
ACCEPT tcp  --  anywhere anywhere tcp dpt:38469
ACCEPT tcp  --  anywhere anywhere tcp dpt:5666
ACCEPT tcp  --  anywhere anywhere tcp dpt:39543
ACCEPT tcp  --  anywhere anywhere tcp dpt:55863
ACCEPT tcp  --  anywhere anywhere tcp dpt:38468
ACCEPT udp  --  anywhere anywhere udp dpt:963
ACCEPT tcp  --  anywhere anywhere tcp dpt:965
ACCEPT tcp  --  anywhere anywhere tcp dpt:ctdb
ACCEPT tcp  --  anywhere anywhere tcp dpt:netbios-ssn
ACCEPT tcp  --  anywhere anywhere tcp
dpt:microsoft-ds
ACCEPT tcp  --  anywhere anywhere tcp
dpts:24009:24108
ACCEPT tcp  --  anywhere anywhere tcp
dpts:49152:49251
ACCEPT tcp  --  anywhere anywhere tcp
dpts:49217:49316
ACCEPT tcp  --  anywhere anywhere tcp
dpt:zabbix-agent /* Zabbix agent */
REJECT all  --  anywhere anywhere reject-with
icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target prot opt source   destination
REJECT all  --  anywhere anywhere PHYSDEV match !
--physdev-is-bridged reject-with icmp-host-prohibited

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination

And in the glusterd.log has nothing else but:

[2019-01-25 11:02:32.617694] I [MSGID: 106499]
[glusterd-handler.c:4303:__glusterd_handle_status_volume]
0-management: Received status volume req for volume ssd6
[2019-01-25 11:02:32.623892] I [MSGID: 106499]
[glusterd-handler.c:4303:__glusterd_handle_status_volume]
0-management: Received status volume req for volume ssd9
[2019-01-25 11:03:31.847006] I [MSGID: 106488]
[glusterd-handler.c:1548:__glusterd_handle_cli_get_volume]
0-management: Received get vol req
[2019-01-25 11:04:33.023685] I [MSGID: 106499]
[glusterd-handler.c:4303:__glusterd_handle_status_volume]
0-management: Received status volume req for volume hdd2
[2019-01-25 11:04:33.030549] I [MSGID: 106499]
[glusterd-handler.c:4303:__glusterd_handle_status_volume]
0-management: Received status volume req for volume sdd8
[2019-01-25 11:04:33.037024] I [MSGID: 106499]
[glusterd-handler.c:4303:__glusterd_handle_status_volume]
0-management: Received status volume

[ovirt-users] Re: Ovirt 4.3 / New Install / NFS (broken)

2019-01-14 Thread Marcin Sobczyk 

On 1/13/19 7:14 PM, Nir Soffer wrote:
On Sun, Jan 13, 2019 at 4:35 PM Gianluca Cecchi 
mailto:gianluca.cec...@gmail.com>> wrote:




On Sun, Jan 13, 2019 at 12:38 PM Gianluca Cecchi
mailto:gianluca.cec...@gmail.com>> wrote:

On Sun, Jan 13, 2019 at 10:20 AM Shani Leviim
mailto:slev...@redhat.com>> wrote:

Hi Devin,
This one was solved in the following patch:
https://gerrit.ovirt.org/#/c/96746/

*Regards,
*
*Shani Leviim
*


On Sun, Jan 13, 2019 at 10:13 AM Devin Acosta
mailto:linuxguru...@gmail.com>>
wrote:

I installed the latest 4.3 release candidate and tried
to add an NFS mount to the Data Center, and it errors
in the GUI with “Error while executing action New NFS
Storage Domain: Invalid parameter”, then in the
vdsm.log I see it is passing “block_size=None”. Does
this regardless if NFS v3 or v4.

InvalidParameterException: Invalid parameter:
'block_size=None'


Hi,
could be the same I have in this thread during single host HCI
install:
https://www.mail-archive.com/users@ovirt.org/msg52875.html


It looks the same issue.

This was was broken for few days, and was fixed last week.


?

Gianluca


I have not understood where to find the to-be-patched file
vdsm-api.yml
It seems it is not in engine and host...


The yaml file is the source - on the host the file is stored in a 
binary format

that is 100 times faster to load.

Marcin, do we have an easy way to update the yaml on a host without 
building

vdsm from source?

Nir

Hi,

There are no yamls on the host but you can replace the binaries 
describing the API:


 * download 'vdsm-api' rpm that was built from the aforementioned
   patch:
   
https://jenkins.ovirt.org/job/vdsm_standard-on-merge/184/artifact/build-artifacts.el7.x86_64/vdsm-api-4.30.5-2.gitf824ec2.el7.noarch.rpm
 * copy 'usr/lib/python2.7/site-packages/vdsm/rpc/vdsm-api.pickle' from
   the rpm to the same location on your host

Marcin




___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Q55FWT3I2PXTETUXQV6NRRQIHOEAR5LV/