Re: [Openstack-operators] cannot attach new volume to an instance

[Chris Friesen]

For what it's worth, there's a patch series that went into master and is under 
review for backport to Ocata that might help:


https://review.openstack.org/#/q/topic:bug/1686116

Chris

On 07/27/2017 12:30 PM, Ignazio Cassano wrote:

The instance boots from a volume.
Fails attacching a second volume.
A guy suggested to use hw_disk_bus=virtio and it works.
Regards

Il 27/Lug/2017 05:33 PM, "Chris Friesen" > ha scritto:

On 07/27/2017 08:44 AM, Ignazio Cassano wrote:

Hello All,
instance created from images with the following metadata:

hw_disk_bus=scsi
hw_scsi_model=virtio-scsi

do not allow to attach new volume.

Deletting the above metadata in the image and creating a new instance,
it allows
new volume attachment.

I got the same behaviour on all openstack releases from liberty to 
ocata.
Regards
Ignazio


How does it fail?  Does it behave differently if you try to boot an instance
from such a volume?  (As opposed to attaching a volume to a running 
instance.)

Chris


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators





___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] cannot attach new volume to an instance

[Chris Friesen]

On 07/27/2017 12:30 PM, Ignazio Cassano wrote:

The instance boots from a volume.
Fails attacching a second volume.
A guy suggested to use hw_disk_bus=virtio and it works.


Okay...I think this is a known issue with virtio-scsi:

https://bugs.launchpad.net/nova/+bug/1702999

Chris

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] cannot attach new volume to an instance

[Ignazio Cassano]

The instance boots from a volume.
Fails attacching a second volume.
A guy suggested to use hw_disk_bus=virtio and it works.
Regards

Il 27/Lug/2017 05:33 PM, "Chris Friesen"  ha
scritto:

> On 07/27/2017 08:44 AM, Ignazio Cassano wrote:
>
>> Hello All,
>> instance created from images with the following metadata:
>>
>> hw_disk_bus=scsi
>> hw_scsi_model=virtio-scsi
>>
>> do not allow to attach new volume.
>>
>> Deletting the above metadata in the image and creating a new instance, it
>> allows
>> new volume attachment.
>>
>> I got the same behaviour on all openstack releases from liberty to ocata.
>> Regards
>> Ignazio
>>
>
> How does it fail?  Does it behave differently if you try to boot an
> instance from such a volume?  (As opposed to attaching a volume to a
> running instance.)
>
> Chris
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] cannot attach new volume to an instance

[Chris Friesen]

On 07/27/2017 08:44 AM, Ignazio Cassano wrote:

Hello All,
instance created from images with the following metadata:

hw_disk_bus=scsi
hw_scsi_model=virtio-scsi

do not allow to attach new volume.

Deletting the above metadata in the image and creating a new instance, it allows
new volume attachment.

I got the same behaviour on all openstack releases from liberty to ocata.
Regards
Ignazio


How does it fail?  Does it behave differently if you try to boot an instance 
from such a volume?  (As opposed to attaching a volume to a running instance.)


Chris


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators