New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't create new iSCSI (LVM) SR - get error about GFS2 driver #95
Comments
|
Same as my ticket #93, had the same error trying to add a local LVM thick on local raid card... unable to add any additionnal HBA storage. |
That's OK, I'm not trying or wanting to use GFS2, this is simply iSCSI (LVM). OK sorry it's not clear what is a XCP-ng centre bug and what is a XCP-ng bug unless you know what's actually broken. I've copied the bug to xcp-ng/xenadmin#116 |
Also, please use Xen Orchestra that works perfectly well with XCP-ng :p (because there is no Citrix stuff done in the middle :p ) edit: even from the sources, I don't care |
Yeah I get where you’re coming from but it also requires installing a license which is _very_ off-putting.
…--
Sam McLeod
On 7 Nov 2018, at 20:37, Olivier Lambert ***@***.***> wrote:
Also, please use Xen Orchestra that works perfectly well with XCP-ng :p (because there is no Citrix stuff done in the middle :p )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
What are you talking about? Install it from the sources, it's even in the official doc!! https://xen-orchestra.com/docs/from_the_sources.html |
To confirm XO from sources has a different licensing system than the ‘quickest way’ which is the first recommend?
https://xen-orchestra.com/docs/xoa.html#the-quickest-way
Not overtly keen on installing dodgy things like nodejs / NPM just to manager a hypervisor...
…--
Sam McLeod
On 7 Nov 2018, at 20:39, Olivier Lambert ***@***.***> wrote:
What are you talking about? Install it from the sources, it's even in the official doc!! https://xen-orchestra.com/docs/from_the_sources.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
XO from the sources has no license system, all XO features are enabled. What you get with XOA (Xen Orchestra virtual Appliance) is a turnkey system with one click updater, and pro support. Up to you :) edit: just create a Debian VM, and follow the documentation! |
Hmmm... ok... I see the note on building it from the sources: “WARNING 2: It's impossible to predict the result of a build for any Node and NPM versions. Please consider using XOA before trying to play with the manual build, which can be difficult if you are not used to NodeJS and NPM.” FYI - My personal opinion as someone looking at the viability of moving our organisation from XenServer to XCP-NG. If is that if there is a bug with xcp-ng centre with something as basic and mission critical as creating or attaching storage repositories I would expect that to be debugged and fixed (or rejected) rather than expected to install some JavaScript stuff from source to work around the issue. I’m not having a go there, I’m just stating how I feel about this response as a potential user (or customer). |
If you are doing things seriously, you take commercial support with a turnkey product 😉 XO and XCP-ng couldn't exist as it today without enterprise customers paying for it. Home labers or companies without any budget can still use it, just having more time to understand what are they doing. |
Well... I think that comment definitely speaks for itself.
|
Yeah, that's pretty clear. I think this is a dangerous thinking that you have, because it means only big corporations making money on your data can use money to build Open Source projects (React from FB for example). Without any money, we couldn't pay the half-dozen developers working on XO, and it will be the same for XCP-ng team. So clearly, I don't see your point. It's a fair deal: you can have all features for free, but not the support and the turnkey solution. edit: maybe you think XO or XCP-ng are pet projects, or maybe your underestimate the number of years needed to build stuff like that, IDK. But in any case, that's not cool mate :/ We couldn't make it that far without anyone enjoying the turnkey solution and paying for that. |
I didn’t ask for support. I logged a bug and the solution was ‘don’t use it’. |
This is an Open Source project mate. A bug is created, and a volunteer (@borzel ) will try to fix it when he can. |
About the original bug report, there will be effort from those who maintain XCP-ng Center to fix it, and if the root cause appears to be in XCP-ng we're not going to say "we don't care, use XO". So I think you misunderstood the advice to use XO here for "there will be no fix". Closing since there's now xcp-ng/xenadmin#116 |
Olivier and I had an offline conversation as I felt this conversation wasn’t overly productive. I think I misunderstood the intent of Oliviers comments to mean that the fix was to not use xcp-ng centre and instead to run Xen Orchestra from source, Olivier then clarified for me that he actually mean this as an alternative to see if it worked around the issue for me. I didn’t expect support for the software and was trying contribute by logging a bug but perhaps I didn’t word it correctly and I believe this came off as me sounding like I was expecting support without paying (contributing) to the project. Olivier and I have clarified what we both intended with our comments and it’s clear we both misinterpreted each others intent. Im going to try to further debug the issue while knowing that I can run XO from source if I need a workaround / alternative. I’m pleased to hear that the xcp-ng centre bug report will be worked on as it sits within the projects priorities (which was my (perhaps mis communicated) intent). |
Thanks for that message 👍 |
Thanks @sammcj Yes, I confirm that I never intended to tell that the definitive fix was to use XO, I was indeed trying to explain that it worked in XO (so you can add easily a SR from a decent UI if you can't wait for a fix in XCP-ng), which is available for free. Extra note: you can create a shared SR even using XOA Free, which doesn't require any knowledge to deploy/install! (I think I forgot to mention that!) |
Ran into this as well with XCP_NG Center. If you don't want to install XO from source here are the steps for adding the iSCSI SR (for the pool) with the CLI:
This should give some output in XML format and the piece we're interested in is the TargetIQN:
E.g.:
Note the shared=true bit - it's needed, otherwise the command assumes you want to add the SR to the host. Hope this helps. |
@slamj1 Adding a iSCSI SR also works with XOA Free, no need to install it from the sources ;) But thank you for adding a guide with |
Thanks @olivierlambert, I wasn't aware of that. I'll add that to the toolbox :) |
I was able to add a HBA SR via the console with no problem. I imagine it would work for iSCSI as well. |
I was also running into the exact same issue as sammcj . The 'hotfix' build provided by Borzel in the link above provided by stormi resolved the issue for me. @olivierlambert There doesn't appear to be a gui option for iSCSI in XOA (sources), only Local, SMB or NFS - or was the implication to make use of the CLI from within XOA to mount the iSCSI SR successfully? (Or locally mounted iSCSI ?) On a semi-related note re: trying to find the latest release of XCP-ng Center, I've found it's very easy to locate the XCP-ng Server ISO download links, but near impossible to find a recent version of an 'official' XCP-ng Center download - I feel really silly 😵 - Can someone please provide an official link to the latest exe's/msi's? Edit: Realised I needed to mount the ISO and the exe is under /client_install/... |
Here you go: https://github.com/xcp-ng/xenadmin/releases |
@CAPS3 I don't understand. What's missing in XO? You can create an iSCSI SR, be sure your XO is up to date please. |
Thanks once again borzel 👍 @olivierlambert I apologise for the delay in getting back to you and elaborating. I'm currently running xo-server 5.31.1 and xo-web 5.31.0. |
That's because there is a confusion.
|
You're an absolute legend 😁 |
To reproduce:
Expected behaviour:
Screenshots:
Note: The error in this screenshot is only shown after the below GFS2 error occurs and you dismiss the dialogue.
The text was updated successfully, but these errors were encountered: