Hi David,
thx for the info provided.
I understand what "reset-state" does that's why I 've already tried
hard reboot but unfortunately it only brought back the instance at the
error state.
What worries me more is that in the "/etc/libvirt/qemu" there are no
XML files for the erroneous instances, that's why the snapshot fails.
Any ideas?
These all appeared as soon as I 've updated to the latest Ocata
version.
Best,
G.
Hi G.,
I dont have Ocata up anywhere, but as a "best practice", I generally
do the:
nova reset-state --active $UUID
followed immediately by
nova reboot --hard
to try and "restore/resurrect" errored instances. The reset-state
--active doesnt actually do anything to the instance, it just
manipulates the nova db. The reboot --hard does a fairly clean
"reboot" of the instance even if it is off. None of this should
really
have anything to do with CEPH as per se, so not sure it will have the
desired outcome on your cloud though.
On Sun, Oct 8, 2017 at 8:46 AM, Georgios Dimitrakakis wrote:
Hello,
I ve tried today to update my OpenStack installation to the latest
Ocata version.
What I did was to shutoff all running instances, perform all
updates and then rebooted controller and compute nodes.
All seemed to have finished successfully but unfortunately when I
tried to power on instances that had attached to them volumes (which
are provided by Ceph) I got the following error:
libvirtError: unsupported configuration: Found duplicate drive
address for disk with target name sda controller=0 bus=0 target=0
unit=0
and the instance status now is "Error" and "No State" as a Power
state.
This happened only to the instances that already had volumes
attached to them. All the rest instances booted up normally.
I have tried to reset the states of the problematic instances
using: nova reset-state --active $instance_id and then take a
snapshot of them so that I can delete and recreate them.
Unfortunately although the state update was successful the snapshot
couldnt be taken because of this :
InstanceNotRunning: Instance $instance_id is not running.
Any ides of what can I do in order to start my instances again? Any
bug which is related?
Best regards,
G.
_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [1]
Post to : openstack@lists.openstack.org [2]
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [3]
Links:
------
[1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[2] mailto:openstack@lists.openstack.org
[3] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[4] mailto:gior...@acmac.uoc.gr
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
