[ClusterLabs] [EXT] Re: Re: Q: crm shell & shadow CIB; is it broken in SLES15 SP6?

[Windl, Ulrich]

Yes, I realized that both “commit” are not the same. Wouldn’t “force” and “replace” also apply when committing a shadow CIB?
I think things are needlessly complicated as they are now.

Kind regards,
Ulrich Windl

From: Users <users-bounces at clusterlabs.org> On Behalf Of Xin Liang via Users
Sent: Wednesday, June 25, 2025 2:11 PM
To: Cluster Labs - All topics related to open-source clustering welcomed <users at clusterlabs.org>
Cc: Xin Liang <xliang at suse.com>
Subject: [EXT] Re: [ClusterLabs] Re: Q: crm shell & shadow CIB; is it broken in SLES15 SP6?

Hi Ulrich,

I just noticed that the first error is from `crm->configure->commit`, please see the help info `crm configure help commit`
The usage only accepts:
```
Usage:

commit [force] [replace]
```

On Wed, Jun 25, 2025 at 6:01 PM Windl, Ulrich <u.windl at ukr.de<mailto:u.windl at ukr.de>> wrote:
Hi!

I see that I started the commands from a different context.
And that seems to be the point; I tried:
crm(shadow/h01)configure# up
crm(shadow/h01)# cib
crm(shadow/h01)cib# commit shadow
INFO: cib.commit: committed 'shadow' shadow CIB to the cluster

Now the config is being applied.

Isn’t it odd that the syntax of “commit” varies with the context?

Kind regards,
Ulrich Windl

From: Users <users-bounces at clusterlabs.org<mailto:users-bounces at clusterlabs.org>> On Behalf Of Xin Liang via Users
Sent: Wednesday, June 25, 2025 11:50 AM
To: Cluster Labs - All topics related to open-source clustering welcomed <users at clusterlabs.org<mailto:users at clusterlabs.org>>
Cc: Xin Liang <xliang at suse.com<mailto:xliang at suse.com>>
Subject: [EXT] Re: [ClusterLabs] Q: crm shell & shadow CIB; is it broken in SLES15 SP6?

Hi Ulrich,

How to trigger? I can't reproduce with crmsh-4.6.2+20250612.e0482fa-150600.3.35.2.noarch
```
15sp6-1:~ # crm
crm(live/15sp6-1)# cib
crm(live/15sp6-1)cib# new shadow
INFO: cib.new<http://cib.new>: shadow shadow CIB created
crm(shadow/15sp6-1)cib# up
crm(shadow/15sp6-1)# coni
INFO: "coni" is accepted as "configure"
crm(shadow/15sp6-1)configure# primitive d Dummy
crm(shadow/15sp6-1)configure# commit
(unpack_config)         warning: Blind faith: not fencing unseen nodes
crm(shadow/15sp6-1)configure# up
crm(shadow/15sp6-1)# cib
crm(shadow/15sp6-1)cib# diff
Diff: --- 0.6.0 2
Diff: +++ 0.7.0 (null)
+  /cib:  @epoch=7
++ /cib/configuration/resources:  <primitive id="d" class="ocf" provider="heartbeat" type="Dummy"/>
crm(shadow/15sp6-1)cib# commit shadow
INFO: cib.commit: committed 'shadow' shadow CIB to the cluster
```


On Wed, Jun 25, 2025 at 4:39 PM Windl, Ulrich <u.windl at ukr.de<mailto:u.windl at ukr.de>> wrote:
Hi!

Using an old changelog of mine I tried to repeat the configuration I had made in SLES12 (now with SLS15 SP6).
The configuration uses crm shell and a “shadow CIB”.

I could create the CIB justz fine like this:
crm(live/h01)# cib new shadow
INFO: cib.new<http://cib.new>: shadow shadow CIB created

And I also could add the configuration changes , and verify them.

However when using “commit” the live CIB wasn’t updated, and trying  a command like “commit shadow” results in an error message like this:
crm(shadow/h01)configure# commit
crm(shadow/h01)configure#
…
crm(shadow/h01)configure# commit shadow
ERROR: syntax parsing 'configure.commit shadow'

So what the freature dropped, or was it changed, or is the crm shell just broken?
Version used is crmsh-4.6.2+20250612.e0482fa-150600.3.35.2.noarch

Kind regards,
Ulrich Windl

_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20250625/3ecd6d8d/attachment-0001.htm>