Bug 2216111
| Summary: | fdo containers failed at serviceinfo with error SSHkey module missing username or key | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Yi He <yih> |
| Component: | fdo-serviceinfo-api-server-container | Assignee: | idiez |
| Status: | CLOSED COMPLETED | QA Contact: | Xiaofeng Wang <xiaofwan> |
| Severity: | medium | Docs Contact: | Eliane Ramos Pereira <elpereir> |
| Priority: | unspecified | ||
| Version: | 9.3 | CC: | amurdaca, idiez, miabbott, perobins |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-06-28 14:52:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Yi He
2023-06-20 07:14:10 UTC
We need to know how the serviceinfo-api-server config file looks like. I use this config file https://github.com/virt-s1/rhel-edge/blob/main/data/fdo/serviceinfo-api-server.yml: --- service_info: initial_user: null files: null commands: null diskencryption_clevis: - disk_label: /dev/vda4 reencrypt: true binding: pin: tpm2 config: '{}' additional_serviceinfo: null bind: 0.0.0.0:8083 service_info_auth_token: 2IOtlXsSqfcGjnhBLZjPiHIteskzZEW3lncRzpEmgqI= admin_auth_token: Va40bSkLcxwnfml1pmIuaWaOZG96mSMB6fu0xuzcueg= device_specific_store_driver: Directory: path: /etc/fdo/stores/serviceinfo_api_devices PR to fix the issue posted: https://github.com/fedora-iot/fido-device-onboard-rs/pull/519 Tested new fdo containers generated by https://github.com/fedora-iot/fido-device-onboard-rs/pull/519 Still see some error messages, but different from the previous error we were getting, at least the luks part is fixed. Jun 26 22:55:57 vm-1 systemd[1]: Starting FDO client... Jun 26 22:55:57 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:55:57.751Z INFO fdo_client_linuxapp > Found device credential at FileSystemPath { path: "/boot/device-credentials", deactivation_method: None } Jun 26 22:55:57 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:55:57.866Z ERROR fdo_client_linuxapp > Error performing TO1 with ServiceClient { protocol_version: Version1_1, base_url: "http://192.168.200.52:8082", client: Client { accepts: Accepts, proxies: [Proxy(System({}), None)], referer: true, default_headers: {"accept": "/"} }, authorization_token: None, encryption_keys: EncryptionKeys { cipher_suite: None, keys: None }, last_message_type: Some(Error), non_interoperable_kdf_required: Some(false) } Jun 26 22:55:57 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:55:57.867Z ERROR fdo_client_linuxapp > Error Couldn't get TO1 from any Rendezvous server! getting usable To1d from rv_entry RendezvousInterpretedDirective { ip_addresses: Some([IPAddress(192.168.200.52)]), dns_name: None, port: 8082, server_certificate_hash: None, ca_certificate_hash: None, user_input: false, wifi_ssid: None, wifi_password: None, medium: None, protocol: Http, delay: 0, bypass: false } Jun 26 22:57:46 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:57:46.912Z INFO fdo_client_linuxapp > Got TO2 addresses: ["http://192.168.200.51:8081"] Jun 26 22:57:46 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:57:46.912Z INFO fdo_client_linuxapp > Performing TO2 protocol, URL: "http://192.168.200.51:8081" Jun 26 22:57:47 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:57:47.009Z INFO fdo_client_linuxapp::serviceinfo > Creating file "/etc/sudoers.d/fdouser" with 32 bytes (mode 384) Jun 26 22:57:47 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:57:47.014Z INFO fdo_client_linuxapp::serviceinfo > Initiating disk re-encryption, disk-label: /dev/vda4, pin: tpm2, config: {}, reencrypt: true Jun 26 22:57:48 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:57:48.204Z ERROR fdo_client_linuxapp > ServiceInfo failed, error: Error processing returned serviceinfo Jun 26 22:57:48 vm-1 fdo-client-linuxapp[1184]: Caused by: Jun 26 22:57:48 vm-1 fdo-client-linuxapp[1184]: SSHkey module missing username or key Jun 26 22:57:48 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:57:48.211Z ERROR fdo_client_linuxapp > Error performing TO2 ownership protocol Jun 26 22:57:48 vm-1 fdo-client-linuxapp[1184]: Caused by: Jun 26 22:57:48 vm-1 fdo-client-linuxapp[1184]: Error performing the ServiceInfo roundtrips with TO2 address http://192.168.200.51:8081 Jun 26 22:59:23 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:59:23.253Z INFO fdo_client_linuxapp > Got TO2 addresses: ["http://192.168.200.51:8081"] Jun 26 22:59:23 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:59:23.254Z INFO fdo_client_linuxapp > Performing TO2 protocol, URL: "http://192.168.200.51:8081" Jun 26 22:59:23 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:59:23.314Z INFO fdo_client_linuxapp::serviceinfo > Creating file "/etc/sudoers.d/fdouser" with 32 bytes (mode 384) Jun 26 22:59:23 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:59:23.319Z INFO fdo_client_linuxapp::serviceinfo > Initiating disk re-encryption, disk-label: /dev/vda4, pin: tpm2, config: {}, reencrypt: true Jun 26 22:59:24 vm-1 fdo-client-linuxapp[1184]: 2023-06-27T02:59:24.291Z ERROR fdo_client_linuxapp > ServiceInfo failed, error: Error processing returned serviceinfo Verified with new fido containers and new fdo client, worked as expected. Steps: 1. Download fido containers and start in podman. 2. Build simplified installer image with fdo settings in blueprint, boot it. 3. All check passed, no problem found. |