<p>I'm using liquibase in project and it is working fine so far. 
<br/>I added a new changeset and it works good locally, once deployed , the container's state hungs with the following statement:
<strong>"liquibase: Waiting for changelog lock..."</strong>.
<br/><br/>
The limit resources of the deployment are not set.
<br/>The update of table "databasechangeloglock" is not working, cause the pod keeps locking it.
<br/>
How can i solve this?</p>

maryam
<p>See <a href="https://stackoverflow.com/questions/30386274/is-there-a-liquibase-lock-timeout/30398337">other question here</a>. If the lock happens and the process exits unexpectedly, then the lock will stay there. </p>

<p>According to <a href="https://stackoverflow.com/a/19081612/13752392">this answer</a>, you can remove the lock by running SQL directly:</p>

<pre class="lang-sql prettyprint-override"><code>UPDATE DATABASECHANGELOGLOCK SET LOCKED=0, LOCKGRANTED=null, LOCKEDBY=null where ID=1;
</code></pre>

<blockquote>
  <p>Note: Depending on your DB engine, you may need to use FALSE or 'f' instead of <code>0</code> for the <code>LOCKED</code> value.</p>
</blockquote>

<p>Per your question, your process itself is creating a new lock and still failing every time, then most likely it is the process that is exiting/failing for a different reason (or checking for the lock in the wrong order. </p>

<p>Another option is to consider the <a href="https://github.com/liquibase/liquibase-nochangeloglock" rel="noreferrer">Liquibase No ChangeLog Lock extension</a>.</p>

<blockquote>
  <p>Note: This is probably a last resort. The extension could be an option if you were having more trouble with the changelog lock than getting any benefit (e.g. only running one instance of the app and don't really need locking). It is likely not the "best" solution, but is certainly an option depending on what you need. The README in the link says this too.</p>
</blockquote>
