Open Stack

On 7/14/2017 6:49 AM, nidhi.hada at wipro.com wrote:
> Hello all,
> 
> This is regarding bug 1667794 as mentioned in subject.
> 
> Its review is going on here.
> 
> https://review.openstack.org/#/c/474949/
> 
> *_Bug is - _**_Nova treats hostname as pattern_*
> 
> *_Description_*
> 
> Nova commands such as "hypervisor-list --matching <substring>",
> 
> host-evacuate-live and host-evacuate and few more, treat the
> 
> user-specified "host-name" as the input to the HTTP
> 
> /os-hypervisors/{hypervisor_hostname_pattern}/search API.
> 
> *Nova checks "host-name" as a pattern instead of exact match,*
> 
> *which causes problem with some commands such as*
> 
> *nova host-evacuate-live compute-1 where in host-evacuate*
> 
> *action will apply to all "compute-1", "compute-10".*
> 
> *That is not right.*
> 
> Correcting it by using exact match.
> 
> We have fixed it and put it for review. We need your opinion on this.
> 
> *_Kindly share your opinion in case this does not seem to be an 
> acceptable fix to anyone._*
> 
> Thanks
> 
> Nidhi
> 
> The information contained in this electronic message and any attachments 
> to this message are intended for the exclusive use of the addressee(s) 
> and may contain proprietary, confidential or privileged information. If 
> you are not the intended recipient, you should not disseminate, 
> distribute or copy this e-mail. Please notify the sender immediately and 
> destroy all copies of this message and any attachments. WARNING: 
> Computer viruses can be transmitted via email. The recipient should 
> check this email and any attachments for the presence of viruses. The 
> company accepts no liability for any damage caused by any virus 
> transmitted by this email. www.wipro.com
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

Thanks for bringing this up. Your fix is in the wrong place, see the 
comments in the patch.

-- 

Thanks,

Matt