Failed to Start Kimchi after Updating to ver.1.1.8-1

[wikisuite]

Failed to Start Kimchi after Updating to ver.1.1.8-1

[pcbaldwin]

Hey techana. That was a bug in the wok 2.3.0 RPM packaging: WikiSuite/wok#1

The updated package (wok 2.5.0) is sitting in the test yum repositories (yum --enablerepo=clearos-contribs-testing), but I'll see if I can get the update pushed through to the live yum repositories.

[techana]

Yes, this issue described above occurred to me after upgrading from wok 2.3.0 to wok 2.5.0, which comes with app-kimchi 1.1.8-1.

[pcbaldwin]

This type of RPM packaging issue is always a bit messy. When the wok package is upgraded from 2.3.0 to 2.5.0, this is the order of the install:

Running transaction
  Updating   : wok-2.5.0-1.v7.noarch    
  Installing : spice-html5-0.1.7-1.el7.noarch           
  Updating   : kimchi-2.5.0-0.v7.noarch                 
  Updating   : 1:app-kimchi-core-1.1.9-1.gloo7.noarch   
  Updating   : 1:app-kimchi-1.1.9-1.gloo7.noarch        
  Cleanup    : 1:app-kimchi-1.1.7-1.v7.noarch           
  Cleanup    : 1:app-kimchi-core-1.1.7-1.v7.noarch      
  Cleanup    : kimchi-2.3.1-0.v7.noarch                 
  Cleanup    : wok-2.3.1-0.v7.noarch      <-- this is where dhparams.pem is deleted

Adding a post-install check for dhparams.pem in wok 2.5.0 won't work since that file still exists at that point of the RPM upgrade process. I'm sure there's a good reason for this RPM behavior, but it makes things a bit more challenging.

More to come.