This bug was fixed in the package maas - 1.2+bzr1373+dfsg-
0ubuntu1~12.04.1
---
maas (1.2+bzr1373+dfsg-0ubuntu1~12.04.1) precise-proposed; urgency=low
* MAAS Stable Release Update (LP: #1109283). See changelog entry bellow.
* debian/maas-dhcp.maas-dhcp-server.upstart: leases file
This bug was fixed in the package maas - 1.2+bzr1373+dfsg-0ubuntu1
---
maas (1.2+bzr1373+dfsg-0ubuntu1) quantal-proposed; urgency=low
* MAAS Stable Release Update (LP: #1109283):
This SRU brings a new upstream release of MAAS that removes
the usage of a cobbler code copy,
Yes it will continue to work without manual configuration. We've already
discussed this with ScottK via the IRC channel and he had agreed that
this is good to go.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Tags removed: verification-failed
** Tags added: verification-done
--
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/1109283
Title:
[SRU] maas to Quantal and Precise
To manage
Hi Scott,
No not really... so if people set things manually, a MAAS upgrade to the
SRU package won't break configurations because MAAS does not touch
/etc/dnsmasq.conf at all. So MAAS upgrade should leave /etc/dnsmasq.conf
as ism and dnsmasq should continue to work as expected.
Cheers
--
You
And MaaS will continue to work without manual configuration?
--
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/1109283
Title:
[SRU] maas to Quantal and Precise
To manage notifications
I wanted to avoid involvement with this SRU as I am risk of being to
close to this issue to safely unbiased. However, I feel i can add some
value. Therefore, please consider this to a be complementing comment -
rather than pushing in either direction.
My understanding is that if users used the
On Wednesday, April 24, 2013 04:19:41 PM you wrote:
Whilst i'd normally entirely agree that this update poses scope for
concern, the positives outweigh these concerns. I understood that this
was the primary reason this issue was progressed to the TB for
discussion.
Would you please point me
I would also like to add the following:
The non-recommend implementation of cobbler based maas-dhcp will always
destroy user configuration because cobbler will always generate the file
/etc/dnsmasq.conf. When a does manual configuration for their dnsmasq
service (regardless of whether they are
I still don't think I have a clear answer to my question in
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1109283/comments/18
--
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/1109283
Scott,
If they did edit it and have a working system and then install the update,
what will happen? If I'm reading you right, their changes, that made the
system work, will be lost. Is that right?
If they were to upgrade to a cobbler based MAAS version, then yes their
changes (in
Their changes won't be lost, but they also won't be used since (AIUI) you
aren't using dnsmasq.conf anymore. If that's right then there are two cases:
1. Made manual dnsmasq.conf changes, but the automatic magic now works, so it
doesn't matter.
2. Made manual dnsmasq.conf changes, but the
2013/4/25 Dave Walker davewal...@ubuntu.com:
maas-dhcp is a universe package, that was never designed to be a core
part of MAAS. It was provided as developers were making use of it, and
it seemed useful to provide for this purpose. However it was
intentionally left in universe.
If the
@Nobuto,
Thanks for your input, but as described in the wikipage (which no longer
exists) it was *a* way of configuring a DHCP server, not *the* prime way
of configuring one. Either way, MAAS itself is *NOT* aware if there's a
DHCP server configured or not.
@Scott,
Yes, changes won't be lost,
On Thursday, April 25, 2013 01:07:51 AM you wrote:
Now, since the SRU version of MAAS can be DNS/DHCP aware, and if the
user wants MAAS to manage this, then the user will have to manually
migrate from using the external dnsmasq to using a MAAS managed
DNS/DHCP service, which is what I believe
Please don't ping pong the bug status
I didn't touch the bug status.
It's my understanding from reading the bug, that if users that have already
manually configured things once and have a working system install the new
package, things will stop working until they do additional manual
Hi Scott,
It is my understanding that if a user does something *unsupported*, say
manually edit a file of an X python module to say hack their fixes in
order for it to work the way they want it (which can break a system),
then an SRU (or any new package version) will upgrade that file not
caring
OK, let me see if I understand now ...
If a current precise user didn't manually edit their dnsmasq.conf, then their
MaaS is certain to be not working and so there's no risk of regression.
If they did edit it and have a working system and then install the update,
what will happen? If I'm
On Tuesday, April 23, 2013 11:11:24 PM Julian Edwards wrote:
Please don't ping pong the bug status
I didn't touch the bug status.
Sorry, it was a tag, not a status, but a very important one for the SRU
process.
--
You received this bug notification because you are a member of Ubuntu
Please note that when this upgrade runs, it will render some existing
installations unusable until they configure the cluster controller.
Previously, MAAS depended on external configuration of DHCP etc via
Cobbler or manually. Now that Cobbler has gone, it must be configured
in MAAS where it was
I don't think making the package broken without additional configuration
is acceptable in an SRU. This should have been mentioned up front.
Thanks for noticing Julian.
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a
Is there no way to provide sane migration here? SRUing something that
breaks people's configurations seems like a non-starter.
--
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/1109283
To be clear, MAAS as its currently stands in precise has a *broken*
implementation of DHCP/DNS when managed by cobbler. Most of the times it
did not work well out of the box and decreases the user experience.
That being said, all of the stakeholders were aware and had been
notified that when an
How are these upgrade instructions to be communicated to users?
--
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/1109283
Title:
[SRU] maas to Quantal and Precise
To manage
Also, it seems to me that not mentioning this in the SRU bug, well, the nicest
way I can put it, is 'substantially incomplete'. This isn't the kind of thing
that should be handles via I talked to someone on the release team and they
said it was fine (BTW, ubuntu-sru and ubuntu-release are not
I am largely unfamiliar with the Ubuntu SRU process so I'm contributing
where I can here, please excuse my lack of understanding. I am upstream
in this case so I'll write from that point of view.
The existing 12.04 package is already *broken* which is the whole reason
for this SRU. It was
Please don't ping pong the bug status.
** Tags removed: verification-done
** Tags added: verification-failed
--
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/1109283
Title:
[SRU] maas
It might have been smarter not to shove MaaS into precise during release
week, but we are where we are. It may be demo ware from an upstream
PoV, but it's part of an Ubuntu LTS release.
I know the general topic of MaaS was addressed with the tech board, but
not, I don't believe, requiring
Hi Scott,
We are in the process of drafting the upgrade instructions, and we will
communicate them through normal means, ML's, blog posts, etc, unless you
believe a debconf message should also be showed.
I, however, feel the need to clarify this, since I fail to see how the
MAAS SRU is causing a
Right. I got it.
The point is that whatever users are using MaaS on precise now from the
archive have already done some manual configuration, so the fact that the
current package requires manual configuration isn't a concern from an SRU
perspective.
It's my understanding from reading the
Hello Andres, or anyone else affected,
Accepted maas into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/maas/1.2+bzr1373+dfsg-
0ubuntu1~12.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Andres, or anyone else affected,
Accepted maas into quantal-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/maas/1.2+bzr1373+dfsg-
0ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/maas
** Branch linked: lp:ubuntu/quantal-proposed/maas
--
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/1109283
Title:
[SRU] maas to
** Description changed:
[Impact]
As part of the MAAS Next Steps bluepring [1], we would like to SRU a new
version of MAAS to both Precise and Quantal.
For Quantal:
- - Fixes various issues
+ - Fixes various issues
https://launchpad.net/ubuntu/+source/maas/1.2+bzr1349+dfsg-0ubuntu1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu Quantal)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Branch linked: lp:~andreserl/maas/precise_packaging_sru
--
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/1109283
Title:
[SRU] maas to Quantal and Precise
To manage notifications
** Branch linked: lp:~maas-maintainers/maas/packaging.precise.sru
--
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/1109283
Title:
[SRU] maas to Quantal and Precise
To manage
** Description changed:
- Please SRU MAAS to Quantal and Precise
+ [Impact]
+ As part of the MAAS Next Steps bluepring [1], we would like to SRU a new
version of MAAS to both Precise and Quantal.
+
+ For Quantal:
+ - Fixes various issues
+
39 matches
Mail list logo
