Comments (19)
Ok, I suspect its because the agent is using dmidecode to get the total available memory and when this is run on a virtualbox guest no memory information is returned:
# dmidecode -t 17
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.5 present.
A cursory look suggests dmidecode does return memory information for libvirt guests and vsphere guests, but seemingly not for virtualbox guests. Despite not showing information, it exits with error code 0, so does not fail in the same way as it would if dmidecode could not be run.
from assisted-installer-agent.
from assisted-installer-agent.
did u use core user?
…
On Thu, Dec 17, 2020, 23:04 Timothy Rees @.***> wrote: Using assisted installer with guest VM on virtualbox, RAM is not correctly detected. Cannot progress with install because minimum 16 GiB is not met, despite the guest having 16GiB. See below: [image: Screenshot 2020-12-17 at 21 46 43] https://user-images.githubusercontent.com/4464624/102542493-2ee44400-40b2-11eb-9207-2b9095471823.png [image: Screenshot 2020-12-17 at 21 54 29] https://user-images.githubusercontent.com/4464624/102542702-75d23980-40b2-11eb-9413-6a6a6c5aeb57.png At the time of opening this I can't attach the agent logs because for some reason I can't ssh to the host, despite generating an ISO with my public key. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#148>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLPP4YX4ZWQ5ICFU7NQKKTSVJW5DANCNFSM4VAHMANQ .
Sorry, I had an issue with using my private key through the jump host. I am in now. Please see below:
[root@localhost core]# ps -ef | grep agent
root 1789 1 0 21:28 ? 00:00:00 /usr/local/bin/agent --url https://api.openshift.com --cluster-id 48b9443a-9558-4a4a-8965-d295aaaac129 --agent-version registry.redhat.io/openshift4/assisted-installer-agent-rhel8:v4.6.0-47 --insecure=false
root 1797 1789 0 21:28 ? 00:00:00 podman run --rm -ti --privileged --pid=host --net=host -v /dev:/dev:rw -v /opt:/opt:rw -v /run/systemd/journal/socket:/run/systemd/journal/socket -v /var/log:/var/log:rw --env PULL_SECRET_TOKEN --env HTTP_PROXY --env HTTPS_PROXY --env NO_PROXY --env http_proxy --env https_proxy --env no_proxy --name next-step-runner registry.redhat.io/openshift4/assisted-installer-agent-rhel8:v4.6.0-47 next_step_runner --url https://api.openshift.com --cluster-id 48b9443a-9558-4a4a-8965-d295aaaac129 --host-id cfcd2084-95d5-65ef-66e7-dff9f98764da --agent-version registry.redhat.io/openshift4/assisted-installer-agent-rhel8:v4.6.0-47 --insecure=false
root 1857 1844 0 21:28 pts/0 00:00:00 next_step_runner --url https://api.openshift.com --cluster-id 48b9443a-9558-4a4a-8965-d295aaaac129 --host-id cfcd2084-95d5-65ef-66e7-dff9f98764da --agent-version registry.redhat.io/openshift4/assisted-installer-agent-rhel8:v4.6.0-47 --insecure=false
root 5398 1857 2 21:34 pts/0 00:00:00 podman run --privileged --net=host --rm --quiet --name free_addresses_scanner -v /var/log:/var/log -v /run/systemd/journal/socket:/run/systemd/journal/socket registry.redhat.io/openshift4/assisted-installer-agent-rhel8:v4.6.0-47 free_addresses ["192.168.179.0/24"]
root 5399 1857 2 21:34 pts/0 00:00:00 podman run --privileged --net=host --rm --quiet -v /var/log:/var/log -v /run/systemd/journal/socket:/run/systemd/journal/socket registry.redhat.io/openshift4/assisted-installer-agent-rhel8:v4.6.0-47 dhcp_lease_allocate {"api_vip_mac":"00:1a:4a:98:f3:09","ingress_vip_mac":"00:1a:4a:c1:8a:64","interface":"enp0s3"}
root 5885 4009 0 21:34 pts/1 00:00:00 grep --color=auto agent
[root@localhost core]# sudo journalctl -u agent
-- Logs begin at Thu 2020-12-17 21:27:49 UTC, end at Thu 2020-12-17 21:35:09 UTC. --
Dec 17 21:27:56 localhost systemd[1]: Starting agent.service...
Dec 17 21:27:57 localhost podman[1311]: Trying to pull registry.redhat.io/openshift4/assisted-installer-agent-rhel8:v4.6.0-47...
Dec 17 21:27:59 localhost podman[1311]: Getting image source signatures
Dec 17 21:27:59 localhost podman[1311]: Copying blob sha256:6500ac87b29ffd00c8655be65a6824dfcf9fc0accc625158ef1060bcedc84ca8
Dec 17 21:27:59 localhost podman[1311]: Copying blob sha256:3f4c014de0a9cc6af27f18d601322829a255b83a7735ae41ec858613d6d2e130
Dec 17 21:27:59 localhost podman[1311]: Copying blob sha256:1b8dabac56ed728c17a670d327474ab87dc392dc17721854ea599a7753326579
Dec 17 21:27:59 localhost podman[1311]: Copying blob sha256:d35c047b7ebf24aee9f9b3e3f685d661f37aa366333a06d516b465143b036d8c
Dec 17 21:28:26 localhost podman[1311]: Copying config sha256:6531200a61ae0a36ad18a088f9e14b646d242ef362e05fc8dc25933b12818875
Dec 17 21:28:26 localhost podman[1311]: Writing manifest to image destination
Dec 17 21:28:26 localhost podman[1311]: Storing signatures
Dec 17 21:28:34 localhost systemd[1]: agent.service: Found left-over process 1628 (conmon) in control group while starting unit. Ignoring.
Dec 17 21:28:34 localhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Dec 17 21:28:34 localhost systemd[1]: agent.service: Found left-over process 1660 (podman) in control group while starting unit. Ignoring.
Dec 17 21:28:34 localhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Dec 17 21:28:34 localhost systemd[1]: Started agent.service.
Dec 17 21:28:35 localhost agent[1789]: time="17-12-2020 21:28:35" level=info msg="Running next step runner. Command: podman, Args: [\"run\" \"--rm\" \"-ti\" \"--privileged\" \"--pid=host\" \"--net=host\>
[root@localhost core]# less /var/log/agent.log
/var/log/agent.log: No such file or directory
[root@localhost core]# podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
39ee7c43a91e registry.redhat.io/openshift4/assisted-installer-agent-rhel8:v4.6.0-47 dhcp_lease_alloca... 5 seconds ago Up 5 seconds ago modest_hopper
588052956fee registry.redhat.io/openshift4/assisted-installer-agent-rhel8:v4.6.0-47 next_step_runner ... 7 minutes ago Up 7 minutes ago next-step-runner
[root@localhost core]# free -m
total used free shared buff/cache available
Mem: 16034 348 12670 1248 3015 14152
Swap: 0 0 0
[root@localhost core]#
from assisted-installer-agent.
@ori-amizur FYI
from assisted-installer-agent.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from assisted-installer-agent.
/remove-lifecycle stale
from assisted-installer-agent.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from assisted-installer-agent.
/remove-lifecycle stale
from assisted-installer-agent.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from assisted-installer-agent.
/remove-lifecycle stale
@eliorerz did we make any progress with this?
from assisted-installer-agent.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from assisted-installer-agent.
from assisted-installer-agent.
/remove-lifecycle stale
from assisted-installer-agent.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from assisted-installer-agent.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
/remove-lifecycle stale
from assisted-installer-agent.
Solved by #227
from assisted-installer-agent.
/close
from assisted-installer-agent.
/remove-lifecycle rotten
from assisted-installer-agent.
@omertuc: Closing this issue.
In response to this:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from assisted-installer-agent.
Related Issues (20)
- Agent doesn't report memory installed on the system on KVM based instances on EC2 HOT 9
- Future Release Branches Frozen For Merging | branch:release-4.8 HOT 4
- Non distinct UUID causes hosts not to show up HOT 6
- Future Release Branches Frozen For Merging | branch:release-ocm-2.6
- Support using the inventory when not running in a container HOT 4
- Future Release Branches Frozen For Merging | branch:release-4.17 branch:release-4.18
- No connectivity to the majority of hosts in the cluster - connectivity check fails between hosts HOT 4
- uuid generation of systems with identical/collision Serial HOT 4
- assisted installer service getting error - chronyc: error while loading shared libraries: libnettle.so.8 HOT 8
- Agent not find my vswitch interface HOT 5
- Future Release Branches Frozen For Merging | branch:release-ocm-2.7
- Future Release Branches Frozen For Merging | branch:release-ocm-2.8
- Unable to pull okd binaries on nodes behind a proxy HOT 1
- agent-config.yaml: hosts parameter is not optional as stated in the docs HOT 1
- Future Release Branches Frozen For Merging | branch:release-ocm-2.9
- Future Release Branches Frozen For Merging | branch:release-ocm-2.10
- Future Release Branches Frozen For Merging | branch:release-ocm-2.11 HOT 2
- Future Release Branches Frozen For Merging | branch:release-4.16 branch:release-4.17
- ASUS motherboard unset serial
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from assisted-installer-agent.