[Yahoo-eng-team] [Bug 1752789] [NEW] init rc script not working properly at first boot

2018-03-01 Thread KIM JUNHO 
Public bug reported:

Hi, I'm newbie on cloud-init. I used qemu-system-x86_64 using kvm and 
cloud-init for provisioning ubuntu-cloud-image.
I want to file system mount using 9p file system. If I want to use it, I need 
to put my path on the qemu starting command like '-fsdev .. something like 
that' and in the virtual machine, I need to mount using 9p type file system 
using mount command. So, I choose using ubuntu run-level script which is 
writing script on the init.d and use update-rc.d command. When I tried to 
normal script file such as 'touch /blah/blah', it worked properly.

Also, it wrote successfully into file, and execute that script, it works
(which means that it can attach 9p-filesystem, just it does not work on
first time boot).

However, when I tried to attach 9p-file system. It does not working.
When I reboot the instance, it successfully attched the file system. So,
I reasonably consider that cloud-init cannot working properly before
boot. Rest of this issue detail is the detail I follow the guideline.

Many thanks :)

1. Tell us your cloud provider

-> Ubuntu 16.04 cloud xenial-amd64 img

2. Any appropriate cloud-init configuration you can provide us

Content-Type: multipart/mixed; boundary="==BOUNDARY=="
MIME-Version: 1.0

--==BOUNDARY==
MIME-Version: 1.0
Content-Type: text/cloud-config; charset="us-ascii"

#cloud-config
users:
  - root
disable_root: False
chpasswd:
  list:
- root:root
  expire: False
hostname: 632b7b18
manage_etc_hosts: true
ssh_pwauth: true
write_files:
 - path: /etc/init.d/ceph-9p-script-0
   content: |
#!/bin/bash
### BEGIN INIT INFO
# Provides: ceph-9p-script-0
# Required-Start: $all
# Required-Stop:
# Default-start: 2 3 5
# Default-stop:
# Short-Description: 9p fileStorage Mount Script
# Description: 9p fileStorage Mount Script
### END INIT INFO

mkdir -p /root/test; mount -t 9p -o trans=virtio,version=9p2000.L
host_share_0 /root/test

 - path: /etc/init.d/startscript
   content: |
#!/bin/bash
### BEGIN INIT INFO
# Provides: startscript
# Required-Start: $all
# Required-Stop:
# Default-start: 2 3 5
# Default-stop:
# Short-Description: Vm Custom Start Script
# Description: Vm Custom Start Script
### END INIT INFO

timeout 5s /root/start.sh
 - path: /root/start.sh
   content: |
#!/bin/bash
touch /root/startTest


runcmd:
 - /bin/bash -c 'if grep -q 10.0.0.2 /etc/resolv.conf; then :; else echo 
"nameserver 10.0.0.2" >> /etc/resolv.conf; fi'
 - /bin/bash -c 'echo 9p 9pnet 9pnet_virtio >> /etc/initramfs-tools/modules; 
sudo update-initramfs -u'
 - /bin/bash -c 'chmod +x /etc/init.d/ceph-9p-script-0; update-rc.d 
ceph-9p-script-0 defaults'


merge_type: 'list(append)+dict(recurse_array,no_replace)+str()'

--==BOUNDARY==--


3. Perform the following on the system and attach it to this bug:

Run:
  cloud-init collect

If your cloud-init does not have that sub command, then please collect:
  dmesg > dmesg.txt
  journalctl -o short-precise > journal.txt
  tar -cvf cloud-init.tar dmesg.txt journal.txt /var/log/cloud-init.log 
/var/log/cloud-init-output.log /run/cloud-init

4. attach cloud-init.tar to this bug.
If you feel that there may be sensitive data involved, consider re-creating on 
a new instance that has no sensitive data.



I attached as a file.

I masked some string for sensitive data. But, it does not matter for
watch you log.

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

** Attachment added: "I followed step 3 and 4"
   
https://bugs.launchpad.net/bugs/1752789/+attachment/5066658/+files/cloud-init.tar

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

Title:
  init rc script not working properly at first boot

Status in cloud-init:
  New

Bug description:
  Hi, I'm newbie on cloud-init. I used qemu-system-x86_64 using kvm and 
cloud-init for provisioning ubuntu-cloud-image.
  I want to file system mount using 9p file system. If I want to use it, I need 
to put my path on the qemu starting command like '-fsdev .. something like 
that' and in the virtual machine, I need to mount using 9p type file system 
using mount command. So, I choose using ubuntu run-level script which is 
writing script on the init.d and use update-rc.d command. When I tried to 
normal script file such as 'touch /blah/blah', it worked properly.

  Also, it wrote successfully into file, and execute that script, it
  works (which means that it can attach 9p-filesystem, just it does not
  work on first time boot).

  However, when I tried to attach 9p-file system. It does not working.
  When I reboot the instance, it successfully attched the file system.
  So, I reasonably consider that cloud-init cannot working properly
  before boot. Rest of this issue detail is the detail I follow the
  guideline.

  Many thanks :)

  1. Tell us your cloud

[Yahoo-eng-team] [Bug 1752711] Re: cloud-init no longer processes user data on GCE in artful

2018-03-01 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init - 18.1-5-g40e77380-0ubuntu1

---
cloud-init (18.1-5-g40e77380-0ubuntu1) bionic; urgency=medium

  * New upstream snapshot.
- GCE: fix reading of user-data that is not base64 encoded. (LP: #1752711)
- doc: fix chef install from apt packages example in RTD.
- Implement puppet 4 support [Romanos Skiadas] (LP: #1446804)
- subp: Fix subp usage with non-ascii characters when no system locale.
  (LP: #1751051)
- salt: configure grains in grains file rather than in minion config.
  [Daniel Wallace]

 -- Chad Smith   Thu, 01 Mar 2018 15:47:04
-0700

** Changed in: cloud-init (Ubuntu Bionic)
   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/1752711

Title:
  cloud-init no longer processes user data on GCE in artful

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Artful:
  Confirmed
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  If I pass in user data like so:

  $ cat cfg
  #!/bin/sh
  touch /tmp/foobar

  $ gcloud compute instances create aa-$(date +%y%m%d-%H%M) --image-family 
ubuntu-1710 --image-project ubuntu-os-cloud-devel --metadata-from-file 
user-data=cfg
  ...

  Then in the instance:

  $ ls /tmp/foobar
  $ sudo cat /var/lib/cloud/instance/user-data.txt
  $ curl 
"http://metadata.google.internal/computeMetadata/v1/instance/attributes/user-data;
 -H "Metadata-Flavor: Google"
  #/bin/sh
  touch /tmp/foobar

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1752711/+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 1751051] Re: UnicodeEncodeError when creating user with non-ascii chars

2018-03-01 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init - 18.1-5-g40e77380-0ubuntu1

---
cloud-init (18.1-5-g40e77380-0ubuntu1) bionic; urgency=medium

  * New upstream snapshot.
- GCE: fix reading of user-data that is not base64 encoded. (LP: #1752711)
- doc: fix chef install from apt packages example in RTD.
- Implement puppet 4 support [Romanos Skiadas] (LP: #1446804)
- subp: Fix subp usage with non-ascii characters when no system locale.
  (LP: #1751051)
- salt: configure grains in grains file rather than in minion config.
  [Daniel Wallace]

 -- Chad Smith   Thu, 01 Mar 2018 15:47:04
-0700

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

Title:
  UnicodeEncodeError when creating user with non-ascii chars

Status in cloud-init:
  Confirmed
Status in subiquity:
  New
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  I was testing subiquity, and at the user creation prompt typed in
  "André D'Silva" for the username, and just "andre" for the login.

  The installer finished fine, but upon first login I couldn't login.
  Booting into rescue mode showed me that the user had not been created.

  Checking cloud-init logs, I find the UnicodeEncodeError.
  2018-02-22 12:44:01,386 - __init__.py[DEBUG]: Adding user andre
  2018-02-22 12:44:01,387 - util.py[WARNING]: Failed to create user andre
  2018-02-22 12:44:01,387 - util.py[DEBUG]: Failed to create user andre
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/distros/__init__.py", line 
463, in add_user
  util.subp(adduser_cmd, logstring=log_adduser_cmd)
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1871, in subp
  env=env, shell=shell)
File "/usr/lib/python3.6/subprocess.py", line 709, in __init__
  restore_signals, start_new_session)
File "/usr/lib/python3.6/subprocess.py", line 1275, in _execute_child
  restore_signals, start_new_session, preexec_fn)
  UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in position 
4: ordinal not in range(128)

  user-data contains this:
  #cloud-config
  hostname: sbqt
  users:
  - gecos: "Andr\xE9 D'Silva"
groups: [adm, cdrom, dip, lpadmin, plugdev, sambashare, debian-tor, 
libvirtd, lxd,
  sudo]
lock-passwd: false
name: andre
passwd: 
$6$UaxxahbQam4Ko1g7$WB5tNuCR84DvWwI7ovxDiofIdLP47pG2USPel2iIQV/qzzT3pAb1VtlbelCR2iCNRxCoJgsVafcNtqdfz1/IL1
shell: /bin/bash
ssh_import_id: ['lp:ahasenack']

  cloud-init is 17.2-34-g644048e3-0ubuntu1 from bionic/main.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1751051/+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 1538565] Re: Guest CPU does not support 1Gb hugepages with explicit models

2018-03-01 Thread Chris Friesen 
In recent versions of qemu the "Skylake-Server" cpu model has the flag,
but any earlier Intel processor models do not.

** Changed in: nova
   Status: Expired => Confirmed

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

Title:
  Guest CPU does not support 1Gb hugepages with explicit models

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  The CPU flag pdpe1gb indicates that the CPU model supports 1 GB
  hugepages - without it, the Linux operating system refuses to allocate
  1 GB huge pages (and other things might go wrong if it did).

  Not all Intel CPU models support 1 GB huge pages, so the qemu options
  -cpu Haswell and -cpu Broadwell give you a vCPU that does not have the
  pdpe1gb flag. This is the correct thing to do, since the VM might be
  running on a Haswell that does not have 1GB huge pages.

  Problem is that Nova flavor extra specs with the libvirt driver for
  qemu/kvm only allow to define the CPU model, either an explicit model
  or "host". The host option means that all CPU flags in the host CPU
  are passed to the vCPU. However, the host option complicates VM
  migration since the CPU would change after migration.

  In conclusion, there is no good way to specify a CPU model that would
  imply the pdpe1gb flag.

  Huge pages are used eg with dpdk. They improve the performance of the
  VM mainly by reducing tlb size.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538565/+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 1752731] [NEW] documentation first installation RH7.4

2018-03-01 Thread Jack Wood 
Public bug reported:

a clean installation on RHEL 7.4 and django.wsgi hangs.  The install doc
needs to add the following lines:

Edit the /etc/httpd/conf.d/openstack-dashboard.conf file and just before
WSGIScriptAlias put:

WSGIApplicationGroup %{GLOBAL}

Otherwise - the openstack-dashboard.conf file that is in the rpm could
be updated so the users wont have to do it...

Thanks

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

Title:
  documentation first installation RH7.4

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  a clean installation on RHEL 7.4 and django.wsgi hangs.  The install
  doc needs to add the following lines:

  Edit the /etc/httpd/conf.d/openstack-dashboard.conf file and just
  before WSGIScriptAlias put:

  WSGIApplicationGroup %{GLOBAL}

  Otherwise - the openstack-dashboard.conf file that is in the rpm could
  be updated so the users wont have to do it...

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1752731/+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 1752736] [NEW] Nova compute dies if it cannot authenticate to RabbitMQ

2018-03-01 Thread Mohammed Naser 
Public bug reported:

At the moment, nova-compute will die if it fails to authenticate to the
messaging cluster and it will not retry on start.  It is possible that
the vhost is not ready yet so it should be handled here:

https://github.com/openstack/nova/blob/stable/pike/nova/conductor/api.py#L61-L78

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

Title:
  Nova compute dies if it cannot authenticate to RabbitMQ

Status in OpenStack Compute (nova):
  New

Bug description:
  At the moment, nova-compute will die if it fails to authenticate to
  the messaging cluster and it will not retry on start.  It is possible
  that the vhost is not ready yet so it should be handled here:

  
https://github.com/openstack/nova/blob/stable/pike/nova/conductor/api.py#L61-L78

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1752736/+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 1752711] Re: cloud-init no longer processes user data on GCE in artful

2018-03-01 Thread Scott Moser 
** Changed in: cloud-init
   Status: New => Confirmed

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

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => High

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Bionic)
   Importance: High
   Status: Confirmed

** Also affects: cloud-init (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Artful)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: cloud-init (Ubuntu Artful)
   Importance: Undecided => Critical

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

Title:
  cloud-init no longer processes user data on GCE in artful

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Artful:
  Confirmed
Status in cloud-init source package in Bionic:
  Confirmed

Bug description:
  If I pass in user data like so:

  $ cat cfg
  #!/bin/sh
  touch /tmp/foobar

  $ gcloud compute instances create aa-$(date +%y%m%d-%H%M) --image-family 
ubuntu-1710 --image-project ubuntu-os-cloud-devel --metadata-from-file 
user-data=cfg
  ...

  Then in the instance:

  $ ls /tmp/foobar
  $ sudo cat /var/lib/cloud/instance/user-data.txt
  $ curl 
"http://metadata.google.internal/computeMetadata/v1/instance/attributes/user-data;
 -H "Metadata-Flavor: Google"
  #/bin/sh
  touch /tmp/foobar

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1752711/+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 1752704] Re: queens missing 'Launch Instance' button on admin panel

2018-03-01 Thread Corey Bryant 
Alright I think this is invalid. I thought this was possible on prior
releases but appears to not be the case.

** Changed in: horizon (Ubuntu)
   Status: New => Invalid

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

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

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

Title:
  queens missing 'Launch Instance' button on admin panel

Status in Ubuntu Cloud Archive:
  Invalid
Status in OpenStack Dashboard (Horizon):
  Invalid
Status in horizon package in Ubuntu:
  Invalid

Bug description:
  In Queens, the admin panel is missing the 'Launch Instance' button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1752704/+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 1752711] [NEW] cloud-init no longer processes user data on GCE in artful

2018-03-01 Thread Dan Watkins 
Public bug reported:

If I pass in user data like so:

$ cat cfg
#!/bin/sh
touch /tmp/foobar

$ gcloud compute instances create aa-$(date +%y%m%d-%H%M) --image-family 
ubuntu-1710 --image-project ubuntu-os-cloud-devel --metadata-from-file 
user-data=cfg
...

Then in the instance:

$ ls /tmp/foobar
$ sudo cat /var/lib/cloud/instance/user-data.txt
$ curl 
"http://metadata.google.internal/computeMetadata/v1/instance/attributes/user-data;
 -H "Metadata-Flavor: Google"
#/bin/sh
touch /tmp/foobar

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

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

Title:
  cloud-init no longer processes user data on GCE in artful

Status in cloud-init:
  New

Bug description:
  If I pass in user data like so:

  $ cat cfg
  #!/bin/sh
  touch /tmp/foobar

  $ gcloud compute instances create aa-$(date +%y%m%d-%H%M) --image-family 
ubuntu-1710 --image-project ubuntu-os-cloud-devel --metadata-from-file 
user-data=cfg
  ...

  Then in the instance:

  $ ls /tmp/foobar
  $ sudo cat /var/lib/cloud/instance/user-data.txt
  $ curl 
"http://metadata.google.internal/computeMetadata/v1/instance/attributes/user-data;
 -H "Metadata-Flavor: Google"
  #/bin/sh
  touch /tmp/foobar

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1752711/+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 1752704] Re: queens issues with 'Launch Instance' and 'Delete Instances' admin panel buttons

2018-03-01 Thread Corey Bryant 
** Attachment added: "horizon screenshot"
   
https://bugs.launchpad.net/horizon/+bug/1752704/+attachment/5066418/+files/horizon_stable_queens_tempest.png

** Also affects: horizon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Description changed:

- In Queens, the admin panel is missing the 'Launch Instance' button and
- the 'Delete Instances' button is disabled. I'll attach a screenshot from
- a devstack deployment. The screenshot unfortunately doesn't capture my
- mouse which better shows the disabled button.
+ In Queens, the admin panel is missing the 'Launch Instance' button.

** Summary changed:

- queens issues with 'Launch Instance' and 'Delete Instances' admin panel 
buttons
+ queens missing 'Launch Instance' button on admin panel

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

Title:
  queens missing 'Launch Instance' button on admin panel

Status in Ubuntu Cloud Archive:
  New
Status in OpenStack Dashboard (Horizon):
  New
Status in horizon package in Ubuntu:
  New

Bug description:
  In Queens, the admin panel is missing the 'Launch Instance' button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1752704/+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 1752704] [NEW] queens missing 'Launch Instance' button on admin panel

2018-03-01 Thread Corey Bryant 
Public bug reported:

In Queens, the admin panel is missing the 'Launch Instance' button.

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

** Affects: horizon
 Importance: Undecided
 Status: New

** Affects: horizon (Ubuntu)
 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/1752704

Title:
  queens missing 'Launch Instance' button on admin panel

Status in Ubuntu Cloud Archive:
  New
Status in OpenStack Dashboard (Horizon):
  New
Status in horizon package in Ubuntu:
  New

Bug description:
  In Queens, the admin panel is missing the 'Launch Instance' button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1752704/+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 1752660] Re: keystone requires cffi to be installed for fernat tokens

2018-03-01 Thread Corey Bryant 
Hi Graham,

Thanks for reporting this. It would be good if this was specified in
upstream keystone's requirements as well, so adding upstream to the bug.

Thanks,
Corey

** Changed in: cloud-archive
   Status: New => Triaged

** Also affects: keystone
   Importance: Undecided
   Status: New

** Also affects: keystone (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: keystone (Ubuntu)
   Status: New => Triaged

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

Title:
  keystone requires cffi to be installed for fernat tokens

Status in Ubuntu Cloud Archive:
  Triaged
Status in OpenStack Identity (keystone):
  New
Status in keystone package in Ubuntu:
  Triaged

Bug description:
  When installing keystone (via apt-get install keystone) apt does not
  install python-cffi, which is required for keystone to implement
  fernat tokens (the current recommended token type)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: keystone 2:13.0.0-0ubuntu1~cloud0 [origin: Canonical]
  Uname: Linux 4.4.88-mainline-rev1 x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB:
   {
  "impl": "launchpad",
  "project": "cloud-archive",
  "bug_pattern_url": 
"http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml;,
   }
  Date: Thu Mar  1 17:19:34 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: keystone
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.keystone.keystone.conf: 2018-03-01T16:51:52.734036

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1752660/+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 1746608] Re: Nova not always using get to access driver capabilites dict

2018-03-01 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/539715
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=2dd322a64291c20da33f28fd5c302ff27e70eae4
Submitter: Zuul
Branch:master

commit 2dd322a64291c20da33f28fd5c302ff27e70eae4
Author: esberglu 
Date:   Wed Jan 31 16:29:57 2018 -0600

Use dict.get() when accessing capabilities dict

Many compute drivers override the driver capabilities dict [1]. The
code should be using dict.get() to avoid throwing KeyErrors if the
overriding dictionaries do not have the corresponding keys. If the
key is not found it will be assumed the the capability is not supported
and default to false. This ensures that no drivers are broken because
they are missing a capability.

[1] 
https://github.com/openstack/nova/blob/5251f18d87/nova/virt/driver.py#L124-L134

Change-Id: I1fa04fa110f2c65e10c065c61f2f0f58c1fad646
Closes-Bug: #1746608


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

Title:
  Nova not always using get to access driver capabilites dict

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  When accessing the capabilities dict [1], nova should be using
  dict.get(). Since many compute drivers override the capabilities
  dictionary,

  capabilites['capability']

  will fail with a KeyError if their dictionary has not been updated to
  include the capability. By using get() it will default instead of
  throwing the KeyError.

  [1]
  
https://github.com/openstack/nova/blob/5251f18d87/nova/virt/driver.py#L124-L134

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1746608/+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 1752604] [NEW] Tabs may not appear in angular instance wizard

2018-03-01 Thread David Gutman 
Public bug reported:

In the launch instance wizard, when a specific tab is disabled (by
example not matching the required policy) then some other tabs may not
be displayed.

After a long analysis :
Each tabs resolved itself if it should or shouldn't be displayed (ready or 
not). But at the first rejection  (first tab ready=false), the wizard will 
display all "ready" tabs without waiting for other tabs to be ready or not. 
If all tabs had been resolved before the first reject, the display is correct, 
but sometimes when the reject finishes first, a lot of tabs are missing.

This bugs is not current because I think it is not common to hide tabs.

** Affects: horizon
 Importance: Undecided
 Assignee: David Gutman (david.gutman)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => David Gutman (david.gutman)

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

Title:
  Tabs may not appear in angular instance wizard

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In the launch instance wizard, when a specific tab is disabled (by
  example not matching the required policy) then some other tabs may not
  be displayed.

  After a long analysis :
  Each tabs resolved itself if it should or shouldn't be displayed (ready or 
not). But at the first rejection  (first tab ready=false), the wizard will 
display all "ready" tabs without waiting for other tabs to be ready or not. 
  If all tabs had been resolved before the first reject, the display is 
correct, but sometimes when the reject finishes first, a lot of tabs are 
missing.

  This bugs is not current because I think it is not common to hide
  tabs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1752604/+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 1750728] Re: api-ref: Missing a response code in resource provider API

2018-03-01 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/546494
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=b2cf359491a7609b9c634450e36cf5f8e19feac1
Submitter: Zuul
Branch:master

commit b2cf359491a7609b9c634450e36cf5f8e19feac1
Author: Takashi NATSUME 
Date:   Wed Feb 21 14:36:04 2018 +0900

[placement] api-ref: Fix a missing response code

In "List resource providers" API,
a 400 badRequest is missing in API reference.
So add it.

Change-Id: I92fcbd6bc1477dd0fe6554c0ba631b9cb7d6fa53
Closes-Bug: #1750728


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

Title:
  api-ref:  Missing a response code in resource provider API

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  400 is missing in "List resource providers" API

  https://developer.openstack.org/api-ref/placement/#resource-providers
  
https://github.com/openstack/nova/blob/c9087bd6c5ed0ec0e7c8fcd8f48c1fcb9f3d6a4a/nova/api/openstack/placement/handlers/resource_provider.py#L214

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1750728/+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 1742584] Re: nova reset-state does not work : Reset state for server "" failed: Policy doesn't allow os_compute_api:os-admin-actions:reset_state to be performed

2018-03-01 Thread Takashi NATSUME 
It seems an issue on nova side (policy configuration).
Needs nova version and policy configuration file (policy.yaml).


** Changed in: python-novaclient
   Status: New => Incomplete

** Also affects: nova
   Importance: Undecided
   Status: New

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

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

Title:
  nova reset-state does not work : Reset state for server "" failed:
  Policy doesn't allow os_compute_api:os-admin-actions:reset_state to be
  performed

Status in OpenStack Compute (nova):
  Incomplete
Status in python-novaclient:
  Incomplete

Bug description:
  According to openstack admin guide document, server reset stat should
  but it fails to reset.

  nova reset-state --active vmname or id

  Error throws like

  Reset state for server "vmname" failed: Policy doesn't allow 
os_compute_api:os-admin-actions:reset_state to be performed. (HTTP 403) 
(Request-ID: req-c8ee6de5-fa79-410b-91e1-9d3241415353)
  ERROR (CommandError): Unable to reset the state for the specified server(s).

  
  Dubug details:

  [root@controller-newton nova]# nova reset-state --active QA_Hyb_Config01
  Reset state for server QA_Hyb_Config01 failed: Policy doesn't allow 
os_compute_api:os-admin-actions:reset_state to be performed. (HTTP 403) 
(Request-ID: req-af1e7d59-87ba-4ee3-a048-6ed5de252c02)
  ERROR (CommandError): Unable to reset the state for the specified server(s).
  [root@controller-newton nova]# nova --debug --os-tenant-name hybrid 
--os-username hybrid reset-state QA_Hyb_Config01
  DEBUG (extension:157) found extension EntryPoint.parse('v2token = 
keystoneauth1.loading._plugins.identity.v2:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oauth1 = 
keystoneauth1.extras.oauth1._loading:V3OAuth1')
  DEBUG (extension:157) found extension EntryPoint.parse('admin_token = 
keystoneauth1.loading._plugins.admin_token:AdminToken')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcauthcode = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuthorizationCode')
  DEBUG (extension:157) found extension EntryPoint.parse('v2password = 
keystoneauth1.loading._plugins.identity.v2:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3samlpassword = 
keystoneauth1.extras._saml2._loading:Saml2Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3password = 
keystoneauth1.loading._plugins.identity.v3:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcaccesstoken = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAccessToken')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcpassword = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
  DEBUG (extension:157) found extension EntryPoint.parse('v3kerberos = 
keystoneauth1.extras.kerberos._loading:Kerberos')
  DEBUG (extension:157) found extension EntryPoint.parse('token = 
keystoneauth1.loading._plugins.identity.generic:Token')
  DEBUG (extension:157) found extension 
EntryPoint.parse('v3oidcclientcredentials = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectClientCredentials')
  DEBUG (extension:157) found extension EntryPoint.parse('v3tokenlessauth = 
keystoneauth1.loading._plugins.identity.v3:TokenlessAuth')
  DEBUG (extension:157) found extension EntryPoint.parse('v3token = 
keystoneauth1.loading._plugins.identity.v3:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('v3totp = 
keystoneauth1.loading._plugins.identity.v3:TOTP')
  DEBUG (extension:157) found extension EntryPoint.parse('password = 
keystoneauth1.loading._plugins.identity.generic:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3fedkerb = 
keystoneauth1.extras.kerberos._loading:MappedKerberos')
  DEBUG (extension:157) found extension EntryPoint.parse('token_endpoint = 
openstackclient.api.auth_plugin:TokenEndpoint')
  DEBUG (session:337) REQ: curl -g -i -X GET http://192.168.84.11:35357/v3 -H 
"Accept: application/json" -H "User-Agent: nova keystoneauth1/2.12.2 
python-requests/2.11.1 CPython/2.7.5"
  INFO (connectionpool:214) Starting new HTTP connection (1): 192.168.84.11
  DEBUG (connectionpool:401) "GET /v3 HTTP/1.1" 200 253
  DEBUG (session:366) RESP: [200] Date: Thu, 11 Jan 2018 00:36:29 GMT Server: 
Apache/2.4.6 (CentOS) mod_wsgi/3.4 Python/2.7.5 Vary: X-Auth-Token 
x-openstack-request-id: req-1905db04-30fc-43fa-a27f-b790a6091721 
Content-Length: 253 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive 
Content-Type: application/json
  RESP BODY: {"version": {"status": "stable", "updated": 
"2016-10-06T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v3+json"}], "id": "v3.7", "links": 
[{"href": "http://192.168.84.11:35357/v3/;, "rel": "self"}]}}

  DEBUG (base:165) Making authentication