This repository has been archived by the owner on Aug 30, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 147
Yum fails on latest centos7 base image due to $releasever being invalid #488
Comments
Oh! Thanks for your note. We will fix!
…On Thu, Aug 8, 2019 at 1:46 AM Karl Stoney ***@***.***> wrote:
Hi,
Can't use yum in the latest base image, rpm -q --qf '%{version}\n'
centos-release is used by yum to calculate $releasever.
On the previous release:
***@***.*** app]$ rpm -q --qf '%{version}\n' centos-release
7
On the current release:
***@***.*** app]# rpm -q --qf '%{version}\n' centos-release
package centos-release is not installed
I worked around this by doing echo 7 > /etc/yum/vars/releasever.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#488?email_source=notifications&email_token=AAF76UTLPLVWWY7SUG53BJTQDPMO3A5CNFSM4IKH3MNKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HECYXFQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAF76URCFKLYLUVEIPECJ33QDPMO3ANCNFSM4IKH3MNA>
.
--
*Have build/release/devinfra questions? *
*Join us on Google Chat in the Nest Devinfra Chat
<https://chat.google.com/room/AAAAZjVzpI4>*
|
There was an image update yesterday. Issue is still present |
Okay, I've checked in your workaround and regenerated.
gcr.io/gcp-runtimes/centos7:latest now shows
[root@b62256e73472 /]# yum history
Loaded plugins: fastestmirror, ovl
ID | Command line | Date and time | Action(s) |
Altered
-------------------------------------------------------------------------------
4 | -y remove bind-libs bind | 2019-06-25 16:17 | Erase |
7
3 | -q -y erase kernel* *fir | 2019-06-25 16:17 | Erase |
4
2 | install -q -y bind-utils | 2019-06-25 16:16 | Install |
56 EE
1 | -q -y --installroot=/tar | 2019-06-25 16:15 | Install |
95 PP
history list
[root@b62256e73472 /]# rpm -q --qf '%{version}\n' centos-release
7
…On Tue, Aug 20, 2019 at 2:12 AM Sumesh S ***@***.***> wrote:
There was an image update yesterday. Issue is still present
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#488?email_source=notifications&email_token=AAF76UWKKT6FOZ2YCAUTK7DQFOYOZA5CNFSM4IKH3MNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4VT3FQ#issuecomment-522927510>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAF76URLD7FZEDKBEMSJWFLQFOYOZANCNFSM4IKH3MNA>
.
--
*Have build/release/devinfra questions? *
*Join us on Google Chat in the Nest Devinfra Chat
<https://chat.google.com/room/AAAAZjVzpI4>*
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Can't use yum in the latest base image,
rpm -q --qf '%{version}\n' centos-release
is used by yum to calculate$releasever
.On the previous release:
On the current release:
I worked around this by doing
echo 7 > /etc/yum/vars/releasever
.The text was updated successfully, but these errors were encountered: