← Back to issue list

When cleanbuild starts, the container has no connection and prints an ugly error

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1719952
Type
issue
State
closed
Author
~nhaines
Labels
cleanbuild
Created
Updated
Closed

Current evaluation

Abandoned due to inactivity. The report described misleading network error tracebacks during snapcraft cleanbuild startup before container connectivity. No fix or discussion was provided.

Suggested action:

No scores available.

Issue body

When snapcraft cleanbuild is run, the container prints a long error message before the container establishes a network connection. The build continues once the network connection is established and is not affected by the delay, so the error message is therefore not useful yet gives the impression of impending failure. (snapcraft) nhaines@savanna:~/workspace/jekyll$ snapcraft cleanbuild The ruby plugin is currently in beta, its API may break. Use at your own risk Creating snapcraft-nonconjunctively-unisotropous-virgil Starting snapcraft-nonconjunctively-unisotropous-virgil Waiting for a network connection... Traceback (most recent call last): File "/usr/lib/python3.5/urllib/request.py", line 1254, in do_open h.request(req.get_method(), req.selector, req.data, headers) File "/usr/lib/python3.5/http/client.py", line 1106, in request self._send_request(method, url, body, headers) File "/usr/lib/python3.5/http/client.py", line 1151, in _send_request self.endheaders(body) File "/usr/lib/python3.5/http/client.py", line 1102, in endheaders self._send_output(message_body) File "/usr/lib/python3.5/http/client.py", line 934, in _send_output self.send(msg) File "/usr/lib/python3.5/http/client.py", line 877, in send self.connect() File "/usr/lib/python3.5/http/client.py", line 849, in connect (self.host,self.port), self.timeout, self.source_address) File "/usr/lib/python3.5/socket.py", line 693, in create_connection for res in getaddrinfo(host, port, 0, SOCK_STREAM): File "/usr/lib/python3.5/socket.py", line 732, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -3] Temporary failure in name resolution During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib/python3.5/urllib/request.py", line 163, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.5/urllib/request.py", line 466, in open response = self._open(req, data) File "/usr/lib/python3.5/urllib/request.py", line 484, in _open '_open', req) File "/usr/lib/python3.5/urllib/request.py", line 444, in _call_chain result = func(*args) File "/usr/lib/python3.5/urllib/request.py", line 1282, in http_open return self.do_open(http.client.HTTPConnection, req) File "/usr/lib/python3.5/urllib/request.py", line 1256, in do_open raise URLError(err) urllib.error.URLError: <urlopen error [Errno -3] Temporary failure in name resolution> Network connection established Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Abandoned due to inactivity. The report described misleading network error tracebacks during snapcraft cleanbuild startup before container connectivity. No fix or discussion was provided.
qwen/qwen3.6-35b-a3b Closed without resolution or comments, the reported cleanbuild startup network error was abandoned or superseded by newer versions. No fix was implemented.
qwen/qwen3.6-35b-a3b Closed without resolution. The misleading network error during container startup was not addressed, indicating the issue was abandoned or superseded by newer Snapcraft versions.
qwen3.6-35b-a3b-mtp-q6 Closed without resolution and likely superseded by updated cleanbuild implementations that handle transient connectivity more gracefully.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1624075 cleanbuild - Don't try to stop a non-existent container snapcraft (launchpad) closed Closed without resolution, likely abandoned. The report detailed snapcraft cleanbuild failing when attempting to stop a non-existent LXC container.
73%