Bump this is also affecting us causing quite a lot of downtime just to
add a vlan interface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052137
Title:
bonded link goes down on reconfigure
To
I honestly don't know if it's been in Rocky or not. The code change
suggests that it got introduced with the system scoping which appeared
in Stein as far as I know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No. I'm not affiliated with any organisation in this regard. Just like
the Octavia OSSA haha.
Thanks for asking tho :)
On December 5, 2019 5:57:21 PM UTC, Jeremy Stanley wrote:
>Daniel, is there any organization you want credited along with you for
>reporting this defect?
>
>Gage, I think the
With recent release of OpenStack Train this issue reappears...
Upgrading from Stein to Train will require all VMs to be hard-rebooted
to be migrated as a final step because Live Migration fails with:
Oct 17 10:28:43 h2.1.openstack.r0cket.net libvirtd[1545]: Unable to read from
monitor:
Verified Version 4.0.0-0ubuntu1.2~cloud0
(Hit enter too fast)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847243
Title:
Update Octavia-* packages as per OSSA-2019-005 / CVE-2019-17134
To
cloud-archive/stein tested and working correctly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847243
Title:
Update Octavia-* packages as per OSSA-2019-005 / CVE-2019-17134
To manage
Hi James,
Thanks for the link!
I honestly didn't know that tool existed and neither did the Octavia
Team Members I interacted with.
I will rebuild an image right away and give it a shot.
/Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Update:
Ok, it just can't find amphora-agent because it's looking into the wrong
repositories regardless of the config. My bad. I could find the amphora-agent
package in the repository manually.
/Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Marc,
I'm afraid a patch-fix will not work because amphora images are created
by the end-user using `diskimage-create.sh` which uses pip/git to pull
the agent.
Although I do understand that from a OS Maintainer's perspective this
patch solves the issue outlined in the CVE and keeps aligned to
After another edit, namely a symlink of cloud-init.target into the
multi-user.target.wants directory it finally boots up with cloud-init
and everything work as expected.
This is quite a lot of manual work for something that's presented as
`Ready to use`.
I'd like to contribute to the review/QA
Creating /etc/systemd/network/default.network with contents:
```
[Match]
Type=en*
[Network]
DHCP=yes
```
is a valid workaround. However, cloud-init is still not run for some
reason, but at least the VM now initializes the NICs.
Are these images tested? are the results somewhere reviewable? It
I'm also running into this issue..
using today's https://cloud-
images.ubuntu.com/daily/server/bionic/current/bionic-server-cloudimg-
amd64.img - converted into vmdk and using vmxnet3 or e1000 or e1000e
adapters. In any constellation it does not initialize any interfaces or
attempts any DHCP
** Attachment added: "Console log"
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1761573/+attachment/5174094/+files/d008743c08a84012b6aca41efbe5b456
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- It seems that cloud-init under Zesty is broken when run from vmware.
+ It seems that cloud-init is broken when run from vmware.
It works fine if I trigger it manually via `systemd start cloud-
init.service` and it will find the datasource correctly and set things
Public bug reported:
It seems that cloud-init under Zesty is broken when run from vmware.
It works fine if I trigger it manually via `systemd start cloud-
init.service` and it will find the datasource correctly and set things
up accordingly but it fails to start during bootup.
There's
15 matches
Mail list logo
