Re: [Users] iscsi discovery issue

2013-02-25 Thread Alex Leonhardt
Hi Dafna,

I just started working on this again, and it now did pick up the change -
so my assumption for now is that it must have been locally cached on the
Hyper-Visor... I'll do some more testing to re-create this and if it
happens again, i'll email you the logs.

Thanks,
Alex


On 22 February 2013 17:14, Alex Leonhardt alex.t...@gmail.com wrote:

  Will do when back on it early next week.

 Alex

 On 02/20/2013 03:22 PM, Dafna Ron wrote:

 Hi Alex,

 theoretically, even if the target is already logged in, engine is
 sending a query called getDeviceList which should update the information
 that was changed for the target.

 can you please attach the logs (both engine and vdsm)?
 also, if you can give me more information on what storage are you using
 and what exact commands (or steps) you did it would be most appreciated.

 Thanks,

 Dafna



 On 02/20/2013 04:26 PM, Alex Leonhardt wrote:

  I thought of that, however, the node wasn't logged in to anything, in
 fact, it didnt even know about the target / disk. I dont think it got
 that far. Then I checked the engine host too, but nothing there either.

 I wont be doing much more testing today / this week, but really hope
 someone can shed some light here as will have to pick this up again
 beginning of next week.

 It's fair enough and not a biggie if it's simply a bug, but there
 simply must be some record of where these things are being written to ?

 Alex



 On 20 February 2013 14:01, Jonathan Horne 
 jho...@skopos.usmailto:jho...@skopos.us jho...@skopos.us wrote:

 I have seem the same thing in the past, you might try to get on
 the node itself and issue a logout command : iscsiadm -m node --logout



 Then retry the discovery.



 *From:*users-boun...@ovirt.org mailto:users-boun...@ovirt.org 
 users-boun...@ovirt.org
 [mailto:users-boun...@ovirt.org users-boun...@ovirt.org 
 mailto:users-boun...@ovirt.org users-boun...@ovirt.org]
 *On Behalf Of *Alex Leonhardt
 *Sent:* Wednesday, February 20, 2013 4:13 AM
 *To:* oVirt Mailing List
 *Subject:* [Users] iscsi discovery issue



 Hi All,



 I've successfully discovered a ISCSI target, however, when I tried
 to add it as storage to the engine, it complained of being too
 small, so I resized the file and restarted tgtd on the server.



 The problem is that the engine doesnt seem to bother
 re-discoverying the target ? How can I remove its cache / current
 entries ? It never added it as a storage domain, so it is safe to
 remove that entry I suppose ?



 Why would the engine not try to re-read the device stats when
 adding a storage domain ?



 Thanks

 Alex



 --



 | RHCE | Senior Systems Engineer | www.vcore.co
 http://www.vcore.co http://www.vcore.co | www.vsearchcloud.com
 http://www.vsearchcloud.com http://www.vsearchcloud.com |


 
 This is a PRIVATE message. If you are not the intended recipient,
 please delete without copying and kindly advise us by e-mail of
 the mistake in delivery. NOTE: Regardless of content, this e-mail
 shall not operate to bind SKOPOS to any order or other contract
 unless pursuant to explicit written agreement or government
 initiative expressly permitting the use of e-mail for such purpose.




 --

 | RHCE | Senior Systems Engineer | www.vcore.co http://www.vcore.co 
 http://www.vcore.co
 | www.vsearchcloud.com http://www.vsearchcloud.com 
 http://www.vsearchcloud.com |


 ___
 Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users




-- 

| RHCE | Senior Systems Engineer | www.vcore.co | www.vsearchcloud.com |
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] iscsi discovery issue

2013-02-25 Thread Dafna Ron
Hi Alex,

glad that it worked out.
if you do manage to reproduce you know where to find me :)

thanks,
Dafna


On 02/25/2013 04:11 PM, Alex Leonhardt wrote:
 Hi Dafna,

 I just started working on this again, and it now did pick up the
 change - so my assumption for now is that it must have been locally
 cached on the Hyper-Visor... I'll do some more testing to re-create
 this and if it happens again, i'll email you the logs.

 Thanks,
 Alex


 On 22 February 2013 17:14, Alex Leonhardt alex.t...@gmail.com
 mailto:alex.t...@gmail.com wrote:

 Will do when back on it early next week.

 Alex

 On 02/20/2013 03:22 PM, Dafna Ron wrote:
 Hi Alex,

 theoretically, even if the target is already logged in, engine is
 sending a query called getDeviceList which should update the information
 that was changed for the target.

 can you please attach the logs (both engine and vdsm)?
 also, if you can give me more information on what storage are you using
 and what exact commands (or steps) you did it would be most appreciated.

 Thanks,

 Dafna



 On 02/20/2013 04:26 PM, Alex Leonhardt wrote:
 I thought of that, however, the node wasn't logged in to anything, in
 fact, it didnt even know about the target / disk. I dont think it got
 that far. Then I checked the engine host too, but nothing there either. 

 I wont be doing much more testing today / this week, but really hope
 someone can shed some light here as will have to pick this up again
 beginning of next week. 

 It's fair enough and not a biggie if it's simply a bug, but there
 simply must be some record of where these things are being written to ?

 Alex



 On 20 February 2013 14:01, Jonathan Horne jho...@skopos.us 
 mailto:jho...@skopos.us
 mailto:jho...@skopos.us wrote:

 I have seem the same thing in the past, you might try to get on
 the node itself and issue a logout command : iscsiadm -m node 
 --logout

  

 Then retry the discovery.

  

 *From:*users-boun...@ovirt.org mailto:users-boun...@ovirt.org 
 mailto:users-boun...@ovirt.org
 [mailto:users-boun...@ovirt.org mailto:users-boun...@ovirt.org]
 *On Behalf Of *Alex Leonhardt
 *Sent:* Wednesday, February 20, 2013 4:13 AM
 *To:* oVirt Mailing List
 *Subject:* [Users] iscsi discovery issue

  

 Hi All,

  

 I've successfully discovered a ISCSI target, however, when I tried
 to add it as storage to the engine, it complained of being too
 small, so I resized the file and restarted tgtd on the server. 

  

 The problem is that the engine doesnt seem to bother
 re-discoverying the target ? How can I remove its cache / current
 entries ? It never added it as a storage domain, so it is safe to
 remove that entry I suppose ? 

  

 Why would the engine not try to re-read the device stats when
 adding a storage domain ? 

  

 Thanks

 Alex

  

 -- 

  

 | RHCE | Senior Systems Engineer | www.vcore.co 
 http://www.vcore.co
 http://www.vcore.co | www.vsearchcloud.com 
 http://www.vsearchcloud.com
 http://www.vsearchcloud.com |


 
 
 This is a PRIVATE message. If you are not the intended recipient,
 please delete without copying and kindly advise us by e-mail of
 the mistake in delivery. NOTE: Regardless of content, this e-mail
 shall not operate to bind SKOPOS to any order or other contract
 unless pursuant to explicit written agreement or government
 initiative expressly permitting the use of e-mail for such purpose.




 -- 

 | RHCE | Senior Systems Engineer | www.vcore.co http://www.vcore.co 
 http://www.vcore.co
 | www.vsearchcloud.com http://www.vsearchcloud.com 
 http://www.vsearchcloud.com |


 ___
 Users mailing list
 Users@ovirt.org mailto:Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users




 -- 

 | RHCE | Senior Systems Engineer | www.vcore.co http://www.vcore.co
 | www.vsearchcloud.com http://www.vsearchcloud.com |


 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


-- 
Dafna Ron
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] iscsi discovery issue

2013-02-22 Thread Alex Leonhardt

Will do when back on it early next week.

Alex

On 02/20/2013 03:22 PM, Dafna Ron wrote:

Hi Alex,

theoretically, even if the target is already logged in, engine is
sending a query called getDeviceList which should update the information
that was changed for the target.

can you please attach the logs (both engine and vdsm)?
also, if you can give me more information on what storage are you using
and what exact commands (or steps) you did it would be most appreciated.

Thanks,

Dafna



On 02/20/2013 04:26 PM, Alex Leonhardt wrote:

I thought of that, however, the node wasn't logged in to anything, in
fact, it didnt even know about the target / disk. I dont think it got
that far. Then I checked the engine host too, but nothing there either.

I wont be doing much more testing today / this week, but really hope
someone can shed some light here as will have to pick this up again
beginning of next week.

It's fair enough and not a biggie if it's simply a bug, but there
simply must be some record of where these things are being written to ?

Alex



On 20 February 2013 14:01, Jonathan Hornejho...@skopos.us
mailto:jho...@skopos.us  wrote:

 I have seem the same thing in the past, you might try to get on
 the node itself and issue a logout command : iscsiadm -m node --logout



 Then retry the discovery.



 *From:*users-boun...@ovirt.orgmailto:users-boun...@ovirt.org
 [mailto:users-boun...@ovirt.orgmailto:users-boun...@ovirt.org]
 *On Behalf Of *Alex Leonhardt
 *Sent:* Wednesday, February 20, 2013 4:13 AM
 *To:* oVirt Mailing List
 *Subject:* [Users] iscsi discovery issue



 Hi All,



 I've successfully discovered a ISCSI target, however, when I tried
 to add it as storage to the engine, it complained of being too
 small, so I resized the file and restarted tgtd on the server.



 The problem is that the engine doesnt seem to bother
 re-discoverying the target ? How can I remove its cache / current
 entries ? It never added it as a storage domain, so it is safe to
 remove that entry I suppose ?



 Why would the engine not try to re-read the device stats when
 adding a storage domain ?



 Thanks

 Alex



 --



 | RHCE | Senior Systems Engineer | www.vcore.co
 http://www.vcore.co  | www.vsearchcloud.com
 http://www.vsearchcloud.com  |


 
 This is a PRIVATE message. If you are not the intended recipient,
 please delete without copying and kindly advise us by e-mail of
 the mistake in delivery. NOTE: Regardless of content, this e-mail
 shall not operate to bind SKOPOS to any order or other contract
 unless pursuant to explicit written agreement or government
 initiative expressly permitting the use of e-mail for such purpose.




--

| RHCE | Senior Systems Engineer | www.vcore.cohttp://www.vcore.co
| www.vsearchcloud.comhttp://www.vsearchcloud.com  |


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] iscsi discovery issue

2013-02-20 Thread Alex Leonhardt
Hi All,

I've successfully discovered a ISCSI target, however, when I tried to add
it as storage to the engine, it complained of being too small, so I resized
the file and restarted tgtd on the server.

The problem is that the engine doesnt seem to bother re-discoverying the
target ? How can I remove its cache / current entries ? It never added it
as a storage domain, so it is safe to remove that entry I suppose ?

Why would the engine not try to re-read the device stats when adding a
storage domain ?

Thanks
Alex

-- 

| RHCE | Senior Systems Engineer | www.vcore.co | www.vsearchcloud.com |
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] iscsi discovery issue

2013-02-20 Thread Jonathan Horne
I have seem the same thing in the past, you might try to get on the node itself 
and issue a logout command : iscsiadm -m node --logout

Then retry the discovery.

From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of 
Alex Leonhardt
Sent: Wednesday, February 20, 2013 4:13 AM
To: oVirt Mailing List
Subject: [Users] iscsi discovery issue

Hi All,

I've successfully discovered a ISCSI target, however, when I tried to add it as 
storage to the engine, it complained of being too small, so I resized the file 
and restarted tgtd on the server.

The problem is that the engine doesnt seem to bother re-discoverying the target 
? How can I remove its cache / current entries ? It never added it as a storage 
domain, so it is safe to remove that entry I suppose ?

Why would the engine not try to re-read the device stats when adding a storage 
domain ?

Thanks
Alex

--

| RHCE | Senior Systems Engineer | www.vcore.cohttp://www.vcore.co | 
www.vsearchcloud.comhttp://www.vsearchcloud.com |


This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to 
any order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] iscsi discovery issue

2013-02-20 Thread Alex Leonhardt
I thought of that, however, the node wasn't logged in to anything, in fact,
it didnt even know about the target / disk. I dont think it got that far.
Then I checked the engine host too, but nothing there either.

I wont be doing much more testing today / this week, but really hope
someone can shed some light here as will have to pick this up again
beginning of next week.

It's fair enough and not a biggie if it's simply a bug, but there simply
must be some record of where these things are being written to ?

Alex



On 20 February 2013 14:01, Jonathan Horne jho...@skopos.us wrote:

  I have seem the same thing in the past, you might try to get on the node
 itself and issue a logout command : iscsiadm -m node --logout



 Then retry the discovery.



 *From:* users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] *On
 Behalf Of *Alex Leonhardt
 *Sent:* Wednesday, February 20, 2013 4:13 AM
 *To:* oVirt Mailing List
 *Subject:* [Users] iscsi discovery issue



 Hi All,



 I've successfully discovered a ISCSI target, however, when I tried to add
 it as storage to the engine, it complained of being too small, so I resized
 the file and restarted tgtd on the server.



 The problem is that the engine doesnt seem to bother re-discoverying the
 target ? How can I remove its cache / current entries ? It never added it
 as a storage domain, so it is safe to remove that entry I suppose ?



 Why would the engine not try to re-read the device stats when adding a
 storage domain ?



 Thanks

 Alex



 --



 | RHCE | Senior Systems Engineer | www.vcore.co | www.vsearchcloud.com |

 --
 This is a PRIVATE message. If you are not the intended recipient, please
 delete without copying and kindly advise us by e-mail of the mistake in
 delivery. NOTE: Regardless of content, this e-mail shall not operate to
 bind SKOPOS to any order or other contract unless pursuant to explicit
 written agreement or government initiative expressly permitting the use of
 e-mail for such purpose.




-- 

| RHCE | Senior Systems Engineer | www.vcore.co | www.vsearchcloud.com |
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] iscsi discovery issue

2013-02-20 Thread Dafna Ron
Hi Alex,

theoretically, even if the target is already logged in, engine is
sending a query called getDeviceList which should update the information
that was changed for the target.

can you please attach the logs (both engine and vdsm)?
also, if you can give me more information on what storage are you using
and what exact commands (or steps) you did it would be most appreciated.

Thanks,

Dafna



On 02/20/2013 04:26 PM, Alex Leonhardt wrote:
 I thought of that, however, the node wasn't logged in to anything, in
 fact, it didnt even know about the target / disk. I dont think it got
 that far. Then I checked the engine host too, but nothing there either. 

 I wont be doing much more testing today / this week, but really hope
 someone can shed some light here as will have to pick this up again
 beginning of next week. 

 It's fair enough and not a biggie if it's simply a bug, but there
 simply must be some record of where these things are being written to ?

 Alex



 On 20 February 2013 14:01, Jonathan Horne jho...@skopos.us
 mailto:jho...@skopos.us wrote:

 I have seem the same thing in the past, you might try to get on
 the node itself and issue a logout command : iscsiadm -m node --logout

  

 Then retry the discovery.

  

 *From:*users-boun...@ovirt.org mailto:users-boun...@ovirt.org
 [mailto:users-boun...@ovirt.org mailto:users-boun...@ovirt.org]
 *On Behalf Of *Alex Leonhardt
 *Sent:* Wednesday, February 20, 2013 4:13 AM
 *To:* oVirt Mailing List
 *Subject:* [Users] iscsi discovery issue

  

 Hi All,

  

 I've successfully discovered a ISCSI target, however, when I tried
 to add it as storage to the engine, it complained of being too
 small, so I resized the file and restarted tgtd on the server. 

  

 The problem is that the engine doesnt seem to bother
 re-discoverying the target ? How can I remove its cache / current
 entries ? It never added it as a storage domain, so it is safe to
 remove that entry I suppose ? 

  

 Why would the engine not try to re-read the device stats when
 adding a storage domain ? 

  

 Thanks

 Alex

  

 -- 

  

 | RHCE | Senior Systems Engineer | www.vcore.co
 http://www.vcore.co | www.vsearchcloud.com
 http://www.vsearchcloud.com |


 
 This is a PRIVATE message. If you are not the intended recipient,
 please delete without copying and kindly advise us by e-mail of
 the mistake in delivery. NOTE: Regardless of content, this e-mail
 shall not operate to bind SKOPOS to any order or other contract
 unless pursuant to explicit written agreement or government
 initiative expressly permitting the use of e-mail for such purpose.




 -- 

 | RHCE | Senior Systems Engineer | www.vcore.co http://www.vcore.co
 | www.vsearchcloud.com http://www.vsearchcloud.com |


 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


-- 
Dafna Ron
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users