[ovirt-users] NFS
Nikolai Sednev
nsednev at redhat.com
Tue Dec 16 13:50:21 UTC 2014
Hi,
Can you check iptables configured correctly, then put to maintenance host, power-cycle the host and after powered up and reachable, activate it in WEBUI?
Thanks in advance.
Best regards,
Nikolai
____________________
Nikolai Sednev
Senior Quality Engineer at Compute team
Red Hat Israel
34 Jerusalem Road,
Ra'anana, Israel 43501
Tel: +972 9 7692043
Mobile: +972 52 7342734
Email: nsednev at redhat.com
IRC: nsednev
----- Original Message -----
From: users-request at ovirt.org
To: users at ovirt.org
Sent: Tuesday, December 16, 2014 3:31:27 PM
Subject: Users Digest, Vol 39, Issue 96
Send Users mailing list submissions to
users at ovirt.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ovirt.org/mailman/listinfo/users
or, via email, send a message with subject or body 'help' to
users-request at ovirt.org
You can reach the person managing the list at
users-owner at ovirt.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Users digest..."
Today's Topics:
1. Re: NFS (Nir Soffer)
2. Re: Problem after update ovirt to 3.5 (Simone Tiraboschi)
3. Re: Problem after update ovirt to 3.5 (Yedidyah Bar David)
4. Re: How to update zanata's source text ? (Alexander Wels)
5. Re: bash: ./autogen.sh: No such file or directory (Nir Soffer)
6. Re: VM disk tab doesn't show storage name after 3.5 upgrade
(Nir Soffer)
7. Re: NFS (Bob Doolittle)
----------------------------------------------------------------------
Message: 1
Date: Tue, 16 Dec 2014 07:45:57 -0500 (EST)
From: Nir Soffer <nsoffer at redhat.com>
To: Koen Vanoppen <vanoppen.koen at gmail.com>
Cc: users at ovirt.org
Subject: Re: [ovirt-users] NFS
Message-ID:
<1775969167.13951943.1418733957101.JavaMail.zimbra at redhat.com>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> From: "Koen Vanoppen" <vanoppen.koen at gmail.com>
> To: users at ovirt.org
> Sent: Tuesday, December 16, 2014 10:00:32 AM
> Subject: [ovirt-users] NFS
>
> Dear all,
>
> We recently added 2 hypervisors to the domain on ovirt, but for some reason
> they can't connect to the nfs share:
> When I manually try to mount the nfs-share ([root at ovirthyp01dev ~]# mount
> -vvv -t nfs -o vers=3,tcp progress:/media/NfsProgress /rhev/data-center/mnt/
Looks like your server does not accept nfs version 3 - does it work
if you remove the vers=3 option?
> progress.brusselsairport.aero \:_media_NfsProgress/)
> :
> mount: external mount: argv[3] = "-v"
> mount: external mount: argv[4] = "-o"
> mount: external mount: argv[5] = "rw,vers=3,tcp"
> mount.nfs: timeout set for Tue Dec 16 08:56:47 2014
> mount.nfs: trying text-based options 'vers=3,tcp,addr=10.110.56.20'
> mount.nfs: prog 100003, trying vers=3, prot=6
> mount.nfs: portmap query failed: RPC: Program not registered
> mount.nfs: requested NFS version or transport protocol is not supported
>
> From vdsm.log:
> Thread-277::ERROR::2014-12-16
> 08:46:32,504::storageServer::211::Storage.StorageServer.MountConnection::(connect)
> Mount failed: (32, ';mount.nfs: requested NFS version or transport protocol
> is not supported\n')
> Traceback (most recent call last):
> File "/usr/share/vdsm/storage/storageServer.py", line 209, in connect
> self._mount.mount(self.options, self._vfsType)
> File "/usr/share/vdsm/storage/mount.py", line 223, in mount
> return self._runcmd(cmd, timeout)
> File "/usr/share/vdsm/storage/mount.py", line 239, in _runcmd
> raise MountError(rc, ";".join((out, err)))
> MountError: (32, ';mount.nfs: requested NFS version or transport protocol is
> not supported\n')
> Thread-277::ERROR::2014-12-16
> 08:46:32,508::hsm::2433::Storage.HSM::(connectStorageServer) Could not
> connect to storageServer
> Traceback (most recent call last):
> File "/usr/share/vdsm/storage/hsm.py", line 2430, in connectStorageServer
> conObj.connect()
> File "/usr/share/vdsm/storage/storageServer.py", line 328, in connect
> return self._mountCon.connect()
> File "/usr/share/vdsm/storage/storageServer.py", line 217, in connect
> raise e
> MountError: (32, ';mount.nfs: requested NFS version or transport protocol is
> not supported\n')
>
> Any ideas? The rest (4 others) didn't have any problems...
4 other servers?
Try to compare the configuration between these servers.
Nir
------------------------------
Message: 2
Date: Tue, 16 Dec 2014 07:48:17 -0500 (EST)
From: Simone Tiraboschi <stirabos at redhat.com>
To: Juan Jose <jj197005 at gmail.com>
Cc: users at ovirt.org
Subject: Re: [ovirt-users] Problem after update ovirt to 3.5
Message-ID:
<1161380684.12062869.1418734097118.JavaMail.zimbra at redhat.com>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> From: "Juan Jose" <jj197005 at gmail.com>
> To: "Yedidyah Bar David" <didi at redhat.com>, sbonazzo at redhat.com
> Cc: users at ovirt.org
> Sent: Tuesday, December 16, 2014 1:03:17 PM
> Subject: Re: [ovirt-users] Problem after update ovirt to 3.5
>
> Hello everybody,
>
> It was the firewall, after upgrade my engine the NFS configuration had
> disappered, I have configured again as Red Hat says and now it works
> properly again.
>
> Many thank again for the indications.
We already had a patch for it [1],
it will released next month with oVirt 3.5.1
[1] http://gerrit.ovirt.org/#/c/32874/
> Juanjo.
>
> On Mon, Dec 15, 2014 at 2:32 PM, Yedidyah Bar David < didi at redhat.com >
> wrote:
>
>
> ----- Original Message -----
> > From: "Juan Jose" < jj197005 at gmail.com >
> > To: users at ovirt.org
> > Sent: Monday, December 15, 2014 3:17:15 PM
> > Subject: [ovirt-users] Problem after update ovirt to 3.5
> >
> > Hello everybody,
> >
> > After upgrade my engine to oVirt 3.5, I have also upgraded one of my hosts
> > to
> > oVirt 3.5. After that it seems that all have gone good aparently.
> >
> > But in some seconds my ISO domain is desconnected and it is impossible to
> > Activate. I'm attaching my engine.log. The below error is showed each time
> > I
> > try to Activate the ISO domain. Before the upgrade it was working without
> > problems:
> >
> > 2014-12-15 13:25:07,607 ERROR
> > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> > (org.ovirt.thread.pool-8-thread-5) [460733dd] Correlation ID: null, Call
> > Stack: null, Custom Event ID: -1, Message: Failed to connect Host host1 to
> > the Storage Domains ISO_DOMAIN.
> > 2014-12-15 13:25:07,608 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
> > (org.ovirt.thread.pool-8-thread-5) [460733dd] FINISH,
> > ConnectStorageServerVDSCommand, return:
> > {81c0a853-715c-4478-a812-6a74808fc482=477}, log id: 3590969e
> > 2014-12-15 13:25:07,615 ERROR
> > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> > (org.ovirt.thread.pool-8-thread-5) [460733dd] Correlation ID: null, Call
> > Stack: null, Custom Event ID: -1, Message: The error message for connection
> > ovirt-engine.siee.local:/var/lib/exports/iso-20140303082312 returned by
> > VDSM
> > was: Problem while trying to mount target
> > 2014-12-15 13:25:07,616 ERROR
> > [org.ovirt.engine.core.bll.storage.NFSStorageHelper]
> > (org.ovirt.thread.pool-8-thread-5) [460733dd] The connection with details
> > ovirt-engine.siee.local:/var/lib/exports/iso-20140303082312 failed because
> > of error code 477 and error message is: problem while trying to mount
> > target
> >
> > If any other information is required, please tell me.
>
> Is the ISO domain on the engine host?
>
> Please check there iptables and /etc/exports, /etc/exports.d.
>
> Please post the setup (upgrade) log, check /var/log/ovirt-engine/setup.
>
> Thanks,
> --
> Didi
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
------------------------------
Message: 3
Date: Tue, 16 Dec 2014 07:52:09 -0500 (EST)
From: Yedidyah Bar David <didi at redhat.com>
To: Juan Jose <jj197005 at gmail.com>
Cc: users at ovirt.org
Subject: Re: [ovirt-users] Problem after update ovirt to 3.5
Message-ID:
<1501161471.29130974.1418734329990.JavaMail.zimbra at redhat.com>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> From: "Juan Jose" <jj197005 at gmail.com>
> To: "Yedidyah Bar David" <didi at redhat.com>, sbonazzo at redhat.com
> Cc: users at ovirt.org
> Sent: Tuesday, December 16, 2014 2:03:17 PM
> Subject: Re: [ovirt-users] Problem after update ovirt to 3.5
>
> Hello everybody,
>
> It was the firewall, after upgrade my engine the NFS configuration had
> disappered, I have configured again as Red Hat says and now it works
> properly again.
>
> Many thank again for the indications.
Sorry I didn't mention it before, this is a known bug [1]. Will be fixed
in 3.5.1.
[1] https://bugzilla.redhat.com/1109326
--
Didi
------------------------------
Message: 4
Date: Tue, 16 Dec 2014 07:52:33 -0500
From: Alexander Wels <awels at redhat.com>
To: plysan <plysab at gmail.com>
Cc: "Users at ovirt.org List" <users at ovirt.org>
Subject: Re: [ovirt-users] How to update zanata's source text ?
Message-ID: <3939744.arHGUUsGyg at awels>
Content-Type: text/plain; charset="us-ascii"
On Tuesday, December 16, 2014 10:35:18 AM plysan wrote:
> 2014-12-15 22:27 GMT+08:00 Einav Cohen <ecohen at redhat.com>:
> > > ----- Original Message -----
> > > From: "Alexander Wels" <awels at redhat.com>
> > > Sent: Monday, December 15, 2014 7:45:41 AM
> > >
> > > On Sunday, December 14, 2014 03:03:56 PM plysan wrote:
> > > > Hi,
> > > >
> > > > When I'm trying to compile ovirt-engine-3.5 branch with pulled zanata
> > > > source files, I get webadmin compilation errors. And the error message
> >
> > lead
> >
> > > > me to the outdated zanata translation
> > > > file: org.ovirt.engine.ui.webadmin.ApplicationMessages
> > > > The file has a source text called "{0} (VLAN {1})", but recent commit
> > > > b068ec755198c27e65f936809104ba5068cd8fd2
> > > > has changed the text to "(VLAN {0})"
> > > >
> > > > So is there a way to update the zanata's source text (text on the
> >
> > left) ?
> >
> > > > It seems that I don't get any options to update it, I can only update
> >
> > the
> >
> > > > target text (text on the right).
> > > >
> > > > thanks.
> > >
> > > The zanata source text is generated from default values from the ovirt
> >
> > source
> >
> > > code. Einav should know more about exactly how that is done. You should
> > > always
> > > match the translation to the source and not the other way around. So I
> >
> > am not
> >
> > > sure why you are trying to change the source.
> >
> > Alexander is correct; the source text cannot and should not be changed
> > directly in Zanata.
> >
> > in order to update the source (English) text in Zanata, it needs to be
> > pushed to Zanata from the source code.
> >
> > generally, we are not updating anything in Zanata for 3.5 anymore, since
> > we are not planning any additional translation cycles for ovirt 3.5;
> > however, since we are planning out-of-cycle possible updates for the
> > German
> > and Italian translation as an exception for 3.5, it *may* also involve
> > pushing the updated source text to Zanata as part of the process, but this
> > will not happen any time soon, to my understanding.
> >
> > I am not sure if you were trying to pull the latest translations from
> > Zanata
> > and then build ovirt-engine-3.5, or simply tried to build ovirt-engine-3.5
> > as is;
> > if you were trying to build ovirt-engine-3.5 as-is and failed, that's bad
> > -
> > we need to fix that ASAP (however, I am pretty sure that we would have
> > been
> > notified about this issue already from jenkins / other people / etc.).
> > I recommend to not attempt pulling the translations from Zanata yourself,
> > as the pull itself is not enough - need to move some files around, run a
> > few
> > clean-up scripts, etc. If you still want to pull the translations
> > yourself,
> > and you are encountering problems as the ones you mentioned above - simply
> > remove/"fix" the problematic translations *locally on the .properties
> > files
> > that you pulled from Zanata - NOT in Zanata itself*.
>
> Thanks for your responses.
>
> If I want to make some translation updates in zh_CN, Is it means that the
> workflow is first modifying ovirt source code translations and then update
> it to zanata ?
> But zanata has a user friendly UI and has features that translator likes.
> So I think first modifying translations in zanata and then update it to the
> source code is better. Just my thoughts :)
>
The flow for some new text is the following:
1. The developer writes some new functionality.
2. The developer writes the *English* default message for that functionality.
This includes a key to be used by the translators.
3. Some process takes those new message(s) and puts the *English* translation
and the key into zanata.
4. The translator sees the key AND the English version in zanata and provides
the localized version in zanata.
5. Some process pulls the translation from zanata and puts it into the source
code (In a properties file).
As you can see by the workflow the translator simply translated the English
version of some message in zanata and that then automatically gets into the
source code without the translator having to do anything besides that. Once
you have made the change in zanata it will eventually end up in the project.
The process in step 5 is not automatic.
Now if you want to change a message in a particular locale and immediately see
it, then you have manually modify the properties file for the locale you are
interested in and compile the project.
> thanks.
>
> > > _______________________________________________
> > > Users mailing list
> > > Users at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
------------------------------
Message: 5
Date: Tue, 16 Dec 2014 08:24:52 -0500 (EST)
From: Nir Soffer <nsoffer at redhat.com>
To: Ilan Hirsfeld <ilan.hirsfeld at gmail.com>
Cc: users <users at ovirt.org>
Subject: Re: [ovirt-users] bash: ./autogen.sh: No such file or
directory
Message-ID:
<595905649.13968762.1418736292641.JavaMail.zimbra at redhat.com>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> From: "Ilan Hirsfeld" <ilan.hirsfeld at gmail.com>
> To: "Yeela Kaplan" <ykaplan at redhat.com>
> Cc: "users" <users at ovirt.org>
> Sent: Monday, December 15, 2014 6:00:47 PM
> Subject: Re: [ovirt-users] bash: ./autogen.sh: No such file or directory
>
> Are you sure???
> Because in instruction is written:
> "Fedora and Red Hat Enterprise Linux 6 users must verify the following
Thanks for reporting this, fixed now.
> packages are installed before attempting to build:"
> As far as I understand I EL7 not EL6. if you still think I have to do the
> requested command line so should I have to do the previous command lines of
> EL6 such as:
> yum install
> http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
> yum install http://danken.fedorapeople.org/python-pep8-1.4.5-2.el6.noarch.rpm
> Am I wrong?
> Regards,
> Ilan.
Nir
------------------------------
Message: 6
Date: Tue, 16 Dec 2014 08:28:27 -0500 (EST)
From: Nir Soffer <nsoffer at redhat.com>
To: Ernest Beinrohr <Ernest.Beinrohr at axonpro.sk>
Cc: users <users at ovirt.org>
Subject: Re: [ovirt-users] VM disk tab doesn't show storage name after
3.5 upgrade
Message-ID:
<964774187.13970271.1418736507786.JavaMail.zimbra at redhat.com>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> From: "Ernest Beinrohr" <Ernest.Beinrohr at axonpro.sk>
> To: "users" <users at ovirt.org>
> Sent: Monday, December 15, 2014 4:01:05 PM
> Subject: [ovirt-users] VM disk tab doesn't show storage name after 3.5 upgrade
>
> Before 3.5 in VM disk tab, there was the name of the storage on which the
> disks resides. After the upgrade to 3.5 this information is missing.
>
>
> PS: as a workaround I have to "edit" the disk to see where it it. I have 7
> storages so this info is important for me.
Sounds like a regression, please open a bug for this.
Nir
------------------------------
Message: 7
Date: Tue, 16 Dec 2014 08:31:23 -0500
From: Bob Doolittle <bob at doolittle.us.com>
To: Koen Vanoppen <vanoppen.koen at gmail.com>, "users at ovirt.org"
<users at ovirt.org>
Subject: Re: [ovirt-users] NFS
Message-ID: <5490342B.6070107 at doolittle.us.com>
Content-Type: text/plain; charset="windows-1252"
95% of the time this is a firewall issue.
As a test, I'd disable your firewall completely and see if that
rectifies it. If so, you can work on proper firewall rules to allow
oVirt to work.
-Bob
On 12/16/2014 03:30 AM, Koen Vanoppen wrote:
> Already installed... :-) and the service nfs and rpcbind are running
>
> 2014-12-16 9:07 GMT+01:00 Karli Sj?berg <karli.sjoberg at slu.se
> <mailto:karli.sjoberg at slu.se>>:
>
> On Tue, 2014-12-16 at 09:00 +0100, Koen Vanoppen wrote:
> > Dear all,
> >
> >
> > We recently added 2 hypervisors to the domain on ovirt, but for some
> > reason they can't connect to the nfs share:
> > When I manually try to mount the nfs-share ([root at ovirthyp01dev ~]#
> > mount -vvv -t nfs -o vers=3,tcp
> > progress:/media/NfsProgress
> /rhev/data-center/mnt/progress.brusselsairport.aero
> <http://progress.brusselsairport.aero>\:_media_NfsProgress/)
> > :
> > mount: external mount: argv[3] = "-v"
> > mount: external mount: argv[4] = "-o"
> > mount: external mount: argv[5] = "rw,vers=3,tcp"
> > mount.nfs: timeout set for Tue Dec 16 08:56:47 2014
> > mount.nfs: trying text-based options 'vers=3,tcp,addr=10.110.56.20'
> > mount.nfs: prog 100003, trying vers=3, prot=6
> > mount.nfs: portmap query failed: RPC: Program not registered
> > mount.nfs: requested NFS version or transport protocol is not
> > supported
> >
> >
> > From vdsm.log:
> > Thread-277::ERROR::2014-12-16
> >
> 08:46:32,504::storageServer::211::Storage.StorageServer.MountConnection::(connect)
> Mount failed: (32, ';mount.nfs: requested NFS version or transport
> protocol is not supported\n')
> > Traceback (most recent call last):
> > File "/usr/share/vdsm/storage/storageServer.py", line 209, in
> > connect
> > self._mount.mount(self.options, self._vfsType)
> > File "/usr/share/vdsm/storage/mount.py", line 223, in mount
> > return self._runcmd(cmd, timeout)
> > File "/usr/share/vdsm/storage/mount.py", line 239, in _runcmd
> > raise MountError(rc, ";".join((out, err)))
> > MountError: (32, ';mount.nfs: requested NFS version or transport
> > protocol is not supported\n')
> > Thread-277::ERROR::2014-12-16
> > 08:46:32,508::hsm::2433::Storage.HSM::(connectStorageServer)
> Could not
> > connect to storageServer
> > Traceback (most recent call last):
> > File "/usr/share/vdsm/storage/hsm.py", line 2430, in
> > connectStorageServer
> > conObj.connect()
> > File "/usr/share/vdsm/storage/storageServer.py", line 328, in
> > connect
> > return self._mountCon.connect()
> > File "/usr/share/vdsm/storage/storageServer.py", line 217, in
> > connect
> > raise e
> > MountError: (32, ';mount.nfs: requested NFS version or transport
> > protocol is not supported\n')
> >
> >
> > Any ideas? The rest (4 others) didn't have any problems...
> >
> >
> > plain text document attachment (ATT00001)
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org <mailto:Users at ovirt.org>
> > http://lists.ovirt.org/mailman/listinfo/users
>
> # yum install -y nfs-utils
>
> ?
>
>
>
> --
>
> Med V?nliga H?lsningar
>
> -------------------------------------------------------------------------------
> Karli Sj?berg
> Swedish University of Agricultural Sciences Box 7079 (Visiting Address
> Kron?sv?gen 8)
> S-750 07 Uppsala, Sweden
> Phone: +46-(0)18-67 15 66 <tel:%2B46-%280%2918-67%2015%2066>
> karli.sjoberg at slu.se <mailto:karli.sjoberg at slu.se>
>
>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20141216/6fbaaec0/attachment.html>
------------------------------
_______________________________________________
Users mailing list
Users at ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
End of Users Digest, Vol 39, Issue 96
*************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20141216/7871413e/attachment-0001.html>
More information about the Users
mailing list