[DISCUSS] Next CloudMonkey release v6.1.0

[Rohit Yadav]

All,

It's been over a year since the last CloudMonkey (cmk) release. While cmk 
appears to stable (given no major complains) we've had a few fixes since the 
last release and we must work on a release in near future (likely after 4.14 
and Primate tech preview).

I've triaged a few issues for the next v6.1.0 milestone, kindly provide any 
feedback, comments on this thread and report issues/feature requests here 
https://github.com/apache/cloudstack-cloudmonkey/issues

Thanks.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

Re: Problem accessing /client/ - Service Unavailable

[Luis]

Hi
I agree that the script should be granting the privileges but for some reason 
is not happening. I have been installing CS more than 20 the las week and I 
always have to do the granting privileges, just saying but maybe that past is 
disabled in the script. I may be wrong.

Sent from Yahoo Mail on Android 
 
  On Fri, May 8, 2020 at 10:34 AM, Nicolas Vazquez 
wrote:   Hi Jisha,

Just adding to Luis' comments, granting privileges shouldn't be necessary,
the script should handle that for you. Please consider the steps in the
documentation as well:
http://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html#database-installation-and-configuration

Regards,
Nicolas Vazquez

El vie., 8 may. 2020 a las 10:45, Luis Martinez
() escribió:

> Sure,
>
>
> this line contains the user and password for the user cloud, I also
> changed the password for the user root
>
> cloudstack-setup-databases cloud:Password1@localhost
> --deploy-as=root:Password1
>
> here are the instructions to change the password for root
>
> 1.- after installing mysql runs this (sudo mysql_secure_installation)
> running this will ask you for root password, press (enter) because there
> is no password at the moment then it will ask you if you want to change
> the root password, press y (remember the password you are going to use)
> and for the following questions press y
>
> 2.- service mysql restart
> 3.- mysql -u root -p (this line will allow you to connect to mysql and
> it will ask you for root password )
>
> 4.- run the following lines
>
> GRANT ALL PRIVILEGES ON *.* TO 'cloud'@'%';
> GRANT ALL PRIVILEGES ON *.* TO 'root'@'%';
> FLUSH PRIVILEGES;
> quit
>
> 5.- service mysql restart
>
> 6.- ready to run this line
>
> cloudstack-setup-databases cloud:(any password you want to use, this
> will be encrypted and saved in db.properties)@localhost
> --deploy-as=root:*(here use the password for mysql root)*
>
> *7.- run the rest of you process
> *
>
> **On 5/8/2020 8:46 AM, Jisha Ashokan wrote:
>
> > Thank you, but the password is encrypted in
> /etc/cloudstack/management/db.properties . Can you please tell me how did
> you change the password?
> >
> > Thank you,
> >
> > On 2020/05/08 11:55:38, Luis  wrote:
> >> I had the same problem and it may be because the user doesn't have the
> correct privileges to the database. You have to login to the database and
> grant the user access to the database.
> >>
> >> Sent from Yahoo Mail on Android
> >>
> >>    On Fri, May 8, 2020 at 2:23 AM, Jisha Ashokan
> wrote:  Hello,
> >>
> >> After installing Cloudstack,
> >>
> >> IP:8080/client/
> >>
> >> gives HTTP ERROR 503
> >> Problem accessing /client/. Reason: Service Unavailable
> >>
> >> Tried restarting using
> >>
> >> service cloudstack-management restart
> >>
> >> Accessing the URL, and
> >>
> >> grep -i -E 'error|exception'
> /var/log/cloudstack/management/management-server.log gives
> >>
> >> --
> >> 2020-05-08 10:46:21,300 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context initialization -
> cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to
> check for database integrity.
> >> org.springframework.context.ApplicationContextException: Failed to
> start bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to
> check for database integrity.
> >> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to
> acquire lock to check for database integrity.
> >> 2020-05-08 11:28:04,678 ERROR [c.c.u.d.DbUtil] (main:null) (logid:)
> GET_LOCK() throws exception
> >> java.sql.SQLException: Operation not allowed for a result set of type
> ResultSet.TYPE_FORWARD_ONLY.
> >>      at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129)
> >>      at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
> >>      at
> com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
> >> 2020-05-08 11:28:04,684 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context initialization -
> cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to
> check for database integrity.
> >> org.springframework.context.ApplicationContextException: Failed to
> start bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to
> check for database integrity.
> >> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to
> acquire lock to check for database integrity.
> >

Re: [DISCUSS] Primate - publishing release and docs

[Riepl, Gregor (SWISS TXT)]

Hi Rohit,

Let me comment on just a few of the topics:

> Release cycle

I think we should definitely have a daily/nightly build, at least as long as a 
lot of changes are incoming.

I'm think along the lines of a parallel installation, so all versions can be 
tested and users still get a fallback in case of bugs:
- Stable legacy UI (included in cloudstack-management-server, as long as it's 
available)
- Stable new UI (alongside legacy UI, updated manually)
- Beta test from nightly (updated by an automated script)

> Versioning

Nightlies should not bear a release version, IMHO.
Something like cloudstack-primate-nightly-20200506.x86_64.rpm would be enough.
These should be built and published automatically, and no voting should take 
place.

When an actual stable/beta release is made, it should only contain the version 
and not the date, such as cloudstack-primate-0.4.0.x86_64.rpm
These could be voted on, depending on how often they're released.

> Package types and documentation

I'm in favour of supplying all three types of packages, and adding installation 
instructions for all three.
For the container variant, it may also make sense to provide an example 
Kubernetes manifest. In can contribute that if desired.

Regards,
Gregor

From: Rohit Yadav 
Sent: 08 May 2020 12:21
To: dev ; Sven Vogel 
Cc: users@cloudstack.apache.org 
Subject: Re: [DISCUSS] Primate - publishing release and docs

Hi Daan,

Thanks for replying and participating. Some points:

  *   The document links within Primate is a different topic than the docs for 
Primate itself, the scope of current discussion is limited to documentation for 
Primate. The doc link within Primate would be done against the 1.0/GA 
milestone, it would require going through all the sections/APIs against the 
current CloudStack docs and put a link (or part of it).
  *   The documentation for Primate currently won't be huge, perhaps a single 
long page would do (to explain how to install).
  *   Primate would be a separately installable package and installing 
cloudstack-management won't automatically trigger installing it (at least in 
the tech preview, we can discuss how we handle longer term starting with GA/1.0 
later).
  *   We've setup automation for all kinds of packaging formats/channels (we 
already have that for rpm/deb and archive formats, except for dockerhub hosting 
which is in discussion with ASF infra). I think publishing artifacts should be 
quick and mostly automated.
  *   Github has a new feature called Github packages for each repo, where one 
can host things like npm, docker packages etc. We can explore this feature.
On a Github release wrt a git tag, we can upload an artifact (I've seen many 
projects doing this).
  *   On releasing without voting, my thought and preference is that as our 
users test Primate, and report bugs and until GA/1.0 we fix those issues, 
implement missing feature users get faster fixes via a "preview" or "testing" 
or "beta" release channel periodically (deb/rpms repos, archives, docker 
container builds).

Doing this would require that we agree on this strategy, without a single 
tag/version but a set of releases (with a timestamp, so packages would look 
like cloudstack-primate-$version-$date). So effectively we're saying - let's 
release the tech preview without doing an official release (which would mean a 
fix git tag/version). This is where the discussion of a single tech preview 
release vs rolling tech preview release would come in.

Looking forward to more feedback from our dev/user community and of course our 
VP @Sven Vogel who has been a major Primate-SIG 
collaborator. Thanks.

Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Daan Hoogland 
Sent: Thursday, May 7, 2020 12:34
To: dev 
Cc: users@cloudstack.apache.org 
Subject: Re: [DISCUSS] Primate - publishing release and docs

Hey Rohit,
This is a lot to take in at once. We have discussed some of those off line
but let me give my initial answers to your discussion points inline.
Hopefully those more directly involved and with more at stake can give some
input as well.

On Wed, May 6, 2020 at 3:03 PM Rohit Yadav 
wrote:

> All,
>
> With this thread I want to start a discussion around:
>
>   *   How do we host/publish technical preview release
>   *   How do we host/publish technical preview documentation (release
> notes, setup/install instructions)
>
> To set the expectation:
>
>   *   This thread limits discussion wrt technical preview (beta).
>   *   Plan we've already agreed, just to recap: 

...

>   *   References:
>  *   Voting thread: https://markmail.org/message/tblrbrtew6cvrusr
>  *   Proposal:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>  *   Discussion thread: https://markmail.org/message/z6fuvw4regig7aqb
>
...

>   *   Outstanding issues wrt 0.5-technic

Re: Problem accessing /client/ - Service Unavailable

[Nicolas Vazquez]

Hi Jisha,

Just adding to Luis' comments, granting privileges shouldn't be necessary,
the script should handle that for you. Please consider the steps in the
documentation as well:
http://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html#database-installation-and-configuration

Regards,
Nicolas Vazquez

El vie., 8 may. 2020 a las 10:45, Luis Martinez
() escribió:

> Sure,
>
>
> this line contains the user and password for the user cloud, I also
> changed the password for the user root
>
> cloudstack-setup-databases cloud:Password1@localhost
> --deploy-as=root:Password1
>
> here are the instructions to change the password for root
>
> 1.- after installing mysql runs this (sudo mysql_secure_installation)
> running this will ask you for root password, press (enter) because there
> is no password at the moment then it will ask you if you want to change
> the root password, press y (remember the password you are going to use)
> and for the following questions press y
>
> 2.- service mysql restart
> 3.- mysql -u root -p (this line will allow you to connect to mysql and
> it will ask you for root password )
>
> 4.- run the following lines
>
> GRANT ALL PRIVILEGES ON *.* TO 'cloud'@'%';
> GRANT ALL PRIVILEGES ON *.* TO 'root'@'%';
> FLUSH PRIVILEGES;
> quit
>
> 5.- service mysql restart
>
> 6.- ready to run this line
>
> cloudstack-setup-databases cloud:(any password you want to use, this
> will be encrypted and saved in db.properties)@localhost
> --deploy-as=root:*(here use the password for mysql root)*
>
> *7.- run the rest of you process
> *
>
> **On 5/8/2020 8:46 AM, Jisha Ashokan wrote:
>
> > Thank you, but the password is encrypted in
> /etc/cloudstack/management/db.properties . Can you please tell me how did
> you change the password?
> >
> > Thank you,
> >
> > On 2020/05/08 11:55:38, Luis  wrote:
> >> I had the same problem and it may be because the user doesn't have the
> correct privileges to the database. You have to login to the database and
> grant the user access to the database.
> >>
> >> Sent from Yahoo Mail on Android
> >>
> >>On Fri, May 8, 2020 at 2:23 AM, Jisha Ashokan
> wrote:   Hello,
> >>
> >> After installing Cloudstack,
> >>
> >> IP:8080/client/
> >>
> >> gives HTTP ERROR 503
> >> Problem accessing /client/. Reason: Service Unavailable
> >>
> >> Tried restarting using
> >>
> >> service cloudstack-management restart
> >>
> >> Accessing the URL, and
> >>
> >> grep -i -E 'error|exception'
> /var/log/cloudstack/management/management-server.log gives
> >>
> >> --
> >> 2020-05-08 10:46:21,300 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context initialization -
> cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to
> check for database integrity.
> >> org.springframework.context.ApplicationContextException: Failed to
> start bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to
> check for database integrity.
> >> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to
> acquire lock to check for database integrity.
> >> 2020-05-08 11:28:04,678 ERROR [c.c.u.d.DbUtil] (main:null) (logid:)
> GET_LOCK() throws exception
> >> java.sql.SQLException: Operation not allowed for a result set of type
> ResultSet.TYPE_FORWARD_ONLY.
> >>  at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129)
> >>  at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
> >>  at
> com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
> >> 2020-05-08 11:28:04,684 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context initialization -
> cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to
> check for database integrity.
> >> org.springframework.context.ApplicationContextException: Failed to
> start bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to
> check for database integrity.
> >> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to
> acquire lock to check for database integrity.
> >> --
> >>
> >> Please help.
> >>
> >>
> >>
>

Re: Problem accessing /client/ - Service Unavailable

[Luis Martinez]

Sure,


this line contains the user and password for the user cloud, I also 
changed the password for the user root


cloudstack-setup-databases cloud:Password1@localhost 
--deploy-as=root:Password1


here are the instructions to change the password for root

1.- after installing mysql runs this (sudo mysql_secure_installation) 
running this will ask you for root password, press (enter) because there 
is no password at the moment then it will ask you if you want to change 
the root password, press y (remember the password you are going to use) 
and for the following questions press y


2.- service mysql restart
3.- mysql -u root -p (this line will allow you to connect to mysql and 
it will ask you for root password )


4.- run the following lines

GRANT ALL PRIVILEGES ON *.* TO 'cloud'@'%';
GRANT ALL PRIVILEGES ON *.* TO 'root'@'%';
FLUSH PRIVILEGES;
quit

5.- service mysql restart

6.- ready to run this line

cloudstack-setup-databases cloud:(any password you want to use, this 
will be encrypted and saved in db.properties)@localhost 
--deploy-as=root:*(here use the password for mysql root)*


*7.- run the rest of you process
*

**On 5/8/2020 8:46 AM, Jisha Ashokan wrote:


Thank you, but the password is encrypted in  
/etc/cloudstack/management/db.properties . Can you please tell me how did you 
change the password?

Thank you,

On 2020/05/08 11:55:38, Luis  wrote:

I had the same problem and it may be because the user doesn't have the correct 
privileges to the database. You have to login to the database and grant the 
user access to the database.

Sent from Yahoo Mail on Android
  
   On Fri, May 8, 2020 at 2:23 AM, Jisha Ashokan wrote:   Hello,


After installing Cloudstack,

IP:8080/client/

gives HTTP ERROR 503
Problem accessing /client/. Reason: Service Unavailable

Tried restarting using

service cloudstack-management restart

Accessing the URL, and

grep -i -E 'error|exception' 
/var/log/cloudstack/management/management-server.log gives

--
2020-05-08 10:46:21,300 WARN  [o.a.c.s.m.c.ResourceApplicationContext] 
(main:null) (logid:) Exception encountered during context initialization - 
cancelling refresh attempt: 
org.springframework.context.ApplicationContextException: Failed to start bean 
'cloudStackLifeCycle'; nested exception is 
com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
check for database integrity.
org.springframework.context.ApplicationContextException: Failed to start bean 
'cloudStackLifeCycle'; nested exception is 
com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
check for database integrity.
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to acquire 
lock to check for database integrity.
2020-05-08 11:28:04,678 ERROR [c.c.u.d.DbUtil] (main:null) (logid:) GET_LOCK() 
throws exception
java.sql.SQLException: Operation not allowed for a result set of type 
ResultSet.TYPE_FORWARD_ONLY.
     at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129)
     at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
     at 
com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
2020-05-08 11:28:04,684 WARN  [o.a.c.s.m.c.ResourceApplicationContext] 
(main:null) (logid:) Exception encountered during context initialization - 
cancelling refresh attempt: 
org.springframework.context.ApplicationContextException: Failed to start bean 
'cloudStackLifeCycle'; nested exception is 
com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
check for database integrity.
org.springframework.context.ApplicationContextException: Failed to start bean 
'cloudStackLifeCycle'; nested exception is 
com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
check for database integrity.
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to acquire 
lock to check for database integrity.
--

Please help.

   

Re: Problem accessing /client/ - Service Unavailable

[Jisha Ashokan]

Now, I see this error : 

Caused by: com.cloud.utils.exception.CloudRuntimeException: 
cleanupForServer:Exception:cleanupForServer:Exception:Table 'cloud.op_lock' 
doesn't exist
Caused by: com.cloud.utils.exception.CloudRuntimeException: 
cleanupForServer:Exception:Table 'cloud.op_lock' doesn't exist
Caused by: java.sql.SQLSyntaxErrorException: Table 'cloud.op_lock' doesn't exist
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120)
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
at 
com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)

However, the table op_lock exists. 

---
| op_host_capacity |
| op_host_transfer |
| op_host_upgrade  |
| op_it_work   |
| op_lock  |
| op_networks  |
| op_nwgrp_work
---

On 2020/05/08 12:50:36, Jisha Ashokan  wrote: 
> Hello,
> 
> Why are these showing different? 
> 
> grep password /etc/cloudstack/management/db.properties
> db.cloud.password=ENC(UXU8b795z8qG6w8Q3/06tk5kjuDhCy4l)
> db.usage.password=ENC(lfGEk0FBmq1HoScapNcRxXMX+nTGAZIf)
> db.simulator.password=cloud
> 
> 
> 
> On 2020/05/08 06:19:28, Jisha Ashokan  wrote: 
> > Hello,
> > 
> > After installing Cloudstack, 
> > 
> > IP:8080/client/
> > 
> > gives HTTP ERROR 503
> > Problem accessing /client/. Reason: Service Unavailable
> > 
> > Tried restarting using 
> > 
> > service cloudstack-management restart
> > 
> > Accessing the URL, and 
> > 
> > grep -i -E 'error|exception' 
> > /var/log/cloudstack/management/management-server.log gives 
> > 
> > --
> > 2020-05-08 10:46:21,300 WARN  [o.a.c.s.m.c.ResourceApplicationContext] 
> > (main:null) (logid:) Exception encountered during context initialization - 
> > cancelling refresh attempt: 
> > org.springframework.context.ApplicationContextException: Failed to start 
> > bean 'cloudStackLifeCycle'; nested exception is 
> > com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> > check for database integrity.
> > org.springframework.context.ApplicationContextException: Failed to start 
> > bean 'cloudStackLifeCycle'; nested exception is 
> > com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> > check for database integrity.
> > Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to 
> > acquire lock to check for database integrity.
> > 2020-05-08 11:28:04,678 ERROR [c.c.u.d.DbUtil] (main:null) (logid:) 
> > GET_LOCK() throws exception 
> > java.sql.SQLException: Operation not allowed for a result set of type 
> > ResultSet.TYPE_FORWARD_ONLY.
> > at 
> > com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129)
> > at 
> > com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
> > at 
> > com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
> > 2020-05-08 11:28:04,684 WARN  [o.a.c.s.m.c.ResourceApplicationContext] 
> > (main:null) (logid:) Exception encountered during context initialization - 
> > cancelling refresh attempt: 
> > org.springframework.context.ApplicationContextException: Failed to start 
> > bean 'cloudStackLifeCycle'; nested exception is 
> > com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> > check for database integrity.
> > org.springframework.context.ApplicationContextException: Failed to start 
> > bean 'cloudStackLifeCycle'; nested exception is 
> > com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> > check for database integrity.
> > Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to 
> > acquire lock to check for database integrity.
> > --
> > 
> > Please help. 
> > 
> > 
> 

Re: [VOTE] Apache CloudStack 4.14.0.0 RC2

[Andrija Panic]

Thanks Nicolas, let's aim to fix that one in 4.15!

On Fri, 8 May 2020, 15:03 Nicolas Vazquez,  wrote:

> Hi,
>
> I'm reverting my vote as the issue was already present in 4.13. There is a
> problem casting between java classes that needs fixing but is not a blocker
> for RC2.
>
> Regards,
> Nicolas Vazquez
>
> El vie., 8 may. 2020 a las 1:20, Nicolas Vazquez ( >)
> escribió:
>
> > Here is a fix for the issue above:
> > https://github.com/apache/cloudstack/pull/4062
> >
> > El jue., 7 may. 2020 a las 15:58, Nicolas Vazquez (<
> > nicovazque...@gmail.com>) escribió:
> >
> >> Hi Andrija,
> >>
> >> I have found this issue when testing RC2:
> >> https://github.com/apache/cloudstack/issues/4061, giving -1 atm.
> >>
> >> Regards,
> >> Nicolas Vazquez
> >>
> >> El mié., 6 may. 2020 a las 17:45, Andrija Panic (<
> andrija.pa...@gmail.com>)
> >> escribió:
> >>
> >>> Hi All,
> >>>
> >>> I've created a 4.14.0.0 release (RC2), with the following artefacts up
> >>> for
> >>> testing and a vote:
> >>>
> >>> Git Branch and Commit SH:
> >>>
> >>>
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200506T2028
> >>> Commit: 377c9c8ab2eecca57b0073065c018fe9a010a520
> >>>
> >>> Source release (checksums and signatures are available at the same
> >>> location):
> >>> https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/
> >>>
> >>> PGP release keys (signed using 3DC01AE8):
> >>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>>
> >>> The vote will be open until 12th May 2020.
> >>>
> >>> For sanity in tallying the vote, can PMC members please be sure to
> >>> indicate
> >>> "(binding)" with their vote?
> >>>
> >>> [ ] +1 approve
> >>> [ ] +0 no opinion
> >>> [ ] -1 disapprove (and reason why)
> >>>
> >>> Additional information:
> >>>
> >>> For users' convenience, I've built packages from
> >>> 377c9c8ab2eecca57b0073065c018fe9a010a520 and published RC2 repository
> >>> here:
> >>> http://packages.shapeblue.com/testing/41400rc2/  (CentOS 7 and
> >>> Debian/generic, both with noredist support)
> >>> and here
> >>>
> >>>
> https://download.cloudstack.org/testing/4.14.0.0-RC20200506T2028/ubuntu/bionic/
> >>> (Ubuntu 18.04 specific, no noredist support - thanks to Gabriel):
> >>>
> >>> The release notes are still work-in-progress, but for the upgrade
> >>> instructions (including the new systemVM templates) you may refer to
> the
> >>> following URL:
> >>>
> >>>
> https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112/upgrading/index.html
> >>>
> >>> 4.14.0.0 systemVM templates are available from here:
> >>> http://download.cloudstack.org/systemvm/4.14/
> >>>
> >>> NOTES on issues fixed in this RC2 release:
> >>>
> >>> (these do *NOT* require a full retest if you were testing RC1 already -
> >>> just if you were affected by these 2 issues):
> >>> -  https://github.com/apache/cloudstack/pull/4055 (explicit timezone
> in
> >>> db.properties, fixes only new installations of 4.14, while for the
> >>> upgrade
> >>> process the documentation has been upgraded accordingly in
> >>> https://github.com/apache/cloudstack-documentation/pull/112/files)
> >>> -  https://github.com/apache/cloudstack/pull/4057   (fix regression
> >>> where
> >>> one could not delete a snapshot created from a volume on Local storage)
> >>>
> >>> Regards,
> >>>
> >>> Andrija Panić
> >>>
> >>
>

Re: Problem accessing /client/ - Service Unavailable

[Jisha Ashokan]

Hello,

Why are these showing different? 

grep password /etc/cloudstack/management/db.properties
db.cloud.password=ENC(UXU8b795z8qG6w8Q3/06tk5kjuDhCy4l)
db.usage.password=ENC(lfGEk0FBmq1HoScapNcRxXMX+nTGAZIf)
db.simulator.password=cloud



On 2020/05/08 06:19:28, Jisha Ashokan  wrote: 
> Hello,
> 
> After installing Cloudstack, 
> 
> IP:8080/client/
> 
> gives HTTP ERROR 503
> Problem accessing /client/. Reason: Service Unavailable
> 
> Tried restarting using 
> 
> service cloudstack-management restart
> 
> Accessing the URL, and 
> 
> grep -i -E 'error|exception' 
> /var/log/cloudstack/management/management-server.log gives 
> 
> --
> 2020-05-08 10:46:21,300 WARN  [o.a.c.s.m.c.ResourceApplicationContext] 
> (main:null) (logid:) Exception encountered during context initialization - 
> cancelling refresh attempt: 
> org.springframework.context.ApplicationContextException: Failed to start bean 
> 'cloudStackLifeCycle'; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> check for database integrity.
> org.springframework.context.ApplicationContextException: Failed to start bean 
> 'cloudStackLifeCycle'; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> check for database integrity.
> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to acquire 
> lock to check for database integrity.
> 2020-05-08 11:28:04,678 ERROR [c.c.u.d.DbUtil] (main:null) (logid:) 
> GET_LOCK() throws exception 
> java.sql.SQLException: Operation not allowed for a result set of type 
> ResultSet.TYPE_FORWARD_ONLY.
>   at 
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129)
>   at 
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
>   at 
> com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
> 2020-05-08 11:28:04,684 WARN  [o.a.c.s.m.c.ResourceApplicationContext] 
> (main:null) (logid:) Exception encountered during context initialization - 
> cancelling refresh attempt: 
> org.springframework.context.ApplicationContextException: Failed to start bean 
> 'cloudStackLifeCycle'; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> check for database integrity.
> org.springframework.context.ApplicationContextException: Failed to start bean 
> 'cloudStackLifeCycle'; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> check for database integrity.
> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to acquire 
> lock to check for database integrity.
> --
> 
> Please help. 
> 
> 

Re: [VOTE] Apache CloudStack 4.14.0.0 RC2

[Nicolas Vazquez]

Hi,

I'm reverting my vote as the issue was already present in 4.13. There is a
problem casting between java classes that needs fixing but is not a blocker
for RC2.

Regards,
Nicolas Vazquez

El vie., 8 may. 2020 a las 1:20, Nicolas Vazquez ()
escribió:

> Here is a fix for the issue above:
> https://github.com/apache/cloudstack/pull/4062
>
> El jue., 7 may. 2020 a las 15:58, Nicolas Vazquez (<
> nicovazque...@gmail.com>) escribió:
>
>> Hi Andrija,
>>
>> I have found this issue when testing RC2:
>> https://github.com/apache/cloudstack/issues/4061, giving -1 atm.
>>
>> Regards,
>> Nicolas Vazquez
>>
>> El mié., 6 may. 2020 a las 17:45, Andrija Panic ()
>> escribió:
>>
>>> Hi All,
>>>
>>> I've created a 4.14.0.0 release (RC2), with the following artefacts up
>>> for
>>> testing and a vote:
>>>
>>> Git Branch and Commit SH:
>>>
>>> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200506T2028
>>> Commit: 377c9c8ab2eecca57b0073065c018fe9a010a520
>>>
>>> Source release (checksums and signatures are available at the same
>>> location):
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/
>>>
>>> PGP release keys (signed using 3DC01AE8):
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>
>>> The vote will be open until 12th May 2020.
>>>
>>> For sanity in tallying the vote, can PMC members please be sure to
>>> indicate
>>> "(binding)" with their vote?
>>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>> Additional information:
>>>
>>> For users' convenience, I've built packages from
>>> 377c9c8ab2eecca57b0073065c018fe9a010a520 and published RC2 repository
>>> here:
>>> http://packages.shapeblue.com/testing/41400rc2/  (CentOS 7 and
>>> Debian/generic, both with noredist support)
>>> and here
>>>
>>> https://download.cloudstack.org/testing/4.14.0.0-RC20200506T2028/ubuntu/bionic/
>>> (Ubuntu 18.04 specific, no noredist support - thanks to Gabriel):
>>>
>>> The release notes are still work-in-progress, but for the upgrade
>>> instructions (including the new systemVM templates) you may refer to the
>>> following URL:
>>>
>>> https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112/upgrading/index.html
>>>
>>> 4.14.0.0 systemVM templates are available from here:
>>> http://download.cloudstack.org/systemvm/4.14/
>>>
>>> NOTES on issues fixed in this RC2 release:
>>>
>>> (these do *NOT* require a full retest if you were testing RC1 already -
>>> just if you were affected by these 2 issues):
>>> -  https://github.com/apache/cloudstack/pull/4055 (explicit timezone in
>>> db.properties, fixes only new installations of 4.14, while for the
>>> upgrade
>>> process the documentation has been upgraded accordingly in
>>> https://github.com/apache/cloudstack-documentation/pull/112/files)
>>> -  https://github.com/apache/cloudstack/pull/4057   (fix regression
>>> where
>>> one could not delete a snapshot created from a volume on Local storage)
>>>
>>> Regards,
>>>
>>> Andrija Panić
>>>
>>

Re: Problem accessing /client/ - Service Unavailable

[Jisha Ashokan]

Thank you, but the password is encrypted in  
/etc/cloudstack/management/db.properties . Can you please tell me how did you 
change the password? 

Thank you,

On 2020/05/08 11:55:38, Luis  wrote: 
> I had the same problem and it may be because the user doesn't have the 
> correct privileges to the database. You have to login to the database and 
> grant the user access to the database.
> 
> Sent from Yahoo Mail on Android 
>  
>   On Fri, May 8, 2020 at 2:23 AM, Jisha Ashokan wrote:  
>  Hello,
> 
> After installing Cloudstack, 
> 
> IP:8080/client/
> 
> gives HTTP ERROR 503
> Problem accessing /client/. Reason: Service Unavailable
> 
> Tried restarting using 
> 
> service cloudstack-management restart
> 
> Accessing the URL, and 
> 
> grep -i -E 'error|exception' 
> /var/log/cloudstack/management/management-server.log gives 
> 
> --
> 2020-05-08 10:46:21,300 WARN  [o.a.c.s.m.c.ResourceApplicationContext] 
> (main:null) (logid:) Exception encountered during context initialization - 
> cancelling refresh attempt: 
> org.springframework.context.ApplicationContextException: Failed to start bean 
> 'cloudStackLifeCycle'; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> check for database integrity.
> org.springframework.context.ApplicationContextException: Failed to start bean 
> 'cloudStackLifeCycle'; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> check for database integrity.
> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to acquire 
> lock to check for database integrity.
> 2020-05-08 11:28:04,678 ERROR [c.c.u.d.DbUtil] (main:null) (logid:) 
> GET_LOCK() throws exception 
> java.sql.SQLException: Operation not allowed for a result set of type 
> ResultSet.TYPE_FORWARD_ONLY.
>     at 
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129)
>     at 
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
>     at 
> com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
> 2020-05-08 11:28:04,684 WARN  [o.a.c.s.m.c.ResourceApplicationContext] 
> (main:null) (logid:) Exception encountered during context initialization - 
> cancelling refresh attempt: 
> org.springframework.context.ApplicationContextException: Failed to start bean 
> 'cloudStackLifeCycle'; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> check for database integrity.
> org.springframework.context.ApplicationContextException: Failed to start bean 
> 'cloudStackLifeCycle'; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
> check for database integrity.
> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to acquire 
> lock to check for database integrity.
> --
> 
> Please help. 
> 
>   
> 

Re: Problem accessing /client/ - Service Unavailable

[Luis]

I had the same problem and it may be because the user doesn't have the correct 
privileges to the database. You have to login to the database and grant the 
user access to the database.

Sent from Yahoo Mail on Android 
 
  On Fri, May 8, 2020 at 2:23 AM, Jisha Ashokan wrote:   
Hello,

After installing Cloudstack, 

IP:8080/client/

gives HTTP ERROR 503
Problem accessing /client/. Reason: Service Unavailable

Tried restarting using 

service cloudstack-management restart

Accessing the URL, and 

grep -i -E 'error|exception' 
/var/log/cloudstack/management/management-server.log gives 

--
2020-05-08 10:46:21,300 WARN  [o.a.c.s.m.c.ResourceApplicationContext] 
(main:null) (logid:) Exception encountered during context initialization - 
cancelling refresh attempt: 
org.springframework.context.ApplicationContextException: Failed to start bean 
'cloudStackLifeCycle'; nested exception is 
com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
check for database integrity.
org.springframework.context.ApplicationContextException: Failed to start bean 
'cloudStackLifeCycle'; nested exception is 
com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
check for database integrity.
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to acquire 
lock to check for database integrity.
2020-05-08 11:28:04,678 ERROR [c.c.u.d.DbUtil] (main:null) (logid:) GET_LOCK() 
throws exception 
java.sql.SQLException: Operation not allowed for a result set of type 
ResultSet.TYPE_FORWARD_ONLY.
    at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129)
    at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
    at 
com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
2020-05-08 11:28:04,684 WARN  [o.a.c.s.m.c.ResourceApplicationContext] 
(main:null) (logid:) Exception encountered during context initialization - 
cancelling refresh attempt: 
org.springframework.context.ApplicationContextException: Failed to start bean 
'cloudStackLifeCycle'; nested exception is 
com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
check for database integrity.
org.springframework.context.ApplicationContextException: Failed to start bean 
'cloudStackLifeCycle'; nested exception is 
com.cloud.utils.exception.CloudRuntimeException: Unable to acquire lock to 
check for database integrity.
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to acquire 
lock to check for database integrity.
--

Please help. 

  

Re: [DISCUSS] Primate - publishing release and docs

[Rohit Yadav]

Hi Daan,

Thanks for replying and participating. Some points:

  *   The document links within Primate is a different topic than the docs for 
Primate itself, the scope of current discussion is limited to documentation for 
Primate. The doc link within Primate would be done against the 1.0/GA 
milestone, it would require going through all the sections/APIs against the 
current CloudStack docs and put a link (or part of it).
  *   The documentation for Primate currently won't be huge, perhaps a single 
long page would do (to explain how to install).
  *   Primate would be a separately installable package and installing 
cloudstack-management won't automatically trigger installing it (at least in 
the tech preview, we can discuss how we handle longer term starting with GA/1.0 
later).
  *   We've setup automation for all kinds of packaging formats/channels (we 
already have that for rpm/deb and archive formats, except for dockerhub hosting 
which is in discussion with ASF infra). I think publishing artifacts should be 
quick and mostly automated.
  *   Github has a new feature called Github packages for each repo, where one 
can host things like npm, docker packages etc. We can explore this feature.
On a Github release wrt a git tag, we can upload an artifact (I've seen many 
projects doing this).
  *   On releasing without voting, my thought and preference is that as our 
users test Primate, and report bugs and until GA/1.0 we fix those issues, 
implement missing feature users get faster fixes via a "preview" or "testing" 
or "beta" release channel periodically (deb/rpms repos, archives, docker 
container builds).

Doing this would require that we agree on this strategy, without a single 
tag/version but a set of releases (with a timestamp, so packages would look 
like cloudstack-primate-$version-$date). So effectively we're saying - let's 
release the tech preview without doing an official release (which would mean a 
fix git tag/version). This is where the discussion of a single tech preview 
release vs rolling tech preview release would come in.

Looking forward to more feedback from our dev/user community and of course our 
VP @Sven Vogel who has been a major Primate-SIG 
collaborator. Thanks.

Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Daan Hoogland 
Sent: Thursday, May 7, 2020 12:34
To: dev 
Cc: users@cloudstack.apache.org 
Subject: Re: [DISCUSS] Primate - publishing release and docs

Hey Rohit,
This is a lot to take in at once. We have discussed some of those off line
but let me give my initial answers to your discussion points inline.
Hopefully those more directly involved and with more at stake can give some
input as well.

On Wed, May 6, 2020 at 3:03 PM Rohit Yadav 
wrote:

> All,
>
> With this thread I want to start a discussion around:
>
>   *   How do we host/publish technical preview release
>   *   How do we host/publish technical preview documentation (release
> notes, setup/install instructions)
>
> To set the expectation:
>
>   *   This thread limits discussion wrt technical preview (beta).
>   *   Plan we've already agreed, just to recap: 

...

>   *   References:
>  *   Voting thread: https://markmail.org/message/tblrbrtew6cvrusr
>  *   Proposal:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>  *   Discussion thread: https://markmail.org/message/z6fuvw4regig7aqb
>
...

>   *   Outstanding issues wrt 0.5-technical-preview milestone:
> https://github.com/apache/cloudstack-primate/milestone/1
>   *   Oustanding PRs for 0.5-technical-preview:
> https://github.com/apache/cloudstack-primate/pulls?q=is%3Aopen+is%3Apr+no%3Amilestone
>
...

>   1.  Documentation for tech preview:
>
> It is preferred that Primate be developed, maintained and released
> separately from CloudStack. Primate would require its own docs
> website/location for hosting release notes etc. I can think of two ways:
>
>  *   For tech preview, let's just a section/topic on Primate on how
> users can install and use Primate on the docs website:
> http://docs.cloudstack.apache.org/en/latest/primateguide (it does not
> exist, just for example)
> For each CloudStack release, the docs may be updated, including list of
> supported/required versions matrix (both CloudStack and Primate).
> For tech preview, this needs to be on the 4.14.0.0 docs website.
>
>  *   On Github wiki: https://github.com/apache/cloudstack-primate/wiki
> we can maintain a copy of text/pages from above ^^, as well as links on the
> Github release for every git tag. A general guide (agnostic of Primate
> version) could be written/hosted there.
> (similar to CloudStack releases, for example:
> https://github.com/apache/cloudstack/releases/tag/4.13.0.0)
>
I think Primate should be documented by means of help pop-ups with links to
the underlaying API and admin docs. How big do you expect this
do