[2.2] Rack registration fails if machine has domain in hostname
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Данило Шеган |
Bug Description
Everything works fine when:
$ cat /etc/hostname
maas
Doesn't work at all when:
$ cat /etc/hostname
maas.domain.bad
=> /var/log/
2017-04-27 15:05:17 provisioningser
2017-04-27 15:05:17 ClusterClient,
==> /var/log/
2017-04-27 15:05:17 maasserver.
2017-04-27 15:05:17 RegionServer,
2017-04-27 15:05:17 maasserver.
Traceback (most recent call last):
File "/usr/lib/
current.result = callback(
File "/usr/lib/
_inlineCall
File "/usr/lib/
result = result.
File "/usr/lib/
return g.throw(self.type, self.value, self.tb)
--- <exception caught here> ---
File "/usr/lib/
process, rack_controller, self.host)
File "/usr/lib/
result = inContext.theWork()
File "/usr/lib/
inContext.
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
return func_outside_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwds)
File "/usr/lib/
process=
File "/usr/lib/
return getattr(
File "/usr/lib/
self.
maasserver.
==> /var/log/
2017-04-27 15:05:17 provisioningser
2017-04-27 15:05:17 ClusterClient,
==> /var/log/
2017-04-27 15:05:17 maasserver.
2017-04-27 15:05:17 RegionServer,
Related branches
- Blake Rouse (community): Approve
-
Diff: 113 lines (+57/-3)4 files modifiedsrc/maasserver/rpc/rackcontrollers.py (+10/-1)
src/maasserver/rpc/tests/test_rackcontrollers.py (+43/-0)
src/provisioningserver/rpc/clusterservice.py (+1/-1)
src/provisioningserver/rpc/tests/test_clusterservice.py (+3/-1)
Changed in maas: | |
milestone: | 2.2.0rc3 → 2.2.0rc4 |
assignee: | nobody → Данило Шеган (danilo) |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
I've originally managed to reproduce this, but don't seem to be able to anymore. I've tried both with my existing local MAAS server, and with a MAAS setup using the following:
uvt-kvm create --ssh-public- key-file ~/.ssh/ authorized_ keys maas1 next-proposed
uvt-kvm ssh --insecure maas1 sudo apt-add-repository ppa:maas/
uvt-kvm ssh --insecure maas1 sudo apt update
uvt-kvm ssh --insecure maas1 sudo apt install maas
uvt-kvm create --ssh-public- key-file ~/.ssh/ authorized_ keys maas2 next-proposed controller
uvt-kvm ssh --insecure maas2 sudo apt-add-repository ppa:maas/
uvt-kvm ssh --insecure maas2 sudo apt update
uvt-kvm ssh --insecure maas2 sudo apt install maas-rack-
echo maas2.test | uvt-kvm ssh --insecure maas2 sudo tee /etc/hostname
I reboot the "maas2" VM and attempt to register it as a rack controller on the first (use "uvt-kvm ip maas1/2" to find out IP address for each).
I get none of the tracebacks, but the domain name is not being created, so I'll re-focus on that part of the bug.