On 10/15/20 11:27 AM, Jeff Bailey wrote:
On 10/15/2020 12:07 PM, Michael Thomas wrote:
On 10/15/20 10:19 AM, Jeff Bailey wrote:
On 10/15/2020 10:01 AM, Michael Thomas wrote:
Getting closer...
I recreated the storage domain and added rbd_default_features=3 to
ceph.conf. Now I see the new
On 10/15/2020 12:07 PM, Michael Thomas wrote:
On 10/15/20 10:19 AM, Jeff Bailey wrote:
On 10/15/2020 10:01 AM, Michael Thomas wrote:
Getting closer...
I recreated the storage domain and added rbd_default_features=3 to
ceph.conf. Now I see the new disk being created with (what I think
is)
On 10/15/20 10:19 AM, Jeff Bailey wrote:
On 10/15/2020 10:01 AM, Michael Thomas wrote:
Getting closer...
I recreated the storage domain and added rbd_default_features=3 to
ceph.conf. Now I see the new disk being created with (what I think
is) the correct set of features:
# rbd info
On 10/15/2020 10:01 AM, Michael Thomas wrote:
Getting closer...
I recreated the storage domain and added rbd_default_features=3 to
ceph.conf. Now I see the new disk being created with (what I think
is) the correct set of features:
# rbd info
Getting closer...
I recreated the storage domain and added rbd_default_features=3 to
ceph.conf. Now I see the new disk being created with (what I think is)
the correct set of features:
# rbd info rbd.ovirt.data/volume-f4ac68c6-e5f7-4b01-aed0-36a55b901
fbf
rbd image
Hi Benny,
You are correct, I tried attaching to a running VM (which failed), then
tried booting a new VM using this disk (which also failed). I'll use
the workaround in the bug report going forward.
I'll just recreate the storage domain, since at this point I have
nothing in it to lose.
sorry, accidentally hit send prematurely, the database table is
driver_options, the options are json under driver_options
On Wed, Oct 14, 2020 at 5:32 PM Benny Zlotnik wrote:
>
> Did you attempt to start a VM with this disk and it failed, or you
> didn't try at all? If it's the latter then the
Did you attempt to start a VM with this disk and it failed, or you
didn't try at all? If it's the latter then the error is strange...
If it's the former there is a known issue with multipath at the
moment, see[1] for a workaround, since you might have issues with
detaching volumes which later,
On 10/14/20 3:30 AM, Benny Zlotnik wrote:
Jeff is right, it's a limitation of kernel rbd, the recommendation is
to add `rbd default features = 3` to the configuration. I think there
are plans to support rbd-nbd in cinderlib which would allow using
additional features, but I'm not aware of
Jeff is right, it's a limitation of kernel rbd, the recommendation is
to add `rbd default features = 3` to the configuration. I think there
are plans to support rbd-nbd in cinderlib which would allow using
additional features, but I'm not aware of anything concrete.
Additionally, the path for the
On 10/13/2020 5:01 PM, Michael Thomas wrote:
After getting past the proxy issue, I was finally able to run the
engine-setup --reconfigure-optional-components. The new
ManagedBlockStorage storage domain exists, and I was able to create a
disk. However, I am unable to attach the disk to a
After getting past the proxy issue, I was finally able to run the
engine-setup --reconfigure-optional-components. The new
ManagedBlockStorage storage domain exists, and I was able to create a
disk. However, I am unable to attach the disk to a running VM.
The engine.log shows the following,
Setting both http_proxy and https_proxy fixed the issue.
Thanks for the tip!
--Mike
I am not sure, it's been a long time since I tried that.
Feel free to file a bug.
You can also try setting env var 'http_proxy' for engine-setup, e.g.:
http_proxy=MY_PROXY_URL engine-setup
On Wed, Sep 30, 2020 at 4:43 PM Benny Zlotnik wrote:
>
> Not sure about this, adding +Yedidyah Bar David
>
> On Wed, Sep 30, 2020 at 3:04 PM Michael Thomas wrote:
> >
> > I hadn't installed the necessary packages when the engine was first
> > installed.
> >
> > However, running 'engine-setup
Not sure about this, adding +Yedidyah Bar David
On Wed, Sep 30, 2020 at 3:04 PM Michael Thomas wrote:
>
> I hadn't installed the necessary packages when the engine was first
> installed.
>
> However, running 'engine-setup --reconfigure-optional-components'
> doesn't work at the moment because
I hadn't installed the necessary packages when the engine was first
installed.
However, running 'engine-setup --reconfigure-optional-components'
doesn't work at the moment because (by design) my engine does not have a
network route outside of the cluster. It fails with:
[ INFO ] DNF
When you ran `engine-setup` did you enable cinderlib preview (it will
not be enabled by default)?
It should handle the creation of the database automatically, if you
didn't you can enable it by running:
`engine-setup --reconfigure-optional-components`
On Wed, Sep 30, 2020 at 1:58 AM Michael
Hi Benny,
Thanks for the confirmation. I've installed openstack-ussuri and ceph
Octopus. Then I tried using these instructions, as well as the deep
dive that Eyal has posted at https://www.youtube.com/watch?v=F3JttBkjsX8.
I've done this a couple of times, and each time the engine fails
The feature is currently in tech preview, but it's being worked on.
The feature page is outdated, but I believe this is what most users
in the mailing list were using. We held off on updating it because the
installation instructions have been a moving target, but it is more
stable now and I will
19 matches
Mail list logo
