[Yahoo-eng-team] [Bug 1746455] [NEW] cloud-init vSphere cloud provider DHCP unique hostname issue

2018-01-31 Thread Calvin Hartwell
Public bug reported:

Hi all,

Reported first for k8s: 
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
Juju bug reported here: https://bugs.launchpad.net/juju/+bug/1746358

Basically cloud-init is not giving newly provisioned machines on vSphere
their correct hostname before the DHCP lease is given, meaning that
every instance during DHCP has the hostname 'ubuntu' which messes up the
entries on the DNS server.

Cheers,

- Calvin

** Affects: cloud-init
 Importance: Undecided
 Status: New


** Tags: cloud-init cpe-onsite dhcp juju k8s vsphere

** Tags added: cloud-init juju k8s kubernetes

** Tags removed: kubernetes
** Tags added: dhcp vsphere

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1746455

Title:
  cloud-init vSphere cloud provider DHCP unique hostname issue

Status in cloud-init:
  New

Bug description:
  Hi all,

  Reported first for k8s: 
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/480
  Juju bug reported here: https://bugs.launchpad.net/juju/+bug/1746358

  Basically cloud-init is not giving newly provisioned machines on
  vSphere their correct hostname before the DHCP lease is given, meaning
  that every instance during DHCP has the hostname 'ubuntu' which messes
  up the entries on the DNS server.

  Cheers,

  - Calvin

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1746455/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1569714] [NEW] Don't select the user's primary project on editing User

2016-04-13 Thread Calvin
Public bug reported:

When editing user in the 'Identity/Users' Page ,  the select control of
primary project  don't select the user's primary project.

I debugged and found that 'user.project_id' in Line 136 of File
horizon/openstack_dashboard/dashboards/identity/users/views.py always
return None.

** Affects: horizon
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1569714

Title:
  Don't select the user's primary project on editing User

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When editing user in the 'Identity/Users' Page ,  the select control
  of primary project  don't select the user's primary project.

  I debugged and found that 'user.project_id' in Line 136 of File
  horizon/openstack_dashboard/dashboards/identity/users/views.py always
  return None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1569714/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1569713] [NEW] user.project_id

2016-04-13 Thread Calvin
Public bug reported:

When editing user info in the 'Identity/Users' Page ,  the select
control of primary project  don't select the user's primary project.

I debugged and found that 'user.project_id' in Line 136 of File
horizon/openstack_dashboard/dashboards/identity/users/views.py always
return None.

** Affects: horizon
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1569713

Title:
  user.project_id

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When editing user info in the 'Identity/Users' Page ,  the select
  control of primary project  don't select the user's primary project.

  I debugged and found that 'user.project_id' in Line 136 of File
  horizon/openstack_dashboard/dashboards/identity/users/views.py always
  return None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1569713/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1427295] [NEW] nova-network with multi-host and update_dns_entries crashes during instance termination

2015-03-02 Thread Calvin Walton
Public bug reported:

I have Openstack Nova set up using nova-network in multi-host mode. I
wanted all instances to be able to resolve each-other via dns, so I
enabled update_dns_entries=True in nova.conf

Upon terminating an instance, I get the following traceback in nova-
compute.log on the compute node hosting the instance:

Traceback (most recent call last):

  File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, 
line 134, in _dispatch_and_reply
incoming.message))

  File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, 
line 177, in _dispatch
return self._do_dispatch(endpoint, method, ctxt, args)

  File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, 
line 123, in _do_dispatch
result = getattr(endpoint, method)(ctxt, **new_args)

  File /usr/lib/python2.7/dist-packages/nova/network/floating_ips.py, line 
187, in deallocate_for_instance
super(FloatingIP, self).deallocate_for_instance(context, **kwargs)

  File /usr/lib/python2.7/dist-packages/nova/network/manager.py, line 568, in 
deallocate_for_instance
network_ids = [fixed_ip.network_id for fixed_ip in fixed_ips]

AttributeError: 'str' object has no attribute 'network_id'

Some spelunking reveals that this was introduced in the following commit:
https://github.com/openstack/nova/commit/03d34c975586788dc25249b5e0b962fc0634008c
which changed the fixed_ips array to contain a list of string ip address, 
rather than fixed_ip objects, but neglected to update the code under the 
CONF.update_dns_entries branch below to match.

** Affects: nova
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1427295

Title:
  nova-network with multi-host and update_dns_entries crashes during
  instance termination

Status in OpenStack Compute (Nova):
  New

Bug description:
  I have Openstack Nova set up using nova-network in multi-host mode. I
  wanted all instances to be able to resolve each-other via dns, so I
  enabled update_dns_entries=True in nova.conf

  Upon terminating an instance, I get the following traceback in nova-
  compute.log on the compute node hosting the instance:

  Traceback (most recent call last):

File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, 
line 134, in _dispatch_and_reply
  incoming.message))

File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, 
line 177, in _dispatch
  return self._do_dispatch(endpoint, method, ctxt, args)

File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, 
line 123, in _do_dispatch
  result = getattr(endpoint, method)(ctxt, **new_args)

File /usr/lib/python2.7/dist-packages/nova/network/floating_ips.py, line 
187, in deallocate_for_instance
  super(FloatingIP, self).deallocate_for_instance(context, **kwargs)

File /usr/lib/python2.7/dist-packages/nova/network/manager.py, line 568, 
in deallocate_for_instance
  network_ids = [fixed_ip.network_id for fixed_ip in fixed_ips]

  AttributeError: 'str' object has no attribute 'network_id'

  Some spelunking reveals that this was introduced in the following commit:
  
https://github.com/openstack/nova/commit/03d34c975586788dc25249b5e0b962fc0634008c
  which changed the fixed_ips array to contain a list of string ip address, 
rather than fixed_ip objects, but neglected to update the code under the 
CONF.update_dns_entries branch below to match.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1427295/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp