** Changed in: nova (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Title:
Filter scheduler not respecting the force_hosts hint
Reviewed: https://review.openstack.org/21018
Committed:
http://github.com/openstack/openstack-manuals/commit/d9b0e389b94ae8972ba3404069bcb0866c53e26c
Submitter: Jenkins
Branch:stable/folsom
commit d9b0e389b94ae8972ba3404069bcb0866c53e26c
Author: atul jha koolhea...@gmail.com
Date: Tue Nov
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Title:
Filter scheduler not respecting the force_hosts hint
To
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Title:
Filter scheduler not respecting the force_hosts hint
To
Reviewed: https://review.openstack.org/15983
Committed:
http://github.com/openstack/openstack-manuals/commit/3faca61ce3c20aea60d900afaaf9a9c7a19342d6
Submitter: Jenkins
Branch:master
commit 3faca61ce3c20aea60d900afaaf9a9c7a19342d6
Author: atul jha koolhea...@gmail.com
Date: Tue Nov 13
so what is the actual syntax for OpenStack Essex?
I also did not find anything in the docs (maybe I am blind) that you can
specify a hostname as part of the availability zone's name.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
There is an explanatory comment on the review for the doc update but we
have not back ported to Essex docs - see
https://review.openstack.org/#/c/15983/
Anne Gentle
Content Stacker
a...@openstack.org
On Nov 17, 2012, at 9:23 AM, Christian Parpart tra...@gmail.com wrote:
so what is the actual
** Changed in: openstack-manuals
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Title:
Filter scheduler not respecting the force_hosts
** Changed in: openstack-manuals
Assignee: (unassigned) = koolhead17 (koolhead17)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Title:
Filter scheduler not respecting
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Duplicate of https://bugs.launchpad.net/nova/+bug/1053754
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Title:
Filter scheduler not respecting the force_hosts hint
To manage
Hm, I'm getting:
error: unrecognized arguments: --availability-zone
Try `nova' for more information.
I'm running Essex. Is this a Folsom-only option? No way to get around it
in Essex?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
force_hosts is not a hint meant to be exposed to a user. if you want to
force a host as an admin you can use the availability zone syntax:
nova boot --image uuid --flavor m1.tiny --key_name mykey
--availability-zone nova:sleepy
** Changed in: nova
Status: New = Won't Fix
--
You received
Then perhaps this is a documentation bug instead. --hint force_hosts
is the currently-documented method in the Compute Administration Manual:
http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-
host-to-boot-instances-on.html
--
You received this bug notification because you
** Project changed: nova = openstack-manuals
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Title:
Filter scheduler not respecting the force_hosts hint
To manage
openstacl-manuals: to fix this bug
$ nova boot --image 1 --flavor 2 --key_name test --hint
force_hosts=server2 my-first-server
becomes
nova boot --image uuid --flavor m1.tiny --key_name mykey
--availability-zone nova:server2
An extra explanation of what an 'availability zone' is is necessary.
I ran into the same problem. It seems that HostState.passes_filters
gets called with different data in filter_properties than it expects.
The attached patch makes it work, but I doubt it's a completely correct
solution, since I don't handle more than one host in the force_hosts
list.
** Patch
The attachment nova_1061665.patch of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag 'patch'
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Title:
Filter scheduler not respecting the force_hosts hint
19 matches
Mail list logo
