[Bug 1374663] Re: [SRU] agent/linux/ip_lib.py does not correctly handle output from 'iproute2' command

[Shane Peters]

** Changed in: cloud-archive/icehouse
 Assignee: Shane Peters (shaner) => (unassigned)

** Changed in: neutron (Ubuntu Trusty)
 Assignee: Shane Peters (shaner) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374663

Title:
  [SRU] agent/linux/ip_lib.py does not correctly handle output from
  'iproute2' command

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781039] Re: GCE cloudinit and ubuntu keys from metadata to ubuntu authorized_keys

[Shane Peters]

** Tags added: sts-sponser

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781039

Title:
  GCE cloudinit and ubuntu keys from metadata to ubuntu authorized_keys

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781039] Re: GCE cloudinit and ubuntu keys from metadata to ubuntu authorized_keys

[Shane Peters]

Updated SRU template. Let me know if there's anything I'm missing.

** Description changed:

- Per documentation at https://wiki.ubuntu.com/GoogleComputeEngineSSHKeys
- ssh keys for cloudinit and ubuntu users should both be added to the
- 'ubuntu' users authorized_keys file.
+ [Impact]
+ 
+  * Per documentation at
+ https://wiki.ubuntu.com/GoogleComputeEngineSSHKeys ssh keys for
+ cloudinit and ubuntu users should both be added to the 'ubuntu' users
+ authorized_keys file.
+ 
+  * This works fine in Xenial (16.04) and higher, but doesn't work for
+ Trusty (14.04).
  
  
- This works fine in Xenial (16.04) and higher, but doesn't work for Trusty 
(14.04).
+ [Test Case]
+ 
+  * Create a file that contains ssh public keys
+ 
+$ cat googlekeys
+test:ssh-rsa  t...@example.com
+ubuntu:ssh-rsa  t...@example.com
+cloudinit:ssh-rsa  t...@example.com
+   
+   * Create an ubuntu 14.04 instance
+   
+ gcloud compute instances create ubuntu1404cloudinit --image-family 
ubuntu-1404-lts --image-project ubuntu-os-cloud 
--metadata-from-file=ssh-keys=googlekeys --metadata=block-project-ssh-keys=True
+   
+   * Create an ubuntu 16.04 instance
+   
+ gcloud compute instances create ubuntu1604cloudinit --image-family 
ubuntu-1604-lts --image-project ubuntu-os-cloud 
--metadata-from-file=ssh-keys=googlekeys --metadata=block-project-ssh-keys=True
+ 
+   * Notice that the ubuntu user in the ubuntu 14.04 instance contains no keys 
from cloud-init (the keys there are added by the google daemon):
+ 
+ $ sudo cat /home/ubuntu/.ssh/authorized_keys
+ # Added by Google
+ ssh-rsa  
t...@example.com
+   
+   * However, in 16.04,
+   
+ $ sudo cat /home/ubuntu/.ssh/authorized_keys
+ ssh-rsa  t...@example.com
+ ssh-rsa  t...@example.com
+ # Added by Google
+ ssh-rsa  
t...@example.com
  
  
- [REPRODUCE] 
+ [Regression Potential] 
  
- # create a file that contains ssh public keys
+  * DatasourceGCE.py is heavily modified to fix this behavior in 14.04.
+ That said, there is a medium amount of regression potential when using
+ the GCE datasource. More specificallly, there is now stricter checking
+ of the metadata source when used(platform_check=True).
  
- $ cat googlekeys 
- test:ssh-rsa  t...@example.com 
- ubuntu:ssh-rsa  t...@example.com 
- cloudinit:ssh-rsa  t...@example.com 
- 
- 
- # create an ubuntu 14.04 instance 
- 
- gcloud compute instances create ubuntu1404cloudinit --image-family
- ubuntu-1404-lts --image-project ubuntu-os-cloud --metadata-from-file
- =ssh-keys=googlekeys --metadata=block-project-ssh-keys=True
- 
- # create an ubuntu 16.04 instance
- 
- gcloud compute instances create ubuntu1604cloudinit --image-family
- ubuntu-1604-lts --image-project ubuntu-os-cloud --metadata-from-file
- =ssh-keys=googlekeys --metadata=block-project-ssh-keys=True
- 
- 
- Notice that the ubuntu user in the ubuntu 14.04 instance contains no
- keys from cloud-init (the keys there are added by the google daemon):
- 
- $ sudo cat /home/ubuntu/.ssh/authorized_keys 
- # Added by Google 
- ssh-rsa  t...@example.com 
- 
- 
- In 16.04, 
- 
- $ sudo cat /home/ubuntu/.ssh/authorized_keys 
- ssh-rsa  t...@example.com 
- ssh-rsa  t...@example.com 
- # Added by Google 
- ssh-rsa  t...@example.com 
- 
- 
- [EXPECTED BEHAVIOR]
- 
- The ubuntu and cloudinit keys in metadata should be added to the ubuntu
- user by cloud-init.
+  * Significant testing has been completed via the Google Compute
+ platform as well as other none-GCE datasources (lxd) to confirm
+ functionality and to test for possible regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781039

Title:
  GCE cloudinit and ubuntu keys from metadata to ubuntu authorized_keys

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781039] Re: GCE cloudinit and ubuntu keys from metadata to ubuntu authorized_keys

[Shane Peters]

Hi Scott,
Thanks for the guidance! I think I got it now, let me know if you see the merge 
proposal.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781039

Title:
  GCE cloudinit and ubuntu keys from metadata to ubuntu authorized_keys

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781039] Re: GCE cloudinit and ubuntu keys from metadata to ubuntu authorized_keys

[Shane Peters]

I've tested a "first boot" scenario using a customised image with this patched 
cloud-init and it works as expected (you can see both cloudinit and ubuntu keys 
above the 'Added by google' comment).

$ cat googlekeys 
carbon:ssh-rsa BZCRI2M shaner@carbon
ubuntu:ssh-rsa B65Otq/ shaner@ubuntu
cloudinit:ssh-rsa ..6s3oSv shaner@cloudinit

# USING CUSTOM IMAGE WITH UPGRADED CLOUD-INIT
#
$ gcloud compute instances create trusty1 --image custom-cloud-init 
--image-project firm-lacing-209716 --metadata-from-file=ssh-keys=googlekeys 
--metadata=block-project-ssh-keys=True
$ ssh ubuntu@x.x.x.x cat .ssh/authorized_keys
ssh-rsa B65Otq/ shaner@ubuntu
ssh-rsa ..6s3oSv shaner@cloudinit
# Added by Google
ssh-rsa B65Otq/ shaner@ubuntu


# USING EXISTING IMAGE

$ gcloud compute instances create trust2 --image-family ubuntu-1404-lts 
--image-project ubuntu-os-cloud --metadata-from-file=ssh-keys=googlekeys 
--metadata=block-project-ssh-keys=True

$ ssh ubuntu@${IP} cat .ssh/authorized_keys
# Added by Google
ssh-rsa B.z65Otq/ shaner@ubuntu

$ scp cloud-init_0.7.5-0ubuntu1.23_all.deb ubuntu@${IP}:~/
$ ssh ubuntu@${IP} sudo dpkg -i cloud-init_0.7.5-0ubuntu1.23_all.deb
$ ssh ubuntu@${IP} sudo rm -rf /var/lib/cloud/instances
$ ssh ubuntu@${IP} sudo reboot
$ ssh ubuntu@${IP} cat .ssh/authorized_keys
ssh-rsa .6s3oSv shaner@cloudinit
# Added by Google
ssh-rsa B65Otq/ shaner@ubuntu


You'll notice in this second example, the 'ubuntu' key from my googlekeys file 
isn't added on top like you would expect if the image had an upgraded 
cloud-init. This is because the code is duplicate checking and won't add a key 
if it already exists.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781039

Title:
  GCE cloudinit and ubuntu keys from metadata to ubuntu authorized_keys

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781039] Re: GCE cloudinit and ubuntu keys from metadata to ubuntu authorized_keys

[Shane Peters]

** Patch added: "lp-1781039-gce-datasource-update.patch"
   
https://bugs.launchpad.net/ubuntu/trusty/+source/cloud-init/+bug/1781039/+attachment/5172307/+files/lp-1781039-gce-datasource-update.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781039

Title:
  GCE cloudinit and ubuntu keys from metadata to ubuntu authorized_keys

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1613900] Re: Unable to use 'Any' availability zone when spawning instance

[Shane Peters]

** Tags removed: verification-mitaka-needed verification-needed
** Tags added: verification-done verification-done-mitaka

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613900

Title:
  Unable to use 'Any' availability zone when spawning instance

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725421] Re: [mitaka] Hide nova lock/unlock if nova api <2.9 and when >= 2.9, "Lock/Unlock Instance" should not be shown at same time.

[Shane Peters]

Currently working on verification. I'm running into an issue where the
(mitaka) nova-api isn't returning the 'locked' field which this patch
relies on.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725421

Title:
  [mitaka] Hide nova lock/unlock if nova api <2.9 and when >= 2.9,
  "Lock/Unlock Instance" should not be shown at same time.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1613900] Re: Unable to use 'Any' availability zone when spawning instance

[Shane Peters]

** Tags removed: verification-mitaka-needed verification-needed 
verification-needed-xenial
** Tags added: verification-done verification-done-xenial 
verification-mitaka-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613900

Title:
  Unable to use 'Any' availability zone when spawning instance

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725421] Re: [mitaka] Nova lock/unlock should be hidden if nova api <2.9

[Shane Peters]

** Description changed:

  [Impact]
  
  * Similar/related to lp:1505845, which was fixed for Newton.
-   Lock/unlock options are displayed in Horizon despite Nova API <2.9,
-   which causes user confusion.
+   Lock/unlock options are displayed in Horizon despite Nova API <2.9,
+   which causes user confusion.
  
  [Test Case]
  
- * Create a new instance and you will see both "Lock Instance" and "Unlock
-   Instance" are available. Only one of them should be applicable at the
-   time.
+   1. Log into Horizon dashboard.
+   2. Create new instance.
+   3. Wait for instance to switch to 'running' state.
+   4. On the newly created instance, under Actions, you'll
+  see both 'Lock Instance' and 'Unlock Instance' are
+  available, even after locking the instance.
  
  [Regression Potential]
  
  * Regression potential is low. This bug has been fixed in all releases of
-   OpenStack starting with Newton. The patch did have to be modified
-   slightly to apply to mitaka.
+   OpenStack starting with Newton. The patch did have to be modified
+   slightly to apply to mitaka.
  
  [Discussion]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725421

Title:
  [mitaka] Nova lock/unlock should be hidden if nova api <2.9

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725421] Re: [mitaka] Nova lock/unlock should be hidden if nova api <2.9

[Shane Peters]

** Description changed:

- Similar/related to lp:1505845, which was fixed for Newton.  Lock/unlock
- options are displayed in Horizon despite Nova API <2.9, causing user
- confusion.
+ [Impact]
  
- Xenial, Mitaka, 17.02 charms, OSD is 2:9.1.2-0ubuntu1, Nova API
- CURRENT=2.1.
+ * Similar/related to lp:1505845, which was fixed for Newton.
+   Lock/unlock options are displayed in Horizon despite Nova API <2.9,
+   which causes user confusion.
+ 
+ [Test Case]
+ 
+ * Create a new instance and you will see both "Lock Instance" and "Unlock
+   Instance" are available. Only one of them should be applicable at the
+   time.
+ 
+ [Regression Potential]
+ 
+ * Regression potential is low. This bug has been fixed in all releases of
+   OpenStack starting with Newton. The patch did have to be modified
+   slightly to apply to mitaka.
+ 
+ [Discussion]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725421

Title:
  [mitaka] Nova lock/unlock should be hidden if nova api <2.9

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1613900] Re: Unable to use 'Any' availability zone when spawning instance

[Shane Peters]

Thanks Corey!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613900

Title:
  Unable to use 'Any' availability zone when spawning instance

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1613900] Re: Unable to use 'Any' availability zone when spawning instance

[Shane Peters]

Backport of patch to Mitaka for Ubuntu Cloud Archive.

** Patch added: "horizon_9.1.2-0ubuntu4.patch"
   
https://bugs.launchpad.net/horizon/+bug/1613900/+attachment/5030577/+files/horizon_9.1.2-0ubuntu4.patch

** Changed in: horizon (Ubuntu)
 Assignee: (unassigned) => Shane Peters (shaner)

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

** Changed in: horizon (Ubuntu)
Milestone: None => xenial-updates

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613900

Title:
  Unable to use 'Any' availability zone when spawning instance

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1613900] Re: Unable to use 'Any' availability zone when spawning instance

[Shane Peters]

** Changed in: cloud-archive
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613900

Title:
  Unable to use 'Any' availability zone when spawning instance

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725421] Re: [mitaka] Nova lock/unlock should be hidden if nova api <2.9

[Shane Peters]

** Patch added: "fix_1725421.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1725421/+attachment/5021439/+files/fix_1725421.debdiff

** Changed in: horizon (Ubuntu)
   Status: Triaged => In Progress

** Changed in: horizon (Ubuntu)
Milestone: None => xenial-updates

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725421

Title:
  [mitaka] Nova lock/unlock should be hidden if nova api <2.9

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725421] Re: [mitaka] Nova lock/unlock should be hidden if nova api <2.9

[Shane Peters]

** Changed in: horizon (Ubuntu)
 Assignee: (unassigned) => Shane Peters (shaner)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725421

Title:
  [mitaka] Nova lock/unlock should be hidden if nova api <2.9

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1710917] Re: ability to disable apache mod_status

[Shane Peters]

** Changed in: openstack-dashboard (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710917

Title:
  ability to disable apache mod_status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openstack-dashboard/+bug/1710917/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1710917] Re: ability to disable apache mod_status

[Shane Peters]

** Changed in: openstack-dashboard (Ubuntu)
 Assignee: (unassigned) => Shane Peters (shaner)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710917

Title:
  ability to disable apache mod_status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openstack-dashboard/+bug/1710917/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1710917] Re: ability to disable apache mod_status

[Shane Peters]

Perhaps it would be better to have this fix in charmhelpers apache
hardening code.

** Tags added: sts

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710917

Title:
  ability to disable apache mod_status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openstack-dashboard/+bug/1710917/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1710917] [NEW] ability to disable apache mod_status

[Shane Peters]

Public bug reported:

The openstack-dashboard /server-status page is accessible by default.
While useful for some, the existence of the this page may be considered
a vulnerability.

The workaround for this would be to execute 'a2dismod status && service
restart apache2' on the openstack-dashboard unit.

Suggest making this a charm option, enabled by default.

** Affects: openstack-dashboard (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710917

Title:
  ability to disable apache mod_status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openstack-dashboard/+bug/1710917/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1647875] [NEW] nodes out of sync - assertion failure in fil0fil.c

[Shane Peters]

Public bug reported:

Description

==
After deploying three three nodes inside LXC containers on ppc64, two eventually
die off with the below after some time:

161203  1:23:32 [Note] WSREP: Quorum results:
version= 2,
component  = PRIMARY,
conf_id= 3,
members= 2/2 (joined/total),
act_id = 11574,
last_appl. = 11546,
protocols  = 0/4/2 (gcs/repl/appl),
group UUID = 662a7e74-b8ea-11e6-835c-93f3e79b4cfa
161203  1:23:32 [Note] WSREP: Flow-control interval: [23, 23]
161203  1:23:33 [Note] WSREP: New cluster view: global state: 
662a7e74-b8ea-11e6-835c-93f3e79b4cfa:11574, view# 4: Primary, number of nodes: 
2, my index: 0, protocol version 2
161203  1:23:33 [Note] WSREP: wsrep_notify_cmd is not defined, skipping 
notification.
161203  1:23:33 [Note] WSREP: Assign initial position for certification: 11574, 
protocol version: 2
161203  1:23:38 [Note] WSREP:  cleaning up 8b3e9500-b8ea-11e6-b511-179fa3961d2c 
(tcp://10.0.0.193:4567)
161203  5:50:42  InnoDB: Assertion failure in thread 70365577277824 in file 
fil0fil.c line 5288
InnoDB: Failing assertion: node->n_pending > 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
05:50:42 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.
Please help us make Percona XtraDB Cluster better by reporting any
bugs at  https://bugs.launchpad.net/percona-xtradb-cluster

key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=423
max_threads=3002
thread_count=422
connection_count=422
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6603710 K 
 bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x4
/usr/sbin/mysqld(my_print_stacktrace+0x44)[0x52c5b114]
/usr/sbin/mysqld(handle_fatal_signal+0x500)[0x52aa6e20]
[0x3fffa9e60478]
/lib/powerpc64le-linux-gnu/libc.so.6(gsignal+0x48)[0x3fffa96b0ae8]
/lib/powerpc64le-linux-gnu/libc.so.6(abort+0x26c)[0x3fffa96b699c]
/usr/sbin/mysqld(+0x7643c0)[0x52d743c0]
/usr/sbin/mysqld(+0x771d34)[0x52d81d34]
/usr/sbin/mysqld(+0x6c2a08)[0x52cd2a08]
/lib/powerpc64le-linux-gnu/libpthread.so.0(+0x89a4)[0x3fffa9d489a4]
/lib/powerpc64le-linux-gnu/libc.so.6(clone+0x98)[0x3fffa978f400]
You may download the Percona XtraDB Cluster operations manual by visiting
http://www.percona.com/software/percona-xtradb-cluster/. You may find 
information
in the manual which will help you identify the cause of the crash.
161203 05:50:42 mysqld_safe Number of processes running now: 0
161203 05:50:42 mysqld_safe WSREP: not restarting wsrep node automatically
161203 05:50:42 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid 
ended


Environment
===
Trusty 14.04.5 LTS ppc64el

** Affects: percona-xtradb-cluster-5.5 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: sts

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647875

Title:
  nodes out of sync - assertion failure in fil0fil.c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.5/+bug/1647875/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1374663] Re: [SRU] agent/linux/ip_lib.py does not correctly handle output from 'iproute2' command

[Shane Peters]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374663

Title:
  [SRU] agent/linux/ip_lib.py does not correctly handle output from
  'iproute2' command

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1374663] Re: [SRU] agent/linux/ip_lib.py does not correctly handle output from 'iproute2' command

[Shane Peters]

I can confirm this bug is fixed in trusty/icehouse using kernel linux-
image-generic-lts-xenial.

Installed: 1:2014.1.5-0ubuntu7

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374663

Title:
  [SRU] agent/linux/ip_lib.py does not correctly handle output from
  'iproute2' command

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1374663] Re: agent/linux/ip_lib.py does not correctly handle output from 'iproute2' command

[Shane Peters]

Corey,
  I appreciate the feedback! Here's an updated patch.

** Patch added: "lp1374663.debdiff"
   
https://bugs.launchpad.net/neutron/+bug/1374663/+attachment/4772061/+files/lp1374663.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374663

Title:
  agent/linux/ip_lib.py does not correctly handle output from 'iproute2'
  command

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1374663] Re: agent/linux/ip_lib.py does not correctly handle output from 'iproute2' command

[Shane Peters]

** Changed in: neutron (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374663

Title:
  agent/linux/ip_lib.py does not correctly handle output from 'iproute2'
  command

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1374663] Re: agent/linux/ip_lib.py does not correctly handle output from 'iproute2' command

[Shane Peters]

Patch for neutron_2014.1.5-0ubuntu6

** Patch added: "trusty_lp1374663.debdiff"
   
https://bugs.launchpad.net/neutron/+bug/1374663/+attachment/4770768/+files/trusty_lp1374663.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374663

Title:
  agent/linux/ip_lib.py does not correctly handle output from 'iproute2'
  command

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1374663] Re: agent/linux/ip_lib.py does not correctly handle output from 'iproute2' command

[Shane Peters]

** Description changed:

- The get_devices() method in neutron/agent/linux/ip_lib.py chokes if
- 'iproute2' presents interface names containing '@', such as ipip
- tunnels:
+ [Impact]
  
- 513: tunl0@NONE:  mtu 1480 qdisc noop state DOWN mode DEFAULT 
group default 
- link/ipip 0.0.0.0 brd 0.0.0.0
+  * The get_devices() method in neutron/agent/linux/ip_lib.py chokes if 
'iproute2' presents interface names containing '@', such as ipip tunnels and 
macvlan devices:
+   
+   tunl0@NONE:  mtu 1480 qdisc noop state DOWN mode DEFAULT 
group default
+   clone@eth0:  mtu 1454 qdisc noop state 
DOWN mode DEFAULT
+ 
+   * The mere presence of one of the above interface names will cause the
+ code to fail with:
  
- And macvlan devices:
+   RuntimeError:
+   Command: ['ip', 'addr', 'show', 'tunl0@NONE']
+   Exit code: 1
+   Stdout: ''
+   Stderr: 'Device "tunl0@NONE" does not exist.\n'
  
- 4: clone@eth0:  mtu 1454 qdisc noop state DOWN mode 
DEFAULT group default 
- link/ether c6:dd:66:a5:f6:5c brd ff:ff:ff:ff:ff:ff
  
- Consider the follow sample code:
+ [Test Case]
  
- from neutron.agent.linux.ip_lib import IPWrapper
+  * This has been seen in the vpn_agent.log after upgrading to a xenial kernel 
(4.4.0-45-generic) in a trusty/icehouse environment.
+
+ /var/log/neutron/vpn_agent.log:
+ ERROR neutron.agent.linux.interface [-] Failed unplugging interface   
'qg-e75da35-63@if10' 
  
- ip = IPWrapper()
- for iface in ip.get_devices():
- print iface.name, iface.addr.list()
  
- The mere presence of one of the above interface names will cause the
- code to fail with:
+ [Regression Potential]
  
- RuntimeError: 
- Command: ['ip', 'addr', 'show', 'tunl0@NONE']
- Exit code: 1
- Stdout: ''
- Stderr: 'Device "tunl0@NONE" does not exist.\n'
+   * iproute2 is still used, however, a search path was added
+ (/sys/class/net) which returns the interfaces without the '@'.
  
- This can cause failures in, e.g.,
- neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py, which
- performs almost exactly the same iteration in the
- get_interface_by_ip() method.
+   * This has been fixed since Kilo so there is minimal regression
+ potential.
+ 
+ 
+ [ Other Info ]
+ 
+   *

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374663

Title:
  agent/linux/ip_lib.py does not correctly handle output from 'iproute2'
  command

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs