[ovirt-users] Re: Unable to attach ISO domain to Datacenter
I was finally able to attach ISO Domain to Datacenter after moving all Datacenter's Storage Domains and Hosts to MAINTAINANCE except on the Host where I was creating the ISO Domain. It looks like a bug on oVirt that didn't allow to simply add a ISO Domain after all other hosts and Data Domains has been previously added to my Datacenter. However, I'm glad I was finally able to attach the ISO Domain to my Datacenter. Thanks for everyone assistance ___ 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/RMUKB7HPIFXVE7DVETTTISUUUWZ7LP4G/
[ovirt-users] Re: Unable to attach ISO domain to Datacenter
Hello. I tried to reinstall my whole environment using oficial oVirt ISO image and the same problem occurs. I also tried to give full access to vdsm user in sudoers file and the results are exactly the same. This is the error on showed on oVirt Manager: VDSM command AttachStorageDomainVDS failed: Cannot obtain lock: u"id=e65b4f0f-faa1-4cdc-9d2a-ab4fccfec0b0, rc=1, out=[], err=['setsid: failed to execute /usr/bin/ionice: Permission denied']" In other hand, the node server's vdsm.log file shows no errors. The engine.log still shows the same errors as my previous posts with logs. I don't know what else can I do. Please help. Thanks, Ivan ___ 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/J6ZI7A7QTDZMVVOGZLNMPQGVC2A3EJ5R/
[ovirt-users] Re: Unable to attach ISO domain to Datacenter
I've tried to commenting out this line on /etc/pam.d/password-auth: authrequisite pam_succeed_if.so uid >= 1000 quiet_success However, although it has stopped complaining about "requirement uid >= 1000 not met by user vdsm" on /var/log/secure , the error trying to attach ISO Domain to Datacenter still persists, showing the same error message, so it looks that this was not the cause of the problem :-( Going back to stage zero. ___ 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/TTD4PH2FIUK23427RSEWYQOGJSM7C7KB/
[ovirt-users] Re: Unable to attach ISO domain to Datacenter
> On Tuesday, December 3, 2019, Ivan Apolonio > > This line shuts logging, worth to comment it out during check. Plus, do you > have an #includedir setting in your /etc/sudoers file? > > The vdsm.log snippet seems later than the error in the engine.log, could > you provide one covering the failing attempt? Hello, Amit. It looks that commenting out that last line (Defaults:vdsm !syslog) did the trick to help identify the problem. According to /var/log/secure log file, vdsm uid is being blocked to sudo due to pam requirements: Dec 4 10:53:36 Rosinha sudo: pam_unix(sudo:auth): authentication failure; logname=root uid=36 euid=0 tty=/dev/pts/0 ruser=vdsm rhost= user=vdsm Dec 4 10:53:36 Rosinha sudo: pam_succeed_if(sudo:auth): requirement "uid >= 1000" not met by user "vdsm" Dec 4 10:58:38 Rosinha sudo: pam_unix(sudo:auth): conversation failed Dec 4 10:58:38 Rosinha sudo: pam_unix(sudo:auth): auth could not identify password for [vdsm] Dec 4 10:58:38 Rosinha sudo: pam_succeed_if(sudo:auth): requirement "uid >= 1000" not met by user "vdsm" This "uid >= 1000" requirement is the CentOS 7 default. What is the best way to work around it? I'm asking that because if I just comment this rule on pam configuration files, it is going to allow other system users to sudo, which would lead to security issues. Thanks, Ivan ___ 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/7NKVMVBQ5Z746JRV5U6UCVEW4SW2UFOS/
[ovirt-users] Re: Unable to attach ISO domain to Datacenter
Hello Amit. Thanks for you reply. This is the content of /etc/sudoers.d/50_vdsm file (it's the default generated by ovirt install): Cmnd_Alias VDSM_LIFECYCLE = \ /usr/sbin/dmidecode -s system-uuid Cmnd_Alias VDSM_STORAGE = \ /usr/sbin/fsck -p *, \ /usr/sbin/tune2fs -j *, \ /usr/sbin/mkfs -q -j *, \ /usr/bin/kill, \ /usr/bin/chown vdsm\:qemu *, \ /usr/bin/chown vdsm\:kvm *, \ /usr/sbin/iscsiadm *, \ /usr/sbin/lvm, \ /usr/bin/setsid /usr/bin/ionice -c ? -n ? /usr/bin/su vdsm -s /bin/sh -c /usr/libexec/vdsm/spmprotect.sh*, \ /usr/sbin/service vdsmd *, \ /usr/sbin/reboot -f vdsm ALL=(ALL) NOPASSWD: VDSM_LIFECYCLE, VDSM_STORAGE Defaults:vdsm !requiretty Defaults:vdsm !syslog I was pretty curious about the format of the line "/usr/bin/setsid /usr/bin/ionice -c ? -n ? /usr/bin/su vdsm -s /bin/sh -c /usr/libexec/vdsm/spmprotect.sh*", but looking at source code (https://github.com/oVirt/vdsm/blob/master/static/etc/sudoers.d/50_vdsm.in) it looks to be just like that. If I need to change anything on this file, it looks that there's some bug on vdsm package. In other hand, I watched the /var/log/secure file while I was trying to attach a Datacenter to ISO Domain and it didn't showed anything new, meaning that the referred "ionice" command was not executed via sudo by vdsm. If it's is true, that could explain the "permission denied" error. About the NFS export, it is exactly the same as parameters as Data Domain exports (which works perfectly): exportfs -v /storage/vm 172.31.17.0/24(sync,wdelay,hide,no_subtree_check,sec=sys,rw,secure,root_squash,no_all_squash) /storage/vm 172.31.48.0/24(sync,wdelay,hide,no_subtree_check,sec=sys,rw,secure,root_squash,no_all_squash) /storage/iso (sync,wdelay,hide,no_subtree_check,sec=sys,rw,secure,root_squash,no_all_squash) What else do I need to check? Thanks Ivan ___ 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/BPEKZ4JEDMLLMDXCJWX5IOIKYIU5NRVF/
[ovirt-users] Re: Unable to attach ISO domain to Datacenter
Any one? ___ 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/YZNU62VK4SIHWY44Y3R75UNWTUTI4NQH/
[ovirt-users] Re: Unable to attach ISO domain to Datacenter
> Can you edit the VM ?If yes, remove the DVD and try again. Sorry if I was not clear enough, but I NEED to boot from CD, but as I've described on the first post of this topic, I'm getting error when trying to attach an ISO Domain to a Datacenter. ___ 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/2TJBYIDFQXUB2VDDB6X4QNLGJNVU2UQM/
[ovirt-users] Re: Unable to attach ISO domain to Datacenter
I've posted the logs asked. Do you have any clue about what's wrong? I tried Downloading the official Ovirt-Node ISO and the same thing happens :-( ___ 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/PLMU3PTZSTMIM3D7WRPN4FV5SOU5D4BJ/
[ovirt-users] Re: Unable to attach ISO domain to Datacenter
I'm unable to start VMs via command line without ISO domain. Please Help. = ERROR status: 409 reason: Conflict detail: Cannot run VM with attached CD without an active ISO domain. Alternatives: - Attach an ISO Domain (to enable CD operations). - Change the boot sequence, using the Edit VM command (Boot Sub-Tab). - Select a different boot device (using the 'Run Once' command). ___ 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/35EN6KIFPBM5I3EL5WEAPXQ4TGFXY22O/
[ovirt-users] Re: Unable to attach ISO domain to Datacenter
Further system information: oVirt installed packets: $ rpm -qa '*ovirt*' ovirt-engine-restapi-4.3.6.7-1.el7.noarch ovirt-web-ui-1.6.0-1.el7.noarch ovirt-vmconsole-proxy-1.0.7-2.el7.noarch python2-ovirt-host-deploy-1.8.4-1.el7.noarch ovirt-host-4.3.5-1.el7.x86_64 ovirt-engine-dwh-4.3.6-1.el7.noarch cockpit-machines-ovirt-195.1-1.el7.centos.0.1.noarch ovirt-ansible-repositories-1.1.5-1.el7.noarch ovirt-ansible-roles-1.1.7-1.el7.noarch python2-ovirt-engine-lib-4.3.7.2-1.el7.noarch ovirt-provider-ovn-1.2.27-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.3.7.2-1.el7.noarch ovirt-engine-setup-4.3.7.2-1.el7.noarch ovirt-ansible-cluster-upgrade-1.1.14-1.el7.noarch ovirt-cockpit-sso-0.1.1-1.el7.noarch ovirt-engine-ui-extensions-1.0.10-1.el7.noarch ovirt-engine-4.3.6.7-1.el7.noarch ovirt-hosted-engine-setup-2.3.12-1.el7.noarch ovirt-ansible-vm-infra-1.1.22-1.el7.noarch ovirt-engine-setup-plugin-cinderlib-4.3.7.2-1.el7.noarch python-ovirt-engine-sdk4-4.3.2-2.el7.x86_64 ovirt-release43-4.3.7-1.el7.noarch python2-ovirt-setup-lib-1.2.0-1.el7.noarch ovirt-engine-wildfly-overlay-17.0.1-1.el7.noarch ovirt-imageio-proxy-1.5.2-0.el7.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch ovirt-vmconsole-1.0.7-2.el7.noarch ovirt-engine-wildfly-17.0.1-1.el7.x86_64 ovirt-ansible-image-template-1.1.12-1.el7.noarch ovirt-ansible-manageiq-1.1.14-1.el7.noarch ovirt-engine-tools-4.3.6.7-1.el7.noarch ovirt-engine-dbscripts-4.3.6.7-1.el7.noarch cockpit-ovirt-dashboard-0.13.8-1.el7.noarch ovirt-engine-extension-aaa-ldap-1.3.10-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.3.7.2-1.el7.noarch ovirt-host-deploy-java-1.8.4-1.el7.noarch ovirt-hosted-engine-ha-2.3.6-1.el7.noarch ovirt-engine-metrics-1.3.5.1-1.el7.noarch ovirt-engine-extensions-api-impl-4.3.7.2-1.el7.noarch ovirt-engine-dwh-setup-4.3.6-1.el7.noarch ovirt-engine-api-explorer-0.0.5-1.el7.noarch ovirt-host-deploy-common-1.8.4-1.el7.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.7.2-1.el7.noarch ovirt-engine-vmconsole-proxy-helper-4.3.7.2-1.el7.noarch ovirt-engine-tools-backup-4.3.6.7-1.el7.noarch ovirt-ansible-engine-setup-1.1.9-1.el7.noarch ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch ovirt-engine-webadmin-portal-4.3.6.7-1.el7.noarch ovirt-imageio-daemon-1.5.2-0.el7.noarch ovirt-vmconsole-host-1.0.7-2.el7.noarch ovirt-engine-setup-plugin-websocket-proxy-4.3.7.2-1.el7.noarch ovirt-host-dependencies-4.3.5-1.el7.x86_64 ovirt-ansible-hosted-engine-setup-1.0.32-1.el7.noarch ovirt-imageio-proxy-setup-1.5.2-0.el7.noarch ovirt-iso-uploader-4.3.2-1.el7.noarch ovirt-ansible-disaster-recovery-1.2.0-1.el7.noarch ovirt-engine-extension-aaa-jdbc-1.1.10-1.el7.noarch ovirt-engine-backend-4.3.6.7-1.el7.noarch ovirt-engine-extension-aaa-ldap-setup-1.3.10-1.el7.noarch ovirt-imageio-common-1.5.2-0.el7.x86_64 ovirt-engine-cli-3.6.9.2-1.el7.noarch ovirt-provider-ovn-driver-1.2.27-1.el7.noarch ovirt-engine-setup-base-4.3.7.2-1.el7.noarch ovirt-engine-websocket-proxy-4.3.7.2-1.el7.noarch ovirt-ansible-infra-1.1.13-1.el7.noarch Kernel Version: $ uname -r 3.10.0-1062.4.3.el7.x86_64 RedHat Version: $ cat /etc/redhat-release CentOS Linux release 7.7.1908 (Core) ___ 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/3NEMXEWZYBGBZK4PK7FVIKCCUWQGZGPV/
