-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-10.0
-
Yes
-
Important
-
subs-client-tools
-
5
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
Unspecified
-
None
What were you trying to do that didn't work?
During testing of RHCCC, rhcd was not getting started/enabled.
What is the impact of this issue to you?
This breaks cloud automatic registration workflow (connecting rhcd/yggdrasil to console dot)
Please provide the package NVR for which the bug is seen:
yggdrasil-0.4.5-3.el10_0.x86_64 rhc-0.3.2-1.el10.x86_64 redhat-cloud-client-configuration-1-13.el10.noarch
How reproducible is this bug?: 100% so far
Steps to reproduce
- Spin up RHEL 10 image on AWS
- Install redhat-cloud-client-configuration
- Attempt reboot/firstboot autoreg process
Expected results
rhcd/yggdrasil should automatically be enabled/started by autoreg processes with RHCCC.
Actual results
# ll /usr/lib/systemd/system/rhcd.service
ls: cannot access '/usr/lib/systemd/system/rhcd.service': No such file or directory
- is related to
-
RHEL-101898 [rhccc] We should use yggdrasil (not rhcd) on rhel-10
-
- Release Pending
-