That would work. As long as it is possible to rollback the campaign it
is fine.
On 10/20/2017 03:18 PM, Alex Jones wrote:
>
> I understand the intention. It makes sense.
>
> One of the other solutions I had considered is to put a check at the
> beginning of SmfCampaign::initExecution(). If the
A rollback will not work if a unexpected cluster-reboot was done before PBE was
enabled. SMF looses its runtime data in that case, so your patch would cause
issues for rollback. The intention is to be able to test the system and then
decide to proceed with rollback or commit. That means reboots
- **summary**: smf: refactor smfd directory structure --> smf: refactor smfd
folders
---
** [tickets:#2633] smf: refactor smfd folders**
**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Tue Oct 17, 2017 11:52 AM UTC by Rafael Odzakow
**Last Updated:** Tue Oct 17, 2017 11:52 AM
---
** [tickets:#2633] smf: refactor smfd directory structure**
**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Tue Oct 17, 2017 11:52 AM UTC by Rafael Odzakow
**Last Updated:** Tue Oct 17, 2017 11:52 AM UTC
**Owner:** nobody
---
Sent from sourceforge.net because opensaf
01:40 PM UTC
**Owner:** Rafael Odzakow
The puropse of this ticket is to decrease campaign execution time, without
rewriting the campaign.
If configured, smfd will automatically upgrade the nodes one by one in a
rolling manner, with actions fetched from all rolling procedures in the
cam
- **status**: review --> fixed
---
** [tickets:#2622] base: double start failed**
**Status:** fixed
**Milestone:** 5.17.10
**Created:** Tue Oct 10, 2017 11:29 AM UTC by Rafael Odzakow
**Last Updated:** Mon Oct 16, 2017 12:41 PM UTC
**Owner:** Rafael Odzakow
Previously named funct
issue was found on ubuntu 14.04 where subsys folder is not created by default.
Move the pid removal to be called after pidofproc.
---
** [tickets:#2622] base: double start failed**
**Status:** review
**Milestone:** 5.17.10
**Created:** Tue Oct 10, 2017 11:29 AM UTC by Rafael Odzakow
**Last
- **status**: assigned --> fixed
---
** [tickets:#2555] smf: execLevel for balanced upgrade**
**Status:** fixed
**Milestone:** 5.17.10
**Created:** Wed Aug 16, 2017 11:39 AM UTC by Rafael Odzakow
**Last Updated:** Fri Aug 18, 2017 03:57 PM UTC
**Owner:** Rafael Odzakow
Currently the
ofproc for amfnd pid.
---
** [tickets:#2622] base: double start failed**
**Status:** review
**Milestone:** 5.17.10
**Created:** Tue Oct 10, 2017 11:29 AM UTC by Rafael Odzakow
**Last Updated:** Tue Oct 10, 2017 11:30 AM UTC
**Owner:** Rafael Odzakow
Previously named function "check_en
---
** [tickets:#2622] double start failed**
**Status:** review
**Milestone:** 5.17.10
**Created:** Tue Oct 10, 2017 11:29 AM UTC by Rafael Odzakow
**Last Updated:** Tue Oct 10, 2017 11:29 AM UTC
**Owner:** Rafael Odzakow
Previously named function "check_env" overwrites pid
- **summary**: double start failed --> [base] double start failed
---
** [tickets:#2622] [base] double start failed**
**Status:** review
**Milestone:** 5.17.10
**Created:** Tue Oct 10, 2017 11:29 AM UTC by Rafael Odzakow
**Last Updated:** Tue Oct 10, 2017 11:29 AM UTC
**Owner:** Raf
* unassigned
**Milestone:** 5.17.10
**Created:** Wed Sep 27, 2017 12:01 PM UTC by Rafael Odzakow
**Last Updated:** Wed Sep 27, 2017 12:01 PM UTC
**Owner:** Rafael Odzakow
Investigation needed. There is a lot of log spam on large installations when
deleting these objects. It could be caused by SMF deletin
ade delete of SMF objects which contain many
> thousand objects.
- **assigned_to**: Rafael Odzakow
- **Component**: unknown --> smf
- **Part**: - --> d
- **Priority**: major --> minor
---
** [tickets:#2599] smf: remove cascading delete for runtime objects**
**Status:** unassig
---
** [tickets:#2599] smf: remove cascading delete for runtime objects**
**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Wed Sep 27, 2017 12:01 PM UTC by Rafael Odzakow
**Last Updated:** Wed Sep 27, 2017 12:01 PM UTC
**Owner:** nobody
Investigation needed. There is a lot of log
- **status**: review --> fixed
- **Comment**:
commit f3ef8eebf44f0eab4dcc65f83fe3119a77ef5067 (HEAD -> develop,
origin/develop)
Author: Rafael Odzakow <rafael.odza...@ericsson.com>
Date: Mon Sep 25 13:52:03 2017 +0200
smf: try to wait for opensafd status before r
ait for opensafd status before executing reboot
**
**Status:** review
**Milestone:** 5.17.10
**Created:** Fri May 19, 2017 10:55 AM UTC by Rafael Odzakow
**Last Updated:** Mon Aug 14, 2017 11:22 AM UTC
**Owner:** Rafael Odzakow
There are cases when opensafd startup is still ongoing and SMF will s
that are
not part of the balanced group to be executed after a balanced procedure.
---
** [tickets:#2555] smf: execLevel for balanced upgrade**
**Status:** assigned
**Milestone:** 5.17.10
**Created:** Wed Aug 16, 2017 11:39 AM UTC by Rafael Odzakow
**Last Updated:** Thu Aug 17, 2017 10:18 AM
- **status**: unassigned --> assigned
- **assigned_to**: Rafael Odzakow
---
** [tickets:#2555] smf: execLevel for balanced upgrade**
**Status:** assigned
**Milestone:** 5.17.10
**Created:** Wed Aug 16, 2017 11:39 AM UTC by Rafael Odzakow
**Last Updated:** Wed Aug 16, 2017 11:39 AM UTC
**Ow
---
** [tickets:#2555] smf: execLevel for balanced upgrade**
**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Wed Aug 16, 2017 11:39 AM UTC by Rafael Odzakow
**Last Updated:** Wed Aug 16, 2017 11:39 AM UTC
**Owner:** nobody
Currently the SMF created balanced procedures get
19, 2017 10:55 AM UTC by Rafael Odzakow
**Last Updated:** Fri Jul 28, 2017 08:24 AM UTC
**Owner:** Rafael Odzakow
There are cases when opensafd startup is still ongoing and SMF will send out a
reboot command for a node. Because opensafd has taken a lock the reboot command
will not be able to c
- **Comment**:
Setting it to minor until it shows up again.
---
** [tickets:#2441] smf: coredump and syslog flood after immnd crash**
**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Apr 27, 2017 09:05 AM UTC by Rafael Odzakow
**Last Updated:** Mon Aug 14, 2017 11:23 AM UTC
- **Priority**: major --> minor
---
** [tickets:#2441] smf: coredump and syslog flood after immnd crash**
**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Apr 27, 2017 09:05 AM UTC by Rafael Odzakow
**Last Updated:** Fri Jul 28, 2017 08:25 AM UTC
**Owner:** Rafael Odzakow
S
---
** [tickets:#2541] nid: order of system log print out is not correct**
**Status:** review
**Milestone:** 5.17.10
**Created:** Wed Aug 02, 2017 07:52 AM UTC by Rafael Odzakow
**Last Updated:** Wed Aug 02, 2017 07:52 AM UTC
**Owner:** Rafael Odzakow
using echo -n in opensafd causes delay
- **status**: review --> fixed
---
** [tickets:#2521] smf: no node locking when procedures are empty**
**Status:** fixed
**Milestone:** 5.17.10
**Created:** Wed Jul 05, 2017 09:13 AM UTC by Rafael Odzakow
**Last Updated:** Wed Jul 19, 2017 10:08 AM UTC
**Owner:** Rafael Odzakow
procedu
for rolling upgrades only
commit 653edb5d9b217f1a3280b5aed8597fb53ffa5f61
---
** [tickets:#2521] smf: no node locking when procedures are empty**
**Status:** review
**Milestone:** 5.17.10
**Created:** Wed Jul 05, 2017 09:13 AM UTC by Rafael Odzakow
**Last Updated:** Thu Jul 13, 2017 03:20 PM
For rolling upgrades only
commit 653edb5d9b217f1a3280b5aed8597fb53ffa5f61 (HEAD -> develop,
origin/develop, ticket-2521)
Author: Rafael Odzakow <rafael.odza...@ericsson.com>
Date: Wed Jul 19 11:52:57 2017 +0200
smf: no node locking when procedures are empty [#2521]
---
**
- **status**: assigned --> review
---
** [tickets:#2521] smf: no node locking when procedures are empty**
**Status:** review
**Milestone:** 5.17.10
**Created:** Wed Jul 05, 2017 09:13 AM UTC by Rafael Odzakow
**Last Updated:** Thu Jul 13, 2017 03:20 PM UTC
**Owner:** Rafael Odza
ets:#2521] smf: no node locking when procedures are empty**
**Status:** assigned
**Milestone:** 5.17.10
**Created:** Wed Jul 05, 2017 09:13 AM UTC by Rafael Odzakow
**Last Updated:** Fri Jul 07, 2017 08:29 AM UTC
**Owner:** Rafael Odzakow
procedures can be empty to improve uptime SMF should not l
- **status**: unassigned --> assigned
---
** [tickets:#2521] smf: remove node locking with empty procedures**
**Status:** assigned
**Milestone:** 5.17.10
**Created:** Wed Jul 05, 2017 09:13 AM UTC by Rafael Odzakow
**Last Updated:** Wed Jul 05, 2017 09:13 AM UTC
**Owner:** Rafael Odza
---
** [tickets:#2521] smf: remove node locking with empty procedures**
**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Wed Jul 05, 2017 09:13 AM UTC by Rafael Odzakow
**Last Updated:** Wed Jul 05, 2017 09:13 AM UTC
**Owner:** Rafael Odzakow
---
Sent from sourceforge.net
- **status**: unassigned --> fixed
- **assigned_to**: Rafael Odzakow
- **Comment**:
fixed in
commit 3e1d1091270fa83cb8efe5458d6050b56f41f001
Author: Rafael Odzakow <rafael.odza...@ericsson.com>
Date: Fri Jun 30 10:57:36 2017 +0200
smf: 20 seconds timeout in getting node de
For the node that is not allowed to join the CLM cluster will this solution
also block IMM (and other services) from starting up?
---
** [tickets:#2451] clm: Make the cluster reset admin op safe**
**Status:** unassigned
**Milestone:** 5.17.08
**Created:** Wed May 03, 2017 10:51 AM UTC by
This issue is as far as I could see a bug. In other campaign sequences SMF will
wait with rebootTimeout before doing any operation after reboot. In this
campaign sequence the first operation type after a reboot was to to a CLI
command on a payload node. This timed out because the CLI command is
try if mutex is
taken.
---
** [tickets:#2459] try-again for opensafd stop**
**Status:** fixed
**Milestone:** 5.17.08
**Created:** Thu May 11, 2017 12:42 PM UTC by Rafael Odzakow
**Last Updated:** Tue Jun 13, 2017 08:01 AM UTC
**Owner:** Rafael Odzakow
Today there is no way for
Going for a short vacation, here is the untested patch. Use rebootTimeout to
increase the timeout for it.
commit 2ffbd1c5cd3f4193fd631130eef60b17c92892e6 (HEAD -> ticket-2499)
Author: Rafael Odzakow <rafael.odza...@ericsson.com>
Date: Tue Jun 20 16:10:12 2017 +0200
smf: 20 second
It should be enough to wrap getNodeDestination in waitForGetNodeDestination in
SmfCliCommandAction::execute(). Other getNodeDestination calls are not needing
to wait for nodes or have custom code for retry.
---
** [tickets:#2499] SMF: 20 seconds timeout in getting node destination is not
If you have the logs please send them my way.
---
** [tickets:#2499] SMF: 20 seconds timeout in getting node destination is not
enough**
**Status:** unassigned
**Milestone:** 5.17.08
**Created:** Fri Jun 16, 2017 08:04 AM UTC by Tai Dinh
**Last Updated:** Tue Jun 20, 2017 03:03 AM UTC
waitForNodeDestination already uses smfRebootTimeout. Is it still timing out or
was getNodeDestination called without the waitFor wrapper?
---
** [tickets:#2499] SMF: 20 seconds timeout in getting node destination is not
enough**
**Status:** unassigned
**Milestone:** 5.17.08
**Created:** Fri
1, 2017 12:42 PM UTC by Rafael Odzakow
**Last Updated:** Mon May 15, 2017 01:56 PM UTC
**Owner:** Rafael Odzakow
Today there is no way for SMF (or others) to know when opensafd start is
completed. Calling stop when a start is ongoing will not stop opensafd so the
reboot will not shutdown opensa
- **status**: unassigned --> review
---
** [tickets:#2464] smf: try to wait for opensafd status before executing reboot
**
**Status:** review
**Milestone:** 5.17.08
**Created:** Fri May 19, 2017 10:55 AM UTC by Rafael Odzakow
**Last Updated:** Fri May 19, 2017 10:55 AM UTC
**Owner:** Raf
- **status**: assigned --> review
---
** [tickets:#2459] improve state report for opensafd**
**Status:** review
**Milestone:** 5.17.08
**Created:** Thu May 11, 2017 12:42 PM UTC by Rafael Odzakow
**Last Updated:** Thu May 11, 2017 12:43 PM UTC
**Owner:** Rafael Odzakow
Today there is no
- **summary**: graceful shutdown of opensafd --> improve state report for
opensafd
---
** [tickets:#2459] improve state report for opensafd**
**Status:** assigned
**Milestone:** 5.17.08
**Created:** Thu May 11, 2017 12:42 PM UTC by Rafael Odzakow
**Last Updated:** Thu May 11, 2017 12:42
---
** [tickets:#2459] graceful shutdown of opensafd**
**Status:** assigned
**Milestone:** 5.17.08
**Created:** Thu May 11, 2017 12:42 PM UTC by Rafael Odzakow
**Last Updated:** Thu May 11, 2017 12:42 PM UTC
**Owner:** Rafael Odzakow
Today there is no way for SMF (or others) to know when
I consider the AMF objects as an interface and some external code outside of
OpenSAF might be reading that campaignDN attribute.
---
** [tickets:#2419] smf: when fixing ticket #2145 a NBC problem was introduced**
**Status:** wontfix
**Milestone:** 5.2.0
**Created:** Mon Apr 10, 2017 11:11 AM
- **status**: fixed --> unassigned
- **Blocker**: --> False
---
** [tickets:#2402] base: "hardening" use of lockfile in opensafd**
**Status:** unassigned
**Milestone:** 5.2.RC2
**Created:** Wed Mar 29, 2017 10:40 AM UTC by Hans Nordebäck
**Last Updated:** Mon Apr 24, 2017 01:37 PM UTC
I have seen a issue with the lockfile. Here are some parts from the system log:
21:59:15 SC-1 opensafd: Starting OpenSAF Services(5.2.0 -
8767:c1cc2a915e72:default) (Using TCP)
- Reboot command is issued from SC-2:
21:59:16 SC-2 osafsmfd[599]: NO STEP: Reboot node for removal
46 matches
Mail list logo
