*** This bug is a duplicate of bug 1876258 ***
https://bugs.launchpad.net/bugs/1876258
** This bug has been marked a duplicate of bug 1876258
ubuntu 20.04 pxe installation fails with no such file or directory
/dev/disk/by-id exception
--
You received this bug notification because you are
@Patricia I also tried to deploy scalebot charm and use some VMs
(scalebot-dev-controller2 and 3). They are able to deploy now. Thanks
for looking this issue, and thanks @Ryan for your helpful information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
thanks again Ryan.
manually adding serial to uvtool's virtio disk makes them work again - able to
deploy via MAAS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895922
Title:
maas could not deploy
Hi Patricia,
You'll need to upgrade MAAS itself. The curtin_userdata is what's sent
to the nodes deploying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895922
Title:
maas could not deploy a kvm
Ryan, thanks. I tried adding curtin's daily PPA. I've added this to MAAS'
curtin_userdata
```
add_repo: ["add-apt-repository", "-y", "ppa:curtin-dev/daily"]
update: ["sh", "-c", "apt-get update"]
install: ["sh", "-c", "apt install -y curtin"]
```
I can see on MAAS' logs latest curtin was
I believe this is a duplicate of:
https://bugs.launchpad.net/curtin/+bug/1876258
This has already been fixed in curtin, you can test with curtin's daily PPA, or
curtin in groovy.
W.r.t uvtool; like MAAS, uvtool should generate serial disk attributes
for all virtio disks by default.
** Chang
Robie, I just added uvtool because we cannot deploy anymore enlisted VMs
created via uvtool, which previously were working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895922
Title:
maas could no
I don't understand why you think there is a bug in uvtool here. Please
could you explain and provide steps to reproduce specifically for
uvtool?
** Changed in: uvtool
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
some info about this issue:
1. when it was working (able to deploy the enlisted VMs) we had MAAS 2.8.1 and
curtin version `curtin: Installation started.
(19.3-26-g82f23e3d-0ubuntu1~18.04.1)`.
2. it is possible to deploy VMs created via MAAS KVM host type virsh.
3. the VMs that we can not deploy
** Description changed:
Curtin process failed during MaaS deployment. The infrastructure worked
well until ~3 weeks ago.
-
[Steps to Reproduce]
1. Enlist and commission a KVM-based VM in MaaS 2.8.2 (8577-g.a3e674063)
2. Deploy the VM node
+
+ reproducing environment: nodes named aft
There were deployed kvm nodes and they are running well, so I inclined
to think the kvm host and its communication with maas are both good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895922
Title:
More logs from curtin and /var/log
** Attachment added: "lp1895922-01.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1895922/+attachment/5411540/+files/lp1895922-01.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
The log file from comment1 was fetched in the vm node by logging into
the target deployment node.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895922
Title:
maas could not deploy a kvm-based vm vi
I did see the /dev/disk/by-id folder. However, there is /dev/disk/by-
uuid in the vm node instead:
ubuntu@scalebot-dev-controller5:~$ ls /dev/
blockecryptfs initctl loop2 mem ppp
shm tty1 tty17 tty24 tty31 tty39 tty46 tty53 tty60 ttyS1
14 matches
Mail list logo
