When we try with older versions of LXD (i.e., 2.0.9 and 2.0.10) the instance is created normally, but when we update to newer versions I get the error.Searching for the problem in the logs we found out that there is a Neutron related issue with LXD2.13.Particularly the source of the problem seems to be that the qbr, qvo interfaces to the Linux and integration bridge respectively are not created normally.
![]()
![]() Docker Could Not Generate Persistent Address For No Such File Or Directory Update To NewerDocker Could Not Generate Persistent Address For No Such File Or Directory How To Deal WithCould not generate persistent MAC address for qvb52ecbb0d-f0: No such file or directory Could you tell me how to deal with this issue The reason why we need a newer version of LXD than 2.0.9 or 2.0.10 is because later I need to support a USB passthrough through the virtual instance which is not supported for these old versions. Cinder Volumes for LXD Instances in Ubuntu 16.04.1 Installing nova-lxd on centos Can nova-compute-lxd run lxd instances alongside kvm instances Pike: Is it possible to view the console tab on LXD LXD image server vs glance nova-lxd with ceph storage possible Feedback About This Page Report a bug OpenStack Projects OpenStack Security Common Questions Blog Community User Groups Events Jobs Companies Contribute Documentation OpenStack Manuals Getting Started API Documentation Wiki Branding Legal Logos Guidelines Trademark Policy Privacy Policy OpenStack CLA OpenStack is a trademark of OpenStack Foundation. So maybe its something in the configuration there I would have thought they install a standard Ubuntu but apparently they modify some things. Feb 18 09:42:26 REDACTED systemd-udevd25569: linkconfig: autonegotiation is unset or enabled, the speed and duplex are not writable. Feb 18 09:42:26 REDACTED systemd-udevd25569: Could not generate persistent MAC address for veth9c1a796: No such file or directory. Feb 18 09:42:26 REDACTED systemd-udevd25568: Could not generate persistent MAC address for vethde93f21: No such file or directory. Feb 18 09:42:26 REDACTED containerd447: time2019-02-18T09:42:26.25644596601:00 levelinfo msgshim containerd-shim started addresscontainerd-shimmoby2f890ab51cb6473379880ffc47b5740fe0ac91d07af86439ca57f55d273befccshim.sock debugfalse pid25581. Feb 18 09:42:26 REDACTED containerd447: time2019-02-18T09:42:26.62737119001:00 levelinfo msgshim reaped id2f890ab51cb6473379880ffc47b5740fe0ac91d07af86439ca57f55d273befcc. Feb 18 09:42:26 REDACTED dockerd16966: time2019-02-18T09:42:26.63088683701:00 levelerror msgstream copy error: reading from a closed fifo. Feb 18 09:42:26 REDACTED dockerd16966: time2019-02-18T09:42:26.86476405301:00 levelerror msg2f890ab51cb6473379880ffc47b5740fe0ac91d07af86439ca57f55d273befcc cleanup: failed to delete container from containerd: no such container. Feb 18 09:42:26 REDACTED dockerd16966: time2019-02-18T09:42:26.87394693801:00 levelerror msgHandler for POST v1.39containers2f890ab51cb6473379880ffc47b5740fe0ac91d07af86439ca57f55d273befccstart returned error: OCI runtime create failed: containerlinux.go:344: starting container process caused processlinux.go:297: getting the final childs pid from pipe caused read init-p: connection reset by peer: unknown. Error response from daemon: OCI runtime create failed: containerlinux.go:344: starting container process caused processlinux.go:297: getting the final childs pid from pipe caused read init-p: connection reset by peer: unknown. Feb 18 09:44:01 REDACTED systemd-udevd25652: Could not generate persistent MAC address for vethd29d69f: No such file or directory. Feb 18 09:44:01 REDACTED systemd-udevd25651: linkconfig: autonegotiation is unset or enabled, the speed and duplex are not writable. Feb 18 09:44:01 REDACTED systemd-udevd25651: Could not generate persistent MAC address for vethd000744: No such file or directory. Feb 18 09:44:01 REDACTED containerd447: time2019-02-18T09:44:01.44146118501:00 levelinfo msgshim containerd-shim started addresscontainerd-shimmoby565ba386c40cec5e0c52f72e80ad421ec30f878870311b1557f6e29f46374ad9shim.sock debugfalse pid25664. Feb 18 09:44:01 REDACTED containerd447: time2019-02-18T09:44:01.92181112401:00 levelinfo msgshim reaped id565ba386c40cec5e0c52f72e80ad421ec30f878870311b1557f6e29f46374ad9. Feb 18 09:44:02 REDACTED dockerd16966: time2019-02-18T09:44:01.94998610701:00 levelerror msgstream copy error: reading from a closed fifo. Feb 18 09:44:02 REDACTED dockerd16966: time2019-02-18T09:44:01.95901369701:00 levelerror msgstream copy error: reading from a closed fifo. Feb 18 09:44:02 REDACTED dockerd16966: time2019-02-18T09:44:02.29805805501:00 levelerror msg565ba386c40cec5e0c52f72e80ad421ec30f878870311b1557f6e29f46374ad9 cleanup: failed to delete container from containerd: no such container. Feb 18 09:44:02 REDACTED dockerd16966: time2019-02-18T09:44:02.29813490901:00 levelerror msgHandler for POST v1.39containers565ba386c40cstart returned error: OCI runtime create failed: containerlinux.go:344: starting container process caused processlinux.go:297: getting the final childs pid from pipe caused read init-p: connection reset by peer: unknown. Also a downgrade to 18.09.1 does not work:-( A general Ubuntu LTS problem. The top comment in this ticket ( 597 (comment) ) shows that just starting a hello-world container, without memory-limits set fails, so that doesnt seem to be related at a glance. Possibly the runc CVE fix results in more processes (or threads) to be started, so wondering if thats the underlying cause. Even Ubuntus mainline builds have some sort of suffix on the kernel version. If that assertion is true, then in terms of repeatability 4.4.0-142-generic 597 (comment) seems like more approachable recreate target.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |