Created attachment 1279593[details]
Sosreport and all logs in /var/log, /tmp/ from rhvh
Description of problem:
It reports "No packages marked for update" when upgrade from rhvh-4.1-20170506 to rhvh-4.1-20170512 via "# yum update".
But can access upgrade process with " #yum install redhat-virtualization-host-image-update-4.1-20170512.0.el7_3.noarch.rpm "
Version-Release number of selected component (if applicable):
From:
redhat-virtualization-host-4.1-20170506.0
imgbased-0.9.24-0.1.el7ev.noarch
redhat-virtualization-host-image-update-placeholder-4.1-1.1.el7.noarch
To:
redhat-virtualization-host-4.1-20170512.0
imgbased-0.9.25-0.1.el7ev.noarch
redhat-virtualization-host-image-update-4.1-20170512.0.el7_3.noarch.rpm
How reproducible:
100%
Steps to Reproduce:
1. Install RHVH 4.1.2 build redhat-virtualization-host-4.1-20170506.0 via interactive anaconda.
2. Login RHVH, setup local repos(rhvh-4.1-20170512.0) and update to rhvh-4.1-20170512.0:
# yum update
3. Download redhat-virtualization-host-image-update-4.1-20170512.0.el7_3.noarch.rpm, and update to rhvh-4.1-20170512.0:
# yum install redhat-virtualization-host-image-update-4.1-20170512.0.el7_3.noarch.rpm
Actual results:
1. After step 2, it reports "No packages marked for update":
[root@ibm-x3650m5-04 home]# yum update
Loaded plugins: imgbased-persist, product-id, search-disabled-repos, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Repo rhel-7-server-rhvh-4-source-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem
Repo rhel-7-server-rhvh-4-source-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem
Repo rhel-7-server-rhvh-4-beta-debug-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem
Repo rhel-7-server-rhvh-4-beta-debug-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem
Repo rhel-7-server-rhvh-4-debug-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem
Repo rhel-7-server-rhvh-4-debug-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem
Repo rhel-7-server-rhvh-4-beta-source-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem
Repo rhel-7-server-rhvh-4-beta-source-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem
Repo rhel-7-server-rhvh-4-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem
Repo rhel-7-server-rhvh-4-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem
Repo rhel-7-server-rhvh-4-beta-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem
Repo rhel-7-server-rhvh-4-beta-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem
rhel-7-server-rhvh-4-beta-debug-rpms | 2.9 kB 00:00:00
rhel-7-server-rhvh-4-beta-rpms | 2.9 kB 00:00:00
rhel-7-server-rhvh-4-beta-source-rpms | 2.9 kB 00:00:00
rhel-7-server-rhvh-4-debug-rpms | 2.9 kB 00:00:00
rhel-7-server-rhvh-4-rpms | 2.9 kB 00:00:00
rhel-7-server-rhvh-4-source-rpms | 2.9 kB 00:00:00
(1/6): rhel-7-server-rhvh-4-beta-debug-rpms/primary_db | 1.7 kB 00:00:00
(2/6): rhel-7-server-rhvh-4-source-rpms/primary_db | 4.1 kB 00:00:00
(3/6): rhel-7-server-rhvh-4-beta-rpms/primary_db | 9.4 kB 00:00:00
(4/6): rhel-7-server-rhvh-4-beta-source-rpms/primary_db | 4.1 kB 00:00:00
(5/6): rhel-7-server-rhvh-4-rpms/primary_db | 9.4 kB 00:00:00
(6/6): rhel-7-server-rhvh-4-debug-rpms/primary_db | 1.7 kB 00:00:00
No packages marked for update
2. After step 3, can upgrade to rhvh-4.1-20170512.0.
Excepted results:
After step 2, should upgrade to rhvh-4.1-20170512.0 successful
Additional info:
1. Also encountered this issue when upgrade from rhvh-4.1-0.20170421.0 to rhvh-4.1-20170512.0
2. No such issue when upgrade from rhvh-4.1-0.20170202.0 to rhvh-4.1-20170512.0 on the same machine with the same local repos.
Sorry, Ying. This bug has attention.
We're waiting on package signing in order to build tomorrow, which will resolve this. I was hoping for signing today, but did not get it...
Test Version:
From:
redhat-virtualization-host-4.1-20170506.0
imgbased-0.9.24-0.1.el7ev.noarch
redhat-virtualization-host-image-update-placeholder-4.1-1.1.el7.noarch
To:
redhat-virtualization-host-4.1-20170518.0
imgbased-0.9.26-0.1.el7ev.noarch
redhat-virtualization-host-image-update-4.1-20170518.0.el7_3.noarch
Test steps:
Same as comment 0
Test results:
After step 2, upgrade to rhvh-4.1-20170518.0 successful
Upgrade from redhat-virtualization-host-4.1-20170421.0 to rhvh-4.1-20170518.0 also successful.
So this bug is fixed in redhat-virtualization-host-4.1-20170518.0, change the status to VERIFIED.
Created attachment 1279593 [details] Sosreport and all logs in /var/log, /tmp/ from rhvh Description of problem: It reports "No packages marked for update" when upgrade from rhvh-4.1-20170506 to rhvh-4.1-20170512 via "# yum update". But can access upgrade process with " #yum install redhat-virtualization-host-image-update-4.1-20170512.0.el7_3.noarch.rpm " Version-Release number of selected component (if applicable): From: redhat-virtualization-host-4.1-20170506.0 imgbased-0.9.24-0.1.el7ev.noarch redhat-virtualization-host-image-update-placeholder-4.1-1.1.el7.noarch To: redhat-virtualization-host-4.1-20170512.0 imgbased-0.9.25-0.1.el7ev.noarch redhat-virtualization-host-image-update-4.1-20170512.0.el7_3.noarch.rpm How reproducible: 100% Steps to Reproduce: 1. Install RHVH 4.1.2 build redhat-virtualization-host-4.1-20170506.0 via interactive anaconda. 2. Login RHVH, setup local repos(rhvh-4.1-20170512.0) and update to rhvh-4.1-20170512.0: # yum update 3. Download redhat-virtualization-host-image-update-4.1-20170512.0.el7_3.noarch.rpm, and update to rhvh-4.1-20170512.0: # yum install redhat-virtualization-host-image-update-4.1-20170512.0.el7_3.noarch.rpm Actual results: 1. After step 2, it reports "No packages marked for update": [root@ibm-x3650m5-04 home]# yum update Loaded plugins: imgbased-persist, product-id, search-disabled-repos, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Repo rhel-7-server-rhvh-4-source-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem Repo rhel-7-server-rhvh-4-source-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem Repo rhel-7-server-rhvh-4-beta-debug-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem Repo rhel-7-server-rhvh-4-beta-debug-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem Repo rhel-7-server-rhvh-4-debug-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem Repo rhel-7-server-rhvh-4-debug-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem Repo rhel-7-server-rhvh-4-beta-source-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem Repo rhel-7-server-rhvh-4-beta-source-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem Repo rhel-7-server-rhvh-4-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem Repo rhel-7-server-rhvh-4-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem Repo rhel-7-server-rhvh-4-beta-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877.pem Repo rhel-7-server-rhvh-4-beta-rpms forced skip_if_unavailable=True due to: /etc/pki/entitlement/5858345830546115877-key.pem rhel-7-server-rhvh-4-beta-debug-rpms | 2.9 kB 00:00:00 rhel-7-server-rhvh-4-beta-rpms | 2.9 kB 00:00:00 rhel-7-server-rhvh-4-beta-source-rpms | 2.9 kB 00:00:00 rhel-7-server-rhvh-4-debug-rpms | 2.9 kB 00:00:00 rhel-7-server-rhvh-4-rpms | 2.9 kB 00:00:00 rhel-7-server-rhvh-4-source-rpms | 2.9 kB 00:00:00 (1/6): rhel-7-server-rhvh-4-beta-debug-rpms/primary_db | 1.7 kB 00:00:00 (2/6): rhel-7-server-rhvh-4-source-rpms/primary_db | 4.1 kB 00:00:00 (3/6): rhel-7-server-rhvh-4-beta-rpms/primary_db | 9.4 kB 00:00:00 (4/6): rhel-7-server-rhvh-4-beta-source-rpms/primary_db | 4.1 kB 00:00:00 (5/6): rhel-7-server-rhvh-4-rpms/primary_db | 9.4 kB 00:00:00 (6/6): rhel-7-server-rhvh-4-debug-rpms/primary_db | 1.7 kB 00:00:00 No packages marked for update 2. After step 3, can upgrade to rhvh-4.1-20170512.0. Excepted results: After step 2, should upgrade to rhvh-4.1-20170512.0 successful Additional info: 1. Also encountered this issue when upgrade from rhvh-4.1-0.20170421.0 to rhvh-4.1-20170512.0 2. No such issue when upgrade from rhvh-4.1-0.20170202.0 to rhvh-4.1-20170512.0 on the same machine with the same local repos.