[VMware-dvs] Controller becames KVM Compute node manually by simple command

Bug #1513739 reported by Vyacheslav Tabolin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel VMware DVS plugin
Invalid
High
Partner Centric Engineering

Bug Description

Controller became KVM Compute node when customer tries to reboot vmware-compute service by the same command like at special vmware-compute nodes:

service nova-compute restart

It needs to block on controller nodes.

Tags: dvs
Changed in fuel-plugins:
assignee: nobody → slops (slavchick)
affects: fuel-plugins → vmware-dvs
Changed in vmware-dvs:
importance: Undecided → High
Igor Gajsin (igajsin)
affects: vmware-dvs → fuel-plugins
Changed in fuel-plugins:
milestone: none → 7.0
tags: added: dvs
Changed in fuel-plugins:
assignee: Vyachestav Tabolin (slavchick) → Partner Centric Engineering (fuel-partner-engineering)
affects: fuel-plugins → fuel-plugin-vmware-dvs
Changed in fuel-plugin-vmware-dvs:
milestone: 7.0 → none
milestone: none → 1.1.0
Revision history for this message
Igor Gajsin (igajsin) wrote :

When an user has the root access to the controller he can do many dangerous things which we can't prevent.
The nova-compute service can't start automaticly due to

# cat /etc/init/nova-compute.override
manual

And that is everything that we can do for that.

Changed in fuel-plugin-vmware-dvs:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.