volume attachment issue while running the knife openstack server create

[polaaditya]

The mount point of the physical device attached to the instance while creation is different from the physical device attached inside the instance...
Instance Log:

but the disk attached to instance is different.when i try to run sudo fdisk -l in the instance

Is there anyway to pass the mountpoint of the device such as /dev/vdb in the command line using knife openstack server create...
the command which i used to bring up the server is
knife openstack server create --no-host-key-verify --node-ssl-verify-mode none --openstack-volumes --flavor --image --ssh-user <IMAGE_USER> -S --identity-file --network-ids --openstack-floating-ip --insecure --yes -VV --hint openstack -N <INSTANCE_NAME> --openstack-groups <SEC_GROUP> --run-list “" --environment

[jjasghar]

So you're trying to attach the /dev/vdd to the box that you did fdisk -l on? Can you confirm that in horizon/nova/cinder that there is the /dev/vdd and it's attached to something?

Can you show me the attached drive to whatever instance using knife-openstack the failure, then show me the attached drive via nova?

If we aren't doing something correct here it's probably due to fog, and i'd like to figure out where it's breaking.

[polaaditya]

i have created a volume using cinder create and this volume id is attached in the options while using "openstack server create --openstack-volumes"


attached the screenshots for both of them

[jjasghar]

So it seems that it's created..."randomly?"

https://github.com/chef/knife-openstack/blob/master/lib/chef/knife/openstack_server_create.rb#L55-L64

I'll have to make it so you can declare the mountpoint.

[jjasghar]

That's a feature request, and i'll have to put it on as a TODO.

[polaaditya]

Thanks @jjasghar...can we also enable the option for "delete on termination" to choose from command line and also the fetch the volume size instead of nil ...
https://github.com/chef/knife-openstack/blob/master/lib/chef/knife/openstack_server_create.rb#L61-L63

[jjasghar]

Sounds reasonable. I can't promise you this'll happen fast, but at least we know what we need to fix now 🤘