** 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
** 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
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
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
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/
** 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
** 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
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.
** 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.
** 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
** 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
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:
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 P
** 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
** 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
--
** 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 n
** 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
** 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_sta
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
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
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=
** 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
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]
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
** 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'
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.
** 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
27 matches
Mail list logo
