[Yahoo-eng-team] [Bug 1648645] Re: Cannot specify version of salt-minion

[Joshua Powers]

Hey thanks for following up! Sorry about the original delay in getting
back to you, but I appreciate you letting us know your change.

If you wanted to, you could contribute to the salt module to allow for a
version from a specific URL or apt repo, but the solution you came up
with works as well!

** Changed in: cloud-init
   Status: Incomplete => Invalid

-- 
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/1648645

Title:
  Cannot specify version of salt-minion

Status in cloud-init:
  Invalid

Bug description:
  When installing salt-minion via cloud-init it always installs the
  latest version, providing no way to specify a specific version of the
  package.

  The file https://git.launchpad.net/cloud-
  init/tree/cloudinit/config/cc_salt_minion.py installs the package and
  this can't even be overridden using the arbitrary package install
  (packages property).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1648645/+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 1654457] Re: Image signature documentation modify barbican auth_endpoint

[Brian Rosmaita]

Not sure why this commit was marked DocImpact given that it committed
the documentation.  Fix was released in Ocata.

** Changed in: glance
   Status: New => Fix Released

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

Title:
  Image signature documentation modify barbican auth_endpoint

Status in Glance:
  Fix Released

Bug description:
  https://review.openstack.org/364840
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/glance" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 857cb490a300453b578426de6655187670384ade
  Author: Darren White 
  Date:   Fri Sep 2 11:57:45 2016 +0100

  Image signature documentation modify barbican auth_endpoint
  
  Add a configuration section to the image signature documentation
  describing how to change the keystone endpoint of barbican if
  keystone is not on localhost.
  
  If auth_endpoint is incorrect then image signing will fail as barbican
  will not be able to connect to keystone.
  
  DocImpact
  
  Added an example of changing the auth_endpoint.
  
  Closes-Bug: 1620539
  
  Change-Id: I8f8978f0c0dfc337e917c4d710dc8db1351070d2

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1654457/+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 1712763] Re: a typo of format_cpu_spec doc

[OpenStack Infra]

Reviewed:  https://review.openstack.org/497750
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=ca62a3c8446b34d8149d6eb8c7588e0db830b3bb
Submitter: Jenkins
Branch:master

commit ca62a3c8446b34d8149d6eb8c7588e0db830b3bb
Author: liu-lixiu 
Date:   Thu Aug 24 16:30:05 2017 +0800

fix a typo in format_cpu_spec doc

It allow_ranges is true -> If allow_ranges is true

Change-Id: Ia285c1dfb851a652f36e8ce1adb7c0e88853ac3a
Closes-Bug:#1712763


** Changed in: nova
   Status: In Progress => Fix Released

-- 
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/1712763

Title:
  a typo of format_cpu_spec doc

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  "It allow_ranges is true" should be "If allow_ranges is true"

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1712763/+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 1713180] [NEW] need documentation for configuring image import

[Brian Rosmaita]

Public bug reported:

Need to add a brief section to the Admin guide on configuring the
interoperable image import introduced in Pike.

** Affects: glance
 Importance: High
 Assignee: Brian Rosmaita (brian-rosmaita)
 Status: Triaged


** Tags: documentation

** Changed in: glance
Milestone: None => queens-1

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

Title:
  need documentation for configuring image import

Status in Glance:
  Triaged

Bug description:
  Need to add a brief section to the Admin guide on configuring the
  interoperable image import introduced in Pike.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1713180/+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 1710250] Re: glance v2 has no proper 'copy-from' method

[Brian Rosmaita]

Glance v2 doesn't have copy-from by design.  The v1 implementation is
insecure.  See, for example,
https://wiki.openstack.org/wiki/OSSN/OSSN-0078

That being said, in Queens we plan to implement a copy-from
functionality using the interoperable image import process.  I don't
know if it will be a "proper" copy-from, but it should be functional.

** Changed in: glance
   Status: New => Invalid

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

Title:
  glance v2 has no proper 'copy-from' method

Status in Glance:
  Invalid

Bug description:
  If one is following the documented steps, there is no way to import an
  image from a remote URL using glance v2, unless one enables deprecated
  options.

  It's asinine to force users to hairpin an image file - (e.g. download
  from remote URL to local FS, then upload to image service)

  A workaround https://bugs.launchpad.net/glance/+bug/1595335 notes that
  `show_multiple_locations` is required for this to work via Horizon,
  and https://bugs.launchpad.net/glance/+bug/1618583 has this option
  deprecated.

  This not only affects Horizon, as using the CLI commands to set an
  image's location causes a 403 error, unless we set
  `show_multiple_locations=True`.

  There has got to be a way to accomplish this easily as the v1 `--copy-
  from` method. It needs to be documented, only documenting examples
  using `--file` is a poor assumption of actual use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1710250/+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 1713177] [NEW] api-ref missing 'protected' filter query for image-list call

[Brian Rosmaita]

Public bug reported:

The 'protected' filter isn't listed among the query options for the
image-list call.  It was introduced in Pike by Change-Id:
Ie90d952e3f69b3f489f056ff506e63f96376

** Affects: glance
 Importance: Low
 Assignee: Brian Rosmaita (brian-rosmaita)
 Status: Triaged


** Tags: api-ref

** Changed in: glance
   Importance: Undecided => Low

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

Title:
  api-ref missing 'protected' filter query for image-list call

Status in Glance:
  Triaged

Bug description:
  The 'protected' filter isn't listed among the query options for the
  image-list call.  It was introduced in Pike by Change-Id:
  Ie90d952e3f69b3f489f056ff506e63f96376

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1713177/+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 1713163] [NEW] test_delete_saving_image fails because image hasn't transitioned to SAVING

[Ihar Hrachyshka]

Public bug reported:

http://logs.openstack.org/33/440933/4/check/gate-tempest-dsvm-neutron-
linuxbridge-ubuntu-xenial/ebfa453/logs/testr_results.html.gz


Traceback (most recent call last):
  File "tempest/api/compute/images/test_images.py", line 48, in 
test_delete_saving_image
wait_until='SAVING')
  File "tempest/api/compute/base.py", line 301, in create_image_from_server
image_id, wait_until)
  File "tempest/common/waiters.py", line 179, in wait_for_image_status
raise lib_exc.TimeoutException(message)
tempest.lib.exceptions.TimeoutException: Request timed out
Details: (ImagesTestJSON:test_delete_saving_image) Image 
93090479-409d-49f9-b2d3-2bc11a40f967 failed to reach SAVING state (current 
state ACTIVE) within the required time (196 s).


I briefly looked at the test case, and it seems to me that it may happen when 
the image snapshot is produced quicker than tempest being able to catch the 
intermittent transition. If so, the test case may need a refinement to check 
that a snapshot was produced and not that the state was in SAVING for some time.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: gate-failure

** Tags added: gate-failure

-- 
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/1713163

Title:
  test_delete_saving_image fails because image hasn't transitioned to
  SAVING

Status in OpenStack Compute (nova):
  New

Bug description:
  http://logs.openstack.org/33/440933/4/check/gate-tempest-dsvm-neutron-
  linuxbridge-ubuntu-xenial/ebfa453/logs/testr_results.html.gz

  
  Traceback (most recent call last):
File "tempest/api/compute/images/test_images.py", line 48, in 
test_delete_saving_image
  wait_until='SAVING')
File "tempest/api/compute/base.py", line 301, in create_image_from_server
  image_id, wait_until)
File "tempest/common/waiters.py", line 179, in wait_for_image_status
  raise lib_exc.TimeoutException(message)
  tempest.lib.exceptions.TimeoutException: Request timed out
  Details: (ImagesTestJSON:test_delete_saving_image) Image 
93090479-409d-49f9-b2d3-2bc11a40f967 failed to reach SAVING state (current 
state ACTIVE) within the required time (196 s).

  
  I briefly looked at the test case, and it seems to me that it may happen when 
the image snapshot is produced quicker than tempest being able to catch the 
intermittent transition. If so, the test case may need a refinement to check 
that a snapshot was produced and not that the state was in SAVING for some time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1713163/+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 1713162] [NEW] Kernel panic when configuring APIC timers in an instance

[Ihar Hrachyshka]

Public bug reported:

I am not sure Nova is the best candidate for this, but reporting
nevertheless. Feel free to move to another project that is a better fit.

This happened in gate in Queens.

http://logs.openstack.org/74/495974/4/check/gate-tempest-dsvm-neutron-
full-ubuntu-xenial/c61f703/logs/testr_results.html.gz

In instance console log, we can see:

[0.732045] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[0.736045] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[0.736045] ...trying to set up timer (IRQ0) through the 8259A ...
[0.736045] . (found apic 0 pin 2) ...
[0.736045] ... failed.
[0.736045] ...trying to set up timer as Virtual Wire IRQ...
[0.744045] . failed.
[0.744045] ...trying to set up timer as ExtINT IRQ...
[0.752046] . failed :(.
[0.752046] Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot 
with apic=debug and send a report.  Then try booting with the 'noapic' option.
[0.752046] 
[0.752046] Pid: 1, comm: swapper/0 Not tainted 3.2.0-80-virtual #116-Ubuntu
[0.752046] Call Trace:
[0.752046]  [] panic+0x91/0x1a4
[0.752046]  [] setup_IO_APIC+0x651/0x693
[0.752046]  [] native_smp_prepare_cpus+0x1c4/0x207
[0.752046]  [] kernel_init+0x8c/0x169
[0.752046]  [] kernel_thread_helper+0x4/0x10
[0.752046]  [] ? start_kernel+0x3c7/0x3c7
[0.752046]  [] ? gs_change+0x13/0x13

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: gate-failure

** Tags added: gate-failure

-- 
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/1713162

Title:
  Kernel panic when configuring APIC timers in an instance

Status in OpenStack Compute (nova):
  New

Bug description:
  I am not sure Nova is the best candidate for this, but reporting
  nevertheless. Feel free to move to another project that is a better
  fit.

  This happened in gate in Queens.

  http://logs.openstack.org/74/495974/4/check/gate-tempest-dsvm-neutron-
  full-ubuntu-xenial/c61f703/logs/testr_results.html.gz

  In instance console log, we can see:

  [0.732045] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
  [0.736045] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
  [0.736045] ...trying to set up timer (IRQ0) through the 8259A ...
  [0.736045] . (found apic 0 pin 2) ...
  [0.736045] ... failed.
  [0.736045] ...trying to set up timer as Virtual Wire IRQ...
  [0.744045] . failed.
  [0.744045] ...trying to set up timer as ExtINT IRQ...
  [0.752046] . failed :(.
  [0.752046] Kernel panic - not syncing: IO-APIC + timer doesn't work!  
Boot with apic=debug and send a report.  Then try booting with the 'noapic' 
option.
  [0.752046] 
  [0.752046] Pid: 1, comm: swapper/0 Not tainted 3.2.0-80-virtual 
#116-Ubuntu
  [0.752046] Call Trace:
  [0.752046]  [] panic+0x91/0x1a4
  [0.752046]  [] setup_IO_APIC+0x651/0x693
  [0.752046]  [] native_smp_prepare_cpus+0x1c4/0x207
  [0.752046]  [] kernel_init+0x8c/0x169
  [0.752046]  [] kernel_thread_helper+0x4/0x10
  [0.752046]  [] ? start_kernel+0x3c7/0x3c7
  [0.752046]  [] ? gs_change+0x13/0x13

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1713162/+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 1666446] Re: Create directory

[VinceLe]

Ok
Which permissions the created directories have ?


** Changed in: cloud-init
   Status: Incomplete => Invalid

-- 
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/1666446

Title:
  Create directory

Status in cloud-init:
  Invalid

Bug description:
  Cloud-init has writefiles, but it looks like it does not have the
  capability to create directories.

  how is mixing

  runcmd:
   - mkdir /home/toto/bin

  and

  write_files:
   - content: |
  #!/bin/sh
  echo "Hello world!"

  path: /home/toto/bin/hw.sh
  permissions: '0755'

  going to work ?

  Is runcmd garanteed to happen before write_files ?
  What about a "users" section ?

  This is the same kind of problem that is reported here:
  https://bugs.launchpad.net/cloud-init/+bug/1486113

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1666446/+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 1713158] [NEW] cloud-init.log message do not contain timezone offset info and thus may appear to go backwards

[Scott Moser]

Public bug reported:

the logging info in /var/log/cloud-init.log does not include a timezone
offset:

2017-08-23 19:11:08,115 - util.py[DEBUG]: Attempting to remove
/var/lib/cloud/instance


that causes a problem when cloud-init applies the timezone during boot it can 
appear
to jump forward or backward.

** Affects: cloud-init
 Importance: Medium
 Assignee: Ryan Harper (raharper)
 Status: Fix Committed

** Changed in: cloud-init
   Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init
 Assignee: (unassigned) => Ryan Harper (raharper)

** Changed in: cloud-init
   Status: Confirmed => Fix Committed

-- 
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/1713158

Title:
  cloud-init.log message do not contain timezone offset info and thus
  may appear to go backwards

Status in cloud-init:
  Fix Committed

Bug description:
  the logging info in /var/log/cloud-init.log does not include a
  timezone offset:

  2017-08-23 19:11:08,115 - util.py[DEBUG]: Attempting to remove
  /var/lib/cloud/instance

  
  that causes a problem when cloud-init applies the timezone during boot it can 
appear
  to jump forward or backward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1713158/+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 1588041] Re: [2.0 rc1] juju can't access vSphere VM deployed with Xenial, cloud-init fails to set SSH keys

[Joshua Powers]

** Changed in: cloud-init
   Status: New => Fix Released

-- 
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/1588041

Title:
  [2.0 rc1] juju can't access vSphere VM deployed with Xenial,  cloud-
  init fails to set SSH keys

Status in cloud-init:
  Fix Released
Status in juju:
  Fix Released

Bug description:
  I tried to do a bootstrap with vsphere as a provider using vsphere 6.0 and 
juju 1.25.5.
  -
    vsphere:
  type: vsphere
  host: '**.***.*.***'
  user: 'administra...@vsphere.oil'
  password: '**'
  datacenter: 'dc0'
  bootstrap-timeout: 1800
  logging-config: 
"=DEBUG;juju=DEBUG;golxc=TRACE;juju.container.lxc=TRACE"
  agent-stream: released
  -

  Initially, I did not specify the default series and bootstrap VM
  deployed with Xenial, however, juju  could not connect to it after
  getting the address and seems stuck trying to connect and I had to
  CTRL-C:

  -
  $ juju bootstrap -e vsphere
  ERROR the "vsphere" provider is provisional in this version of Juju. To use 
it anyway, set JUJU_DEV_FEATURE_FLAGS="vsphere-provider" in your shell 
environment
  $ export JUJU_DEV_FEATURE_FLAGS="vsphere-provider"
  $ juju bootstrap -e vsphere
  Bootstrapping environment "vsphere"
  Starting new instance for initial state server
  Launching instance
   - juju-e33e5800-edd9-4af7-8654-6d59b1e98eb9-machine-0
  Installing Juju agent on bootstrap instance
  Waiting for address
  Attempting to connect to 10.245.39.94:22
  Attempting to connect to fe80::250:56ff:fead:1b03:22
  ^CInterrupt signalled: waiting for bootstrap to exit
  ERROR failed to bootstrap environment: interrupted
  -

  When I specified the default series to be trusty, it worked:
  -
    vsphere:
  type: vsphere
  host: '**.***.*.***'
  user: 'administra...@vsphere.oil'
  password: '**'
  datacenter: 'dc0'
  default-series: trusty
  bootstrap-timeout: 1800
  logging-config: 
"=DEBUG;juju=DEBUG;golxc=TRACE;juju.container.lxc=TRACE"
  agent-stream: released
  -

  This was the output:

  -
  $ juju bootstrap -e vsphere
  Bootstrapping environment "vsphere"
  Starting new instance for initial state server
  Launching instance
   - juju-b157863b-3ed4-4ae5-8c3c-82ae7629bff7-machine-0
  Installing Juju agent on bootstrap instance
  Waiting for address
  Attempting to connect to 10.245.45.153:22
  Attempting to connect to fe80::250:56ff:fead:3fa2:22
  Warning: Permanently added '10.245.45.153' (ECDSA) to the list of known hosts.
  sudo: unable to resolve host ubuntuguest
  Logging to /var/log/cloud-init-output.log on remote host
  Running apt-get update
  Running apt-get upgrade
  Installing package: curl
  Installing package: cpu-checker
  Installing package: bridge-utils
  Installing package: rsyslog-gnutls
  Installing package: cloud-utils
  Installing package: cloud-image-utils
  Installing package: tmux
  Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP 
%{http_code}; time %{time_total}s; size %{size_download} bytes; speed 
%{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz 
<[https://streams.canonical.com/juju/tools/agent/1.25.5/juju-1.25.5-trusty-amd64.tgz]>
  Bootstrapping Juju machine agent
  Starting Juju machine agent (jujud-machine-0)
  Bootstrap agent installed
  vsphere -> vsphere
  Waiting for API to become available
  Waiting for API to become available
  Waiting for API to become available
  Waiting for API to become available
  Bootstrap complete
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1588041/+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 1713155] [NEW] can not directly launch image

[Chris Hoge]

Public bug reported:

When attempting to launch an instance from the image dialog, clicking
the "Launch" button on the image row, the dialog will remove it from the
"available" list in the "source" tab.

** 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/1713155

Title:
  can not directly launch image

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When attempting to launch an instance from the image dialog, clicking
  the "Launch" button on the image row, the dialog will remove it from
  the "available" list in the "source" tab.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1713155/+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 1411829] Re: CentOS 7 should be treated like RHEL 7 in dist/rhel.py

[Joshua Powers]

I believe this should be marked as fixed as the uses_systemd function
was updated previous:

https://github.com/cloud-init/cloud-
init/blob/master/cloudinit/distros/__init__.py#L100


** Changed in: cloud-init
   Status: New => Fix Released

-- 
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/1411829

Title:
  CentOS 7 should be treated like RHEL 7 in dist/rhel.py

Status in cloud-init:
  Fix Released

Bug description:
  cloudinit/dists/rhel.py contains the follow code to determine if
  systemd is in use:

  def uses_systemd(self):
  # Fedora 18 and RHEL 7 were the first adopters in their series
  (dist, vers) = util.system_info()['dist'][:2]
  major = (int)(vers.split('.')[0])
  return ((dist.startswith('Red Hat Enterprise Linux') and major >= 7)
  or (dist.startswith('Fedora') and major >= 18))

  
  This will not produce the correct behavior on CentOS 7, Scientific LInux 7, 
or any other RHEL-based distribution.  Among other issues, this will prevent 
cloud-init from setting the system hostname correctly.  Because these 
distributions are treated like RHEL6 and earlier, cloud-init writes the 
persistent hostname into /etc/sysconfig/network, but the hostname is not read 
from this file when the system boots.

  I propose that we replace uses_systemd with the following:

  def uses_systemd(self):
  return os.path.isfile('/usr/bin/systemctl')

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1411829/+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 1249125] Re: smartos datasource should use meta-data for server identification

[Joshua Powers]

Per the docs, you are to use "sdc:uuid" which does appear to be in the
SmartOS handler. There are two change log entries for similar work:

Update SmartOS data source to use v2 metadata.
Convert DataSourceSmartOS to use v2 metadata.

I believe this is fixed, so I am marking, fix released. If you disagree
or have additional details on work required, please reply saying so.

** Changed in: cloud-init
   Status: New => Fix Released

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1249125

Title:
  smartos datasource should use meta-data for server identification

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  New SmartOS documentation shows that the instance ID should be
  detected through the meta-data.

  http://us-east.manta.joyent.com/jmc/public/mdata/index.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1249125/+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 1713150] [NEW] config option help for default value of default_publisher_id is wrong

[Matt Riedemann]

Public bug reported:

The config option help for "default_publisher_id" says the default value
is "$my_ip" but that's not what's actually used:

notifier = rpc.get_notifier('api', publisher_id=(
CONF.notifications.default_publisher_id or CONF.host))

and:

if not publisher_id:
publisher_id = "%s.%s" % (service, host or CONF.host)

** Affects: nova
 Importance: Undecided
 Status: Triaged


** Tags: config

** Changed in: nova
   Status: New => Triaged

** Tags added: config

-- 
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/1713150

Title:
  config option help for default value of default_publisher_id is wrong

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  The config option help for "default_publisher_id" says the default
  value is "$my_ip" but that's not what's actually used:

  notifier = rpc.get_notifier('api', publisher_id=(
  CONF.notifications.default_publisher_id or CONF.host))

  and:

  if not publisher_id:
  publisher_id = "%s.%s" % (service, host or CONF.host)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1713150/+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 1713144] Re: nova metadata service breaks on hostname

[Matt Riedemann]

Looks like netaddr.IPAddress has always expected this to be a IP rather
than a FQDN:

https://github.com/drkjam/netaddr/blob/netaddr-0.7.19/netaddr/ip/__init__.py#L244

I'm not sure how it was working before.

** Changed in: nova
   Status: New => Invalid

-- 
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/1713144

Title:
  nova metadata service breaks on hostname

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  For more than a year, i have deployed  multiple clusters using 
openstack-ansible.
  This particular case is using FQDN for the internal and external endpoint.

  [DEFAULT]
  ...

  # Metadata
  metadata_host = my-int.XXX.com
  metadata_port = 8775
  metadata_workers = 3
  ...

  Recently, this breaks nova-metadata.

  2017-08-25 21:19:02.928 18130 WARNING oslo_reports.guru_meditation_report [-] 
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
  2017-08-25 21:19:02.931 18130 INFO nova.network.driver [-] Loading network 
driver 'nova.network.linux_net'
  2017-08-25 21:19:03.078 18130 CRITICAL nova [-] AddrFormatError: failed to 
detect a valid IP address from 'my-int.XXX.com'
  2017-08-25 21:19:03.078 18130 ERROR nova Traceback (most recent call last):
  2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/bin/nova-api-metadata", line 11, in 
  2017-08-25 21:19:03.078 18130 ERROR nova sys.exit(main())
  2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/cmd/api_metadata.py",
 line 48, in main
  2017-08-25 21:19:03.078 18130 ERROR nova server = 
service.WSGIService('metadata', use_ssl=should_use_ssl)
  2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 309, in __init__
  2017-08-25 21:19:03.078 18130 ERROR nova self.manager = 
self._get_manager()
  2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 364, in _get_manager
  2017-08-25 21:19:03.078 18130 ERROR nova return manager_class()
  2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/api/manager.py", 
line 30, in __init__
  2017-08-25 21:19:03.078 18130 ERROR nova 
self.network_driver.metadata_accept()
  2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/network/linux_net.py",
 line 599, in metadata_accept
  2017-08-25 21:19:03.078 18130 ERROR nova (CONF.metadata_port, 
_iptables_dest(CONF.metadata_host)))
  2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/network/linux_net.py",
 line 588, in _iptables_dest
  2017-08-25 21:19:03.078 18130 ERROR nova if 
((netaddr.IPAddress(ip).version == 4 and ip == '127.0.0.1')
  2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/netaddr/ip/__init__.py",
 line 306, in __init__
  2017-08-25 21:19:03.078 18130 ERROR nova 'address from %r' % addr)
  2017-08-25 21:19:03.078 18130 ERROR nova AddrFormatError: failed to detect a 
valid IP address from 'my-int.XXX.com'
  2017-08-25 21:19:03.078 18130 ERROR nova
  2017-08-25 21:19:09.833 18137 WARNING oslo_reports.guru_meditation_report [-] 
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
  2017-08-25 21:19:09.836 18137 INFO nova.network.driver [-] Loading network 
driver 'nova.network.linux_net'
  2017-08-25 21:19:10.040 18137 CRITICAL nova [-] AddrFormatError: failed to 
detect a valid IP address from 'my-int.XXX.com'
  2017-08-25 21:19:10.040 18137 ERROR nova Traceback (most recent call last):
  2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/bin/nova-api-metadata", line 11, in 
  2017-08-25 21:19:10.040 18137 ERROR nova sys.exit(main())
  2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/cmd/api_metadata.py",
 line 48, in main
  2017-08-25 21:19:10.040 18137 ERROR nova server = 
service.WSGIService('metadata', use_ssl=should_use_ssl)
  2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 309, in __init__
  2017-08-25 21:19:10.040 18137 ERROR nova self.manager = 
self._get_manager()
  2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 364, in _get_manager
  2017-08-25 21:19:10.0

[Yahoo-eng-team] [Bug 1713144] [NEW] nova metadata service breaks on hostname

[admin0]

Public bug reported:

For more than a year, i have deployed  multiple clusters using 
openstack-ansible.
This particular case is using FQDN for the internal and external endpoint.

[DEFAULT]
...

# Metadata
metadata_host = my-int.XXX.com
metadata_port = 8775
metadata_workers = 3
...

Recently, this breaks nova-metadata.

2017-08-25 21:19:02.928 18130 WARNING oslo_reports.guru_meditation_report [-] 
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
2017-08-25 21:19:02.931 18130 INFO nova.network.driver [-] Loading network 
driver 'nova.network.linux_net'
2017-08-25 21:19:03.078 18130 CRITICAL nova [-] AddrFormatError: failed to 
detect a valid IP address from 'my-int.XXX.com'
2017-08-25 21:19:03.078 18130 ERROR nova Traceback (most recent call last):
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/bin/nova-api-metadata", line 11, in 
2017-08-25 21:19:03.078 18130 ERROR nova sys.exit(main())
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/cmd/api_metadata.py",
 line 48, in main
2017-08-25 21:19:03.078 18130 ERROR nova server = 
service.WSGIService('metadata', use_ssl=should_use_ssl)
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 309, in __init__
2017-08-25 21:19:03.078 18130 ERROR nova self.manager = self._get_manager()
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 364, in _get_manager
2017-08-25 21:19:03.078 18130 ERROR nova return manager_class()
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/api/manager.py", 
line 30, in __init__
2017-08-25 21:19:03.078 18130 ERROR nova 
self.network_driver.metadata_accept()
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/network/linux_net.py",
 line 599, in metadata_accept
2017-08-25 21:19:03.078 18130 ERROR nova (CONF.metadata_port, 
_iptables_dest(CONF.metadata_host)))
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/network/linux_net.py",
 line 588, in _iptables_dest
2017-08-25 21:19:03.078 18130 ERROR nova if ((netaddr.IPAddress(ip).version 
== 4 and ip == '127.0.0.1')
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/netaddr/ip/__init__.py",
 line 306, in __init__
2017-08-25 21:19:03.078 18130 ERROR nova 'address from %r' % addr)
2017-08-25 21:19:03.078 18130 ERROR nova AddrFormatError: failed to detect a 
valid IP address from 'my-int.XXX.com'
2017-08-25 21:19:03.078 18130 ERROR nova
2017-08-25 21:19:09.833 18137 WARNING oslo_reports.guru_meditation_report [-] 
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
2017-08-25 21:19:09.836 18137 INFO nova.network.driver [-] Loading network 
driver 'nova.network.linux_net'
2017-08-25 21:19:10.040 18137 CRITICAL nova [-] AddrFormatError: failed to 
detect a valid IP address from 'my-int.XXX.com'
2017-08-25 21:19:10.040 18137 ERROR nova Traceback (most recent call last):
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/bin/nova-api-metadata", line 11, in 
2017-08-25 21:19:10.040 18137 ERROR nova sys.exit(main())
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/cmd/api_metadata.py",
 line 48, in main
2017-08-25 21:19:10.040 18137 ERROR nova server = 
service.WSGIService('metadata', use_ssl=should_use_ssl)
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 309, in __init__
2017-08-25 21:19:10.040 18137 ERROR nova self.manager = self._get_manager()
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 364, in _get_manager
2017-08-25 21:19:10.040 18137 ERROR nova return manager_class()
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/api/manager.py", 
line 30, in __init__
2017-08-25 21:19:10.040 18137 ERROR nova 
self.network_driver.metadata_accept()
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/network/linux_net.py",
 line 599, in metadata_accept
2017-08-25 21:19:10.040 18137 ERROR nova (CONF.metadata_port, 
_iptables_dest(CONF.metadata_host)))
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.

[Yahoo-eng-team] [Bug 1713144] [NEW] nova metadata service breaks on hostname

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

For more than a year, i have deployed  multiple clusters using 
openstack-ansible. 
This particular case is using FQDN for the internal and external endpoint.

[DEFAULT]
...

# Metadata
metadata_host = my-int.XXX.com
metadata_port = 8775
metadata_workers = 3
...


Recently, this breaks nova-console. 

2017-08-25 21:19:02.928 18130 WARNING oslo_reports.guru_meditation_report [-] 
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
2017-08-25 21:19:02.931 18130 INFO nova.network.driver [-] Loading network 
driver 'nova.network.linux_net'
2017-08-25 21:19:03.078 18130 CRITICAL nova [-] AddrFormatError: failed to 
detect a valid IP address from 'my-int.XXX.com'
2017-08-25 21:19:03.078 18130 ERROR nova Traceback (most recent call last):
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/bin/nova-api-metadata", line 11, in 
2017-08-25 21:19:03.078 18130 ERROR nova sys.exit(main())
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/cmd/api_metadata.py",
 line 48, in main
2017-08-25 21:19:03.078 18130 ERROR nova server = 
service.WSGIService('metadata', use_ssl=should_use_ssl)
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 309, in __init__
2017-08-25 21:19:03.078 18130 ERROR nova self.manager = self._get_manager()
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 364, in _get_manager
2017-08-25 21:19:03.078 18130 ERROR nova return manager_class()
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/api/manager.py", 
line 30, in __init__
2017-08-25 21:19:03.078 18130 ERROR nova 
self.network_driver.metadata_accept()
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/network/linux_net.py",
 line 599, in metadata_accept
2017-08-25 21:19:03.078 18130 ERROR nova (CONF.metadata_port, 
_iptables_dest(CONF.metadata_host)))
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/network/linux_net.py",
 line 588, in _iptables_dest
2017-08-25 21:19:03.078 18130 ERROR nova if ((netaddr.IPAddress(ip).version 
== 4 and ip == '127.0.0.1')
2017-08-25 21:19:03.078 18130 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/netaddr/ip/__init__.py",
 line 306, in __init__
2017-08-25 21:19:03.078 18130 ERROR nova 'address from %r' % addr)
2017-08-25 21:19:03.078 18130 ERROR nova AddrFormatError: failed to detect a 
valid IP address from 'my-int.XXX.com'
2017-08-25 21:19:03.078 18130 ERROR nova
2017-08-25 21:19:09.833 18137 WARNING oslo_reports.guru_meditation_report [-] 
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
2017-08-25 21:19:09.836 18137 INFO nova.network.driver [-] Loading network 
driver 'nova.network.linux_net'
2017-08-25 21:19:10.040 18137 CRITICAL nova [-] AddrFormatError: failed to 
detect a valid IP address from 'my-int.XXX.com'
2017-08-25 21:19:10.040 18137 ERROR nova Traceback (most recent call last):
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/bin/nova-api-metadata", line 11, in 
2017-08-25 21:19:10.040 18137 ERROR nova sys.exit(main())
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/cmd/api_metadata.py",
 line 48, in main
2017-08-25 21:19:10.040 18137 ERROR nova server = 
service.WSGIService('metadata', use_ssl=should_use_ssl)
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 309, in __init__
2017-08-25 21:19:10.040 18137 ERROR nova self.manager = self._get_manager()
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/service.py", 
line 364, in _get_manager
2017-08-25 21:19:10.040 18137 ERROR nova return manager_class()
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/api/manager.py", 
line 30, in __init__
2017-08-25 21:19:10.040 18137 ERROR nova 
self.network_driver.metadata_accept()
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/openstack/venvs/nova-15.1.8/lib/python2.7/site-packages/nova/network/linux_net.py",
 line 599, in metadata_accept
2017-08-25 21:19:10.040 18137 ERROR nova (CONF.metadata_port, 
_iptables_dest(CONF.metadata_host)))
2017-08-25 21:19:10.040 18137 ERROR nova   File 
"/o

[Yahoo-eng-team] [Bug 1713141] [NEW] Some links of User doc is invalid

[Dou Rui Yuan]

Public bug reported:

Links of user doc should be replaced with new address:

doc/source/user/glanceapi.rst:

Designated sections (definition) 

> 
https://github.com/openstack/interop/blob/master/doc/source/process/Lexicon.rst

OpenStack Core Definition 

> 
https://github.com/openstack/interop/blob/master/doc/source/process/CoreDefinition.rst

DefCore Guidelines Repository 
> https://github.com/openstack/interop


doc/source/user/metadefs-concepts.rst:

Heat resource types: 
http://docs.openstack.org/developer/heat/template_guide/openstack.html
> https://docs.openstack.org/heat/latest/template_guide/openstack.html

** Affects: glance
 Importance: Undecided
 Assignee: Dou Rui Yuan (rydou)
 Status: In Progress

** Changed in: glance
 Assignee: (unassigned) => Dou Rui Yuan (rydou)

** Changed in: glance
   Status: New => In Progress

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

Title:
  Some links of User doc is invalid

Status in Glance:
  In Progress

Bug description:
  Links of user doc should be replaced with new address:

  doc/source/user/glanceapi.rst:

  Designated sections (definition) 

  > 
https://github.com/openstack/interop/blob/master/doc/source/process/Lexicon.rst

  OpenStack Core Definition 

  > 
https://github.com/openstack/interop/blob/master/doc/source/process/CoreDefinition.rst

  DefCore Guidelines Repository 
  > https://github.com/openstack/interop

  
  doc/source/user/metadefs-concepts.rst:

  Heat resource types: 
http://docs.openstack.org/developer/heat/template_guide/openstack.html
  > https://docs.openstack.org/heat/latest/template_guide/openstack.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1713141/+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 1712107] Re: Install and configure controller node in neutron

[OpenStack Infra]

Reviewed:  https://review.openstack.org/497591
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=13ddee8aaa0607bb5582107187a7bb36f9473e38
Submitter: Jenkins
Branch:master

commit 13ddee8aaa0607bb5582107187a7bb36f9473e38
Author: Boden R 
Date:   Thu Aug 24 13:32:17 2017 -0600

fix formatting in ubuntu controller install guide

The ubuntu controller install guide contains improper indentation and
extraneous new lines. As a result the sub-steps for #1 are not shown
in this HTML (generated) guide.

This one needs to also get back-ported to pike.

Change-Id: Ib2b263c8da49ccc8905cbd59331ce6694de232e6
Closes-Bug: #1712107


** Changed in: neutron
   Status: In Progress => Fix Released

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

Title:
  Install and configure controller node in neutron

Status in neutron:
  Fix Released

Bug description:
  [Documentation :: Pike] Neutron install on controller
  https://docs.openstack.org/neutron/pike/install/controller-install-ubuntu.html

  
  This bug tracker is for errors with the documentation, use the following as a 
template and remove or add fields as you see fit. Convert [ ] into [x] to check 
boxes:

  - [x] This doc is inaccurate in this way: There are 2 #1 steps, you
  have the user log into DB then execute openstacl cli command. Given
  previous docs, I beleive you would like them to create db 'neutron'
  and grant permissions. Must have been omitted by mistake on
  copy+paste.

  ---
  Release: 11.0.0.0rc2.dev19 on 2017-08-21 05:14
  SHA: 3441b3f5940a85e4dd32c1e509e713ee41b33010
  Source: 
https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/controller-install-ubuntu.rst
  URL: 
https://docs.openstack.org/neutron/pike/install/controller-install-ubuntu.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1712107/+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 1712907] Re: contributor internals index incomplete

[OpenStack Infra]

Reviewed:  https://review.openstack.org/497595
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=2750590cde2c2fbf2b62a753966e77b1c0fa8c1d
Submitter: Jenkins
Branch:master

commit 2750590cde2c2fbf2b62a753966e77b1c0fa8c1d
Author: Boden R 
Date:   Thu Aug 24 13:55:41 2017 -0600

update contributor internals index

A number of our RSTs under doc/srouce/contributor/internals/* are not
referenced from the index.rst and as a result are not
published/accessible in our docs.

This patch updates the index to ref all internal pages.

Change-Id: If534f8d6a7da2807285edb6885c800696d1c50a9
Closes-Bug: #1712907


** Changed in: neutron
   Status: In Progress => Fix Released

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

Title:
  contributor internals index incomplete

Status in neutron:
  Fix Released

Bug description:
  The doc/source/contributor/internals/index.rst doesn't reference all
  the .rst files under doc/source/contributor/internals/. As a result
  the index page is incomplete [1] and a number of the contributor
  internal rsts aren't even published/accessible.

  
  [1] https://docs.openstack.org/neutron/latest/contributor/internals/index.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1712907/+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 1680254] Re: VMware: Failed at boot instance from volume

[Vipin Balachandran]

*** This bug is a duplicate of bug 1712281 ***
https://bugs.launchpad.net/bugs/1712281

** This bug has been marked a duplicate of bug 1712281
   Attach volume failed for vmware driver

-- 
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/1680254

Title:
  VMware: Failed at boot instance from volume

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Instance is failing with booting from volume

   [req-e1b1ac9c-3394-44c6-8453-b05f41f2aa16 admin admin]  Instance failed to 
spawn
    Traceback (most recent call last):
  File "/opt/stack/nova/nova/compute/manager.py", line 2120, in 
_build_resources
    yield resources
  File "/opt/stack/nova/nova/compute/manager.py", line 1925, in 
_build_and_run_instance
    block_device_info=block_device_info)
  File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 324, in spawn
    admin_password, network_info, block_device_info)
  File "/opt/stack/nova/nova/virt/vmwareapi/vmops.py", line 791, in spawn
    instance, vi.datastore.ref, adapter_type)
  File "/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 606, in 
attach_root_volume
    self.attach_volume(connection_info, instance, adapter_type)
  File "/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 383, in 
attach_volume
    self._attach_volume_vmdk(connection_info, instance, adapter_type)
  File "/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 337, in 
_attach_volume_vmdk
    if state.lower() != 'poweredoff':
    AttributeError: 'int' object has no attribute 'lower'

  Because in nova/compute/power_state.py, all states are in index, so
  state should be int not str. So the driver code need to be updated
  accordingly.

  Command to reproduce in devstack(all repos are in master level):
  nova boot --nic net-id= --flavor  --block-device 
source=image,id=,dest=volume,size=2,shutdown=preserve,bootindex=0 
mystanceFromVolume1

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1680254/+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 1704010] Re: VMware: attach volume fails with AttributeError

[Vipin Balachandran]

*** This bug is a duplicate of bug 1712281 ***
https://bugs.launchpad.net/bugs/1712281

** This bug is no longer a duplicate of bug 1680254
   VMware: Failed at boot instance from volume
** This bug has been marked a duplicate of bug 1712281
   Attach volume failed for vmware driver

-- 
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/1704010

Title:
  VMware: attach volume fails with AttributeError

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Attaching/detaching volume with adapter type IDE fails with:
  AttributeError: 'int' object has no attribute 'lower'

  2017-07-11 23:20:11.876 ERROR nova.virt.block_device 
[req-15c66739-f62f-405d-ad71-e9e46dfeea88 demo admin] [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] Driver failed to attach volume 
7f94ea59-510c-4c9e-bf5b-9accc59a7a54 at /dev/sdc: AttributeError: 'int' object 
has no attribute 'lower'
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] Traceback (most recent call last):
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835]   File 
"/opt/stack/nova/nova/virt/block_device.py", line 389, in attach
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] device_type=self['device_type'], 
encryption=encryption)
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835]   File 
"/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 328, in attach_volume
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] return 
self._volumeops.attach_volume(connection_info, instance)
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835]   File 
"/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 381, in attach_volume
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] 
self._attach_volume_vmdk(connection_info, instance, adapter_type)
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835]   File 
"/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 335, in 
_attach_volume_vmdk
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] if state.lower() != 'poweredoff':
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] AttributeError: 'int' object has no 
attribute 'lower'
  2017-07-11 23:20:11.876 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] 

  2017-07-11 23:20:56.655 ERROR nova.virt.block_device 
[req-d985d896-119c-40e4-868e-677dbf461df1 demo admin] [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] Failed to detach volume 
af84764d-dd81-4108-8d2f-b39cedeb9aa2 from /dev/sdb: AttributeError: 'int' 
object has no attribute 'lower'
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] Traceback (most recent call last):
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835]   File 
"/opt/stack/nova/nova/virt/block_device.py", line 277, in driver_detach
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] encryption=encryption)
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835]   File 
"/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 333, in detach_volume
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] return 
self._volumeops.detach_volume(connection_info, instance)
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835]   File 
"/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 582, in detach_volume
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] 
self._detach_volume_vmdk(connection_info, instance)
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835]   File 
"/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 535, in 
_detach_volume_vmdk
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] if state.lower() != 'poweredoff':
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835] AttributeError: 'int' object has no 
attribute 'lower'
  2017-07-11 23:20:56.655 TRACE nova.virt.block_device [instance: 
c5a35862-98c2-4b01-9259-fd250c0af835]

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

[Yahoo-eng-team] [Bug 1712412] Re: DVR external port setup fails with KeyError: 'host'

[OpenStack Infra]

Reviewed:  https://review.openstack.org/497009
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=47fbc6157ac4125fa068e64b573433a02c0ce0fc
Submitter: Jenkins
Branch:master

commit 47fbc6157ac4125fa068e64b573433a02c0ce0fc
Author: Swaminathan Vasudevan 
Date:   Wed Aug 23 21:11:58 2017 -0700

DVR: _get_floatingips_bound_to_host throws KeyError

_get_floatingips_bound_to_host function was introduced
recently in dvr_local_router to retrieve the external
interface name for centralizing the floatingip.

This function was throwing a 'KeyError' on fip['host'] and
not required for centralized floatingips anymore.

The get_external_device_interface_name in dvr_local_router
will try to get the 'fg' interface that is required for
the bound floating-ips to clear up some of the rules.
In the case of the centralized unbound floating-ips, the
'qg' external interface is retreived from
get_snat_external_device_interface_name that is defined
in 'dvr_edge_router' and based on the namespace.

So _get_floatingips_bound_to_host can be removed from
get_external_device_inteface_name.

Closes-Bug: 1712412

Change-Id: I94c0a071df32f572745a2c29942956c3da9f309b


** Changed in: neutron
   Status: In Progress => Fix Released

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

Title:
  DVR external port setup fails with KeyError: 'host'

Status in neutron:
  Fix Released

Bug description:
  http://logs.openstack.org/28/481928/9/check/gate-tempest-dsvm-neutron-
  dvr-multinode-scenario-ubuntu-xenial-
  nv/8fb7c92/logs/subnode-2/screen-q-l3.txt.gz?level=TRACE

  Aug 22 07:55:55.697082 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent [-] Failed to process 
compatible router: 02fc503f-72c9-49bd-a4f8-30305a7efb90: KeyError: 'host'
  Aug 22 07:55:55.697264 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent Traceback (most recent 
call last):
  Aug 22 07:55:55.697446 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent   File 
"/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 538, in 
_process_router_update
  Aug 22 07:55:55.697665 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent 
self._process_router_if_compatible(router)
  Aug 22 07:55:55.697850 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent   File 
"/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 475, in 
_process_router_if_compatible
  Aug 22 07:55:55.698048 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent 
self._process_updated_router(router)
  Aug 22 07:55:55.698229 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent   File 
"/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 490, in 
_process_updated_router
  Aug 22 07:55:55.698405 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent ri.process()
  Aug 22 07:55:55.698581 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent   File 
"/opt/stack/new/neutron/neutron/agent/l3/dvr_local_router.py", line 737, in 
process
  Aug 22 07:55:55.698756 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent super(DvrLocalRouter, 
self).process()
  Aug 22 07:55:55.698936 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent   File 
"/opt/stack/new/neutron/neutron/agent/l3/dvr_router_base.py", line 29, in 
process
  Aug 22 07:55:55.699114 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent super(DvrRouterBase, 
self).process()
  Aug 22 07:55:55.699289 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent   File 
"/opt/stack/new/neutron/neutron/agent/l3/ha_router.py", line 436, in process
  Aug 22 07:55:55.699469 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent super(HaRouter, 
self).process()
  Aug 22 07:55:55.699654 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent   File 
"/opt/stack/new/neutron/neutron/common/utils.py", line 189, in call
  Aug 22 07:55:55.699903 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent self.logger(e)
  Aug 22 07:55:55.700084 ubuntu-xenial-2-node-rax-ord-10554784-832133 
neutron-l3-agent[2539]: ERROR neutron.agent.l3.agent   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line

[Yahoo-eng-team] [Bug 1643041] Re: snappy module does not install snaps

[Joshua Powers]

** Changed in: cloud-init
   Status: New => Invalid

-- 
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/1643041

Title:
  snappy module does not install snaps

Status in cloud-init:
  Invalid

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup snappy to 
install hello-world does not work.

  [cloud-config]
  #cloud-config
  snappy:
system_snappy: yes (or auto)
packages: [hello-world]

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
  cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  snappy is installed, however, `snap list` returns no snaps installed.

  [expected result]
  I would have expected the "hello-world" snap to be installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643041/+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 1643022] Re: landscape module does not work

[Joshua Powers]

** Changed in: cloud-init
   Status: New => Invalid

-- 
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/1643022

Title:
  landscape module does not work

Status in cloud-init:
  Invalid

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup landscape does 
not install the landscape-client or set up the config and has no error message.

  [cloud-config]
  #cloud-conifg
  landscape:
client:
  log_level: "info"
  url: "https://landscape.canonical.com/message-system";
  ping_url: "http://landscape.canonical.com/ping";
  data_path: "/var/lib/landscape/client"
  http_proxy: "http://my.proxy.com/foobar";
  https_proxy: "https://my.proxy.com/foobar";
  tags: "server,cloud"
  computer_title: "footitle"
  registration_key: "fookey"
  account_name: "fooaccount"

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
  cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  root@xenial-lxd:/var/log# cat cloud-init.log  | grep landscape
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] stages.py[DEBUG]: Running module 
landscape () with 
frequency once-per-instance
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: start: 
modules-final/config-landscape: running config-landscape with frequency 
once-per-instance
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/xenial-lxd/sem/config_landscape - wb: [420] 24 bytes
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] helpers.py[DEBUG]: Running 
config-landscape using lock ()
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: finish: 
modules-final/config-landscape: SUCCESS: config-landscape ran successfully

  [expected result]
  I would have expected landscape-client to get installed and the configuration 
file to be written.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643022/+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 1713095] [NEW] Nova compute driver init happens before conductor is ready

[Dan Smith]

Public bug reported:

In nova/service.py we poll for conductor readiness before we allow
normal service startup behavior. The ironic driver does RPC to conductor
in its _refresh_hash_ring() code, which may expect conductor be up
before it's not. If so, we'll fail to start up because we called to
conductor, waited a long time, and then timed out.

** 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/1713095

Title:
  Nova compute driver init happens before conductor is ready

Status in OpenStack Compute (nova):
  New

Bug description:
  In nova/service.py we poll for conductor readiness before we allow
  normal service startup behavior. The ironic driver does RPC to
  conductor in its _refresh_hash_ring() code, which may expect conductor
  be up before it's not. If so, we'll fail to start up because we called
  to conductor, waited a long time, and then timed out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1713095/+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 1712281] Re: Attach volume failed for vmware driver

[OpenStack Infra]

Reviewed:  https://review.openstack.org/496140
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=8aa3133e4515cd30f47bea8f3fed9ce4ec883c53
Submitter: Jenkins
Branch:master

commit 8aa3133e4515cd30f47bea8f3fed9ce4ec883c53
Author: DamonLi 
Date:   Tue Aug 22 15:48:33 2017 +0800

Fix bug on vmware driver attach volume failed

The function "get_vm_state" in vmwareapi returns the index of the vm state 
in
nova InstancePowerState. The "int" value do not have .lower() function. This
will cause error when attach volume.

Closes-Bug: #1712281

Change-Id: I7b6d581904219d1ba4615054f9676390170ab1bc


** Changed in: nova
   Status: In Progress => Fix Released

-- 
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/1712281

Title:
  Attach volume failed for vmware driver

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  VMware nova CI always failed when attach volume.
  The error logs are shown as following.

  2017-08-21 23:41:08.001 4576 ERROR nova.compute.manager 
[req-cb1de0dd-4108-4217-ba74-c217bb17cd6f 
tempest-ServersTestBootFromVolume-634134128 
tempest-ServersTestBootFromVolume-634134128] [instance: 
980f0c9e-30d3-4ae5-ae83-e6b8e17cb707] Instance failed to spawn: AttributeError: 
'int' object has no attribute 'lower'
   Traceback (most recent call last):
    File "/opt/stack/nova/nova/compute/manager.py", line 2139, in 
_build_resources
   yield resources
    File "/opt/stack/nova/nova/compute/manager.py", line 1954, in 
_build_and_run_instance
  block_device_info=block_device_info)
     File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 323, in spawn
   admin_password, network_info, block_device_info)
     File "/opt/stack/nova/nova/virt/vmwareapi/vmops.py", line 790, in spawn
   instance, vi.datastore.ref, adapter_type)
     File "/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 604, in 
attach_root_volume
   self.attach_volume(connection_info, instance, adapter_type)
     File "/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 381, in 
attach_volume
   self._attach_volume_vmdk(connection_info, instance, adapter_type)
     File "/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 335, in 
_attach_volume_vmdk
   if state.lower() != 'poweredoff':
   AttributeError: 'int' object has no attribute 'lower'


  
  There are two issue here.
    1. The variable "state" is "int" type, and it doesn't have function 
".lower()"
    2. In nova InstancePowerState, there is no status called "poweredoff". We 
should use power_states.SHUTDOWN instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1712281/+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 1708205] Re: placement allocation representation asymetric on PUT and GET

[Chris Dent]

** Changed in: nova
   Status: Incomplete => Invalid

-- 
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/1708205

Title:
  placement allocation representation asymetric on PUT and GET

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  GET /allocations/{consumer_uuid} is a dict keyed by resource provider
  uuid.

  PUT /allocations/{consumer_uuid} is an array of anonymous json objects
  with 'resource_provider' and 'resources' objects

  This asymmetry is undesirable and confusing. It's probably the result
  of failing to update one side when changing the other, earlier in the
  development of placement.

  Changing it is likely a bit of a bear, would require a microversion of
  course, but might be worth considering to make things more clear for
  the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1708205/+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 1693349] Re: trying to create a resource provider with an already in use uuid causes misleading error

[OpenStack Infra]

Reviewed:  https://review.openstack.org/468928
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=863f0ce0b543631cf13b3d5d6491659931e2697e
Submitter: Jenkins
Branch:master

commit 863f0ce0b543631cf13b3d5d6491659931e2697e
Author: Chris Dent 
Date:   Mon May 29 17:27:22 2017 +

[placement] Disambiguate resource provider conflict message

When creating a resource provider, if the uuid or name (or both)
of the resource provider is already being used a 409 response is
returned. Prior to this change the error message always mentioned
the name of the resource provider, even if it was not the cause of
the duplication. That's misleading and unfriendly.

The new code will list the field and the value of the field that
was duplicated. From looking at the olso_db code that creates a
DBDuplicateEntry it appears that sometimes, but not always, the
exception could list both fields, so allowance for that is made
in the message output and the related gabbi tests.

Because this changes the error message, but not the error response
code, this does not violate the api interoperability guidelines[1],
so I'm willing to say this doesn't require a microversion, and thus
does not require a spec.

[1] 
http://specs.openstack.org/openstack/api-wg/guidelines/api_interoperability.html
If we do think this is a violation, then the guideline should be
made more explicit.

Change-Id: Ibafbfd8302977a2b4e9250fbb5ada283b69d3c25
Closes-Bug: #1693349


** Changed in: nova
   Status: In Progress => Fix Released

-- 
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/1693349

Title:
  trying to create a resource provider with an already in use uuid
  causes misleading error

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  (This is mostly a reminder bug for cdent, by cdent, so I don't forget
  it while doing something else.)

  POST is used to create a resource provider. 'name' is required, 'uuid'
  is optional, if you don't provide one one will be created.

  If you create a provider with $uuid_1 and then create another one with
  a different name but $uuid_1 the error message will be:

 'Conflicting resource provider %(name)s already exists.'

  Which is not actually true. We need to check the columns in the
  DBDuplicateEntry response to choose a to either use name or uuid as
  appropriate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1693349/+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