** Changed in: nova (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute target
** Changed in: nova
Assignee: Maciej Szankin (mszankin) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova
** Changed in: nova
Status: Confirmed => Invalid
--
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/1310340
Title:
live migration fails when use long hostname of a nova compute
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute target
host
To
First thing - title is confusing. Problem is not in hostname length that
is provided as target in live-migration command. Maximum hostname length
is 64, and verified, it works.
Second thing - providing FQDN (which usually is used for hypervisor
hostname) in live migration does not work by design.
First thing - title is confusing. Problem is not in hostname length that
is provided as target in live-migration command. Maximum hostname length
is 64, and verified, it works.
Second thing - providing FQDN (which usually is used for hypervisor
hostname) in live migration does not work by design.
** Changed in: nova
Assignee: (unassigned) => Maciej Szankin (mszankin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova
** Changed in: nova
Assignee: (unassigned) => Maciej Szankin (mszankin)
--
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/1310340
Title:
live migration fails when use long hostname
** Changed in: nova
Assignee: lvmxh (shaohef) => (unassigned)
--
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/1310340
Title:
live migration fails when use long hostname of a nova
** Changed in: nova
Assignee: lvmxh (shaohef) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute target
** Changed in: nova
Assignee: (unassigned) => lvmxh (shaohef)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute target
** Changed in: nova
Assignee: (unassigned) => lvmxh (shaohef)
--
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/1310340
Title:
live migration fails when use long hostname of a nova
** Tags removed: live-migrate
** Tags added: live-migration
--
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/1310340
Title:
live migration fails when use long hostname of a nova compute
** Tags removed: live-migrate
** Tags added: live-migration
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute target
host
Hi Melanie, just wondering why this change was abandoned? Unless I
misunderstood, it seemed that the only objections to Patch Set 4 were
regarding implementation details, not against the approach. Your way of
guarding against accidentally using the wrong non-unique hypervisor host
seems good to
Hi Melanie, just wondering why this change was abandoned? Unless I
misunderstood, it seemed that the only objections to Patch Set 4 were
regarding implementation details, not against the approach. Your way of
guarding against accidentally using the wrong non-unique hypervisor host
seems good to
** Tags added: live-migrate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute target
host
To manage notifications about
** Tags added: live-migrate
--
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/1310340
Title:
live migration fails when use long hostname of a nova compute target
host
To manage
** Changed in: nova (Ubuntu)
Status: New = Triaged
** Changed in: nova (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live
** Changed in: nova (Ubuntu)
Status: New = Triaged
** Changed in: nova (Ubuntu)
Importance: Undecided = Wishlist
--
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/1310340
Title:
** Changed in: nova
Assignee: melanie witt (melwitt) = (unassigned)
--
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/1310340
Title:
live migration fails when use long hostname of a
** Changed in: nova
Assignee: melanie witt (melwitt) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute
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/1310340
** Package changed: horizon (Ubuntu) = nova (Ubuntu)
--
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/1310340
Title:
live migration fails when use long hostname of a nova compute target
** Package changed: horizon (Ubuntu) = nova (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute target
host
To
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live
Removing horizon as it has its own bug and patch up for this bug 1335999
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname
This isn't really a bug, changing to Wishlist.
** Changed in: nova
Importance: Medium = Wishlist
** Changed in: nova
Status: In Progress = Confirmed
** No longer affects: horizon
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I lack permission to remove horizon (Ubuntu), so moving back to New.
** Changed in: horizon (Ubuntu)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
Removing horizon as it has its own bug and patch up for this bug 1335999
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute
This isn't really a bug, changing to Wishlist.
** Changed in: nova
Importance: Medium = Wishlist
** Changed in: nova
Status: In Progress = Confirmed
** No longer affects: horizon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I lack permission to remove horizon (Ubuntu), so moving back to New.
** Changed in: horizon (Ubuntu)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
Yes, I met this problem, horizon give me nodes like node1.expr, while
the database has only node1, causing live migration failure, a little
fix is listed below:
50 def populate_host_choices(self, request, initial):
51 hosts = initial.get('hosts')
52 current_host =
Yes, I met this problem, horizon give me nodes like node1.expr, while
the database has only node1, causing live migration failure, a little
fix is listed below:
50 def populate_host_choices(self, request, initial):
51 hosts = initial.get('hosts')
52 current_host =
There's a Horizon patch up for changing the host name horizon is using
(see bug 1335999 / https://review.openstack.org/#/c/103672/ ) though
it's unclear to me if this will help with resolving this as well?
--
You received this bug notification because you are a member of Ubuntu
Server Team,
@Julie Thanks for linking the Horizon bug and review. That one will
solve the problem of live migrate not working at all through Horizon,
and it's anyway preferred to provide service host name. It won't however
change the fact that we can't use hypervisor_hostname as a migration
target argument.
There's a Horizon patch up for changing the host name horizon is using
(see bug 1335999 / https://review.openstack.org/#/c/103672/ ) though
it's unclear to me if this will help with resolving this as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Julie Thanks for linking the Horizon bug and review. That one will
solve the problem of live migrate not working at all through Horizon,
and it's anyway preferred to provide service host name. It won't however
change the fact that we can't use hypervisor_hostname as a migration
target argument.
** Also affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: horizon (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
** Also affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: horizon (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
I'd think we should change the horizon to use host, instead of long
hostname, or, if we really want to support target at specific one
specific compute node, specify host/hypervisor_hostname?
--jyh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I'd think we should change the horizon to use host, instead of long
hostname, or, if we really want to support target at specific one
specific compute node, specify host/hypervisor_hostname?
--jyh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Fix proposed to branch: master
Review: https://review.openstack.org/101096
** Changed in: nova
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
Fix proposed to branch: master
Review: https://review.openstack.org/101096
** Changed in: nova
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
** Also affects: horizon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long
** Also affects: horizon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova
48 matches
Mail list logo
