# "Currently upgrading" even after a rebuild

**URL:** https://meta.discourse.org/t/currently-upgrading-even-after-a-rebuild/33557
**Category:** Bug
**Created:** [2015年九月22日 06:53 UTC](https://meta.discourse.org/t/currently-upgrading-even-after-a-rebuild/33557 "2015-09-22T06:53:38Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [2015年九月22日 21:02 UTC](https://meta.discourse.org/t/currently-upgrading-even-after-a-rebuild/33557/7 "2015-09-22T21:02:10Z")

</div>

Had you started an upgrade in the web side before you did it on the command line? I’m just trying to understand how the flag got stuck in that position.

The easiest way to unlock it is to flush redis.

```plaintext
$ ./launcher enter app
$ redis-cli flushall

```

---

_[View the full topic](https://meta.discourse.org/t/currently-upgrading-even-after-a-rebuild/33557)._