I've also committed fix for the OpenNebula module few minutes ago.
-- Thank you, Dmitri Chebotarov VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & Messaging 223 Aquia Building, Ffx, MSN: 1B5 Phone: (703) 993-6175 | Fax: (703) 993-3404 > On Mar 13, 2015, at 15:25 , Andy Kurth <[email protected]> wrote: > > This issue has been fixed and committed to trunk. I am not aware of any > pending problems. > -Andy > > On Fri, Mar 13, 2015 at 9:42 AM, Andy Kurth <[email protected]> wrote: > >> I found a bug in RC2 which causes VMware-based reservations to fail if the >> stock VM profiles are used. The bug was tricky to track down because the >> information written to vcld.log did not explain what the underlying problem >> was: >> >> VMware.pm:check_vmhost_disk_space|2213|failed to determine additional >>> bytes required for the vmx and vmdk directories on VM host >> >> >> The actual problem stems from this line in get_image_size_bytes: >> my $vmprofile_vmdisk = $self->data->get_vmhost_profile_vmdisk() || return; >> >> In vcl.sql, the insert statement for the vmprofile table specifies >> 'localdisk' and 'networkdisk' for the vmprofile.vmdisk column. This column >> uses the enum column type and the valid values were changed to 'dedicated' >> or 'shared' in a previous release. The insert statements succeed but the >> vmdisk column gets set to a blank value. Because of this, >> get_vmhost_profile_vmdisk returns false which causes >> check_vmhost_disk_space to fail. >> >> I will update vcl.sql and improve the notify messages in VMware.pm to make >> similar problems easier to track down in the future. >> >> I want to do some additional testing today. I propose we cut RC3 at the >> end of the day. >> >> -Andy >> >> >> >> On Tue, Mar 10, 2015 at 3:57 PM, Josh Thompson <[email protected]> >> wrote: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Aaron identified an issue in RC1 that the update-vcl.sql script was >>> missing an >>> entry for the computerloadstate table. So, with that updated, RC2 is now >>> available. This is basically the same email as last time, but with RC1 >>> changed to RC2 and the vote set to end at 4pm EST Friday, March 13th. >>> >>> As Andy mentioned in his reply to the "release nearly ready" thread, all >>> of >>> the (non-documentation) JIRA issues associated with 2.4 are now resolved. >>> Here is our first try at voting to release 2.4. >>> >>> I created a release artifact based off of trunk. I copied that branch to >>> a >>> tag under the tags area of the repo that is named release-2.4-RC2: >>> >>> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC2/ >>> >>> The artifact is an export from that tag with the addition of Dojo Toolkit >>> version 1.6.2 with a custom VCL profile and Spyc both bundled in the web >>> code. >>> The artifact, MD5 and SHA1 sums, and my GPG signature of it are available >>> from >>> my space on people.a.o: >>> >>> http://people.apache.org/~jfthomps/apache-VCL-2.4-RC2/ >>> >>> The list of resolved JIRA issues associated with this release can be found >>> under 2.4 on the Change Log page in the staging area of the CMS: >>> >>> http://vcl.staging.apache.org/docs/changelog.html >>> >>> This is the first release to include an installation script. Installation >>> instructions on using the script and doing things manually are on the >>> following page in the staging area of the CMS: >>> >>> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html >>> >>> The INSTALLATION file in the release artifact only contains information on >>> using the script. >>> >>> *NOTE* To use the installation script with RC2, you need to give it the >>> - --rc=1 option (which is not included in the output of --help). >>> >>> I was able to successfully do test installs and upgrades, including image >>> deploying and capture. >>> >>> The directory created by extracting the RC2 artifact is >>> "apache-VCL-2.4-RC2" >>> (after extracting, you may want to rename it to "apache-VCL-2.4" if you >>> want >>> to test the manual instruction from the online installation guide). >>> Licensing >>> information about perl and its required modules, php and its required >>> modules, >>> and mysql are stated as "system requirements" according to the information >>> under "System Requirements" on http://www.apache.org/legal/3party.html. >>> >>> After we finalize a release vote, the staging part of the CMS will be >>> published to update the production site. >>> >>> Please vote by 4pm (EST) on Friday, March 13th to publish this release >>> (this >>> allows for 3 business days to vote). Everyone in the community is >>> encouraged >>> to vote if you have at least done some testing. However, only votes by >>> members of the PMC are binding votes. >>> >>> [ ] +1 yes, release VCL 2.4 >>> [ ] 0 dunno >>> [ ] -1 no, don't release VCL 2.4 (provide reasons if this is your vote) >>> >>> Josh >>> - -- >>> - ------------------------------- >>> Josh Thompson >>> VCL Developer >>> North Carolina State University >>> >>> my GPG/PGP key can be found at pgp.mit.edu >>> >>> All electronic mail messages in connection with State business which >>> are sent to or received by this account are subject to the NC Public >>> Records Law and may be disclosed to third parties. >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v2 >>> >>> iEYEARECAAYFAlT/TKQACgkQV/LQcNdtPQOFyACfQslmZVazhy8Ikt43bIuc/fm5 >>> I/oAnAu4io5S/vmKV2b4gCILqs2HgSnG >>> =k22n >>> -----END PGP SIGNATURE----- >>> >>> >>
