I entered a new bug last week regarding how the installer
was broken in two different ways when doing a hard drive
install. I also commented on someone else's problem with
their hard drive install, saying that it was similiar to the
problem I had. My first bug report was closed, being called
a duplicate of the other report (2506). That report was
subsequently closed, saying reopen if it is really broken.
Unfortunately, I don't appear to be able to reopen that bug
(or I can't find that option easily in bugzilla, possibly
because I didn't submit that one). There is no boot.img
mentioned in the Errata, so both of the problems I
encountered still exist in the current set of disks.
Here are brief descriptions of the two problems:
1. Can not upgrade the root partition if it is the
partition containing the install files, fails with an RPM
database not found message after mistakengly unmounting the
2. Can not upgrade the root partition if another partition
contains the install files, if that partition is mentioned
in the /etc/fstab. This causes some strange symlink problem
having to do with /tmp/hdimage to appear.
I consider these bugs severe since most likely the root
partition someone is upgrading either contains the install
files, or the partition that contains them is going to be in
the /etc/fstab. This means most hard drive based upgrades
Feel free to email me for further info...
*** This bug has been marked as a duplicate of 2506 ***
Commit pushed to master at https://github.com/openshift/origin-web-console
Merge pull request #2847 from sg00dwin/empty-project-list-issue2846
Automatic merge from submit-queue.
Hide the .project-list when filtered results are 0
<img width="822" alt="screen shot 2018-02-22 at 10 23 07 am" src="https://user-images.githubusercontent.com/1874151/36546857-704d55fe-17ba-11e8-8556-1cdd17946394.png">