I have resolved enlistment issues by editing manually generator variable
in pserv.yaml for a standalone cluster controller and now the standalone
cluster controller seem to be used for enlistment. However install fails
and clearly in the last installation steps when cloud-init runs
modules:final im
** Changed in: maas (Ubuntu Quantal)
Status: New => Fix Released
** Changed in: maas (Ubuntu Precise)
Status: New => Fix Released
--
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/
** Changed in: maas/1.2
Status: Fix Committed => Fix Released
--
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/1081701
Title:
The metadata address mentioned in the preseed is wron
** Also affects: maas (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a mem
** Changed in: maas (Ubuntu)
Status: New => Confirmed
** Changed in: maas (Ubuntu)
Importance: Undecided => Critical
--
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/1081701
Tit
** Changed in: maas/trunk
Status: Fix Committed => Fix Released
--
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/1081701
Title:
The metadata address mentioned in the preseed is wr
** Changed in: maas/1.2
Status: In Progress => Fix Committed
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong
** Branch linked: lp:~julian-edwards/maas/backport-r1371
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manag
** Branch linked: lp:~rvb/maas/1081701-c-bis
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manage notificati
** Changed in: maas/1.2
Assignee: Gavin Panella (allenap) => Julian Edwards (julian-edwards)
** Changed in: maas/1.2
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bug
** Changed in: maas/trunk
Status: In Progress => Fix Committed
--
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/1081701
Title:
The metadata address mentioned in the preseed is wro
** Branch linked: lp:~rvb/maas/fix-origin-adr
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manage notificat
This is not fixed yet, the enlistment user data is not fixed.
** Changed in: maas/trunk
Status: Fix Committed => In Progress
** Changed in: maas/trunk
Assignee: Gavin Panella (allenap) => Raphaël Badin (rvb)
** Branch linked: lp:~rvb/maas/enlistment-user-data
--
You received this b
** Changed in: maas/trunk
Status: In Progress => Fix Committed
--
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/1081701
Title:
The metadata address mentioned in the preseed is wro
** Changed in: maas/trunk
Assignee: (unassigned) => Gavin Panella (allenap)
** Changed in: maas/trunk
Status: Triaged => In Progress
** Changed in: maas/1.2
Assignee: (unassigned) => Gavin Panella (allenap)
--
You received this bug notification because you are a member of Ubunt
** Branch linked: lp:~allenap/maas/bug-1081701-b
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manage notifi
** Branch linked: lp:~rvb/maas/bug-1081701-d
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manage notificati
Status update:
- a) is landed
- c) has been reviewed (but not yet landed)
- Gavin is working on b)
- d) and e) are still up for grabs :)
--
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
** Branch linked: lp:~rvb/maas/bug-1081701-c
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manage notificati
** Branch linked: lp:~rvb/maas/bug-1081701-a
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manage notificati
Here is a description what it will take to implement solution 2, broken
down into individual tasks:
Once a) is done, all the other tasks can be done independently.
a) add a new colum on nodegroup to store the maas_url as seen by the
cluster
b) have the cluster send that maas_url when cluster sta
Right, when this will be fixed, fixing bug 1081696 will be simply a
matter of using that value (stored on the nodegroup object).
** No longer affects: maas/12.04-nocobbler
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
grar, I meant see also bug 1081696
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manage notifications about
see also bug 1081701
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manage notifications about this bug go to
Ok cheers - I have captured this on
https://blueprints.launchpad.net/maas/+spec/cluster-renders-preseed
--
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/1081701
Title:
The metadata addre
Raphaël and I discussed two options:
1. Render the preseed in the cluster.
2. Send the cluster address to the region during start-up so that it
can render the preseed with the correct address.
We decided that #1 better divides responsibilities, but that we would
go for option #2 for two reaso
Or perhaps this is an argument to start rendering preseeds on the
clusters.
--
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/1081701
Title:
The metadata address mentioned in the preseed
I'm not sure how to approach this at the moment. The preseed is
rendered on the region controller which has no knowledge of how each
cluster accesses it. The only way I can see around this is for the
cluster to send the region the API URL that it is using, which the
region can then store on the n
** Also affects: maas/1.2
Importance: Undecided
Status: New
** Also affects: maas/12.04-nocobbler
Importance: Undecided
Status: New
** Also affects: maas/trunk
Importance: Critical
Status: Triaged
** Changed in: maas/12.04-nocobbler
Milestone: None => 12.04.1-sr
** Changed in: maas
Milestone: None => 12.10-stabilization
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
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/1
30 matches
Mail list logo