I see the same error and same /proc/cmdline args while commissioning a
new maas setup. Rerunning the sudo maas-export-pxe-files does not help
in my case. I am on 12.0.4 LTS
vmdc-admin@ics3-ubuntu3:/var/log/maas$ dpkg -l | grep maas
ii maas
I see the same error and same /proc/cmdline args while commissioning a
new maas setup. Rerunning the sudo maas-export-pxe-files does not help
in my case. I am on 12.0.4 LTS
vmdc-admin@ics3-ubuntu3:/var/log/maas$ dpkg -l | grep maas
ii maas
This bug seems to be back. I initially overlooked this report, so I
filed another one:
https://bugs.launchpad.net/maas/+bug/1302604
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
ignore last comment.
A fresh import works.until you reboot. Even if you changed nothing else in
the configuration of the server or maas, enlistment will no longer work until
you do another maas-import-pxe-files at which time things will work again.
** Tags added: blocks-hwcert-server
**
A fresh import works.until you reboot. Even if you changed nothing
else in the configuration of the server or maas, enlistment will no
longer work until you reboot.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
That sounds as if it's probably just bug 1300548, which is already
fixed. Definitely not the same thing that this bug is about.
** Changed in: maas
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This bug seems to be back. I initially overlooked this report, so I
filed another one:
https://bugs.launchpad.net/maas/+bug/1302604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300026
Title:
A fresh import works.until you reboot. Even if you changed nothing
else in the configuration of the server or maas, enlistment will no
longer work until you reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ignore last comment.
A fresh import works.until you reboot. Even if you changed nothing else in
the configuration of the server or maas, enlistment will no longer work until
you do another maas-import-pxe-files at which time things will work again.
** Tags added: blocks-hwcert-server
**
That sounds as if it's probably just bug 1300548, which is already
fixed. Definitely not the same thing that this bug is about.
** Changed in: maas
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas
Milestone: 14.04 = None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300026
Title:
Enlistment/commissioning boot no longer works
To manage notifications
** Changed in: maas
Milestone: 14.04 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300026
Title:
Enlistment/commissioning boot no longer works
To manage notifications about this bug go
Ok I had this and then re-ran maas-import-pxe-files and the next time my
node booted it enlisted fine.
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = Critical
** Changed in: maas
I wasn't getting any new files from the import script. Am now re-
running the entire import from scratch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300026
Title:
Yay! A fresh import solved it.
** Changed in: maas
Status: Incomplete = Invalid
** Changed in: maas (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Ok I had this and then re-ran maas-import-pxe-files and the next time my
node booted it enlisted fine.
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = Critical
** Changed in: maas
I wasn't getting any new files from the import script. Am now re-
running the entire import from scratch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300026
Title:
Enlistment/commissioning boot
Yay! A fresh import solved it.
** Changed in: maas
Status: Incomplete = Invalid
** Changed in: maas (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
18 matches
Mail list logo