curtin error on arm64 wily deployment for xgene-2 Soc
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
While trying to deploy hwe-w/wily images using MAAS for xgene-2 Soc, I ran into this error:
http://
I searched to see if this was already a filed bug and thought that #1499869 might be related. I see that cloud-init changed fp.read() to fp and I did the same thing in url_helpers.py for curtin (I changed the only fp.read() to fp in that file) that is installed on the MAAS server. When I did that I got past the error as seen here:
http://
The error above is because the root-tgz doesn't have a needed flash-kernel fix that I added to the root-image ephemeral. However, this shows that there is indeed an issue with curtin at the moment.
ubuntu@
python-curtin:
Installed: 0.1.0~bzr314-
Candidate: 0.1.0~bzr314-
Version table:
*** 0.1.0~bzr314-
500 http://
100 /var/lib/
0.
500 http://
0.
500 http://
ubuntu@
maas:
Installed: 1.9.0~beta1+
Candidate: 1.9.0~rc2+
Version table:
1.
500 http://
*** 1.9.0~beta1+
100 /var/lib/
1.
500 http://
1.
500 http://
1.
500 http://
It should be noted that even when changing fp.read() to fp, the ouptut would sometimes be different than the above. Sometimes I also see this now (and this could be the fact that more changes need to be made):
Related branches
- Ryan Harper (community): Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 21 lines (+3/-1)1 file modifiedcurtin/url_helper.py (+3/-1)
Changed in curtin: | |
status: | Fix Committed → Fix Released |
The second paste http:// paste.ubuntu. com/13522047/ seems to show the primary failure is: lvmetad. socket: connect failed: No such file or directory
[ 111.718754] cloud-init[1139]: /run/lvm/
[ 111.730177] cloud-init[1139]: WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
It would seem that something caused lvm to not correctly start on installation.
Could you please get a failure like that and provide the full log?