I don't believe this is to do with networking-calico, so will mark as
Invalid for networking-calico.
** Changed in: networking-calico
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I honestly don't see any evidence of some broken behaviour in Nova if,
particularly, other instances with other guest image using cloud-init
can boot correctly.
Please provide us some logs or better trace of a potential Nova problem
in order for us to classify the potential root cause and a
In Rocky release I’m not experiencing kind of issues. And make sure you
use kvm and not qemu, cause qemu is limited on its performance and kvm
just born to work with latest hardware :)
Best,
Vasili
Sent from iPhone
> On 14 Jan 2020, at 20:35, Dan Watkins wrote:
>
> Hi Vasili,
>
>> From a
Hi Vasili,
>From a cloud-init perspective, there isn't anything we can do so I'm
going to move the upstream task to Invalid too. I'm afraid I don't
really have any advice on how to proceed, as this appears to be a
hypervisor or cloud issue.
Dan
** Changed in: cloud-init
Status: New =>
There is no nested virtualization, all the openstack on bare metal with
regular installation with regular services, the only thing is running is
calico which is eliminate neutron ml2, metadata and dhcp and its running
with calico plugin, calico-dhcp and calico felix. As well as on each
compute
I'm marking the cloud-init task invalid as at this time the logs point
to a nested virtualization/openstack issue with devices not being
present; not related to cloud-init. If further investigation points to
an issue with cloud-init you can move the cloud-init task back to New.
** Changed in:
Unfortunately no; the kernel messages are very much related to nested
virtualization, but I don't know where in your software stack it gets
configured/enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
mariadb, rabbitmq, memcached, etcd, keystone, glance, neutron, nova,
calico-driver, calico-felix, calico-dhcp, nova-api-metadata, bird
any clue on the issue?
Thanks,
Vasili
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
nope, no devstack nor tripleo.. everything straight forward as I
mentioned previously.. installed all those services manually on
controller and compute and connected to l3 switch with bgp of the bird..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For your Openstack deployment, are you running on baremetal?
Are you deploying something like devstack or triple-o which enable nested
virtualization?
https://docs.openstack.org/devstack/latest/guides/devstack-with-nested-kvm.html
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851552
Title:
since ubuntu 18 bionic release and latest, the ubuntu18 cloud image is
unable to boot up on
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851552
Title:
** Also affects: cloud-init
Importance: Undecided
Status: New
** Also affects: openstack-community
Importance: Undecided
Status: New
** Also affects: qemu
Importance: Undecided
Status: New
** Also affects: qemu-kvm
Importance: Undecided
Status: New
**
** Also affects: nova
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/1851552
Title:
since ubuntu 18 bionic release and latest, the ubuntu18 cloud image is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851552
Title:
Hi,
Thanks for shared investigation details.
According to the setup I use, could you assist to understand where and what I'm
missing here that can lead to the issues you mentioned?
### Working setup details ###
[1] The Openstack service installed on Controller and Compute with Ubuntu
18.04.2
> [[0;1;33mDEPEND[0m] Dependency failed for File System Check on
/dev/vdb.
Looking at the bionic log you posted, it never gets a /dev/vdb device.
Can you confirm that the VM configuration on the compute node correctly
was configured with an ephemeral block device?
Here we can see not all of the
Hi Vasili, unfortunately there isn't enough info in the 16.04 logs to
help us work out what's going on with 18.04. Do you have any way of
accessing an 18.04 instance (serial console, perhaps?) that would allow
you to gather more data?
Moving this back to Incomplete for now, apologies for the
see attached collected cloud init logs from ubuntu xenial..
** Attachment added: "cloud-init collect-logs"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1851552/+attachment/5307512/+files/cloud-init.tar.gz
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
--
Hi.
Please attach the output of 'cloud-init collect-logs'. Ideally from the 18.04
instance, but the 16.04 instance would be fine if you're not able to get it
from 18.04.
Then, set the status of this bug back to New.
thanks.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
correction:
see full log https://etherpad.openstack.org/p/ubuntu-xenial-log for
successful creation of instance with latest ubuntu-xenial cloud image
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-
amd64-disk1.img
see full log
see full log https://etherpad.openstack.org/p/ubuntu-xenial-log for
successful creation of instance with latest ubuntu-xenial cloud image
http://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-
amd64.img
see full log https://etherpad.openstack.org/p/ubuntu-bionic-log for
successful
I used the following official latest ubuntu bionic image:
http://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img
And the regular openstack command:
https://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance-provider.html
openstack server create --flavor
the problem is in:
[[0;32m OK [0m] Started Wait for Network to be Configured.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851552
Title:
since ubuntu 18 bionic release and latest, the ubuntu18
The instance creation was working until calico configured on controller
and compute. Ubuntu 16 and Centos releases are booting up successfully.
As known ubuntu began to work with netplan since 18 and all latest
releases. Not sure the issue with cloud init or the order or timing of
booting process
Hello,
Could you please elaborate a bit more on how you came to the conclusion
that the problem is caused specifically by cloud-init? Without some more
context information it's difficult for us to tell if this is actually a
bug and to begin working on it.
If you think this is actually a problem
26 matches
Mail list logo
