*** This bug is a duplicate of bug 1794882 ***
https://bugs.launchpad.net/bugs/1794882
This looks like a duplicate of bug 1794882, which is fixed in 2.7 and
2.8.
** This bug has been marked a duplicate of bug 1794882
dhcpd doesn't start until maas-rackd is restarted
--
You received this
Got the same today with MAAS 2.6.2
$ sudo service maas-dhcpd status
● maas-dhcpd.service - MAAS instance of ISC DHCP server for IPv4
Loaded: loaded (/lib/systemd/system/maas-dhcpd.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-06-05 14:54:44 UTC;
I have the same issue. `sudo systemctl restart maas-rackd.service`
worked for me.
Do you have any idea why this doesn't work automatically? I'm happy to
help debug if you let me know what information is needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I experienced a similar issue when playing around with a test
installation of MAAS earlier.
Appearently I had disabled "managed allocation", which I believe needed
to be re-enabled before my controller would start dhpcd. Hopefully this
will turn up in search results for others facing the same prob
The solution from chaitu worked for me:
sudo systemctl restart maas-rackd.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649397
Title:
maas-dhcpd.service won't start
To manage notification
Hi,
Faced the same issue where DHCPD is not starting .
easy solution is to restart rackd service. This created the file for me.
sudo systemctl maas-rackd.service restart
Hope this solution helps. :-)
Br
Chaithanya
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@James,
So, most of the test openstack deployments with MAAS are done in a flat
network. This, means that:
1. You at least have One Fabric, One "VLAN", One Subnet.
2. You have the Rack Controller NIC connected with an IP of the subnet above
(which means that the NIC is in fabric/vlan above).
Fo
@andreserl, still confused as to why I can't add DHCP to a flat network
space, without applying @obecker's fix from #10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649397
Title:
maas-dhcpd.servi
LaMont,
What you are describing is a completely different thing. If you see
https://bugs.launchpad.net/maas/+bug/1649397/comments/2 , the issue in
this bug is on a freshly installed MAAS. Your issue may be because you
didn't wait long enough for MAAS to instruct the Rack Controller to *re-
generat
One way to reproduce this issue (and the workaround):
1) Install and configure MAAS, with DHCP on at least one subnet on the rack
2) purge maas-rack-controller: this will remove /var/lib/maas/dhcpd.conf
3) reinstall maas-rack-controllerL: this will start the rack controller, but
not recreate /var
sysadmin@sf2-maas00:~$ maas sysadmin vlan update fabric-0 untagged
dhcp_on=True primary_rack=sf2-maas00
Success.
Machine-readable output follows:
{
"mtu": 1500,
"resource_uri": "/MAAS/api/2.0/vlans/0/",
"fabric": "fabric-0",
"name": "untagged",
"secondary_rack": null,
Andres this is a bug so stop closing things without my ok.
The MAAS is fully configured and operational. Since the latest patches it no
longer works because some jack ass broke the code.
I don't like it when people deploy code which is not signed off.
So Andres leave this bug open because it c
James,
You need to configure DHCP on the "untagged" VLAN. You need to have a rack
controller network interface connected to the "untagged" VLAN where you
want to provide DHCP for.
On Mon, Dec 12, 2016 at 6:30 PM james beedy wrote:
> @andreserl, I think the problem may be partially due to the
Olaf,
Maas-DHCP fails to start because there is no dhcpd.conf file.
It doesn't exist because:
You may not have enabled DHCP on the VLAN (which needs a NIC on a rack
controller connected to, with an IP)
Or the rack controller is not fully connected.
On Mon, Dec 12, 2016 at 4:55 PM Olaf Becker <1
@andreserl, I think the problem may be partially due to the fact that we
are trying to configure dhcp on a flat address space, not a vlan. Per
your comments above, you only mention vlan, not flat networks, should
this matter to any affect?
--
You received this bug notification because you are a m
@andreserl yea, I can't get dhcp to light up for the life of me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649397
Title:
maas-dhcpd.service won't start
To manage notifications about this bug go
DHCP will not start, e.g. no green light on the controller on initial
install of MAAS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649397
Title:
maas-dhcpd.service won't start
To manage notifica
root@sf2-maas00:~# service maas-dhcpd status
● maas-dhcpd.service - MAAS instance of ISC DHCP server for IPv4
Loaded: loaded (/lib/systemd/system/maas-dhcpd.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Mon 2016-12-12 21:32:20 UTC; 2min
38s ago
Condition
This happens with the latest official version. We did build 2 different
MAAS Server / Controller and both boxes independently came to the same
result. DHCP somehow is broken.
Bug is confirmed
Olaf B (CRACK CCC Germany)
--
You received this bug notification because you are a member of Ubuntu
Bug
Going to mark this invalid in the meantime, because:
1. The dhcpd service will be automatically started by MAAS
2. It will only be started if a config file has been generated.
3. For a rack controller to generate a config, there must be:
* DHCP enabled (on the VLAN)
* Rack Controller has an in
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649397
Title:
maas-dhcpd.service won't start
To manage notifications about
21 matches
Mail list logo