[rhq-project/rhq] 899943: [1139735, 1157480] More upgrade use cases that did...
by John Mazzitelli
Branch: refs/heads/release/jon3.3.x
Home: https://github.com/rhq-project/rhq
Commit: 8999436f3bfdc8bb7c311d1f27615c69d455f845
https://github.com/rhq-project/rhq/commit/8999436f3bfdc8bb7c311d1f27615c6...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-10-29 (Wed, 29 Oct 2014)
Changed paths:
M modules/common/cassandra-installer/src/main/java/org/rhq/storage/installer/StorageInstaller.java
M modules/enterprise/server/installer/src/main/java/org/rhq/enterprise/server/installer/Installer.java
M modules/enterprise/server/installer/src/main/java/org/rhq/enterprise/server/installer/InstallerService.java
M modules/enterprise/server/installer/src/main/java/org/rhq/enterprise/server/installer/InstallerServiceImpl.java
M modules/enterprise/server/server-control/src/main/java/org/rhq/server/control/command/AbstractInstall.java
M modules/enterprise/server/server-control/src/main/java/org/rhq/server/control/command/Upgrade.java
Log Message:
-----------
[1139735, 1157480] More upgrade use cases that didn't work.
[1139735] An upgrade with a number of storage nodes > than our replication
factor (>= 4) could fail because our check for the storage cluster
version can fail if the auth info or version info are not replicated
to the currently running SNs. To avoid this, for ugrades we now push
all storage cluster interaction to the post-upgrade step (i.e.
rhqctl --storage-schema). This includes the schema creation for a new,
remote storage cluster.
[1157480] An upgrade of standalone storage node can fail because those
installs may not have set proper DB props in rhq-server.properties. It
wasn't required in the past but it is now. In the code we now make sure
the properties are copied forward on upgrade. But there is also doco needed
here because prior to upgrade from an earlier version, using standalone
SNs, the old rhq-server.properties files will need to be updated.
Also, update the --list-versions report to better reflect that it may need
all SNs to be running to perform the storage schema version check.
(cherry picked from commit 1b45c2af77fe3a4670bc4317508780f80ae3f0bc)
Signed-off-by: Jay Shaughnessy <jshaughn(a)redhat.com>
Commit: 3fcbd30e69b1611c95b842ec9651e80f1618c793
https://github.com/rhq-project/rhq/commit/3fcbd30e69b1611c95b842ec9651e80...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-10-29 (Wed, 29 Oct 2014)
Changed paths:
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/rest/ResourceHandlerBean.java
Log Message:
-----------
Merge branch 'release/jon3.3.x' of github.com:rhq-project/rhq into release/jon3.3.x
Commit: 65f745fc70ae63045476ba8e0cd641cda1000677
https://github.com/rhq-project/rhq/commit/65f745fc70ae63045476ba8e0cd641c...
Author: John Mazzitelli <mazz(a)redhat.com>
Date: 2014-10-29 (Wed, 29 Oct 2014)
Changed paths:
M modules/enterprise/agent/src/main/java/org/rhq/enterprise/agent/AgentMain.java
M modules/enterprise/agent/src/main/java/org/rhq/enterprise/agent/i18n/AgentI18NResourceKeys.java
M modules/enterprise/server/server-control/src/main/java/org/rhq/server/control/command/AbstractInstall.java
Log Message:
-----------
BZ 1158228 - to support install on Windows, allow for agent to be told to reload its agent config xml via marker file
(cherry picked from commit 438e10b42c4d8725637eb4582b0a7d072b040ee2)
Signed-off-by: Jay Shaughnessy <jshaughn(a)redhat.com>
Compare: https://github.com/rhq-project/rhq/compare/73e845e155b2...65f745fc70ae
9 years, 6 months
[rhq-project/rhq] 1b45c2: [1139735, 1157480] More upgrade use cases that did...
by Jay Shaughnessy
Branch: refs/heads/master
Home: https://github.com/rhq-project/rhq
Commit: 1b45c2af77fe3a4670bc4317508780f80ae3f0bc
https://github.com/rhq-project/rhq/commit/1b45c2af77fe3a4670bc4317508780f...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-10-29 (Wed, 29 Oct 2014)
Changed paths:
M modules/common/cassandra-installer/src/main/java/org/rhq/storage/installer/StorageInstaller.java
M modules/enterprise/server/installer/src/main/java/org/rhq/enterprise/server/installer/Installer.java
M modules/enterprise/server/installer/src/main/java/org/rhq/enterprise/server/installer/InstallerService.java
M modules/enterprise/server/installer/src/main/java/org/rhq/enterprise/server/installer/InstallerServiceImpl.java
M modules/enterprise/server/server-control/src/main/java/org/rhq/server/control/command/AbstractInstall.java
M modules/enterprise/server/server-control/src/main/java/org/rhq/server/control/command/Upgrade.java
Log Message:
-----------
[1139735, 1157480] More upgrade use cases that didn't work.
[1139735] An upgrade with a number of storage nodes > than our replication
factor (>= 4) could fail because our check for the storage cluster
version can fail if the auth info or version info are not replicated
to the currently running SNs. To avoid this, for ugrades we now push
all storage cluster interaction to the post-upgrade step (i.e.
rhqctl --storage-schema). This includes the schema creation for a new,
remote storage cluster.
[1157480] An upgrade of standalone storage node can fail because those
installs may not have set proper DB props in rhq-server.properties. It
wasn't required in the past but it is now. In the code we now make sure
the properties are copied forward on upgrade. But there is also doco needed
here because prior to upgrade from an earlier version, using standalone
SNs, the old rhq-server.properties files will need to be updated.
Also, update the --list-versions report to better reflect that it may need
all SNs to be running to perform the storage schema version check.
9 years, 6 months
[rhq-project/rhq] 07c3db: Bug 1154678 - [EAP6] - Newly created datasource is...
by Thomas Segismont
Branch: refs/heads/release/jon3.3.x
Home: https://github.com/rhq-project/rhq
Commit: 07c3db0afe16e0105dc026f1b62b401f52311bf5
https://github.com/rhq-project/rhq/commit/07c3db0afe16e0105dc026f1b62b401...
Author: Thomas Segismont <tsegismo(a)redhat.com>
Date: 2014-10-29 (Wed, 29 Oct 2014)
Changed paths:
R modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/DatasourceEnabledAttributeHelper.java
M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/DatasourcesComponent.java
Log Message:
-----------
Bug 1154678 - [EAP6] - Newly created datasource is not enabled even when you have set Enabled=true -- user should be at least warned
When the datasource was created, the 'enabled' attribute was supplied to the EAP6 management interface.
But setting the attribute to true does not enable the datasource. An extra server reload is needed.
To enable a datasource without a server reload, the 'enable' operation needs to be called.
So now the DatasourcesComponent class:
-> no longer supplies the 'enabled' attribute to the CreateResourceDelegate
-> reads the state of the datasource after creation
-> invokes the 'enable' or 'disable' operation (as needed) after creation
(cherry picked from commit d5e65f48de47b1c3258277e5e3e7d16881b679fc)
Signed-off-by: Libor Zoubek <lzoubek(a)redhat.com>
Commit: 42a2d2f80c2325f3403ff35cba7fbd9669434525
https://github.com/rhq-project/rhq/commit/42a2d2f80c2325f3403ff35cba7fbd9...
Author: Thomas Segismont <tsegismo(a)redhat.com>
Date: 2014-10-29 (Wed, 29 Oct 2014)
Changed paths:
M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/DatasourcesComponent.java
Log Message:
-----------
Bug 1154678 - [EAP6] - Newly created datasource is not enabled even when you have set Enabled=true -- user should be at least warned
Fix error in connection properties management code: do not clutter the created datasource Address
(regression detected in Jenkins)
(cherry picked from commit deff314454c6a055c407429032686054d04e6a31)
Signed-off-by: Libor Zoubek <lzoubek(a)redhat.com>
Compare: https://github.com/rhq-project/rhq/compare/c69f16666637...42a2d2f80c23
9 years, 6 months
