cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Toscano (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2913) Spurious error message during install at the end of the RPM build process.
Date Thu, 20 Jun 2013 07:20:19 GMT


Mike Toscano commented on CLOUDSTACK-2913:

I see the same error on my system after compiling 4.1.0 according to the official documentation.

I went ahead and installed the RPMs generated, which occurred without error but when I tried
to run cloud-setup-databases, the script was not present on my system, aside from the source
directory. Guessing this might have something to do with the compile issue but really don't

> Spurious error message during install at the end of the RPM build process.
> --------------------------------------------------------------------------
>                 Key: CLOUDSTACK-2913
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.1.0
>         Environment: Centos.
>            Reporter: Ron Wheeler
>            Priority: Minor
>              Labels: newbie
> While following the installation I got an error message at the end.
> Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.xrJFTd
> + umask 022
> + cd /root/apache-cloudstack-4.1.0-src/packaging/centos63/../../dist/rpmbuild/BUILD
> + cd cloudstack-4.1.0
> + '[' /root/apache-cloudstack-4.1.0-src/dist/rpmbuild/BUILDROOT/cloudstack-4.1.0-0.el6.x86_64
'!=' / ']'
> + rm -rf /root/apache-cloudstack-4.1.0-src/dist/rpmbuild/BUILDROOT/cloudstack-4.1.0-0.el6.x86_64
> + exit 0
> error: File /root/apache-cloudstack-4.1.0-src/dist/rpmbuild/ is not a regular file.
> The error reports a true fact but I am not sure why this is seen to be an error and why
this was reported.
> It is unclear if the build actually finished but I do have 6 files.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message