Hello,<div><br></div><div>Well, I kinda answered my question... It's definitely the combination of renaming/removing /etc/one and upgrading.</div><div><br></div><div>here's the procedure:</div><div><br></div><div>-- install OpenNebula 4.0.1-1 </div>
<div> # cd opennebula-4.0.1-1/</div><div> # dpkg -i *.deb</div><div>-- remove or rename /etc/one</div><div> # mv /etc/one /etc/one.bak</div><div>-- install OpenNebula 4.1.80</div><div> # cd ../opennebula-4.1.80-1/</div>
<div> # dpkg -i *.deb</div><div><br></div><div>>> Configuration file `/etc/one/sunstone-views/admin.yaml'<div>>> ==> Deleted (by you or by a script) since installation.</div><div>>> ==> Package distributor has shipped an updated version.</div>
<div>>> What would you like to do about it ? Your options are:</div><div>>> ...</div><div>>> *** admin.yaml (Y/I/N/O/D/Z) [default=N] ?</div><div>>> etc, etc, etc</div><div><br></div><div>My guess is this is actually a matter of how dpkg works rather than how OpenNebula is packaged, but maybe if two packages are tying to install the same configs this could happen...?</div>
<div><br></div><div>Happy to produce full logs, but I didn't want to clutter up the announcement thread with console logs.</div><div><br></div><div>Thanks!</div><div>Jon A</div><div><br></div><div><br></div><br><div class="gmail_quote">
On Thu, Jul 18, 2013 at 10:07 PM, Jon <span dir="ltr"><<a href="mailto:three18ti@gmail.com" target="_blank">three18ti@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<div><br></div><div>Before I ran the install I renamed /etc/one to /etc/one.bak then I ran `dpkg -f *.deb` in the extracted directory.</div><div>While the install was running, I was prompted if I wanted to keep the current version or the package maintainers version on a number of config files (sunstone, etc).</div>
<div><br></div><div>What is odd is the files in the directory had a date of the 17th or 18th, so they have to have come from the packages.</div><div>Are two of the packages perhaps trying to install configs?</div><div><br>
</div><div>Anyway, out of curiosity I renamed the /etc/one to /etc/one.old and performed another `dpkg -i *.deb`, but I kept getting an error that there was on /etc/one directory. So I removed the packages to attempt a "fresh" install [1], and any subsequent runs of `dpkg -i *.deb` do not produce the same output, so I'm out of ideas.</div>
<div><br></div><div>Mostly thinking out loud. </div><div><br></div><div>The new interface is pretty slick, thanks for all the hard work guys!</div><div><br></div><div>Best Regards,</div><div>Jon A</div><div><br></div><div>
[1] actually, I purged the packages which killed my one.db of course... yeah, yeah, I _SHOULD_ have backups... but it's a lab environment, so really not the end of the world; lesson learned, glad I did it in a test environment. I think it would be nice to include some vocabulary in the upgrade about a backup of one.db not being necessary but to make sure there is one somewhere... just in case.</div>
<div class="HOEnZb"><div class="h5">
<div><br></div><div><br><div><br><div class="gmail_quote">On Thu, Jul 18, 2013 at 8:26 AM, Michael Curran <span dir="ltr"><<a href="mailto:michael.curran@connectsolutions.com" target="_blank">michael.curran@connectsolutions.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I found the guides -- ignore this question<br>
<div><br>
Michael Curran | connectsolutions | Lead Network Architect<br>
Phone <a href="tel:614.568.2285" value="+16145682285" target="_blank">614.568.2285</a> | Mobile <a href="tel:614.403.6320" value="+16144036320" target="_blank">614.403.6320</a> | <a href="http://www.connectsolutions.com" target="_blank">www.connectsolutions.com</a><br>
<br>
-----Original Message-----<br>
</div><div><div>From: <a href="mailto:users-bounces@lists.opennebula.org" target="_blank">users-bounces@lists.opennebula.org</a> [mailto:<a href="mailto:users-bounces@lists.opennebula.org" target="_blank">users-bounces@lists.opennebula.org</a>] On Behalf Of Michael Curran<br>
Sent: Thursday, July 18, 2013 10:18 AM<br>
To: Tino Vazquez; users<br>
Subject: Re: [one-users] OpenNebula 4.2 Flame Beta (4.1.80) is Out!<br>
<br>
I did an inline upgrade -- just installed the new packages -- now get this when I try one start<br>
<br>
oneadmin@u-cmh-neb-dev01:~$ one start<br>
Database version mismatch.<br>
oned failed to start<br>
oneadmin@u-cmh-neb-dev01:~$<br>
<br>
Is there a task that needs to be run to get the database upgraded for this? Or can I just modify the a setting somewhere that will allow the DB to match instead?<br>
<br>
Michael Curran | connectsolutions | Lead Network Architect Phone <a href="tel:614.568.2285" value="+16145682285" target="_blank">614.568.2285</a> | Mobile <a href="tel:614.403.6320" value="+16144036320" target="_blank">614.403.6320</a> | <a href="http://www.connectsolutions.com" target="_blank">www.connectsolutions.com</a><br>
<br>
-----Original Message-----<br>
From: <a href="mailto:users-bounces@lists.opennebula.org" target="_blank">users-bounces@lists.opennebula.org</a> [mailto:<a href="mailto:users-bounces@lists.opennebula.org" target="_blank">users-bounces@lists.opennebula.org</a>] On Behalf Of Tino Vazquez<br>
Sent: Thursday, July 18, 2013 7:33 AM<br>
To: users<br>
Subject: [one-users] OpenNebula 4.2 Flame Beta (4.1.80) is Out!<br>
<br>
Dear Community,<br>
<br>
This is the official announcement of OpenNebula 4.2 Flame Beta (4.1.80). After the ground shaking release that was OpenNebula 4.0 Eagle, now its time to stabilise features in this next release, OpenNebula 4.2 Flame. The principal aim of this release is to strengthen the most demanded and useful features, reducing the complexity in order to better support the most used ones.<br>
<br>
This release includes an important subset of the features originally planned for 4.2, all the missing features have been automatically rescheduled to 4.4. Our goal with this release is to reduce your waiting time to test some exciting new features that are currently ready!<br>
<br>
OpenNebula Flame includes a more polished Sunstone interface, after its redesign in 4.0; with important usability enhancements. Datastore capacity is now monitored and used to limit the amount of storage size used by images. This is a first step to also control the runtime storage used by the VMs. The VMware backend has been completely redesigned with a more comprehensive storage scheme, more functionality and less dependencies. Also we have upgraded the Xen backend to support the new interfaces introduced in Xen 4.0. And last but no least, OneFlow, the multi-tier application (a.k.a. service) manager, it is included and fully integrated in the distribution. It includes also important new features related to service management and elasticity/auto-scaling.<br>
<br>
We are now set to basically bug-fixing and feature-freeze. Note that this is a beta release aimed at testers and developers to try the new features, and send a more than welcomed feedback for the final release.<br>
<br>
As usual OpenNebula releases are named after a Nebula. The Flame Nebula (catalogued as NGC 2024 and Sh2-277) is an emission nebula in the constellation Orion. It is located about 900 to 1,500 light-years away from Earth.<br>
<br>
Let Flame guide you through the Clouds!<br>
<br>
The OpenNebula Team<br>
<br>
<br>
LINKS<br>
<br>
* Complete Release Notes: <a href="http://opennebula.org/software:rnotes:rn-rel4.2beta" target="_blank">http://opennebula.org/software:rnotes:rn-rel4.2beta</a><br>
* Download: <a href="http://downloads.opennebula.org/" target="_blank">http://downloads.opennebula.org/</a><br>
* Documentation: <a href="http://opennebula.org/documentation:rel4.2" target="_blank">http://opennebula.org/documentation:rel4.2</a><br>
<br>
--<br>
Constantino Vázquez Blanco, PhD, MSc<br>
Senior Infrastructure Architect at C12G Labs <a href="http://www.c12g.com" target="_blank">www.c12g.com</a> | @C12G | <a href="http://es.linkedin.com/in/tinova" target="_blank">es.linkedin.com/in/tinova</a><br>
<br>
--<br>
Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the "To" and "cc" box). They are the property of C12G Labs S.L..<br>
Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at <a href="mailto:abuse@c12g.com" target="_blank">abuse@c12g.com</a> and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation.<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
</div></div></blockquote></div><br></div></div>
</div></div></blockquote></div><br></div>