In terms of understanding when this was fixed for what users/versions.
Assuming that MAAS is copying the curtin version from the server, to the
deployed client, which I think is the case, you need to get an updated
Curtin to the MAAS server.
The bug was fix released into curtin
Another of our customers hit this bug again on bionic when their cloud
was redeployed. I understand it will be curtin snap going forward, but
why can't we have at least have a working version in deb repo so that
whoever is still using this will have a better experience?
--
You received this bug
What I wrote on comment#12 is what I've been told by the Canonical's
server team.
As far as I can tell, I don't think support sent any official
communication in the field nor documented it. This way to work is also
fairly new to my knowledge.
Let's talk about this internally on how we want to
So, where have clients (especially MaaS clients) been informed of this
change to Curtin? I can imagine a few would want to add the Curtin PPA
to their list of repos...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately, Canonical don't SRU Curtin anymore as it is moving toward
a SNAP installation where Curtin changes will be released and then
consumed by MAAS (installed as a snap).
Does your customer have MAAS installed as DEB or as SNAP ?
If it's DEB, the procedure changes, meaning that you
Hello. On behalf of an impacted user:
"We have now been blocked for month not being able to provision new
machines without dirty hacks.
There has also not been any activity on that page since we started the
issue.
Any help to push this harder is welcome, this is urgent for us."
--
You
It has been brought to my attention by an impacted user, the following:
"
Thank you for your update. I added this new version of ppa curtin into maas and
restart regiond and now we successfully deployed servers with swap partition
created in maas. It is working as expected.
Maybe one question
@Richard @Ryan,
Thanks, much appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892242
Title:
Curtin doesn't handle type:mount entries without 'path' element
To manage notifications
Tomorrows Curtin daily:ppa should have this (and as you can see, other
fixes)
https://launchpad.net/~curtin-dev/+archive/ubuntu/daily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892242
Title:
We will SRU at some point but we don't have a current timeline.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892242
Title:
Curtin doesn't handle type:mount entries without 'path' element
To
This bug was fixed in the package curtin - 20.1-20-g1304d3ea-0ubuntu1
---
curtin (20.1-20-g1304d3ea-0ubuntu1) groovy; urgency=medium
* New upstream snapshot.
- curthooks: uefi_find_grub_device_ids handle type:mount without path
(LP: #1892242)
- netplan openvswitch
@ryan,
Are you planning to SRU it ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892242
Title:
Curtin doesn't handle type:mount entries without 'path' element
To manage notifications about this
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Bionic)
13 matches
Mail list logo
