Node deployment failed due to WWN [tinyipa]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bifrost |
New
|
Undecided
|
Unassigned |
Bug Description
### Describe the bug
* Currently I am looking out a way to speed up my deployment process,
* If I use custom IPA images build with [1], and corresponding generated images [2], I am able to provision the baremetal node.
* Do not see issue for WWN [deploy.
* Only the case I do see is
A) ipa.initramfs is almost 1G in size.
B) And slowness in deployment, [scans all hardware and then report back, slowing down]
[1]
~~~
ironic-
~~~
[2]
~~~
()[root@spare httpboot]# ls -lhrt ubu_ipa/
total 983M
-rw-r--r-- 1 root root 971M May 9 05:52 ipa.initramfs
-rw-r--r-- 1 ironic ironic 12M May 9 05:52 ipa.kernel
-rw-r--r-- 1 root root 94 May 9 07:27 ipa.kernel.sha256
-rw-r--r-- 1 root root 96 May 9 07:28 ipa.initramfs.
()[root@spare httpboot]#
~~~
* If I use TinyIPA [1], deployment is failing [2], Noting down here, no config change only ipa images changes.
* TinyIPA is not able to find out WWN root device hints.
[1]
~~~
()[root@spare httpboot]# ls -lhrt tiny/
total 205M
-rw-r--r-- 1 root root 5.3M May 6 11:36 ipa.kernel
-rw-r--r-- 1 root root 200M May 6 11:36 ipa.initramfs
()[root@spare httpboot]#
~~~
[2]
~~~
May 17 15:32:17 spare.clear-
~~~
#### Expectation
* We know Tiny images are not suitable for production, but to test the functionality, it should work.
* Looking out for a confirmation If we can use tiny images to test baremetal provisioning like the above emntioned.
#### Blocker:
* If I use custom IPA total deployment time is around 12 min.
Thanks,
cNilesh.