Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a)
Excellent. Confirmed, this fixes the bug and fails with a more descriptive
error.
Steve Atkinson
Director, Network Ops
Telvue Corporation
satkin...@telvue.com
O: 800 885 8886 x240
C: 856 938 9125
On Thu, Jan 1, 2015 at 3:52 AM, Yedidyah Bar David wrote:
> - Original Message -
> > From: "Yedidyah Bar David"
> > To: "Steve Atkinson"
> > Cc: users@ovirt.org
> > Sent: Wednesday, December 31, 2014 11:59:57 PM
> > Subject: Re: [ovirt-users] engine-iso-uploader unexpected behaviour
> (steve a)
> >
> > - Original Message -
> > > From: "Steve Atkinson"
> > > To: "Yedidyah Bar David"
> > > Cc: users@ovirt.org
> > > Sent: Wednesday, December 31, 2014 11:18:39 PM
> > > Subject: Re: [ovirt-users] engine-iso-uploader unexpected behaviour
> (steve
> > > a)
> > >
> > > in our case our nas doesn't support scp but that no fault of the the
> > > manager.
> > >
> > > I was mentioning more specifically that the --nfs-server method seemed
> to
> > > throw an error on an undefined attribute 'domaintype' that is not
> something
> > > that can be supplied in the config file or passed as an argument. the
> out
> > > put from the the debug is further up in my first email.
> >
> > Sorry.
> >
> > You wrote:
> > > Alternatively, using engine-iso-uploader --nfs-server=[path] upload
> [iso]
> > > --verbose returns the following error:
> > >
> > > ERROR: local variable 'domain_type' referenced before assignment
> > > INFO: Use the -h option to see usage.
> > > DEBUG: Configuration:
> > > DEBUG: command: upload
> > > DEBUG: Traceback (most recent call last):
> > > DEBUG: File "/usr/bin/engine-iso-uploader", line 1440, in
> > > DEBUG: isoup = ISOUploader(conf)
> > > DEBUG: File "/usr/bin/engine-iso-uploader", line 455, in __init__
> > > DEBUG: self.upload_to_storage_domain()
> > > DEBUG: File "/usr/bin/engine-iso-uploader", line 1089, in
> > > upload_to_storage_domain
> > > DEBUG: elif domain_type in ('localfs', ):
> > > DEBUG: UnboundLocalError: local variable 'domain_type' referenced
> before
> > > assignment
> >
> > That's indeed a bug. Now pushed a one-line fix [1]. If you can, please
> > try and it report. Thanks!
> >
> > [1] http://gerrit.ovirt.org/36499
>
> It will fail for you, though - it simply tries to mount directly, and as
> you
> said, your engine can't access your storage network. But hopefully fail
> with
> some nicer error message.
>
> Best,
> --
> Didi
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a)
- Original Message -
> From: "Yedidyah Bar David"
> To: "Steve Atkinson"
> Cc: users@ovirt.org
> Sent: Wednesday, December 31, 2014 11:59:57 PM
> Subject: Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a)
>
> - Original Message -
> > From: "Steve Atkinson"
> > To: "Yedidyah Bar David"
> > Cc: users@ovirt.org
> > Sent: Wednesday, December 31, 2014 11:18:39 PM
> > Subject: Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve
> > a)
> >
> > in our case our nas doesn't support scp but that no fault of the the
> > manager.
> >
> > I was mentioning more specifically that the --nfs-server method seemed to
> > throw an error on an undefined attribute 'domaintype' that is not something
> > that can be supplied in the config file or passed as an argument. the out
> > put from the the debug is further up in my first email.
>
> Sorry.
>
> You wrote:
> > Alternatively, using engine-iso-uploader --nfs-server=[path] upload [iso]
> > --verbose returns the following error:
> >
> > ERROR: local variable 'domain_type' referenced before assignment
> > INFO: Use the -h option to see usage.
> > DEBUG: Configuration:
> > DEBUG: command: upload
> > DEBUG: Traceback (most recent call last):
> > DEBUG: File "/usr/bin/engine-iso-uploader", line 1440, in
> > DEBUG: isoup = ISOUploader(conf)
> > DEBUG: File "/usr/bin/engine-iso-uploader", line 455, in __init__
> > DEBUG: self.upload_to_storage_domain()
> > DEBUG: File "/usr/bin/engine-iso-uploader", line 1089, in
> > upload_to_storage_domain
> > DEBUG: elif domain_type in ('localfs', ):
> > DEBUG: UnboundLocalError: local variable 'domain_type' referenced before
> > assignment
>
> That's indeed a bug. Now pushed a one-line fix [1]. If you can, please
> try and it report. Thanks!
>
> [1] http://gerrit.ovirt.org/36499
It will fail for you, though - it simply tries to mount directly, and as you
said, your engine can't access your storage network. But hopefully fail with
some nicer error message.
Best,
--
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a)
- Original Message -
> From: "Steve Atkinson"
> To: "Yedidyah Bar David"
> Cc: users@ovirt.org
> Sent: Wednesday, December 31, 2014 11:18:39 PM
> Subject: Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a)
>
> in our case our nas doesn't support scp but that no fault of the the
> manager.
>
> I was mentioning more specifically that the --nfs-server method seemed to
> throw an error on an undefined attribute 'domaintype' that is not something
> that can be supplied in the config file or passed as an argument. the out
> put from the the debug is further up in my first email.
Sorry.
You wrote:
> Alternatively, using engine-iso-uploader --nfs-server=[path] upload [iso]
> --verbose returns the following error:
>
> ERROR: local variable 'domain_type' referenced before assignment
> INFO: Use the -h option to see usage.
> DEBUG: Configuration:
> DEBUG: command: upload
> DEBUG: Traceback (most recent call last):
> DEBUG: File "/usr/bin/engine-iso-uploader", line 1440, in
> DEBUG: isoup = ISOUploader(conf)
> DEBUG: File "/usr/bin/engine-iso-uploader", line 455, in __init__
> DEBUG: self.upload_to_storage_domain()
> DEBUG: File "/usr/bin/engine-iso-uploader", line 1089, in
> upload_to_storage_domain
> DEBUG: elif domain_type in ('localfs', ):
> DEBUG: UnboundLocalError: local variable 'domain_type' referenced before
> assignment
That's indeed a bug. Now pushed a one-line fix [1]. If you can, please
try and it report. Thanks!
[1] http://gerrit.ovirt.org/36499
Feel free to also open a bz for inclusion in some version earlier than 3.6
(our current master branch).
>
> you are right though. probably not worth it since the best solution would
> be a gui implementation.
That's not what I meant - a gui is obviously more comfortable for casual
use, but for batch/scripting etc you want a command line tool. But
hopefully our implementation for the gui uploader will be first in the
rest api, then in the gui. The rest api will be useful also for scripting -
either directly or by reimplementing the current tool with it.
Thanks and best regards,
--
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a)
in our case our nas doesn't support scp but that no fault of the the manager. I was mentioning more specifically that the --nfs-server method seemed to throw an error on an undefined attribute 'domaintype' that is not something that can be supplied in the config file or passed as an argument. the out put from the the debug is further up in my first email. you are right though. probably not worth it since the best solution would be a gui implementation. thanks again. On Dec 31, 2014 4:10 PM, "Yedidyah Bar David" wrote: > - Original Message - > > From: "Steve Atkinson" > > To: "Yedidyah Bar David" > > Cc: users@ovirt.org > > Sent: Wednesday, December 31, 2014 10:43:23 PM > > Subject: Re: [ovirt-users] engine-iso-uploader unexpected behaviour > (steve a) > > > > Ok well thanks for the help. Moving it by hand is not a huge deal. I just > > assumed that since it was recommended to use the command in the docs that > > it was worth mentioning. case closed I guess. unless we want to consider > > the NFS error worthy of a bug report? > > You mean the attempt to nfs mount the storage directly from the engine? > It has an option to use ssh instead, you can try that too if you feel > curious. See the man page. > > If it's something else, I missed it - please give more details. > > Of course you can open a bug if you want. I guess it will be low priority > and will probably solved eventually by reimplementing the command line > tool using the work that will be done for the "upload from gui" bug. > Still, detailing your structure/flow will be useful as a test case. > > Thanks and best regards, > -- > Didi > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a)
- Original Message - > From: "Steve Atkinson" > To: "Yedidyah Bar David" > Cc: users@ovirt.org > Sent: Wednesday, December 31, 2014 10:43:23 PM > Subject: Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a) > > Ok well thanks for the help. Moving it by hand is not a huge deal. I just > assumed that since it was recommended to use the command in the docs that > it was worth mentioning. case closed I guess. unless we want to consider > the NFS error worthy of a bug report? You mean the attempt to nfs mount the storage directly from the engine? It has an option to use ssh instead, you can try that too if you feel curious. See the man page. If it's something else, I missed it - please give more details. Of course you can open a bug if you want. I guess it will be low priority and will probably solved eventually by reimplementing the command line tool using the work that will be done for the "upload from gui" bug. Still, detailing your structure/flow will be useful as a test case. Thanks and best regards, -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a)
Ok well thanks for the help. Moving it by hand is not a huge deal. I just assumed that since it was recommended to use the command in the docs that it was worth mentioning. case closed I guess. unless we want to consider the NFS error worthy of a bug report? On Dec 31, 2014 3:34 PM, "Yedidyah Bar David" wrote: > - Original Message - > > From: "Steve Atkinson" > > To: "Yedidyah Bar David" > > Cc: users@ovirt.org > > Sent: Wednesday, December 31, 2014 8:22:14 PM > > Subject: Re: [ovirt-users] engine-iso-uploader unexpected behaviour > (steve a) > > If I attempt to mount any of them via NFS from our management network > they > > work just fine. (moved around, read/write operations) > > Copied the ISO I needed directly to it and changed the perms/ownership by > > hand which seems to have worked as a short term solution. > > Good. Not sure it's that short term - it was suggested several times > here and people seem to use it. > > > > > I can see why the --iso-domain argument has issues as it is trying to use > > the our storage network, which isn't routable from the Engine as it only > > has the one network interface. Although that does seem like an oversight. > > Seems like this transfer should pass through the SPM and not try to > > directly mount the NFS share if the --iso-domain flag is used. > > Indeed this is a somewhat complex subject, which is why it was somewhat > neglected so far. There is some work to fix this recently, see e.g.: > > https://bugzilla.redhat.com/show_bug.cgi?id=1122970 > > http://lists.ovirt.org/pipermail/devel/2014-December/thread.html#9481 > http://lists.ovirt.org/pipermail/devel/2014-December/thread.html#9565 > (yes, two separate discussions this month). > > Best, > -- > Didi > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a)
- Original Message - > From: "Steve Atkinson" > To: "Yedidyah Bar David" > Cc: users@ovirt.org > Sent: Wednesday, December 31, 2014 8:22:14 PM > Subject: Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a) > If I attempt to mount any of them via NFS from our management network they > work just fine. (moved around, read/write operations) > Copied the ISO I needed directly to it and changed the perms/ownership by > hand which seems to have worked as a short term solution. Good. Not sure it's that short term - it was suggested several times here and people seem to use it. > > I can see why the --iso-domain argument has issues as it is trying to use > the our storage network, which isn't routable from the Engine as it only > has the one network interface. Although that does seem like an oversight. > Seems like this transfer should pass through the SPM and not try to > directly mount the NFS share if the --iso-domain flag is used. Indeed this is a somewhat complex subject, which is why it was somewhat neglected so far. There is some work to fix this recently, see e.g.: https://bugzilla.redhat.com/show_bug.cgi?id=1122970 http://lists.ovirt.org/pipermail/devel/2014-December/thread.html#9481 http://lists.ovirt.org/pipermail/devel/2014-December/thread.html#9565 (yes, two separate discussions this month). Best, -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] engine-iso-uploader unexpected behaviour (steve a)
On Wed, Dec 31, 2014 at 12:47 PM, Yedidyah Bar David
wrote:
> - Original Message -
> > From: "Steve Atkinson"
> > To: users@ovirt.org
> > Sent: Wednesday, December 31, 2014 7:15:23 PM
> > Subject: [ovirt-users] engine-iso-uploader unexpected behaviour
> >
> > When attempting use the engine-iso-uploader to drop ISOs in my iso
> storage
> > domain I get the following results.
> >
> > Using engine-iso-uploader --iso-domain=[domain] upload [iso] does not
> work
> > because the engine does not have access to our storage network. So it
> > attempts to mount to an address that is not routable. I thought to
> resolve
> > this by adding an interfaces to the Hosted Engine, only to find that I
> > cannot modify the Engine's VM config from the GUI. I receive the error:
> > Cannot add Interface. This VM is not managed by the engine. Actually, I
> get
> > that error whenever I attempt to modify anything about the engine. Maybe
> > this is expected behavior? I can't find any bestpractices regarding
> Hosted
> > Engine administration.
> >
> > Alternatively, using engine-iso-uploader --nfs-server=[path] upload [iso]
> > --verbose returns the following error:
> >
> > ERROR: local variable 'domain_type' referenced before assignment
> > INFO: Use the -h option to see usage.
> > DEBUG: Configuration:
> > DEBUG: command: upload
> > DEBUG: Traceback (most recent call last):
> > DEBUG: File "/usr/bin/engine-iso-uploader", line 1440, in
> > DEBUG: isoup = ISOUploader(conf)
> > DEBUG: File "/usr/bin/engine-iso-uploader", line 455, in __init__
> > DEBUG: self.upload_to_storage_domain()
> > DEBUG: File "/usr/bin/engine-iso-uploader", line 1089, in
> > upload_to_storage_domain
> > DEBUG: elif domain_type in ('localfs', ):
> > DEBUG: UnboundLocalError: local variable 'domain_type' referenced before
> > assignment
>
> Do you run it from the engine's machine? The host? Elsewhere?
> Where is the iso domain?
>
> This sounds to me like a bug, but I didn't check the sources yet.
> Please open one. Thanks.
>
> That said, you can simply copy your iso file directly to the correct
> directory inside the iso domain, which is:
>
> /path-to-iso-domain/SOME-UUID/images/----/
>
> Make sure it's readable to vdsm:kvm (36:36).
>
> Best,
> --
> Didi
>
I'm running the command from the Engine itself, it seems to be the only box
that has this command available. The ISO domain utilizes the same root
share as the DATA and EXPORT domains which seem to work fine. The structure
looks something like:
server:/nfs-share/ovirt-store/iso-store/UUIDblahblah/images/
server:/nfs-share/ovirt-store/export-store/path/path/path
server:/nfs-share/ovirt-store/data-store/UUIDblahblah/images/
Each of storage-domain was created through the Engine. Perms for each
below, which persists all the way down the tree:
drwxr-xr-x. 3 vdsm kvm 4 Nov 14 19:02 data-store
drwxr-xr-x. 3 vdsm kvm 4 Nov 14 19:04 export-store
drwxr-xr-x. 3 vdsm kvm 4 Nov 14 18:18 hosted-engine
drwxr-xr-x. 3 vdsm kvm 4 Nov 14 19:04 iso-store
If I attempt to mount any of them via NFS from our management network they
work just fine. (moved around, read/write operations)
Copied the ISO I needed directly to it and changed the perms/ownership by
hand which seems to have worked as a short term solution.
I can see why the --iso-domain argument has issues as it is trying to use
the our storage network, which isn't routable from the Engine as it only
has the one network interface. Although that does seem like an oversight.
Seems like this transfer should pass through the SPM and not try to
directly mount the NFS share if the --iso-domain flag is used.
Thanks for the quick response.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] engine-iso-uploader unexpected behaviour
- Original Message -
> From: "Steve Atkinson"
> To: users@ovirt.org
> Sent: Wednesday, December 31, 2014 7:15:23 PM
> Subject: [ovirt-users] engine-iso-uploader unexpected behaviour
>
> When attempting use the engine-iso-uploader to drop ISOs in my iso storage
> domain I get the following results.
>
> Using engine-iso-uploader --iso-domain=[domain] upload [iso] does not work
> because the engine does not have access to our storage network. So it
> attempts to mount to an address that is not routable. I thought to resolve
> this by adding an interfaces to the Hosted Engine, only to find that I
> cannot modify the Engine's VM config from the GUI. I receive the error:
> Cannot add Interface. This VM is not managed by the engine. Actually, I get
> that error whenever I attempt to modify anything about the engine. Maybe
> this is expected behavior? I can't find any bestpractices regarding Hosted
> Engine administration.
>
> Alternatively, using engine-iso-uploader --nfs-server=[path] upload [iso]
> --verbose returns the following error:
>
> ERROR: local variable 'domain_type' referenced before assignment
> INFO: Use the -h option to see usage.
> DEBUG: Configuration:
> DEBUG: command: upload
> DEBUG: Traceback (most recent call last):
> DEBUG: File "/usr/bin/engine-iso-uploader", line 1440, in
> DEBUG: isoup = ISOUploader(conf)
> DEBUG: File "/usr/bin/engine-iso-uploader", line 455, in __init__
> DEBUG: self.upload_to_storage_domain()
> DEBUG: File "/usr/bin/engine-iso-uploader", line 1089, in
> upload_to_storage_domain
> DEBUG: elif domain_type in ('localfs', ):
> DEBUG: UnboundLocalError: local variable 'domain_type' referenced before
> assignment
Do you run it from the engine's machine? The host? Elsewhere?
Where is the iso domain?
This sounds to me like a bug, but I didn't check the sources yet.
Please open one. Thanks.
That said, you can simply copy your iso file directly to the correct
directory inside the iso domain, which is:
/path-to-iso-domain/SOME-UUID/images/----/
Make sure it's readable to vdsm:kvm (36:36).
Best,
--
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] engine-iso-uploader unexpected behaviour
When attempting use the engine-iso-uploader to drop ISOs in my iso storage
domain I get the following results.
Using engine-iso-uploader --iso-domain=[domain] upload [iso] does not work
because the engine does not have access to our storage network. So it
attempts to mount to an address that is not routable. I thought to resolve
this by adding an interfaces to the Hosted Engine, only to find that I
cannot modify the Engine's VM config from the GUI. I receive the
error: Cannot add Interface. This VM is not managed by the engine.
Actually, I get that error whenever I attempt to modify anything about the
engine. Maybe this is expected behavior? I can't find any bestpractices
regarding Hosted Engine administration.
Alternatively, using engine-iso-uploader --nfs-server=[path] upload [iso]
--verbose returns the following error:
ERROR: local variable 'domain_type' referenced before assignment
INFO: Use the -h option to see usage.
DEBUG: Configuration:
DEBUG: command: upload
DEBUG: Traceback (most recent call last):
DEBUG: File "/usr/bin/engine-iso-uploader", line 1440, in
DEBUG: isoup = ISOUploader(conf)
DEBUG: File "/usr/bin/engine-iso-uploader", line 455, in __init__
DEBUG: self.upload_to_storage_domain()
DEBUG: File "/usr/bin/engine-iso-uploader", line 1089, in
upload_to_storage_domain
DEBUG: elif domain_type in ('localfs', ):
DEBUG: UnboundLocalError: local variable 'domain_type' referenced before
assignment
Engine is Self Hosted and is Version 3.5.0.1-1.el6.
Thanks!
-Steve
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
