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 <jhorne@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-bounces@ovirt.org [mailto:users-bounces@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 |